Please pardon the delay in response to this thread...
I've been on vacation and am only just now catching up with the list.
On Monday 10 May 2004 10:07 am, Peter Bowyer wrote:
> Best practice (by which I mean regularly-discussed rather than
> defined in a BCP) is to only use a secondary MX when you can assure
> that it has a way of knowing what are valid localparts in the target
> domain, and the same spam and virus rejection policies as the
> primary.
We're looking at using callouts to determine if recipients exist. Is
this a reasonable use of callouts? Can it work? Will it throw us any
other problems?
Our other option would be to maintain a list on the secondary MX; that
would be harder to do, and wouldn't be as close to realtime.
Any suggestions?
Thanks.
Jeff
At which point it probably becomes not a secondary but a
> parallel primary (as someone else mentioned here only today). May as
> well let it deliver on to the destination itself.
>
> It isn't a MUST as in an RFC. But it does make sense.
>
> Peter
>
>
> --
>
> ## List details at http://www.exim.org/mailman/listinfo/exim-users
> Exim details at http://www.exim.org/ ##
--
Jeff Lasman, nobaloney.net, P. O. Box 52672, Riverside, CA 92517 US
Professional Internet Services & Support / Consulting / Colocation
Our blists address used on lists is for list email only
Phone +1 909 324-9706, or see: "
http://www.nobaloney.net/contactus.html"
