On Tue, Jan 16, 2001 at 05:16:45AM -, D. J. Bernstein wrote:
Johan Almqvist writes:
Quoting http://cr.yp.to/proto/mxps.txt
Don't believe everything you read. :-)
My original design made QMTP-only mail exchangers easier but made
QMTP+SMTP mail exchangers harder. This was a bad
D. J. Bernstein writes:
Johan Almqvist writes:
Quoting http://cr.yp.to/proto/mxps.txt
Don't believe everything you read. :-)
My original design made QMTP-only mail exchangers easier but made
QMTP+SMTP mail exchangers harder. This was a bad tradeoff.
Clients should interpret
On Sun, Jan 14, 2001 at 03:05:16PM +0100, Jurjen Oskam wrote:
[snip]
However, when I query for crynwr.com, I get:
crynwr.com 86354 MX 12801 pdam.crynwr.com
crynwr.com 86354 MX 12816 pdam.crynwr.com
This set of MX records compensates for a bug in Russell's QMTP
implementation (that has not
Johan Almqvist writes:
Quoting http://cr.yp.to/proto/mxps.txt
Don't believe everything you read. :-)
My original design made QMTP-only mail exchangers easier but made
QMTP+SMTP mail exchangers harder. This was a bad tradeoff.
Clients should interpret a QMTP priority as ``try QMTP, then try
Situation:
The primary MX for quadpro.stupendous.org is capable of accepting mail
via QMTP, and regularly does so. Of course, it is also capable of
accepting mail via SMTP. The 'secondary' MX is only capable of doing
SMTP.
What are the correct MX-records I should create?
I made:
On Sun, Jan 14, 2001 at 03:05:16PM +0100, Jurjen Oskam wrote:
What are the correct MX-records I should create?
I made:
quadpro.stupendous.org 86323 MX 12801 a.mx.quadpro.stupendous.org
quadpro.stupendous.org 86323 MX 12816 b.mx.quadpro.stupendous.org
That is correct.
quadpro.stupendous.org
On Sun, 14 Jan 2001 15:12:09 +0100, Johan Almqvist
[EMAIL PROTECTED] wrote:
Quoting http://cr.yp.to/proto/mxps.txt
" Example:
[...]
B.EXAMPLE.ORG IN MX 12801 A.EXAMPLE.ORG
IN MX 12816 C.EXAMPLE.ORG
[...]
A sender with a message for B.EXAMPLE.ORG will try
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
