Addition/Always accept messages for special aliases

From iRedMail
Revision as of 02:45, 15 March 2010 by Maxie ro (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Mission

(Almost) always receive e-mail messages for postmaster@*, abuse@*, hostmaster@*, webmaster@*.

Reason

You should always allow to be contacted on the four special aliases listed above. For example, in certain circumstances another postmaster from an external domain would like to contact you about messages coming from his server and considered spam by your local server and not delivered because of a misconfiguration.

Step-by-step configuration

  • Requirements:
    • A properly working iRedMail system;
  • Note:
    • This article was written with a CentOS-based system in mind. Adapt it for your system.
  • Step 1.

Create the lookup table /etc/postfix/accept_special with the following contents (a regular text file):

File:
abuse@ OK
postmaster@ OK 
webmaster@ OK
hostmaster@ OK 
  • Step 2.

Compile the above file using postmap, type hash:

Terminal:
cd /etc/postfix
postmap hash:accept_special
  • Step 3.

Check that the file /etc/postfix/accept_special.db exists.

  • Step 4.

Edit /etc/postfix/main.cf and add the accept_special.db lookup table to smtpd_recipient_restrictions, to a place in the rule chain you see fit for your server:

File:
smtpd_recipient_restrictions = 
	reject_unknown_sender_domain, 
	reject_unknown_recipient_domain, 
	reject_non_fqdn_sender, 
	reject_non_fqdn_recipient, 
	reject_unlisted_recipient, 
	permit_mynetworks, 
	permit_sasl_authenticated, 
	reject_unauth_destination, 
	check_recipient_access hash:/etc/postfix/accept_special, // <-- For example add it here
	[...] 
  • Note:
    • The place where you add it is quite important. For example, I choosed not to add it further above, so I can cut down on the amount of spam I receive on the special aliases. You might want to add it further above or below in the rule chain.
    • For usual iRedMail configuration that's the recommended place to add it.
  • Step 5.

Restart postfix service and make sure everything is working ok by tail-ing the logs.

--Maxie ro 08:45, 15 March 2010 (UTC)

Personal tools