#1  
Old 15th August 2006, 21:00
rodriglm rodriglm is offline
Junior Member
 
Join Date: Dec 2005
Posts: 14
Thanks: 0
Thanked 0 Times in 0 Posts
Default Help with Spamassassin

Hi,

I am using ISPConfig as my email server and ftp in production right now. Using version 2.1.2. Thinking on upgrading to 2.3.1 but later on. What i would like to know is how to block certain domains using spamassassin. I followed the setup for the perfect fedora core 4 with ISPConfig. I would appreciate help in how to do this, thanks.


Luis

Last edited by rodriglm; 15th August 2006 at 21:02. Reason: Misleading subject
Reply With Quote
Sponsored Links
  #2  
Old 15th August 2006, 21:04
sjau sjau is offline
Local Meanie
 
Join Date: Apr 2006
Location: Switzerland
Posts: 1,146
Thanks: 4
Thanked 55 Times in 51 Posts
Default

Do you use Postfix as mailserver?
Reply With Quote
  #3  
Old 15th August 2006, 21:10
rodriglm rodriglm is offline
Junior Member
 
Join Date: Dec 2005
Posts: 14
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Yes, postfix is my mailserver with spamassasin and clamav.
Reply With Quote
  #4  
Old 15th August 2006, 21:18
sjau sjau is offline
Local Meanie
 
Join Date: Apr 2006
Location: Switzerland
Posts: 1,146
Thanks: 4
Thanked 55 Times in 51 Posts
Default

you could change the recipient restrictions in the postfix config to and add this:

Code:
check_sender_access hash:/etc/postfix/sender_checks,
The sender_checks file could look like this:
Code:
# This file must be "compiled" with "postmap"

# Using a domain name
example.tld             554 Spam not tolerated here
discardmail.com         554 Spam not tolerated here
izmail.serveftp.net     554 Spam not tolerated here
mailings@gmx-gmbh.de    REJECT

# Maybe example2.tld is on a DNSbl, but we want to let their
# email in anyway.
example2.tld            OK

# We get lots of spam from example3.tld, but we have somebody
# there from which we do want to hear
someuser@example3.tld   OK
example3.tld            REJECT
and when you have the file the you need to "convert" it do a db --> postmap sender_checks
Reply With Quote
  #5  
Old 16th August 2006, 07:15
bschultz bschultz is offline
Senior Member
 
Join Date: Jul 2006
Posts: 221
Thanks: 11
Thanked 10 Times in 10 Posts
Default

New version of ISPConfig allows for a white and blacklist in the email section of the admin panel.
Reply With Quote
  #6  
Old 16th August 2006, 07:21
sjau sjau is offline
Local Meanie
 
Join Date: Apr 2006
Location: Switzerland
Posts: 1,146
Thanks: 4
Thanked 55 Times in 51 Posts
Default

bschultz: thx for pointing this out I didn't know it as I don't use ispconfig (yet)
Reply With Quote
  #7  
Old 16th August 2006, 16:05
rodriglm rodriglm is offline
Junior Member
 
Join Date: Dec 2005
Posts: 14
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by sjau
you could change the recipient restrictions in the postfix config to and add this:

Code:
check_sender_access hash:/etc/postfix/sender_checks,
The sender_checks file could look like this:
Code:
# This file must be "compiled" with "postmap"

# Using a domain name
example.tld             554 Spam not tolerated here
discardmail.com         554 Spam not tolerated here
izmail.serveftp.net     554 Spam not tolerated here
mailings@gmx-gmbh.de    REJECT

# Maybe example2.tld is on a DNSbl, but we want to let their
# email in anyway.
example2.tld            OK

# We get lots of spam from example3.tld, but we have somebody
# there from which we do want to hear
someuser@example3.tld   OK
example3.tld            REJECT
and when you have the file the you need to "convert" it do a db --> postmap sender_checks

But will this still work with this version of ISPConfig or do i see myself upgrading? Is there another way that it needs to be done in ISPConfig?? Thx.
Reply With Quote
  #8  
Old 16th August 2006, 16:54
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,741 Times in 2,575 Posts
 
Default

As bschultz said, the new ISPConfig version allows you to do it through the web interface. So upgrade to 2.2.6, and don't change anything on the command line.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
config spamassassin hotchilli Server Operation 1 8th July 2006 12:03
Postfix + Amavis + SpamAssassin + ClamAV michele HOWTO-Related Questions 4 1st July 2006 14:36
problem with spamassassin and CentOs 4.2 rickygm Installation/Configuration 1 13th June 2006 11:14
Daemonized version of Spamassassin ddelbia General 1 6th January 2006 16:09
Spamassassin configuration DarkBen Installation/Configuration 1 4th January 2006 10:58


All times are GMT +2. The time now is 15:55.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.