Marc Dirix wrote: > I went back to 2.2.6-rc1 after was stated that 2.2.6 was not stable.
> As I am at 2.2.6-rc1? Are there multiple versions of 2.2.6-rc1? > > On my build server it shows: > > xi:/usr/src/dbmail# svn info > Path: . > URL: https://svn.ic-s.nl/svn/dbmail/branches/dbmail_2_2_branch > Repository Root: https://svn.ic-s.nl/svn/dbmail > Repository UUID: 7b491191-dbf0-0310-aff6-d879d4d69008 > Revision: 2758 That past 2.2.6-rc2, but just before the change that introduced the fatal regression in 2.2.6 final. So you're good there. > > >> So: >> >> - there shouldn't be any non utf8 data in the toaddr field [1] > > That should not matter, dbmail should recover from this. You misunderstand. If there is non utf8 8bit data in that field, postgres barfs. It just shouldn't happen, and the iconv code in dbmail was designed to prevent just that. Of course, email clients will use all kinds of 8bit data and utf7 encoded data in headers, and dbmail will have to deal with it gracefully. And it has for some time now. This is the first report of problems in that area since the cleanups between 2.2.5 and 2.2.6-rc2. >> - your sendmail should queue messages not inserted successfully [2] > > postfix I use on this server. whatever :-) > Oct 11 19:00:50 gamma postfix/lmtp[31544]: C5D5E7DC93: > to=<[EMAIL PROTECTED]>, relay=127.0.0.1[127.0.0.1]:24, > delay=7.6, delays=7.3/0.01/0/0.33, dsn=5.0.0, status=bounced (host > 127.0.0.1[127.0.0.1] said: 511 Recipient <[EMAIL PROTECTED]> > Permanent Failure Address Status Bad destination mailbox address (in > reply to end of DATA command)) Now what did the To header of that message look like I wonder. I'm not sure it should have been a temp failure. Could this have been a + extended address? > The message bounces, instead of temporarily reject. obviously. But that means dbmail didn't drop the message in a black hole. That /would/ have been a real embarrassment. >> - there is obviously also a parsing problem in the address parser here. >> what version of gmime are you using? > > /usr/lib/libgmime-2.0.so.2 /usr/lib/libgmime-2.0.so.2.2.10 That's very good. There have been some issues with gmime's decoding of utf7 headers (which I suspect was the case here), but 2.2.10 should be clean. I would really like to see the To header of that message. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
