Results 1 to 5 of 5

Thread: Clarkconnect in Relay ANTISPAM

  1. #1
    Join Date
    Jul 2009
    Posts
    124

    Clarkconnect in Relay ANTISPAM

    I configured a Clarkconnect (with Postfix + SpamAssassin) to our server for Mail Exchange (SBS2003). I use the option relay_recipients_maps with a perl script (cron) that will search the LDAP alias all existing mail on the Exchange server. I therefore references with ipcop port 25 of our external IP to Clarkconnect now everything works pretty well, here are some options that I added:

    smtpd_helo_required = yes
    smtpd_sender_restrictions = reject_unknown_sender_domain, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_invalid_hostname
    relay_recipient_maps = hash:/etc/postfix/relay_recipients
    show_user_unknown_table_name = No
    header_checks = regexp:/etc/postfix/header_checks
    mime_header_checks = regexp:/etc/postfix/mime_header_checks

    However new messages from exchange are emerging, it would seem that either the mails sent by spammers with internal addresses Sender that do not, once we receive the information for non-delivery:

    From: System Administrator
    Subject: Undeliverable: [SPAM] Activity on your current account

    Your message

    To: Webmaster
    Subject: [SPAM] Activity on your current account
    Sent: Mon, 8 Jun 2009 15:59:11 +0200

    did not reach the following recipient(s):

    Webmaster on Mon, 8 Jun 2009 16:00:12 +0200

    The mail system was unable to deliver this message but did not
    reported a specific reason. Check the address of the recipient and
    try to send the message. If it still fails, contact
    your system administrator.

    My question is: why do we have, with Postfix + SpamAssassin, such messages whereas before it was not?

  2. #2
    Join Date
    Apr 2008
    Posts
    3,339

    Re: Clarkconnect in Relay ANTISPAM

    Out of curiosity what became the smtpd_client_restrictions parameter in your configuration? It is something that I do not understand. I do not use "relay_recipient_maps, and recipient verification using a static file:
    smtpd_recipient_restrictions = ...
    check_recipient_access hash: / etc / postfix / access_recipient

  3. #3
    Join Date
    Jul 2009
    Posts
    124

    Re: Clarkconnect in Relay ANTISPAM

    Here the parameter smtpd_recipient_restrictions:

    smtpd_recipient_restrictions = permit_mynetworks, permit_mynetworks, reject_unauth_destination

    I must add a map in addition to the smtpd_recipient_restrictions relay_recipient? I thought that in this configuration the relay_recipient is enough.

  4. #4
    Join Date
    Apr 2008
    Posts
    3,339

    Re: Clarkconnect in Relay ANTISPAM

    Ok no problem with smtpd_recipient_restrictions. Otherwise something hurts me in your configuration but I do not have time to watch today.

  5. #5
    Join Date
    Jul 2009
    Posts
    124

    Re: Clarkconnect in Relay ANTISPAM

    thank you for the answer! Something hurts you: the fact that Exchange returns "undeliverable" because of spammers who use our addresses to spam? In any case, the duo Postfix + SpamAssassin is very efficient except for this problem.

Similar Threads

  1. Replies: 3
    Last Post: 25-11-2011, 10:27 PM
  2. Is DMZ more suitable to use SMTP relay on Clarkconnect
    By Layton in forum Networking & Security
    Replies: 5
    Last Post: 14-01-2010, 09:06 AM
  3. Squid and Dansguardian on Clarkconnect 5
    By Abdullah30 in forum Networking & Security
    Replies: 4
    Last Post: 28-11-2009, 08:06 PM
  4. Council for Clarkconnect implementation
    By Mindstorm in forum Networking & Security
    Replies: 3
    Last Post: 18-11-2009, 09:42 PM
  5. ClarkConnect 5.0 - Beta 3 Released
    By Lillebror in forum Operating Systems
    Replies: 2
    Last Post: 09-05-2009, 11:57 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,581,687.96484 seconds with 17 queries