From: Arkadi P. <ar...@in...> - 2006-05-31 20:04:12
|
Does anybody know what the following error means? Milter (dk-filter): timeout before data read Milter (dk-filter): to error state It started after some time and since it's started, it happens on every incoming message. dkim-milter-0.5.0 seems to work ok. I just installed the latest version of dk-milter 0.4.0. I run it with = the latest version of sendmail 8.13.16. I invoke it with the following parameters: /usr/bin/dk-filter -l -p inet:8891@localhost -d invidi.com -I \ /etc/mail/dk-internal-hosts -h -H -C bad=3Dt,miss=3Dt -s \ /var/db/domainkeys/smtp.private -S smtp -u dk -m MSA sendmail.mc has this timeouts: INPUT_MAIL_FILTER(`dk-filter', `S=3Dinet:8891@localhost, = T=3DS:15s;R:15s') Arkadi. - - - - - - - Appended by Invidi Technologies Corporation. - - - - - - - DISCLAIMER:=20 This email message is for the sole use of the intended recipients and = may contain confidential and privileged information. Any unauthorized = review, use, disclosure or distribution is prohibited. |
From: Arkadi P. <ar...@in...> - 2006-05-31 20:42:05
|
To troubleshoot the problem, I started sendmail with LogLevel=3D15 So dk-filter times out exactly after 15 sec as was set in sendmail.mc = file after successful header call: May 31 16:23:50 smtp sm-mta[19213]: k4VKNl0j019213: milter=3Ddk-filter, action=3Dheader, continue May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: Milter (dk-filter): timeout before data read May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: Milter (dk-filter): = to error state May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: = milter=3Ddkim-filter, action=3Dheader, continue May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: = milter=3Ddkim-filter, action=3Deoh, continue I assume that it's timing out in eof call but why? Arkadi. ------ Forwarded Message From: Arkadi Poliakevitch <ar...@in...> Date: Wed, 31 May 2006 14:04:22 -0600 To: <dk-...@li...> Conversation: Milter (dk-filter): timeout before data read Subject: Milter (dk-filter): timeout before data read Does anybody know what the following error means? Milter (dk-filter): timeout before data read Milter (dk-filter): to error state It started after some time and since it's started, it happens on every incoming message. dkim-milter-0.5.0 seems to work ok. I just installed the latest version of dk-milter 0.4.0. I run it with = the latest version of sendmail 8.13.16. I invoke it with the following parameters: /usr/bin/dk-filter -l -p inet:8891@localhost -d invidi.com -I \ /etc/mail/dk-internal-hosts -h -H -C bad=3Dt,miss=3Dt -s \ /var/db/domainkeys/smtp.private -S smtp -u dk -m MSA sendmail.mc has this timeouts: INPUT_MAIL_FILTER(`dk-filter', `S=3Dinet:8891@localhost, = T=3DS:15s;R:15s') Arkadi. ------ End of Forwarded Message - - - - - - - Appended by Invidi Technologies Corporation. - - - - - - - DISCLAIMER:=20 This email message is for the sole use of the intended recipients and = may contain confidential and privileged information. Any unauthorized = review, use, disclosure or distribution is prohibited. |
From: Murray S. K. <ms...@se...> - 2006-06-01 17:59:38
|
Arkadi Poliakevitch wrote: > To troubleshoot the problem, I started sendmail with LogLevel=15 > > So dk-filter times out exactly after 15 sec as was set in sendmail.mc file > after successful header call: > > May 31 16:23:50 smtp sm-mta[19213]: k4VKNl0j019213: milter=dk-filter, > action=header, continue > May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: Milter (dk-filter): > timeout before data read > May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: Milter (dk-filter): to > error state > May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: milter=dkim-filter, > action=header, continue > May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: milter=dkim-filter, > action=eoh, continue > > I assume that it's timing out in eof call but why? I don't think it was in the "eof" callback. Note your dkim-filter entries; there's an "eoh" entry, which dk-filter never reported. "eoh" comes before "eof" for both filters. In the "eoh" callback, libdk tries to get both the key and the policy record. Those are two places where DNS timeouts could exceed whatever period of time the MTA is willing to wait for an answer. sid-milter and dkim-milter have a feature to deal with this problem that works when using libar, but it won't work when using the system's resolver. The feature sends periodic "I'm still working on it" messages back to the MTA to keep it happy and prevent timeouts. Are you using your system's resolver or libar? |
From: Arkadi P. <ar...@in...> - 2006-06-01 18:09:20
|
Sorry for typo, I meant eoh, not eof. And yes I compiled with ar and = default timeout for ar is 5 sec I think. I set sendmail timeouts to 15. Shall I try to increase dk-filter timeout with -T option? It's strange = that dkim-filter works. Arkadi. On 6/1/06 11:59 AM, "Murray S. Kucherawy" <ms...@se...> wrote: > Arkadi Poliakevitch wrote: >> To troubleshoot the problem, I started sendmail with LogLevel=3D15 >>=20 >> So dk-filter times out exactly after 15 sec as was set in sendmail.mc = file >> after successful header call: >>=20 >> May 31 16:23:50 smtp sm-mta[19213]: k4VKNl0j019213: = milter=3Ddk-filter, >> action=3Dheader, continue >> May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: Milter = (dk-filter): >> timeout before data read >> May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: Milter = (dk-filter): to >> error state >> May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: = milter=3Ddkim-filter, >> action=3Dheader, continue >> May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: = milter=3Ddkim-filter, >> action=3Deoh, continue >>=20 >> I assume that it's timing out in eof call but why? >=20 > I don't think it was in the "eof" callback. Note your dkim-filter = entries; > there's an "eoh" entry, which dk-filter never reported. "eoh" comes = before > "eof" for both filters. >=20 > In the "eoh" callback, libdk tries to get both the key and the policy = record. > Those are two places where DNS timeouts could exceed whatever period = of time > the=20 > MTA is willing to wait for an answer. >=20 > sid-milter and dkim-milter have a feature to deal with this problem = that works > when using libar, but it won't work when using the system's resolver. = The > feature sends periodic "I'm still working on it" messages back to the = MTA to > keep it happy and prevent timeouts. >=20 > Are you using your system's resolver or libar? >=20 >=20 > _______________________________________________ > dk-milter-discuss mailing list > dk-...@li... > https://lists.sourceforge.net/lists/listinfo/dk-milter-discuss - - - - - - - Appended by Invidi Technologies Corporation. - - - - - - - DISCLAIMER:=20 This email message is for the sole use of the intended recipients and = may contain confidential and privileged information. Any unauthorized = review, use, disclosure or distribution is prohibited. |
From: Arkadi P. <ar...@in...> - 2006-06-01 18:16:33
|
Another interesting observation is when I set DKDEBUG=3Drtd, and = restarted dk-filter, it has never failed since then. It stopped reporting no signature data=20 errors in maillog but reports bad signature errors. Arkadi. ------ Forwarded Message From: Arkadi Poliakevitch <ar...@in...> Date: Thu, 01 Jun 2006 12:09:47 -0600 To: General discussion and usage issues <dk-...@li...> Conversation: Milter (dk-filter): timeout before data read Subject: Re: Milter (dk-filter): timeout before data read Sorry for typo, I meant eoh, not eof. And yes I compiled with ar and = default timeout for ar is 5 sec I think. I set sendmail timeouts to 15. Shall I try to increase dk-filter timeout with -T option? It's strange = that dkim-filter works. Arkadi. On 6/1/06 11:59 AM, "Murray S. Kucherawy" <ms...@se...> wrote: > Arkadi Poliakevitch wrote: >> To troubleshoot the problem, I started sendmail with LogLevel=3D15 >>=20 >> So dk-filter times out exactly after 15 sec as was set in sendmail.mc = file >> after successful header call: >>=20 >> May 31 16:23:50 smtp sm-mta[19213]: k4VKNl0j019213: = milter=3Ddk-filter, >> action=3Dheader, continue >> May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: Milter = (dk-filter): >> timeout before data read >> May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: Milter = (dk-filter): to >> error state >> May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: = milter=3Ddkim-filter, >> action=3Dheader, continue >> May 31 16:24:05 smtp sm-mta[19213]: k4VKNl0j019213: = milter=3Ddkim-filter, >> action=3Deoh, continue >>=20 >> I assume that it's timing out in eof call but why? >=20 > I don't think it was in the "eof" callback. Note your dkim-filter = entries; > there's an "eoh" entry, which dk-filter never reported. "eoh" comes = before > "eof" for both filters. >=20 > In the "eoh" callback, libdk tries to get both the key and the policy = record. > Those are two places where DNS timeouts could exceed whatever period = of time > the=20 > MTA is willing to wait for an answer. >=20 > sid-milter and dkim-milter have a feature to deal with this problem = that works > when using libar, but it won't work when using the system's resolver. = The > feature sends periodic "I'm still working on it" messages back to the = MTA to > keep it happy and prevent timeouts. >=20 > Are you using your system's resolver or libar? >=20 >=20 > _______________________________________________ > dk-milter-discuss mailing list > dk-...@li... > https://lists.sourceforge.net/lists/listinfo/dk-milter-discuss ------ End of Forwarded Message - - - - - - - Appended by Invidi Technologies Corporation. - - - - - - - DISCLAIMER:=20 This email message is for the sole use of the intended recipients and = may contain confidential and privileged information. Any unauthorized = review, use, disclosure or distribution is prohibited. |
From: Murray S. K. <ms...@se...> - 2006-06-01 18:27:55
|
Arkadi Poliakevitch wrote: > Another interesting observation is when I set DKDEBUG=rtd, and restarted > dk-filter, it has never failed since then. It stopped reporting > > no signature data > > errors in maillog but reports > > bad signature > > errors. All of the DKDEBUG options you listed only do additional logging about threads or about libar. They don't otherwise change program logic at all. "no signature data" would be logged less often if DKDEBUG used to contain "s" but was replaced by "rtd". |
From: Arkadi P. <ar...@in...> - 2006-06-01 18:33:14
|
On 6/1/06 12:27 PM, "Murray S. Kucherawy" <ms...@se...> wrote: > Arkadi Poliakevitch wrote: >> Another interesting observation is when I set DKDEBUG=3Drtd, and = restarted >> dk-filter, it has never failed since then. It stopped reporting >>=20 >> no signature data >>=20 >> errors in maillog but reports >>=20 >> bad signature >>=20 >> errors. >=20 > All of the DKDEBUG options you listed only do additional logging about = threads > or about libar. They don't otherwise change program logic at all. That's why I'm saying it's strange, I used to get the same messages from both dk-filter and dkim-filter on the same message: no signature data but after debugging was enabled, I still see "no signature data" = reported by dkim-filter but not by dk-filter. >=20 > "no signature data" would be logged less often if DKDEBUG used to = contain "s" > but was replaced by "rtd". >=20 >=20 > _______________________________________________ > dk-milter-discuss mailing list > dk-...@li... > https://lists.sourceforge.net/lists/listinfo/dk-milter-discuss - - - - - - - Appended by Invidi Technologies Corporation. - - - - - - - DISCLAIMER:=20 This email message is for the sole use of the intended recipients and = may contain confidential and privileged information. Any unauthorized = review, use, disclosure or distribution is prohibited. |
From: Murray S. K. <ms...@se...> - 2006-06-01 18:17:11
|
Arkadi Poliakevitch wrote: > Sorry for typo, I meant eoh, not eof. And yes I compiled with ar and default > timeout for ar is 5 sec I think. I set sendmail timeouts to 15. > > Shall I try to increase dk-filter timeout with -T option? It's strange that > dkim-filter works. Can you tell from the logs what the sending domain was for the message(s) that timed out? Maybe we can spot a DNS problem that would explain the timeouts. For example, if there's a chain of CNAMEs we have to follow behind very slow links, we could easily exceed 15 seconds. Are you compiling dkim-filter with any features enabled? It's one that has the optional "keepalive" code which could be keeping the MTA happy. |
From: Arkadi P. <ar...@in...> - 2006-06-01 18:28:34
|
On 6/1/06 12:17 PM, "Murray S. Kucherawy" <ms...@se...> wrote: > Arkadi Poliakevitch wrote: >> Sorry for typo, I meant eoh, not eof. And yes I compiled with ar and = default >> timeout for ar is 5 sec I think. I set sendmail timeouts to 15. >>=20 >> Shall I try to increase dk-filter timeout with -T option? It's = strange that >> dkim-filter works. >=20 > Can you tell from the logs what the sending domain was for the = message(s) that > timed out? Maybe we can spot a DNS problem that would explain the = timeouts. I doubt this because since once it started to fail, it was failing on = every message, here is sample of domains while dkim-filter was working fine on = the same messages: News.palmnewsletters.com agcsystems.com att.net audio.b21pubs.com b.e.ccialerts.com bounce.uptilt.com bounces.amazon.com dvtel.com lgcnsglobal.com lists.lyx.org lists.scte.org mail2.mediapost.com managementweb.org mx3.atomicpark.com nyc.rr.com plainsboronj.com powermailzz.com prodigy.net redhat.com sciatl.com securityfocus.com susbauer.de verizonnews.policy.net >=20 > For example, if there's a chain of CNAMEs we have to follow behind = very slow > links, we could easily exceed 15 seconds. >=20 > Are you compiling dkim-filter with any features enabled? It's one = that has > the=20 > optional "keepalive" code which could be keeping the MTA happy. No optional features. >=20 >=20 > _______________________________________________ > dk-milter-discuss mailing list > dk-...@li... > https://lists.sourceforge.net/lists/listinfo/dk-milter-discuss - - - - - - - Appended by Invidi Technologies Corporation. - - - - - - - DISCLAIMER:=20 This email message is for the sole use of the intended recipients and = may contain confidential and privileged information. Any unauthorized = review, use, disclosure or distribution is prohibited. |
From: Murray S. K. <ms...@se...> - 2006-06-01 18:43:05
|
Arkadi Poliakevitch wrote: > I doubt this because since once it started to fail, it was failing on every > message, here is sample of domains while dkim-filter was working fine on the > same messages: It sounds like libar could be deadlocked or otherwise stuck or spinning. If you restart dk-filter, does the problem go away? Do you notice the process spinning (which was reported by someone else for dk-filter only)? |
From: Arkadi P. <ar...@in...> - 2006-06-01 18:59:48
|
On 6/1/06 12:42 PM, "Murray S. Kucherawy" <ms...@se...> wrote: > Arkadi Poliakevitch wrote: >> I doubt this because since once it started to fail, it was failing on = every >> message, here is sample of domains while dkim-filter was working fine = on the >> same messages: >=20 > It sounds like libar could be deadlocked or otherwise stuck or = spinning. If > you=20 > restart dk-filter, does the problem go away? It's a live system, I'm trying to avoid too many experiments. One time = after I restarted it, it worked for I think a few sec, then start failing = again but I restarted it in with DKDEBUG set and it's working since yesterday without error messages but also without "no signature data" messages at = all. I used to have my maillog that looks like that: May 29 14:25:41 smtp dk-filter[10217]: k4TIOwQl021836: no signature data May 29 14:25:41 smtp dkim-filter[31531]: k4TIOwQl021836: no signature = data May 29 15:17:32 smtp dk-filter[10217]: k4TJGIkW006448: no signature data May 29 15:17:32 smtp dkim-filter[31531]: k4TJGIkW006448: no signature = data May 29 16:02:10 smtp dk-filter[10217]: k4TK1JbK011136: no signature data May 29 16:02:10 smtp dkim-filter[31531]: k4TK1JbK011136: no signature = data May 29 16:09:56 smtp dk-filter[10217]: k4TK97Xu029101: no signature data May 29 16:09:57 smtp dkim-filter[31531]: k4TK97Xu029101: no signature = data May 29 16:43:50 smtp dk-filter[10217]: k4TKh0UZ003092: no signature data May 29 16:43:50 smtp dkim-filter[31531]: k4TKh0UZ003092: no signature = data May 29 16:46:44 smtp dk-filter[10217]: k4TKjgUU030159: no signature data May 29 16:46:44 smtp dkim-filter[31531]: k4TKjgUU030159: no signature = data May 29 17:22:02 smtp dk-filter[10217]: k4TLL9PT016144: no signature data May 29 17:22:02 smtp dkim-filter[31531]: k4TLL9PT016144: no signature = data May 29 17:30:33 smtp dk-filter[10217]: k4TLTNPO016625: no signature data May 29 17:30:34 smtp dkim-filter[31531]: k4TLTNPO016625: no signature = data May 29 17:41:22 smtp dk-filter[10217]: k4TLeWSI024533: no signature data May 29 17:41:22 smtp dkim-filter[31531]: k4TLeWSI024533: no signature = data May 29 18:01:51 smtp dk-filter[10217]: k4TM0dHQ000408: no signature data May 29 18:01:52 smtp dkim-filter[31531]: k4TM0dHQ000408: no signature = data May 29 18:08:44 smtp dk-filter[10217]: k4TM7uGl010544: no signature data May 29 18:08:44 smtp dkim-filter[31531]: k4TM7uGl010544: no signature = data May 29 18:11:51 smtp dk-filter[10217]: k4TMB5Os007312: no signature data May 29 18:11:51 smtp dkim-filter[31531]: k4TMB5Os007312: no signature = data May 29 18:26:55 smtp dk-filter[10217]: k4TMQEHN013600: no signature data May 29 18:26:56 smtp dkim-filter[31531]: k4TMQEHN013600: no signature = data May 29 18:47:27 smtp dk-filter[10217]: k4TMkfvI020356: no signature data May 29 18:47:27 smtp dkim-filter[31531]: k4TMkfvI020356: no signature = data No it looks like this: May 31 13:05:07 smtp dkim-filter[1694]: k4VH4oQ8031256: no signature = data May 31 13:11:14 smtp dkim-filter[1694]: k4VHAvvC002829: no signature = data May 31 14:39:49 smtp dkim-filter[1694]: k4VIdXp7009340: no signature = data May 31 14:39:55 smtp dkim-filter[1694]: k4VIdYdS023821: no signature = data May 31 14:40:54 smtp dkim-filter[1694]: k4VIeZqL030566: no signature = data May 31 14:42:17 smtp dkim-filter[1694]: k4VIg01X027534: no signature = data ... May 31 15:02:59 smtp dkim-filter[1694]: k4VJ2gbT015943: no signature = data That makes me worried that it actually works at all. :-) Arkadi. > Do you notice the process > spinning=20 > (which was reported by someone else for dk-filter only)? >=20 No. >=20 > _______________________________________________ > dk-milter-discuss mailing list > dk-...@li... > https://lists.sourceforge.net/lists/listinfo/dk-milter-discuss - - - - - - - Appended by Invidi Technologies Corporation. - - - - - - - DISCLAIMER:=20 This email message is for the sole use of the intended recipients and = may contain confidential and privileged information. Any unauthorized = review, use, disclosure or distribution is prohibited. |
From: Arkadi P. <ar...@in...> - 2006-06-01 22:26:31
|
One more thing I noticed is that memory consumption for dk-filter-0.4.0 seems a bit high compared to dkim-filter-0.5.0: >top 23396 dk 2 0 19M 13M sleep poll 0:04 0.00% = dk-filter 1694 dkim 2 0 1376K 1740K sleep poll 0:03 0.00% = dkim-filter I also run dk-filter-0.3.2 and dkim-filter-0.2.2 on another box for much longer period with 168 dk 2 0 1004K 1648K sleep poll 4:42 0.00% = dk-filter 23124 dkim 2 0 1092K 1708K sleep poll 4:50 0.00% dkim-filter If there a way to see if there is a memory leak somewhere in dk-filter -0.4.0? Thanks. Arkadi. ------ Forwarded Message From: Arkadi Poliakevitch <ar...@in...> Reply-To: General discussion and usage issues <dk-...@li...> Date: Thu, 01 Jun 2006 13:00:19 -0600 To: General discussion and usage issues <dk-...@li...> Conversation: Milter (dk-filter): timeout before data read Subject: Re: Milter (dk-filter): timeout before data read On 6/1/06 12:42 PM, "Murray S. Kucherawy" <ms...@se...> wrote: > Arkadi Poliakevitch wrote: >> I doubt this because since once it started to fail, it was failing on = every >> message, here is sample of domains while dkim-filter was working fine = on the >> same messages: >=20 > It sounds like libar could be deadlocked or otherwise stuck or = spinning. If > you=20 > restart dk-filter, does the problem go away? It's a live system, I'm trying to avoid too many experiments. One time = after I restarted it, it worked for I think a few sec, then start failing = again but I restarted it in with DKDEBUG set and it's working since yesterday without error messages but also without "no signature data" messages at = all. I used to have my maillog that looks like that: May 29 14:25:41 smtp dk-filter[10217]: k4TIOwQl021836: no signature data May 29 14:25:41 smtp dkim-filter[31531]: k4TIOwQl021836: no signature = data May 29 15:17:32 smtp dk-filter[10217]: k4TJGIkW006448: no signature data May 29 15:17:32 smtp dkim-filter[31531]: k4TJGIkW006448: no signature = data May 29 16:02:10 smtp dk-filter[10217]: k4TK1JbK011136: no signature data May 29 16:02:10 smtp dkim-filter[31531]: k4TK1JbK011136: no signature = data May 29 16:09:56 smtp dk-filter[10217]: k4TK97Xu029101: no signature data May 29 16:09:57 smtp dkim-filter[31531]: k4TK97Xu029101: no signature = data May 29 16:43:50 smtp dk-filter[10217]: k4TKh0UZ003092: no signature data May 29 16:43:50 smtp dkim-filter[31531]: k4TKh0UZ003092: no signature = data May 29 16:46:44 smtp dk-filter[10217]: k4TKjgUU030159: no signature data May 29 16:46:44 smtp dkim-filter[31531]: k4TKjgUU030159: no signature = data May 29 17:22:02 smtp dk-filter[10217]: k4TLL9PT016144: no signature data May 29 17:22:02 smtp dkim-filter[31531]: k4TLL9PT016144: no signature = data May 29 17:30:33 smtp dk-filter[10217]: k4TLTNPO016625: no signature data May 29 17:30:34 smtp dkim-filter[31531]: k4TLTNPO016625: no signature = data May 29 17:41:22 smtp dk-filter[10217]: k4TLeWSI024533: no signature data May 29 17:41:22 smtp dkim-filter[31531]: k4TLeWSI024533: no signature = data May 29 18:01:51 smtp dk-filter[10217]: k4TM0dHQ000408: no signature data May 29 18:01:52 smtp dkim-filter[31531]: k4TM0dHQ000408: no signature = data May 29 18:08:44 smtp dk-filter[10217]: k4TM7uGl010544: no signature data May 29 18:08:44 smtp dkim-filter[31531]: k4TM7uGl010544: no signature = data May 29 18:11:51 smtp dk-filter[10217]: k4TMB5Os007312: no signature data May 29 18:11:51 smtp dkim-filter[31531]: k4TMB5Os007312: no signature = data May 29 18:26:55 smtp dk-filter[10217]: k4TMQEHN013600: no signature data May 29 18:26:56 smtp dkim-filter[31531]: k4TMQEHN013600: no signature = data May 29 18:47:27 smtp dk-filter[10217]: k4TMkfvI020356: no signature data May 29 18:47:27 smtp dkim-filter[31531]: k4TMkfvI020356: no signature = data No it looks like this: May 31 13:05:07 smtp dkim-filter[1694]: k4VH4oQ8031256: no signature = data May 31 13:11:14 smtp dkim-filter[1694]: k4VHAvvC002829: no signature = data May 31 14:39:49 smtp dkim-filter[1694]: k4VIdXp7009340: no signature = data May 31 14:39:55 smtp dkim-filter[1694]: k4VIdYdS023821: no signature = data May 31 14:40:54 smtp dkim-filter[1694]: k4VIeZqL030566: no signature = data May 31 14:42:17 smtp dkim-filter[1694]: k4VIg01X027534: no signature = data ... May 31 15:02:59 smtp dkim-filter[1694]: k4VJ2gbT015943: no signature = data That makes me worried that it actually works at all. :-) Arkadi. > Do you notice the process > spinning=20 > (which was reported by someone else for dk-filter only)? >=20 No. >=20 > _______________________________________________ > dk-milter-discuss mailing list > dk-...@li... > https://lists.sourceforge.net/lists/listinfo/dk-milter-discuss - - - - - - - Appended by Invidi Technologies Corporation. - - - - - - - DISCLAIMER:=20 This email message is for the sole use of the intended recipients and = may contain confidential and privileged information. Any unauthorized = review, use, disclosure or distribution is prohibited. _______________________________________________ dk-milter-discuss mailing list dk-...@li... https://lists.sourceforge.net/lists/listinfo/dk-milter-discuss ------ End of Forwarded Message |