From: Hirohisa Y. <um...@gm...> - 2008-12-07 17:20:27
|
Hi, With 2.8.0.Beta3, I got many errors: dkim.h:1543: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'dkim_get_arlib' including dkim-types.h before dkim.h is needed. -- end Hirohisa Yamaguchi um...@gm... |
From: Murray S. K. <ms...@se...> - 2008-12-07 20:49:21
|
On Mon, 8 Dec 2008, Hirohisa Yamaguchi wrote: > With 2.8.0.Beta3, I got many errors: > dkim.h:1543: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'dkim_get_arlib' > > including dkim-types.h before dkim.h is needed. I just yanked dkim_get_arlib() out of both dkim.c and dkim.h. The thing for which I needed it isn't happening anymore. |
From: System S. <su...@mi...> - 2008-12-07 22:53:18
|
I have started seeing the following error after the last upgrade: Nov 26 18:32:32 Falcon postfix/smtpd[30645]: EC214454AC: client=mailo[127.0.1.10] Nov 26 18:32:32 Falcon postfix/cleanup[30649]: EC214454AC: message- id=<492...@dh...> Nov 26 18:32:32 Falcon dkim-filter[2199]: EC214454AC: can't parse From: header Nov 26 18:32:32 Falcon postfix/qmgr[2611]: EC214454AC: from=<postmaster@MicroTechniques.com>, size=1407, nrcpt=1 (queue active) The one of interest is from dkim-filter -- 'Can't parse From: header' I have not made any other postfix or mail system changes. ...don dhughes (at) microtechniques.com White Plains, NY |
From: Murray S. K. <ms...@se...> - 2008-12-08 03:18:48
|
On Sun, 7 Dec 2008, System Support wrote: > Nov 26 18:32:32 Falcon dkim-filter[2199]: EC214454AC: can't parse > From: header There haven't been any changes to header parsing code, so I can't think of why this would start happening as a result of the upgrade. Try the attached patch; it does two things: 1) Reports which header is actually being selected rather than always reporting "From:" 2) Gives you the value it wasn't able to parse for a user and domain This will appear in the next beta. |
From: Murray S. K. <ms...@se...> - 2008-12-08 22:31:08
Attachments:
PATCH
|
On Mon, 8 Dec 2008, System Support wrote: >> Try the attached patch; it does two things: > > There was nothing attached. Is this the Dec 7th beta? No, it wasn't in that beta. Sorry for skipping the attachment; it's on this one. |
From: Chris B. <cbe...@co...> - 2008-12-08 23:00:15
|
On Mon, Dec 08, 2008 at 02:30:53PM -0800, Murray S. Kucherawy wrote: > - syslog(LOG_INFO, "%s: can't parse From: header", > - dfc->mctx_jobid); > + syslog(LOG_INFO, > + "%s: can't parse %s: header value `%s'", > + from->hdr_hdr, from->hdr_val, dfc->mctx_jobid); Looks like that last line should really be: dfc->mctx_jobid, from->hdr_hdr, from->hdr_val); - Chris |
From: Murray S. K. <ms...@se...> - 2008-12-08 23:05:15
Attachments:
PATCH
|
On Mon, 8 Dec 2008, Chris Behrens wrote: > Looks like that last line should really be: Ah right. Here's the corrected patch. |
From: System S. <su...@mi...> - 2008-12-08 22:28:22
|
On 7 Dec 2008 at 19:18, Murray S. Kucherawy wrote: > On Sun, 7 Dec 2008, System Support wrote: > > Nov 26 18:32:32 Falcon dkim-filter[2199]: EC214454AC: can't parse > > From: header > > There haven't been any changes to header parsing code, so I can't > think of why this would start happening as a result of the upgrade. > > Try the attached patch; it does two things: Murry, There was nothing attached. Is this the Dec 7th beta? ...don dhughes (at) microtechniques.com White Plains, NY |
From: System S. <su...@mi...> - 2008-12-10 14:45:36
|
On 7 Dec 2008 at 19:18, Murray S. Kucherawy wrote: > On Sun, 7 Dec 2008, System Support wrote: > > Nov 26 18:32:32 Falcon dkim-filter[2199]: EC214454AC: can't parse > > From: header > > There haven't been any changes to header parsing code, so I can't > think of why this would start happening as a result of the upgrade. > > Try the attached patch; it does two things: > > 1) Reports which header is actually being selected rather than always > reporting "From:" > > 2) Gives you the value it wasn't able to parse for a user and domain The error stopped altogether (in any format) after going from Beta2 to Beta4 and applying the patch. ...don dhughes (at) microtechniques.com White Plains, NY |
From: Murray S. K. <ms...@se...> - 2008-12-10 15:32:12
|
On Wed, 10 Dec 2008, System Support wrote: > The error stopped altogether (in any format) after going from Beta2 to > Beta4 and applying the patch. Well, you've got me on that one. I just reviewed the diffs between Beta2 and Beta4, and there's no code change involving header parsing at all. |
From: System S. <su...@mi...> - 2008-12-11 17:11:21
|
On 10 Dec 2008 at 7:32, Murray S. Kucherawy wrote: > On Wed, 10 Dec 2008, System Support wrote: > > The error stopped altogether (in any format) after going from Beta2 > > to Beta4 and applying the patch. > > Well, you've got me on that one. I just reviewed the diffs between > Beta2 and Beta4, and there's no code change involving header parsing > at all. Unless this happens again, let's write this off as some sort of installation problem on my part. ...don dhughes (at) microtechniques.com White Plains, NY |