688
edits
Changes
Jump to navigation
Jump to search
Line 114:
Line 114: − In situ: http://www.sonoracomm.com/index.php?option=com_content&task=view&id=49&Itemid=32+ − The Sonoracomm Howto has been a very well regarded set of instructions for quite a while now. An older version is included here in case you have trouble with the link above.+ − These instructions are aimed mostly at configuring SME as the only mail server, not for using SME with an internal mail server.+ − + + + + Line 241:
Line 244: + + + + + + +
Update description of 'Entire Sonoracomm Howto'; add instructions for 'db spamassassin delprop' per bug 4186
====The entire Sonoracomm howto from Google's text cache====
====The entire Sonoracomm howto from Google's text cache====
* The Sonoracomm HowTo has been a very well regarded set of instructions for SME mail server configuration for quite a while.
* This section was created during an extended outage of the Sonoracomm web server (in 2007?)
* The Sonoracomm HowTo has been updated since this section was created, and is well worth examining. View the current version at: http://www.sonoracomm.com/index.php?option=com_content&task=view&id=49&Itemid=32
Specifically, LearnAsSpam.pl is harder to configure when using an internal mail server - you would have to develop a method for getting the unmarked SPAM into an IMAP folder directly on the SME server itself. Not impossible, but difficult!
* The content below has been modified to include changes suggested in the bug tracker and forums.
* These instructions are aimed mostly at configuring SME as the only mail server, not for using SME with an internal mail server. (Specifically, LearnAsSpam.pl is harder to configure when using an internal mail server - you would have to develop a method for getting the unmarked SPAM into an IMAP folder directly on the SME server itself. Not impossible, but difficult!)
'''SONORA COMMUNICATIONS, INC.'''
'''SONORA COMMUNICATIONS, INC.'''
This is a quick configuration howto, not an in-depth look at SpamAssassin. Much more can be done
This is a quick configuration howto, not an in-depth look at SpamAssassin. Much more can be done
beyond this document, but this will take a big dent out of your spam and free up CPU cycles on your server.
beyond this document, but this will take a big dent out of your spam and free up CPU cycles on your server.
You can view the lists with this command:
You can view the lists with this command:
db spamassassin show
db spamassassin show
You can delete one or more entries from the white/blacklist using
db spamassassin delprop wbl.global name@domain.com *domain2.com
* name@domain.com and *domain2.com must exactly match a value in the output from ''db spamassassin show'' to the ''left'' of the equals sign.
* You do not need to specify ''White'' or ''Black'' when deleting entries.
'''Clam Antivirus'''
'''Clam Antivirus'''