This is a discussion on Verification of Postfix configuration requested within the alt.comp.mail.postfix forums, part of the Mail Servers and Related category; Hello all, We've just moved our clients to a new mail server. Both the old and new config contain ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hello all,
We've just moved our clients to a new mail server. Both the old and new config contain postfix, amavisd-new, mysql and cyrus-imapd. All virtual, transport, etc information is in a flat mysql database. This database is created out of another relational database. We've used these applications for some years now, but due to the changes in suggested configuration layouts, we'd like to 'verify' our configuration in this group. Any comments on configuration faults, performance issues, tweaks, etc. are welcome. So here goes: We host several client domains. Not all want spam and virus filtering so we've stored preferences in our database. Based on *_access check with a "FILTER amavis:[127.0.0.1]:amavis" RHS we filter only those domains that we want to filter: smtpd_recipient_restrictions = ... check_sender_access proxy:mysql:$config_directory/maps/mysql-filter.cf check_recipient_access proxy:mysql:$config_directory/maps/mysql-filter.cf ... The smtpd clients and amavis smtp client are configured like this: smtp inet n - n - - smtpd -o receive_override_options=no_address_mappings -o content_filter=smtp:[127.0.0.1]:postscan localhost:postscan inet n - n - - smtpd -o smtpd_recipient_restrictions=permit_mynetworks,rej ect -o smtpd_authorized_xforward_hosts=127.0.0.0/8 -o receive_override_options=no_unknown_recipient_chec ks,no_header_body_checks amavis unix - - n - 5 smtp -o smtp_bind_address=127.0.0.1 -o smtp_send_xforward_command=yes The "-o content_filter=smtp:[127.0.0.1]:postscan" is for those domains that do not match the mysql-filter.cf and would otherwise not be found in the virtual alias maps because of the receive_override_options=no_address_mappings statement, right? Local delivery is through: mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp I want to change this to "local_transport = lmtp:unix:/var/lib/imap/socket/lmtp" so multi-recipient deliveries are better off, but will have to migrate my aliases.db to virtual aliases first, right? We places "myorigin = mailbox.ourdomain.com" in main.cf because all Cyrus mailboxes are in the "mailbox.ourdomain.com" realm. We would like to have Postfix send out local e-mail with a @truehostname.ourdomain.com suffix, instead of mailbox.ourdomain.com, but I don't see that happening yet. Unless I append @mailbox.ourdomain.com to every virtual aliases, right? The latest Cyrus supports different realms (or virtual domains). One for each client. I can now create a user john@domain1.com and a user john@domain2.com. What would my vitual aliases look like? If I put things like: john@example1.com john@example1.com I would generate a loop. Or do I put john@example1.com lmtp:john@example1.com Thanks all for your input! Regards, Spookyfish |