Re: [AMaViS-user] How to bypass spam filtering

This is a discussion on Re: [AMaViS-user] How to bypass spam filtering within the Amavis User forums, part of the Anti-Spam and Anti-Virus Related Forums category; Bill, > >>> ...I run multiple content-filters, and the first one actually pipes > >>> ...


Go Back   Usenet Forums > Anti-Spam and Anti-Virus Related Forums > Amavis User

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 09-28-2006
Mark Martinec
 
Posts: n/a
Default Re: [AMaViS-user] How to bypass spam filtering

Bill,

> >>> ...I run multiple content-filters, and the first one actually pipes
> >>> mail (via the Postfix "sendmail" command) back into postfix which
> >>> uses the "pickup" daemon to retrieve the message.


If you have a choice, these system messages could be submitted via SMTP
to Postfix on port 10025, e.g. by mini_sendmail, instead of submitted
to maildrop directory through sendmail command.

> >>> I have not been able to figure out
> >>> if there is a way to tell "sendmail" to use an alternate "pickup"
> >>> daemon when piping a message back to Postfix.


I don't think there is a way. Pickup picks messages from a maildrop directory,
and by the time message gets there, it is undistinguishable from other
messages submitted by 'sendmail' binary.

> I wrote a script that delivers the post-scanned MessageSniffer message
> directly to amavisd-new on 127.0.0.1:10024 by using the smtpclient to
> handle the delivery instead the Postfix sendmail client. This appears to
> be working great, and allows me to bypass content filtering on the Postfix
> "pickup" daemon. Chaining the content-filters together also reduces the
> number of message hand-offs and also cuts down on the amount of Postfix
> logging.


Good.

> The message delivery process now looks like: Postfix --> MessageSniffer
> --> Amavisd-new --> Postfix --> Maildrop --> Dovecot, removing the Postfix
> hand-off between MessageSniffer and Amavisd-new.
>
> Mark, is amavisd-new missing anything that I should be concerned about by
> having mail injected via SMTP vs. ESMTP? I noticed that Postfix delivers
> to Amavisd via ESMTP, but the smtpclient delivers via SMTP.


Since you were happy with a previous use of pipe/sendmail, you probably
won't be missing much. As mouss stated, you'd be throwing away DSN
options, PIPELINING and 8BITMIME announced capability, and ability to
pass client IP address to amavisd through XFORWARD smtp command extension,
but you didn't have these before either.

Mark

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?p...rge&CID=DEVDEV
_______________________________________________
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/
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 12:44 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0