|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: Backup MX configuration
From: Kenn Martin (kmartin
infoteam.com)Date: Mon Feb 14 2000 - 15:22:40 CST
- Next message: Wietse Venema: "Re: postconf bug in snapshot-20000204"
- Previous message: Wietse Venema: "Re: Backup MX configuration"
- In reply to: Wietse Venema: "Re: Backup MX configuration"
- Next in thread: Brad Knowles: "Re: Backup MX configuration"
- Reply: Kenn Martin: "Re: Backup MX configuration"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I thought we had tried that in the past without success, but there
was probably some other configuration issue that we had. I will
make a point of testing that method again.
Thanks,
Kenn
On Mon, Feb 14, 2000 at 04:15:33PM -0500, Wietse Venema wrote:
> Well, you COULD drop the permit_mx_backup restriction and rely
> on check_relay_domains for relay control.
>
> Wietse
>
> Kenn Martin:
> > OH! Are there no other reject options to place in front of this
> > directive to prevent this? Or is there another way to accomplish
> > the same goal?
> >
> > On Mon, Feb 14, 2000 at 03:51:09PM -0500, Wietse Venema wrote:
> > > The permit_mx_backup restriction looks at the DNS, not at the
> > > relay_domains parameter. If a host lists you as their backup,
> > > then permit_mx_backup will accept the mail.
> > >
> > > Re: faster flushing: you can tweak the {min,max}imal_backoff_time
> > > parameters.
> > >
> > > Wietse
-- Kenn Martin InfoTeam Lexington
- Next message: Wietse Venema: "Re: postconf bug in snapshot-20000204"
- Previous message: Wietse Venema: "Re: Backup MX configuration"
- In reply to: Wietse Venema: "Re: Backup MX configuration"
- Next in thread: Brad Knowles: "Re: Backup MX configuration"
- Reply: Kenn Martin: "Re: Backup MX configuration"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]