On Sun, Jan 14, 2001 at 03:38:40PM +0100, Jurjen Oskam wrote:
> But I'm interested in the case where an MXPS-aware QMTP-capable sender
> tries to deliver a message to quadpro.stupendous.org (with MX records
> set according to [1], but finds port 209 (QMTP) unavailable. Will such
> a sender then (directly after the failure to deliver to
> a.mx.stupendous.org using QMTP): 1) try to deliver to
> b.mx.quadpro.stupendous.org using SMTP or 2) try to deliver to
> a.mx.stupendous.org using SMTP? And if I change the MX-records to [2],
> will that behaviour change?
In theory you option no. 2 is the best way, it says "try a.mx via qmtp, on
failure try a.mx via smtp, on failure use b.mx via smtp". In practice you
could also use option 1, as the only MXPS capable sender is Russels patched
qmail-remote AFAIK, and everbody using it will support qmtp (everything
else, e. g. the port is closed within the firewall, i would call a
misconfiguration).
Anyway I'd vote for option 2, it's the clearest ;-)
> [1]
> quadpro.stupendous.org 86323 MX 12801 a.mx.quadpro.stupendous.org
> quadpro.stupendous.org 86323 MX 12816 b.mx.quadpro.stupendous.org
> [2]
> quadpro.stupendous.org 86323 MX 12801 a.mx.quadpro.stupendous.org
> quadpro.stupendous.org 86323 MX 12816 a.mx.quadpro.stupendous.org
> quadpro.stupendous.org 86323 MX 12832 b.mx.quadpro.stupendous.org
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
http://www.bsws.de | Germany
