Re: [courier-users] setting up a true backup-mx

Am Freitag, den 13.10.2006, 07:07 -0400 schrieb Sam Varshavchik:
> Bernd Wurst writes:
>
> > Hi.
> >
> > (sorry for double-post, I used the wrong sender-address before and resending this for faster processing.)
> >
> > I set up a courier box as a backup-mx as described in the FAQ.
> >
> > My checks seemed to work.
> > Now our master server is broken and I need the backup-mx to cache all messages.
> > The problem is the pseudo-intelligence of courier to not accept any message to a recipient if former messages could not be delivered.
> >
> > So my backup-mx does nothing but reject messages. So it's use is nonexistent, because causing a temporary failure could also be done by the broken master (connection refused would also be temporary failure).
> >
> > So my question is: Can I tweak courier in any way to accept all messages it's configured for also if there were deliverey problems?
>
> Well, you can certainly turn off backscatter suppression, but you've just
> discovered why backup MXes are no longer needed on the modern Internet.

Unless of course you'd like to get an IPv6 tunnel from sixxs.net. They
require that the domain of the contact email has a secondary MX or they
won't let you sign up.

Most of their rules regarding contact email are silly, but what can you
do.



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=...057&dat=121642
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users