Rocco,
> Note that I'm using Sendmail-milter configuration of amavisd-new... So I
> think that, give that the $notify_method' is so defined:
>
> - $notify_method = 'pipe:flags=q argv=/usr/sbin/sendmail -Ac -i -odd -f
> ${sender} -- ${recipient}';
>
> then the message, one time that is classified as spam, is sent to the
> [EMAIL PROTECTED] through command above. At this point, amavis filter the
> message again... and this causes a loop... Is right my analisys?
Right, the notification itself is checked for content in a
sendmail milter setup, which can potentially cause a loop
if your filter is too trigger-happy regarding spam.
You can add some negative score points to SA for mail
that looks like your own notifications.
In case of admin or recipient notifications you can also
whitelist the sender address (configured by $mailfrom_notify_admin
and $mailfrom_notify_recip). Unfortunately this is not
useful for sender notifications, as these have a null
sender address.
> How I have to modify the setting of $notify_method, without affecting
> the rest of behaviour of the system?
The cleanest solution is to send notifications to a separate mailer,
and this leads more or less to a dual-sendmail solution, which is
subject to much fewer problems than the pre-queue filtering with
a milter setup. Or do yourself a favour and jump on a Postfix wagon.
Mark
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
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/
