--On Donnerstag, 19. Februar 2004 11:21 -0500 Lloyd Zusman <[EMAIL PROTECTED]> wrote:
>> Alternatively you could move the content-filtering into the perlfilter >> or maildropfilter which are both able to reject mail during the transfer. > > One small point: I thought that maildropfilter is used for local > delivery, not global ... ??? It should be localmailfilter(7), once also known as 'whitelist api'. Its especially supported by but not limited to Maildrop at all. The simple api allows to fork something executable after every RCPT TO and DATA and reject the message at this point - and its one of the main reasons why I use courier for incoming mails here. The additional load compared to the persistent courierperlfilter which is somewhat picky with the declaration of variables should not be a problem unless there are multiple incoming mails per second. I'll also scan only the top 4K of the message (including headers), its enough to recognize the common trojans and forged bounces by filename or the first line of the base64-encoded attachment. By using localmailfilter instead of courierperlfilter to launch spamassassin (or spamc) you trade some cpu for simplicity since every invocation gets a fresh perl interpreter without hidden gotchas. Both implementations have the same limitations: no access to the values of HELO or RCPT TO as given by the client (Sam promised this some time ago) and no possiblity to modify content or insert custom headers (the later may be patched away) Roland ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
