-
ache committed patchset 371 of module WebMagick to the WebMagick CVS repository, changing 2 files.
2009-08-24 02:31:29 UTC in WebMagick
-
There is mistake in the v1.0.0 fix. According to RFC4406 "pra" and "mfrom" may come in _any_ order, while the code under !defined(_FFR_NH_MFROM) check the only _one_ of them, "pra" first (see below). The code under defined(_FFR_NH_MFROM) does it right, so just simple unifdef FFR_NH_MFROM at this place:
sid-filter.c:
case SM_SCOPE_PRA:
#ifdef _FFR_NH_MFROM.
2008-06-09 20:28:58 UTC in senderid-milter
-
Thanx, work now, l=19.
2007-08-21 07:17:12 UTC in dkim-milter
-
I have dkim-filter 2.1.1 sendmail 8.14.1
1) This is from maillog sending this 111...111 example message to anywhere (notice l=5 there):
Aug 20 19:43:58 my_machine sm-mta[42761]: l7KFhw4i042761: Milter insert (1): header: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=my.domain.com;\n\ts=default; t=1187624638; bh=+1Av5odmX0hN04f3DnsqksV26Z84m2kLiSxCfMr\n\tsuxQ=; l=5;...
2007-08-20 15:58:06 UTC in dkim-milter
-
Oh, I need to emphasize that l= incorrectly _generated_ by dkim-filter, not checked.
2007-08-20 07:39:08 UTC in dkim-milter
-
Because for this body must be 5(111)+2(empty)+5(111)+2(empty)+5(111), i.e. l=19 (or at least 15 if relaxed mode skips blank lines, I am not sure)
Imagine this body to make it clean:
---------- cut here -------------------
1
---------- cut here -------------------
Currently l=3 for it and whole 1Mb of message text just skipped.
(I use "BodyLengths y" in...
2007-08-20 07:32:07 UTC in dkim-milter
-
In relaxed/relaxed mode l=5 for this body:
---------- cut here -------------------
111
111
111
---------- cut here -------------------
I.e. it stops counting after first empty line found.
2007-08-19 22:03:47 UTC in dkim-milter
-
Specifying -L cause "illegal option" because "L" is not in CMDLINEOPTS.
2007-06-16 14:05:21 UTC in dkim-milter
-
Basically it needs to detect somehow that Sender (or From) becomes overwriten to produce something like this
header.Sender=Changed!
but the only way to detect is to store signer field somewhere in the DKIM tag and put into signature. I am not sure is at allowed by specs. If yes, there is another way possible: just put
header.Sender=saved_in_the_signature_sender.
2007-05-02 01:29:00 UTC in dkim-milter
-
> it seems it counts one additional char per line
I suspect it is due to CR/LF, not just LF.
2007-04-27 14:36:55 UTC in dkim-milter
