Re: [AMaViS-user] RE: How to clean /var/spool/amavis directory automatically

lkolchin wrote:

> I'm getting a lot of the following messages in the logs:

> Dec 26 15:07:04 mail postfix/smtp[17889]: C73D183AEA: to=<username@mydomain.com>,
> orig_to=< username@mydomain.com >, relay=127.0.0.1[127.0.0.1], delay=141564,
> status=deferred (lost connection with 127.0.0.1[127.0.0.1] while sending end
> of data -- message may be sent more than once)

> I'm using postfix along with amavisd-new (SA and ClamAV) on SLES9 machine,
> latest updated versions.

I'm showing the latest SUSE packaged version of amavisd-new is 20060616-p9,
which is rather old (but still should be able to process mail). Do you
know what version of amavisd-new you are actually running?
http://www.novell.com/products/linux...index_all.html

> I've seen on the list archive, that someone suggested to "
> Add status code 2 along with 0 to the success "if" branch
> (file ./amavis/av/sophos), or upgrade to amavisd-new-20021227-p2.
> "

That looks ancient and unrelated to me. There are a lot of possible
reasons for amavisd-new to not work properly, often it is a problem
with one of the external Perl modules or external programs or even a
malformed message that amavisd-new or one of the external
modules/programs chokes on. Read http://www.ijs.si/software/amavisd/#faq-gen
(The Berkeley DB notes will not apply to version 20060616).
It can also be some sort of resource issue, such as running out of
swap space (maybe not enough ram or too many amavisd-new child
processes) or reaching an open file limit. If you have several
gigabytes of amavisd temp directories, this can also be a problem in
itself (snowball effect).

> I don't really understand what should I add and to what file to make
> local delivery work again.

It's not possible for anyone to know until the source of the problem
is found.

> In the following page (see the link) claimed that it is the amavisd fault:
> http://www.irbs.net/internet/postfix/0208/0894.html

It is not a problem with Postfix.

> What should I do to fix it please?
> Regards,
> Leon

Before you can fix it, the problem must first be found. In order to
find the problem, we would need to see if your logs provide clues.
I would start by temporarily increasing the $log_level to 5 (then shut
down and restart amavisd-new), then look through the log for clues. Try
to trace a message from beginning to end, looking for errors reported by
amavis. If you find a good error message or two, this may be where to
start looking for a solution. Look for text like ERROR (or) TROUBLE (or)
error (or) Can't. Also use 'top' to monitor the amavisd-new processes
and memory usage.

Gary V



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/...fo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/