Difference between revisions of "E-mail"

From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search
Line 19: Line 19:
 
Presently, we only mark spam with some header flags, and by prepending "[SPAM] " to the subject of spammy messages. This allows users to do what they wish with spam, alleviating us of any "you marked my important email as spam and deleted it!" blame. The suggested method of dealing with spam is presently to have users use a sieve script.
 
Presently, we only mark spam with some header flags, and by prepending "[SPAM] " to the subject of spammy messages. This allows users to do what they wish with spam, alleviating us of any "you marked my important email as spam and deleted it!" blame. The suggested method of dealing with spam is presently to have users use a sieve script.
  
== [[Amavisd-New|AMaVis]] ==
+
 
<font color="red">Turns out we run [http://www.ijs.si/software/amavisd/ amavisd-new], which likes to pretend it's amavisd.</font>  Check out their site's info for configuration with Postfix: [http://www.ijs.si/software/amavisd/README.postfix.html]. Needs an entry in ''/etc/postfix/master.cf''
 
  
 
== GNU Mailman ==
 
== GNU Mailman ==

Revision as of 20:07, 5 February 2009

This is the set of programs that service NPG e-mail.

Postfix

Centralized set of programs to send/recieve mail, as well as put recieved mail through spam/virus filters. The RPM is pretty good in that it automatically puts entries for some of the below programs in the appropriate configuration files. Sometimes it's necessary to un-comment them, though.

Procmail

Mail Deliver Agent typically used by Postfix. Do we use amavis instead of it?

Dovecot

We run dovecot as our mail server. We're using a pretty much default setup, for ease of administration. The dovecot website has all necessary documention, and most of the system is fairly self-explanatory.

SpamAssassin

Postfix uses SpamAssassin to filter e-mail. Needs an entry in /etc/postfix/master.cf and Procmail configuration

"If SpamAssassin is working, the message will be marked as spam. Note that SpamAssassin only marks messages as spam and that how it does this marking may be affected by your front-end. If you're not using the "spamc" or "spamassassin" program and are using a third-party front-end (especially amavisd), then it may not be completely obvious how spam messages are handled."[1]

Presently, we only mark spam with some header flags, and by prepending "[SPAM] " to the subject of spammy messages. This allows users to do what they wish with spam, alleviating us of any "you marked my important email as spam and deleted it!" blame. The suggested method of dealing with spam is presently to have users use a sieve script.


GNU Mailman

Manages mailing lists.
Web interface on einstein
More info