Hello,
I've been wading through all the information regarding spam fighting and
think I know how I want my configuration to look. I'm hoping someone will
verify it for me, pass along any pointers and most importantly point me in
the right direction for specific tools. What I need is someone to say "Use
procmail for step x; use sendmail for step y". I think that if I have the
process nailed down and get some advice on the proper tools to use I can
handle figuring out how to obtain and configure the individual tools (of
course I wouldn't turn down a cookbook if it were offered).
So, here is what I think it should look like:
- MX records point to mail.domain.com
- mail.domain.com is a linux box running an email server (sendmail,
qmail, ?)
- Something on mail.domain.com processes email and filters for spam
- "good" mail messages are relayed on to the corporate exchange server
for end user consumption
- "bad (spam)" mail messages are relayed on to an internal mail server
(spam.domain.com) that is running squirrelmail (php mail client interface)
so that users who care can check for false positives.
- Something on spam.domain.com deletes messages that are older than 30 days
to prevent the disks from filling up (some users won't care to check for
(and clean up) the messages that were filtered off.
Any help or advice will be greatly appreciated.
Best regards,
Steve
y a r d g n o m e A T e a r t h l i n k D O T n e t
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
