On 1/1/1970, "Sam Varshavchik" <[EMAIL PROTECTED]> wrote:
Solution: don't start throwing spam at Courier.
I realise that (2) is OT but for both I'd appreciate any hints from the list on this - there must be other pop3->fetchmail->courier users out there!
As one such user, I advise against using fetchmail to deliver messages to courier's local smtp server. fetchmail is somewhat less than well behaved, and you might end up losing headers that you wanted to see, later on.
Courier's spam filtering techniques are great if you put them up against the initial delivery, but afterward they're just going to interfere with the operation of fetchamil. It's too late to use them to do any good.
Instead, use maildrop as your "mda", and do your spam filtering in your .maildroprc file. You can choose to send spam to /dev/null or to an alternate folder that you can review if you think something has been mis-classified.
Example fetchmailrc:
set daemon 900 # Poll at 15-minute intervals
defaults
fetchall, no keep,
mda "/usr/lib/courier/bin/maildrop";poll mail.example.com with protocol pop3:
user username there with password mypassword is username here;
------------------------------------------------------- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
