Secondary Mail Server
Phillipus Gunawan
I am planning to experimenting my own Secondary Mail server (MX)
Currently I had a Postfix on my shorewall and working fine to deliver all emails to stupid Exchange07
Setup the DNS, everything ok
To add the flavor, I am planing to ask my best mate so I can leave a small box over his house to host secondary mail server
What I would prefer the 2nd MX is to hold all emails in case my postix is not online
I read few articles, but most of them needing me to list all current email address hold on Postfix / Exch
Is there any way I can set a 2nd MX just to hold all the emails no matter whoever the users are, and deliver it to my primary mail server after its back online?
Thanks for any advice
__________________________________________________________________________________
Win 1 of 4 Sony home entertainment packs thanks to Yahoo!7.
Enter now: http://au.docs.yahoo.com/homepageset/
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Stan Hoeppner
> Hi,
>
> I am planning to experimenting my own Secondary Mail server (MX)
> Currently I had a Postfix on my shorewall and working fine to deliver all emails to stupid Exchange07
> Setup the DNS, everything ok
>
> To add the flavor, I am planing to ask my best mate so I can leave a small box over his house to host secondary mail server
> What I would prefer the 2nd MX is to hold all emails in case my postix is not online
>
> I read few articles, but most of them needing me to list all current email address hold on Postfix / Exch
> Is there any way I can set a 2nd MX just to hold all the emails no matter whoever the users are, and deliver it to my primary mail server after its back online?
Ask this on postfi...@postfix.org
--
Stan
Tony Nelson
> Hi,
>
> I am planning to experimenting my own Secondary Mail server (MX)
> Currently I had a Postfix on my shorewall and working fine to deliver
> all emails to stupid Exchange07
> Setup the DNS, everything ok
>
> To add the flavor, I am planing to ask my best mate so I can leave a
> small box over his house to host secondary mail server
> What I would prefer the 2nd MX is to hold all emails in case my
> postix is not online
>
> I read few articles, but most of them needing me to list all current
> email address hold on Postfix / Exch
> Is there any way I can set a 2nd MX just to hold all the emails no
> matter whoever the users are, and deliver it to my primary mail
> server after its back online?
>
> Thanks for any advice
My advice is not to have a "secondary" MX, as it is just going to be
the main target of spammers, as secondary MX servers usually don't
receive the care given to primary MX servers. It might well cause a
lot of backscatter spam, as spam accepted during the SMTP transaction
will be rejected later, when your primary MX gets it, by sending a
bounce message to some innocent party.
If your mail server will normally be online, and you only expect
outages for some sort of fault, be it hardware, software, or
connectivity, you should just rely on normal SMTP retries.
--
____________________________________________________________________
TonyN.:' <mailto:tonyn...@georgeanelson.com>
' <http://www.georgeanelson.com/>
John Hasler
> ...you should just rely on normal SMTP retries.
Which many servers no longer do correctly.
--
John Hasler
Stan Hoeppner
> TonyN writes:
>> ...you should just rely on normal SMTP retries.
>
> Which many servers no longer do correctly.
Standard retry timeout for most MTAs is 5 days. What exactly do you
mean by the statement above? All "real" MTAs (not necessarily M$
Exchange) handle this correctly, whether Postfix, Sendmail, Exim,
probably even Qmail. Which MTAs do you claim do not handle this correctly?
--
Stan
John Hasler
> ...you should just rely on normal SMTP retries.
I wrote:
> Which many servers no longer do correctly.
Stan writes:
> Standard retry timeout for most MTAs is 5 days. What exactly do you
> mean by the statement above?
That some organizations ignore the standard and deliberately configure
their servers to give up after a few hours.
--
John Hasler
Robert Brockway
> My advice is not to have a "secondary" MX, as it is just going to be
> the main target of spammers, as secondary MX servers usually don't
> receive the care given to primary MX servers. It might well cause a
> lot of backscatter spam, as spam accepted during the SMTP transaction
> will be rejected later, when your primary MX gets it, by sending a
> bounce message to some innocent party.
This is the reason that it is now necessary to verify the delivery address
during the initial SMTP transaction. It is backup MXs not doing this that
causes backscatter spam. The OP mentioned that he needed to do this and
was hoping for a way around it.
To the OP: No there is no way around this requirement thanks to the
spammers. You may want to verify users via LDAP on each MX.
Rob
--
I tried to change the world but they had a no-return policy
http://www.practicalsysadmin.com
Robert Brockway
> That some organizations ignore the standard and deliberately configure
> their servers to give up after a few hours.
I've been seeing less of that. My recent experience is that even
organisations pushing a lot of mail will keep retrying for 24 or 48 hours.
Having said that I have no problem with using backup or multiple primary
MXs if they are properly configured. They should all:
1. Reject undeliverable mail in the first instance.
2. Use the same anti-spam strategies.
3. Receive the same care as any other server (patching, etc)
Rob
--
I tried to change the world but they had a no-return policy
http://www.practicalsysadmin.com