Karl,

> we are using Amavisd-new 2.3.3 with Spamassassin 3.1.3 and Perl 5.8.8 on a
> SuSE Linux Enterprise Server 10 in the following constellation:
>
> Fetchmail fetches e-mails from ISP and forwards them to a server on which
> is amavisd-new with Spamassassin listening on all interfaces at TCP port
> 25. Amavisd-new forwards them after spam check (no virus check) to a IBM
> Lotus Domino server which is running on the same machine. Domino's  SMTP
> server is running on TCP port 125.

Is fetchmail feeding mail directly to amavisd,
or to a MTA? (the later is much preferred)

> Sometimes amavis simply ceases to work.

> Last amavisd-nanny output was:

PID 13388: .             0:11:33 .........:.........:.........:.....>
PID 13389: .             0:01:58 .........:.........:.........:.....>
PID 13392: .             0:11:13 .........:.........:.........:.....>
PID 13393: .             0:10:23 .........:.........:.........:.....>
PID 13394: .             0:08:45 .........:.........:.........:.....>
PID 13395: .             0:10:00 .........:.........:.........:.....>
PID 13396: .             0:08:03 .........:.........:.........:.....>
PID 13408: .             0:04:26 .........:.........:.........:.....>
PID 13440: .             0:06:56 .........:.........:.........:.....>
PID 13481: .             0:12:18 .........:.........:.........:.....>

You have 10 amavisd processes, and all are in a '.' state,
which means the mail processing task has been completed,
but the client (fetchmail?) has not yet closed down the SMTP
session, perhaps because it assumed it may be handy to
keep an open session around for when a next message will arrive.

This may be fine, as long as there is not _more_ clients
attempting to contact amavisd then there are available
amavisd child processes.


> Amavisd's log_level is 5. The last lines of /var/log/mail are:
>
> Jan 18 17:02:53 projahndom1 amavis[13389]: (13389-05-35) prolong_timer
...
> Jan 18 17:02:55 projahndom1 amavis[13389]: (13389-05-36) idle_proc,

Your entire log sample spans only a 2-second time
interval 17:02:53 .. 17:02:55, yet the timestamps
from a fetchmail log shows the problem occurred later:


> And fetchmail's log says:
>
> fetchmail: POP3> LIST 36
> fetchmail: POP3< +OK 36 1918
> fetchmail: POP3> RETR 36
> fetchmail: POP3< +OK 1918 octets
> reading message [EMAIL PROTECTED]:36 of 36 (1918
> octets)
> fetchmail: SMTP> MAIL FROM:<[EMAIL PROTECTED]> SIZE=1918
> fetchmail: SMTP< 250 2.1.0 Sender [EMAIL PROTECTED] OK
> fetchmail: SMTP> RCPT TO:<[EMAIL PROTECTED]>
> fetchmail: SMTP< 250 2.1.5 Recipient [EMAIL PROTECTED] OK
> fetchmail: SMTP> DATA
> fetchmail: SMTP< 354 End data with <CR><LF>.<CR><LF>
> #*******************fetchmail: SMTP>. (EOM)
> fetchmail: SMTP< 250 2.6.0 Ok, id=13389-05-36, from MTA([127.0.0.1]:125):
> 250 Message accepted for delivery flushed
> fetchmail: POP3> DELE 36
> fetchmail: POP3< +OK Message 36 has been deleted.
> fetchmail: POP3> QUIT
> fetchmail: POP3< +OK Pop server at server6.server-einstellung.de signing
> off.

This one above was the message that amavisd log above covered.

> fetchmail: POP3< X-LOCALTIME Thu, 18 Jan 2007 17:03:06 +0100

ten seconds later...

> fetchmail: POP3< .
> fetchmail: POP3> USER t8xa7k26
> fetchmail: POP3< +OK Password required for t8xa7k26.
> fetchmail: POP3> PASS *
> fetchmail: POP3< +OK t8xa7k26 has 43 visible messages (0 hidden)
> octets.
> fetchmail: POP3> STAT
> fetchmail: POP3< +OK 43 365293
> 43 messages for t8xa7k26 at server6.server-einstellung.de (365293 octets).
> fetchmail: POP3> LIST 1
> fetchmail: POP3< +OK 1 15755
> fetchmail: POP3> RETR 1
> fetchmail: POP3< +OK 15755 octets
> reading message [EMAIL PROTECTED]:1 of 43 (15755
> octets)

> fetchmail: smtp listener protocol error
> fetchmail: SMTP connect to 192.168.2.15 failed


> at Thu Jan 18 17:05:33 2007: poll completed
> fetchmail: SMTP> QUIT
> fetchmail: SMTP< 221 2.0.0 defendo.projahn-werkzeuge.de closing connection
> fetchmail: SMTP> QUIT
> fetchmail: SMTP< 221 2.0.0 defendo.projahn-werkzeuge.de closing connection
> fetchmail: SMTP> QUIT
> fetchmail: SMTP< 421 4.3.2 Service shutting down, closing channel
> fetchmail: SMTP> QUIT
> fetchmail: smtp listener protocol error
> fetchmail: SMTP> QUIT
> fetchmail: smtp listener protocol error

fetchmail is shutting down

It appears you have 14 fetchmail sessions,
but only 10 amavisd processes !!??

Looks fetchmail is not closing down a session after it has
finished processing a batch.

It is a bad idea to feed mail from fetchmail directly
to amavisd. There should be an MTA in-between, which
will take care of feeding amavisd with a pipe
just wide enough to be handled.

  Mark

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to