On Mon, 21 Jul 2008, Mike Markley wrote:
Could you clarify one thing for me? I'm not sure from your message if
this issue is causing the filter to stop being able to verify OTHER
messages, or if it's just for messages from this domain.
Unfortunately, it depends... If it was direct-to-mx, then it'd only
affect that one domain.
In this case, however, vger.kernel.org seemed to stop futher delivery
upon receipt of the 4xx code. I saw several of these, and no mails,
and eventually, luckily, on a later queue run, these messages were tried
after others - resulting in eventually catching up - but causing
blockage on vger's side
The latter is
easily explained, as the key listed in DNS does seem to be truncated;
Indeed, that I think is to be expected
the former is definitely an important bug.
Yes, and I'm leaning heavily in that direction - depending upon the
vagaries of MTA queueing/coattailing/pipelining is problematic at best.
This could windup being a DDOS against MTAs (both receiving and sending)
And just for my personal edificiation: What the heck is this +b1
version? :)
Hrm, had me stumped for a moment, but this is it:
dk-milter (1.0.0.dfsg-1+b1) unstable; urgency=low
* Binary-only non-maintainer upload for amd64; no source changes.
* rebuild with libmilter1.0.0
-- Debian amd64 Build Daemon <buildd_i386-excelsior> Mon, 12 May 2008 01:40:41
Probably caught in the mess I caused by changing the libmilter
versioning - painful then, but hopefully less so in the future
--
Rick Nelson
<taniwha> Knghtbrd: we should do a quake episode :knee deep in the code":
you run around shooting at bugs:)
<Knghtbrd> taniwha: I'll pass the idea on to OpenQuartz ;>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
