On Tuesday 02 September 2003 09:15 pm, HaywireMac wrote: > On Wed, 03 Sep 2003 07:35:42 +1000 > > Stephen Kuhn <[EMAIL PROTECTED]> uttered: > > Look - it's dependent on your need and requirement. > > What I want to do is implement that wunderbar procmail recipe you linked > us to, and test it out, eventually I would like to have a mail server up > and running so that it: > > 1. Retrieves the mail from the ISP (fetchmail, precalls mailfilter as > 1st line of defense against the viagra, penis enlargement, (definitely > not needed ;-)), etc.) > > 2. Postfix then deposits the mail, I guess, from what others have > posted, in appropriate users mailboxes (/var/spoo/mail/[username] > > 3. Procmail looks at the mail using said recipe and acts as second line > of defense against .pif attachments, Nigerian free money scams etc. > > 4. IMAP package allows clients on LAN to retrieve mail from mailserver > using POP. > > I gave up on this before, but I really think I can do it this time! > > But I want this to be a *system* service type deal, because I want to > learn it as a sysadmin would see it, rather than as an end user, see?
This doesn't sound too hard. 1. Run Fetchmail as root and pass the mail off through procmail on the way to Postfix. Procmail runs a /etc/procmailrc recipe as a root service and calls the nkvir recipe through an include file from that recipe. You can also add in Spamassassin and any other filters in this recipe. 2. Then the mail goes to Postfix who delivers to local mail box file, /var/spool/mail/user based on aliases or the rewrite done by fetchmail in the .fetchmailrc file ([EMAIL PROTECTED] is jblow here). 3. From the local user directory, create a .forward file that calls procmail and applies a local user.procmailrc recipe to do local filtering, although I imagine this is supposed to catch stuff that is different from the first set of recipes, I am imagining a conservative set of filters for global filtering and a more aggressive set here. So, you could also call spamassassin a second time here and apply user_prefs that would apply a customized set of filters for user mail. Procmail, called from the .forward file would then put the mail into $maildir/user, should be /home/user/Mail/etc. 4. Run an IMAP daemon that allows a user to connect with IMAP and they will pull read and write their mail directly to the maildir directories, no need to use POP which would remove the mail from the server to a local directory, with IMAP, mail stays on the server and the user just accesses through the client direct to the server and their maildir directories. This is way more complex than what I currently do but I think that this is the way that it would work. -- Bryan Phinney Software Test Engineer
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
