Claude,
> > More than likely one of the decoders is hanging on
that
> > mail. Capture whatever message is causing the
problem and run it
> > through "amavisd debug" or with
log_level set to 5.
>
> I have examined the problematic message. It is a bounce
message. In the
> body, there is the short explanation about the bounce
and then comes the
> original message simply attached, ignoring the MIME
structure. Therefore
> the long message will be scanned as if it would be a
simple text.
Did you collect a debug at log level 5 on such a problem
message?
> Is there a solution avoiding the full scanning in text
mode of such
> messages ?
No. Even if it were, it would just avoid one of the
possible
invocations of bad code, and leave the problem unsolved.
Tomorrow some other type of message will trip over the same
problem.
You need to track down the underlying problem.
Xavier,
> I have also this kind of problems... I think it is more
related to
> SpamAssassin because I had to disable all spam scanning
on my system
> to get it working again.
>
> Any hints ?
Collect a sample of a problematic message, feed it to
a command-line spamassassin running in its debug mode,
and see where it gets stuck:
# su vscan -c 'spamassassin -t -D <sample.msg'
Mark
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and
a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
AMaViS-user mailing list
AMaViS-user lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/
|
