On Sun, 14 Jan 2001 20:25:44 +0100, Jurjen Oskam wrote:
On Sun, 14 Jan 2001 13:39:01 -0500 (EST), Russell Nelson
[EMAIL PROTECTED] wrote:
That's a misconfiguration. I'd rather that the email bounced than it
got delivered via SMTP silently. It could be that someone unaware of
...
* Ian Lance Taylor [EMAIL PROTECTED] [010116 19:36]:
Now I see it. You can't call connect twice on the same socket. This
patch, on top of Russ's patch, fixes it.
This patch very much fixes it for my patch, too. Thanks a bunch, Ian!
This leads me to the next thing (concerning my patch):
If
Ian Lance Taylor writes:
Ian Lance Taylor [EMAIL PROTECTED] writes:
I think there may be a problem with the patches to qmail-remote that make
it speak QMTP based on MXPS.
If the QMTP connection fails (because the remote host doesn't have a qmtpd
running) this failure
On Wed, Jan 17, 2001 at 10:21:53AM -0500, Russell Nelson wrote:
[snip]
Thanks for catching and fixing this bug. I'm glad *you* knew that you
can't call connect twice on the same socket.
Actually you can, but only under specific circumstances, being: the
first connect being done nonblocked
* Ian Lance Taylor [EMAIL PROTECTED] [010115 23:53]:
I don't see it. Russ's patch looks like this (at least, in the
version I downloaded):
+if (qmtp_priority(ip.ix[i].pref)) {
+ if (timeoutconn(smtpfd,ip.ix[i].ip,(unsigned int) qmtp_port,timeoutconnect)
== 0) {
+
Johan Almqvist [EMAIL PROTECTED] writes:
* Ian Lance Taylor [EMAIL PROTECTED] [010115 23:53]:
I don't see it. Russ's patch looks like this (at least, in the
version I downloaded):
+if (qmtp_priority(ip.ix[i].pref)) {
+ if (timeoutconn(smtpfd,ip.ix[i].ip,(unsigned int)
Ian Lance Taylor [EMAIL PROTECTED] writes:
I think there may be a problem with the patches to qmail-remote that make
it speak QMTP based on MXPS.
If the QMTP connection fails (because the remote host doesn't have a qmtpd
running) this failure will be logged as
deferral:
Russell Nelson [EMAIL PROTECTED] writes:
Johan Almqvist writes:
Hi!
I think there may be a problem with the patches to qmail-remote that make
it speak QMTP based on MXPS.
If the QMTP connection fails (because the remote host doesn't have a qmtpd
running
That's a
Scott Gifford [EMAIL PROTECTED] writes on 15 January 2001 at 17:24:13 -0500
And, since MXPS is not an accepted Internet standard, the (unlikely,
but possible) situation where somebody has chosen an MX priority which
isn't MXPS-compatible should be handled gracefully.
I think that's the
David Dyer-Bennet writes:
Scott Gifford [EMAIL PROTECTED] writes on 15 January 2001 at 17:24:13 -0500
And, since MXPS is not an accepted Internet standard, the (unlikely,
but possible) situation where somebody has chosen an MX priority which
isn't MXPS-compatible should be
Hi!
I think there may be a problem with the patches to qmail-remote that make
it speak QMTP based on MXPS.
If the QMTP connection fails (because the remote host doesn't have a qmtpd
running) this failure will be logged as
deferral: Connected_to_194.47.249.19_but_connection_died._(#4.4.2)/
Johan Almqvist writes:
Hi!
I think there may be a problem with the patches to qmail-remote that make
it speak QMTP based on MXPS.
If the QMTP connection fails (because the remote host doesn't have a qmtpd
running
That's a misconfiguration. I'd rather that the email bounced than
* Russell Nelson [EMAIL PROTECTED] [010114 19:39]
That's a misconfiguration. I'd rather that the email bounced than it
got delivered via SMTP silently.
Well, at the moment it'll only be bounced after queuelifetime...
It could be that someone unaware of the MXPS standard (which admittedly
On Sun, 14 Jan 2001 13:39:01 -0500 (EST), Russell Nelson
[EMAIL PROTECTED] wrote:
Johan Almqvist writes:
If the QMTP connection fails (because the remote host doesn't have a qmtpd
running
That's a misconfiguration. I'd rather that the email bounced than it
got delivered via SMTP silently.
* Jurjen Oskam [EMAIL PROTECTED] [010114 20:25]
What happens in the following case:
quadpro.stupendous.org 86323 MX 12801 a.mx.quadpro.stupendous.org
quadpro.stupendous.org 86323 MX 12817 b.mx.quadpro.stupendous.org
...when qmtpd isn't reachable on a.mx.quadpro.stupendous.org?
That's
* Johan Almqvist [EMAIL PROTECTED] [010114 15:45]:
I think there may be a problem with the patches to qmail-remote that make
it speak QMTP based on MXPS.
If the QMTP connection fails (because the remote host doesn't have a qmtpd
running) this failure will be logged as
deferral:
16 matches
Mail list logo
