michael.scheidell at secnap
Aug 29, 2011, 10:56 AM
Post #3 of 7
(293 views)
Permalink
|
On 8/29/11 12:46 PM, Andy Jezierski wrote:
>
> Looks like it's up. I've only received one post on the 27th and this
> post. Last post on the 26th was about 4:30CDT.
>
> Andy
just figured it out.
its that qmail bug.
the 10 year old one where if an mx is down for maint, qmail won't try
other mx records.
(sorta)
if the FIRST TIME qmail sends an email, it hits mx1, it seems to 'stick'
there, and will NEVER try mx2,3, or 4.
we run into this all the time.
is it a bug? depending on who you ask.
if it prevents sending email to RFC compliant mail servers, than I think
its a bug.
if it violates RFC's so badly, that it prevents sending email to RFC
compliant mail servers, than I think its a bug.
<http://www.mail-archive.com/qmail [at] id/msg45399.html>
there are 'UNOFFICIAL' patches out there to help qmail conform to RFC's
in this area, but 10 years and counting, its never made it into the
official build.
causes a lot of anger, back and forth when this patch is discussed.
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
>*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
|
