Postfix main.cf wildcard emails using access

postfix

In my postfix main.cf I have:

smtpd_recipient_restrictions = reject_unauth_destination, check_recipient_access regexp:/etc/postfix/access.me

…

virtual_alias_maps    = hash:/etc/postfix/virtual

…

In my virtual file I have:

a@mydomain.com                            xxxx@gmail.com
na@mydomain.com                           xxxx@gmail.com
@mydomain.com                             xxxx@gmail.com

In my access.me file I have:

/^abc/ OK
/a@mydomain.com/  OK
/na@mydomain.com/  REJECT failed test
/@mydomain.com/  REJECT failed test contact us@mydomain.com

With this I have successfully failed (!) to send to na@mydomain.com so I know access.me is being read correctly by postfix.
If I send to xyz@mydomain.com it fails (correctly) rejected by Line 4 of access.me

However if I try to mail abc123@mydomain.com it fails with "User unknown in virtual alias table" which shows that it is accepted by line 1 of access.me, but I need this email to succeed and get through.

So nearly there but I must be misunderstanding postfix logic…
Tim

Best Answer

Having tested it again to provide more information I found that it did actually work (for the first time) so either the virtual file was not the latest version or there was a delay in propagation.

This configuration was designed so that customers could send emails to us where the email address itself was generated from data (ex: location and language of user), since coupled with the sender address the customer need not input anything apart from their comments.

So this does seem to be a valid way to enable customised email addresses to get through postfix while rejecting randomised email addresses / spam.

Tim

Related Solutions

Ubuntu – SMTP 550 5.1.1 error when sending email with postfix via amazon SES

Detailed step by step was taken from this blog.

Download and extract script from this page.
From the README file: These scripts get your AWS access key ID and secret access key from environment variables. The procedure for setting environment variables depends on your operating system. You need to do the following:
- Create an environment variable called AWS_ACCESS_KEY_ID and set it to your AWS access key ID. Your AWS access key ID will look something like: AKIAIOSFODNN7EXAMPLE.
- Create an environment variable called AWS_SECRET_ACCESS_KEY and set it to your AWS secret access key. Your AWS secret access key will look something like: wJalrXUtnFEMI/K7MDENG/bPxRfiCYzEXAMPLEKEY.

Test the setup with sending message from perl script.

$ echo 'test msg' > msgbody.txt
$ ./ses-send-email.pl -s "Test of Amazon SES" -f user@example.com user@gmail.com < msgbody.txt

Request SES Access by go to this page.

Configure postfix. Modify the master.cf to add

aws-email  unix  -       n       n       -       -       pipe
    flags=R user=support argv=/opt/thirdparty/amazon/bin/ses-send-email.pl -r -e https://email.us-east-1.amazonaws.com -f ${sender} ${recipient}

Then Modify the main.cf to add

default_transport = aws-email

Copy SES.pm from extracted folder to /user/local/lib/site_perl (if not existing, create one), this is important!

Script notes:

Amazon SES no longer maintains these scripts. For command-line access to Amazon SES, you can use the AWS Command Line Interface or the AWS Tools for Windows PowerShell. To integrate your mail server with Amazon SES, you can use the Amazon SES Simple Mail Transfer Protocol (SMTP) interface. For more information, see Integrating Amazon SES with Your Existing Email Server.

Postfix header_checks using regexp proper setup

Solved - Following line in /etc/postfix/master.cf was causing conflict :

pickup    fifo  n       -       -       60      1       pickup
    -o content_filter=
#   -o receive_override_options=no_header_body_checks  //commented this line out

Best Answer

Related Solutions

Ubuntu – SMTP 550 5.1.1 error when sending email with postfix via amazon SES

Postfix header_checks using regexp proper setup

Related Topic