[EXIM] Odd problem with Exim 3.02

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Dean Brooks
Datum:  
To: exim-users
Betreff: [EXIM] Odd problem with Exim 3.02
Hi,

Since upgrading to Exim 3.02, I've noticed a rather strange and
annoying problem. We're running under Solaris 2.5.1 on Sun Sparc.

We actually have two configurations of Exim running simultaneously,
on on standard port 25, and one on port 792 which maintains a separate
input queue for intermittently connected hosts.

Since upgrading to 3.02, we started getting reports of actual *logfile*
entries being appended on the end of delivered messages. This morning,
I confirmed that *every* single item in the input queue (on our
port-792 configuration) has an exact duplicate of the "msglog" data appended
onto the end of the -D file.

For example, at the end of one of the -D files, I see the following. I
also see the exact same stuff in the msglog file as well.

1999-06-24 12:36:40 == henry@??? T=forward_smtp defer (-44): retry time not reached for any host
1999-06-24 12:52:10 == henry@??? T=forward_smtp defer (-44): retry time not reached for any host
1999-06-24 13:06:09 == henry@??? T=forward_smtp defer (-44): retry time not reached for any host

Now, what's *really* weird is that our port-25 configuration doesn't
do this at all. The port-792 does it every single time.

The configuration files *are* significantly different, and I can provide
them if necessary. Both implementations use the split-spool-directory
tag, and are quite custom configured.

Has anyone else seen this behavior? We've been running Exim
since the 1.61 days, and I've never seen this before, so I assume
this is a bug somehow?

I'll be glad to provide configuration files, et al, if necessary.


--                                      Regards, Dean
Dean A. Brooks
IgLou Internet Services, Inc.           Voice: (502) 966-3848
Louisville, Kentucky USA                       (800) 436-4456





--
*** Exim information can be found at http://www.exim.org/ ***