> ii debianutils2.12.0 Miscellaneous utilities specific to Debian
> ii exim 3.36-13An MTA (Mail Transport Agent)
>
> Is there anyone who encountered the same problem or is this
> Alpha specific or even specific to my machine?
This should be fixed in debianutils 2.
On Fri, 18 Feb 2005 16:43:48 +0100, Wouter Verhelst
<[EMAIL PROTECTED]> wrote:
>Well, yes, but it works in many more cases, and it's what upstream
>supports.
Frankly, upstream is not quite interested any more in supporting
convert4r4. I have forwarded a bug report regarding the script
upstream, an
On Fri, Feb 18, 2005 at 03:07:49PM +0100, Marc Haber wrote:
> On Fri, 18 Feb 2005 14:51:39 +0100, Wouter Verhelst
> <[EMAIL PROTECTED]> wrote:
> >In all but the most complex cases, migrating exim v3 to exim v4 involves
> >running /usr/sbin/exim_convert4r4 on /etc/exim/exim.conf, and copying te
> >r
From: Marc Haber <[EMAIL PROTECTED]>
Subject: Re: problem of savelog
Date: Fri, 18 Feb 2005 15:55:15 +0100
> On Fri, 18 Feb 2005 23:25:18 +0900 (JST), Atsuhito Kohda
> <[EMAIL PROTECTED]> wrote:
> >From: Marc Haber <[EMAIL PROTECTED]>
> >> If your exim 3 co
On Fri, 18 Feb 2005 23:25:18 +0900 (JST), Atsuhito Kohda
<[EMAIL PROTECTED]> wrote:
>From: Marc Haber <[EMAIL PROTECTED]>
>> If your exim 3 configuration was generated by eximconfig, exim4 will
>> try to guess your answers you have given when configuring exim3, and
>> will pre-seed debconf accordin
From: Marc Haber <[EMAIL PROTECTED]>
Subject: Re: problem of savelog
Date: Fri, 18 Feb 2005 15:06:45 +0100
> >Fine to hear this can be done "today's morning". Is the configuration
> >migrated to the new version (mine is pretty simple), or does one have to
&
On Fri, 18 Feb 2005 14:51:39 +0100, Wouter Verhelst
<[EMAIL PROTECTED]> wrote:
>In all but the most complex cases, migrating exim v3 to exim v4 involves
>running /usr/sbin/exim_convert4r4 on /etc/exim/exim.conf, and copying te
>resulting file to /etc/exim4/exim4.conf.
Actually, this is deprecated.
On Fri, 18 Feb 2005 13:53:20 +0100, Frank Küster <[EMAIL PROTECTED]>
wrote:
>Atsuhito Kohda <[EMAIL PROTECTED]> schrieb:
>> Thanks for your infomation. I met the same problem today's morning
>> so I changed exim to exim4 ;-)
>
>Fine to hear this can be done "today's morning". Is the configuration
On Fri, Feb 18, 2005 at 01:53:20PM +0100, Frank Küster wrote:
> Atsuhito Kohda <[EMAIL PROTECTED]> schrieb:
>
> > Thanks for your infomation. I met the same problem today's morning
> > so I changed exim to exim4 ;-)
>
> Fine to hear this can be done "today's morning". Is the configuration
> mig
Atsuhito Kohda <[EMAIL PROTECTED]> schrieb:
> Thanks for your infomation. I met the same problem today's morning
> so I changed exim to exim4 ;-)
Fine to hear this can be done "today's morning". Is the configuration
migrated to the new version (mine is pretty simple), or does one have to
start
From: Alexandre <[EMAIL PROTECTED]>
Subject: Re: problem of savelog
Date: Fri, 18 Feb 2005 10:47:29 +0100
> On Thu, Feb 17, 2005 at 06:08:15PM +0100, Alexandre wrote:
> > Atsuhito Kohda wrote:
> >
> > > Is there anyone who encountered the same problem or is thi
On Thu, Feb 17, 2005 at 06:08:15PM +0100, Alexandre wrote:
> Atsuhito Kohda wrote:
>
> > Is there anyone who encountered the same problem or is this
> > Alpha specific or even specific to my machine?
>
> Same problem here, on my alphastation which I use as a mailserver.
Mail I received from an
Atsuhito Kohda wrote:
> Is there anyone who encountered the same problem or is this
> Alpha specific or even specific to my machine?
Same problem here, on my alphastation which I use as a mailserver.
--
Alexandre Fayolle LOGILAB, Paris (France).
http://www.logilab
Atsuhito Kohda wrote:
> I found yesterday that mails were not delivered since about
> 6:30 in the morning so I investigated a problem and found
> that /var/log/exim/paniclog said /var/log/exim/mainlog had
> a wrong owner/permission;
[snip]
> However I found today that the situation was worse than
Hi all,
I found yesterday that mails were not delivered since about
6:30 in the morning so I investigated a problem and found
that /var/log/exim/paniclog said /var/log/exim/mainlog had
a wrong owner/permission;
2005-02-16 06:33:49 1D1AKL-0005JC-00 Cannot open main log file "/var/log/exim/m\
ainl
15 matches
Mail list logo
