On Fri, 26 Jan 2001, Pavel Kankovsky wrote:
On Thu, 25 Jan 2001, Dan Peterson wrote:
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/netinet/tcp_usrreq.c
Revision 1.20; dated Feb 28 1998.
Hmm...hmm...right. Ok, I missed it. It did not occur to me 0.0.0.0 is a
broadcast address in Canada.
On Thu, 25 Jan 2001, Markus Stumpf wrote:
If AOL or hotmail would decide to change their MX records to your mailserver
this will for sure also cause you problems.
Actually, Qmail works fine as an incoming MX for Hotmail.com.
mail.hotmail.com, one of Hotmail's incoming mx machines, runs Qmail.
On 25 Jan 2001, D. J. Bernstein wrote:
In fact, it's not a bug; it's a portability problem. If you were using
OpenBSD, you'd see outgoing connections to 0.0.0.0 rejected with EINVAL.
This OpenBSD idiosyncracy is almost exactly two years old [1], i.e.
OpenBSD 2.4 and earlier are affected
On Thu, 25 Jan 2001, Dan Peterson wrote:
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/netinet/tcp_usrreq.c
Revision 1.20; dated Feb 28 1998.
Hmm...hmm...right. Ok, I missed it. It did not occur to me 0.0.0.0 is a
broadcast address in Canada. :)
Anyway, qmail 1.00 was released on February
On Tue, 23 Jan 2001, Dave Sill wrote:
Here's a possible fix. In control/virtualdomains:
[0.0.0.0]:alias-devnull
And in ~alias/.qmail-devnull-default
#
Which should throw away all mail to MX's resolving to 0.0.0.0.
Are you sure that will work? The envelope details won't mention
Peter Samuel [EMAIL PROTECTED] wrote:
On Tue, 23 Jan 2001, Dave Sill wrote:
Here's a possible fix. In control/virtualdomains:
[0.0.0.0]:alias-devnull
And in ~alias/.qmail-devnull-default
#
Which should throw away all mail to MX's resolving to 0.0.0.0.
Are you sure that will
On Tue, 23 Jan 2001, Dave Sill wrote:
Here's a possible fix. In control/virtualdomains:
[0.0.0.0]:alias-devnull
And in ~alias/.qmail-devnull-default
#
Which should throw away all mail to MX's resolving to 0.0.0.0.
My tests show that that won't work:
echo
