Furthermore, if no catchall entry exists, mail will be bounced if there is no explicit match. In other words, with the table below, mail for bogus. Many people have asked how to configure qmail so that mail for a virtual address is forwarded somewhere else for example to a user's Hotmail account without passing through the system at all.
It IS possible. There are two ways of doing it. One is intuitively easier to understand but the code is not perfect and can cause mail loops. The other way takes a little more work but is more reliable. Adding entries to virtual does not instruct qmail-smtpd to accept delivery for a domain.
You still need entries in the rcpthosts list. This table and the flat file can co-exist peacefully. The alias table allows you to specify aliases and mailing lists in a similar way to. You can also "forward" to programs or explicitly named files or directories, just like you can with.
To do this, you must put either ,. Mail for dmp is forwarded to dmp nigelj. Mail for iain is piped through preline. Mail for njp-spam is delivered to the Spam maildir in njp's home directory. Just as with standard qmail, you can use rules involving the alias user to catch mail for nonexistent accounts. In the example above we send mail for the unknown user bogus to iain.
This is the equivalent of adding iain to. Please note: You still need to set up usernames and maildirs for users you use in alias table entries, even if your alias rules send mail off-site. They can be system users listed in the passwd file or virtual users in the mailbox table but they must exist somewhere. Here, mail addressed to customers is forwarded to each of the for example destinations. If you don't want mail for a certain user to be delivered to his mailbox at all but rather be delivered to some remote destination, an entry in the alias table is NOT sufficient!
You must still set up the user either in the mailbox table or as a system user and create his home directory with the correct ownership and permissions as well! It follows that the entry below is effectively a no-op when the default destination is.
Installation 8. Example Configurations 8. Basic Setup 8. Cluster 8. Comparison with stock qmail, migration issues Testing configs, diagnosing problems Performance The qmail-ldap-control patch Basics Installation: qmail-ldap-control Example Configurations - move the control files to ldap Additional Patches The Dash-Trick RBL Tagging A.
Installing packages A. Manual source install B. Operating System specifics D. Introduction This document will probably never be as comprehensively helpful as its inspiration, Life With Qmail by Dave Sill, and it won't explain the basics of qmail and ldap. This fantastic piece of software was developed by Andre Oppermann and Claudio Jeker.
Mailing-List There's also a Mailing list, qmail-ldap qmail-ldap. Configuration Now that you have the schema loaded, a little system configuration is needed. Filling the Directory At this point, you need to create the directory hierarchy and accounts. After you have created the file, load it into your directory with the ldapadd utility. The Big Picture See also the qmail and qmail-ldap big pictures from the qmail-ldap homepage.
Components of qmail-ldap and how they fit together 5. It also handles the. Handles also session forwarding. Just pass the path to a controlled directory. An invocation of tcpserver will listen for connections on a port, when one arrives it will start a client program with args as specified on the tcpserver cmdline, and with envars as specified by UCSPI-TCP. Installation Install ucspi-tcp and daemontools according to Appendix 1.
Normaly not needed. This is necessary on MacOS X Normally, passwords without prefix are treated as crypt passwords. Needs the ZLIB options. This avoids the silly qmail syndrome with high mail injection rates. On some systems -lresolv is needed, too.
If you have problems compiling, double check this. If you have problems compiling, double-check this. You'll need OpenSSL. If you have TLS enabled and compilation problems, double check this. No external script needed. It gets the dir as first and only parameter. DEBUG compiles some debugging code in. Same format as rcpthosts. Default: NULL 8. Default: 0 off 8. Don't forget to set quotawarning, otherwise no quota warning messages are issued.
A sample script:! Lots of other crypt methods like MD5 are possible. Every entry to be used by qmail-ldap should have qmailuser as objectclass, but this isn't checked by default. Starting with patch , it is possible to check this. Note that it MUST match the name given in "me" on the affected server.
If you are starting qmail with qmail-start. In this example, MB or Mails. If deliverymethod isn't set to "localdelivery", mail is only forwarded, no local copy stored. You can only set ONE mail attribute per user, and addresses must be unique. Use mailalternateaddress for additional addresses.
Define as much as you want. There are more possible fields: qmailUID The system uid for this user. If not set, the value from the control file "ldapuid" is taken virtual user environment. I recommend not to use this field, mailmessagestore is the cleaner approach. Only used if qmailDotMode is set to ldapwithprog or both. All environment variables as described in qmail-command 8 are set, and the exit code is handled exactly as described there.
If, for example, the program exits the mail is bounced. In conjunction with forwarding this means to deliver a local copy. It is possible to set more than one value, be carefull. Only used if deliveryMode is set to "reply". Access control with tcpserver Access control is done by tcpserver. A basic tcp file looks like this: This is important for qmail-smtpd: It is also possible to set more than one environment variable: Your run file will look like this:!
Cluster One of qmail-ldap's greatest features: its native clustering support. How clustering works with qmail-ldap It unbelievable simple. Add all domains to be handled by the cluster to the control files rcpthosts and locals on all cluster members - rsync is your friend ;- This should be all.
Comparison with stock qmail, migration issues Volunteers? Testing configs, diagnosing problems Volunteers? Performance yes, performs great! The qmail-ldap-control patch This patch is by Turbo Fredriksson who wrote the following documentation for his patch, too. Where to find the patch. Notes about usage.
What is it? What does it do? Main reason for usage. This can quite easily made even by a sales-person like Stef : Using a simple webinterface and spending some thoughts when setting up multiple qmail servers either as a cluster, or standalones , you can have all the configuration in one place under the same Control DN in the LDAP database , thus making it harder for the unexperienced people to forget a host when modifying system-wide information.
Files still needed for startup. Applying the patch and customise Makefile to reflect your setup. Now it's time to modify the Makefile to reflect your setup. Modify the configuration for your LDAP server. When this is done, restart the LDAP server or make it reread the new configuration. Move control information to the LDAP database.
Basic LDAP object. Moving the 'locals' file to LDAP. Content of existing files after move to LDAP. Now when we have moved all of the information from files to the LDAP database, we should only have the remaining files in the control directory: If your users are coming from various, dynamic IP addresses they can't use your mailserver for sending :- To overcome this limitation there are 3 possibilities: relaying based on the envelope sender - a really bad idea, easy to abuse.
For a patch see below. Therefore, run somthing like the following every 15 mins or whatever you like by cron:! Simple, eh? Arek Dreyer has some extended scripts, I'll put a tgz to the download location. Get it here. Some common problems: 1. The Dash-Trick This patch is slightly modified included as of RBL Tagging qmail-ldap can block messages from servers listed on various rbl lists by default. Manual source install A. Solaris 8 Required Software - Newer versions may be substituted normally.
GCC version 2. Installation is once more really simple: gunzip ucspi-tcp No configuration needed. The control file ldapserver exists and has correct permissions What's the problem? Acknowlegements Dave Sill for support and encouragement, and for letting me call this Life With qmail-ldap in frank homage to his Life With qmail.
DESC 'On which qmail server the messagestore of this user is located. DESC 'Address es to forward all incoming messages to. DESC 'Program to execute for all incoming mails. DESC 'Interpretation of. DESC 'multi field entries of: nolocal, noforward, noprogram, reply'.
DESC 'A reply text for every incoming message'. DESC 'The status of a user account: active, noaccess, disabled, deleted'. DESC 'The size of space the user can have until further messages get bounced. DESC 'The number of messages the user can have until further messages get bounced. DESC 'The maximum size of a single messages the user accepts. DESC 'Group member specified as distinguished name. DESC 'Group member specified as normal rf email address.
0コメント