[Gllug] Rejecting mail at backup MX

Bruce Richardson itsbruce at uklinux.net
Tue Feb 10 18:23:47 UTC 2004

On Tue, Feb 10, 2004 at 06:04:27PM +0000, Greater wrote:
> > > But you can also configure it to put the messages onto the retry queue,
> > > which is going to happen anyway, if the end system is down, so I don't
> > > see the problem.
> > 
> > Again - *precisely what the OP was seeking to avoid*. Retrying and dealing 
> > with the attendant bounces which all fail is a large part of the problem 
> > with backup MX abuse.
> Come again?  If his primary is down, then his secondary will have to put
> incoming messages onto the retry queue.  All that changes with call
> forward is that this happens at a slightly earlier stage.  Am I missing
> something or are you?

Hmm.  I probably forgot to explain that with call forward, if the end
system is down then the messages are placed on the retry queue *and call
forward is retried when the end system is back up*.


It is impolite to tell a man who is carrying you on his shoulders that
his head smells.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: Digital signature
URL: <http://mailman.lug.org.uk/pipermail/gllug/attachments/20040210/4d5be630/attachment.pgp>
-------------- next part --------------
Gllug mailing list  -  Gllug at gllug.org.uk

More information about the GLLUG mailing list