|Newer page:||version 6||Last edited on Friday, May 26, 2006 2:42:05 pm||by AristotlePagaltzis|
|Older page:||version 5||Last edited on Sunday, February 1, 2004 5:46:48 pm||by JustinLarue||Revert|
@@ -1,50 +1,45 @@
as a secondary MX
+!!! as a secondary MX
-As far as I can tell, setting up
to act correctly as a secondary MX is a bit of a drag.
seems to run into problems if it is a secondary MX, and it gets a message when all higher-priority
MXes for the domain are down.
Without special configuration, it will bounce the message with a "mail loops back to me (MX problem?)" error.
+As far as I can tell, setting up to act correctly as a secondary MX is a bit of a drag. seems to run into problems if it is a secondary MX, and it gets a message when all higher-priority MXes for the domain are down. Without special configuration, it will bounce the message with a " mail loops back to me (MX problem?) " error.
The very first steps to setting this up are:
-Add MX records in DNS.
+Add MX records in DNS . For example:
mydomain.com. MX 0 preferredmx.mydomain.com.
MX 10 secondarymx.otherdomain.org.
-MXes with the lowest numbers are given the highest priority.
I'm assuming that you already have a primary setup, and that part won't be explained here.
+MXes with the lowest numbers are given the highest priority. I'm assuming that you already have a primary setup, and that part won't be explained here.
-Now, on the secondary (this assumes you have /etc/mail/access and /etc/mail/mailertable):
+Now, on the secondary (this assumes you have /etc/mail/access and /etc/mail/mailertable ):
-# Add a line containing
mydomain.com RELAY ' to
# Add a line containing 'mydomain.com smtp:preferredmx.mydomain.com'
to /etc/mail/ mailertable (this is the bit that seems to commonly not be mentioned).
# Run 'make' in /etc/mail. Check the timestamps of
access .db and mailertable.db to be sure that they have just been regenerated. If they haven't, 'touch' access and mailertable and check your clock.
#If you don't have a makefile, run "makemap hash access.db
< access; makemap hash mailertable.db < mailertable".
# Restart sendmail (probably "
/ etc/init.d/sendmail restart").
# Try sending a test message from a local address through the secondary to firstname.lastname@example.org
+# Add a line containing mydomain.com RELAY / to /etc/mail/access</ .
You should be all set
. Try making the primary unreachable from the secondary, just to be sure, and repeat step 6. The easiest way to make it unreachable is '
preferredmx # route add secondarymx
. org dev lo'. Do __not__ do that if you are presently logged into preferedmx from secondarymx, and that
is the only way you can reach preferredmx. By doing this you are (temporarily) adding a bad route between the two boxes.. if you don't understand the implications of
that , you probably don't want
to do it. Be sure to 'route del secondarymx.otherdomain.org dev lo' after you are done testing.
+ . preferredmx. . is the that to .
!!!make in /etc/mail doesn
't build sendmail
+ 't .
So you just updated your
/sendmail .mc, but when you run 'make', nothing happens.
If you manually try to make sendmail.cf using 'm4', you get an error along the lines of:
+ /etc/ /sendmail
. mc:10: m4: Cannot open
. m4: No such file or directory
+ . / .
, this means
the sendmail-cf package
+ If you , you to the .
Why there is a seperate package for people who want to actually *configure* sendmail, I don
+ 't .
!!!Respooling an mbox to somewhere else
Not really sendmail as such
, but hey..
+ , .
formail -f -s sendmail newuser@some
. domain.com < /var/mail/spoolfile