Gentoo postfix setup

This is called an open relay and is begging for abuse by spam merchants, likely resulting in your domain to be quickly blacklisted. This defeats the purpose of setting up a personal mail server, if nobody will talk or listen to it. There are means and ways, like SMTP Authentication, that allow you to secure access to your mail server even further. Depending on the trustworthiness of the users connected to the local network, it might be beneficiary to restrict access even for machines within the own subnet.

This also has the benefit of not letting potentially compromised machines in the local network abuse the mail system, but entails additional configuration. To only allow the mail server itself to relay email without authentication, make a change to main.

Address extensions allow you to encode additional information besides the recipient in a valid email address. To enable support for address extensions, edit your main. This feature can be quite useful for sites that require email address registration. If for example some unsolicited mail was delivered to that address, it likely comes from somesite. Soft bounce decreases the chances of endless bounce loops caused by an invalid email setup.

To enable soft bouncing, add this to main. Before testing the basic mail server setup, the verbose flag of the smtp server can be enabled by adding a -v to the smtpd daemon invocation in master. Opendkim runs under the milter user.

This is good, but postfix can't access this. Adding postfix to the milter group solves this easily however. Informing postfix of the change makes immediate use of DKIM, a restart is required due to the change of permissions. To test the DKIM setup a blank email can be sent to check-auth verifier.

Postfix installation is quite straight forward. A basic installation instruction for Postfix should be followed. Fetch the SQL dump and save it as genericmailsql. Follow the on-screen instructions for adding a root password within MySQL as otherwise the database will be wide open. Start the MySQL database server and create the mailsql database:. Fire up the mysql client to grant the proper rights to the mailsql database:.

Verify that the new mailsql user can connect to the mysql server:. The new database has default values and tables set up for two domains. The following tables are included:. That's the thing, I compared the two just to make sure as I'm fairly new to running Postfix et all, originally used qmail. Here's the relevant config files. I agree that the lodical choice for the problem is sasl Code:. I think I've nailed it. The problem is that cyrus-sasl was compiled with the USE flags mysql and ldap, but in the virtual email setup courier-authd talks to MySQL; cyrus just passes the details onto courier's auth daemon.

I've recompiled cyrus-sasl without - in my case - ldap and mysql USE flags and the error messages are now gone from the log file. Posted: Mon Nov 06, pm Post subject:. Posted: Sat Dec 30, pm Post subject:.