My Point was not the part about not being able to decode, but the part where dbmail (or gmime) adds an @host.domain after the non-decodable address. This confuses things.
-- Groet, Marc Dirix On Thu, May 07, 2009 at 10:44:42PM +0200, Paul J Stevens wrote: > John Fawcett wrote: > > It's likely a bug of the sending client (probably a webmail service). > > Shouldn't the from header contain only ascii encoding? > > That's not the point. Even if you are correct (I would assume rfc2047 > would apply to From_ headers as well), we'd like dbmail to gracefully > degrade. > > > John > > > > Aaron Stone wrote: > >> I've noticed this, too. It's not an added header, it's a mis-decoded > >> header. I suspect a GMime bug; perhaps Paul has identified which versions > >> of GMime are buggy in this way? > > Stay current on gmime-2.2. That is the only version I really test. Gmime > is a fast moving target! 2.4 is api/abi incompatible, and 2.6 (already > being worked on) will break that again. Jeff has done some fixes in this > area, and dbmail has it's own share of work-around faulty encodings on > top of that. Running the unit-tests (./configure --with-check; make > check) might help in exposing the trouble spots. > > > > -- > ________________________________________________________________ > Paul Stevens paul at nfg.nl > NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 > The Netherlands________________________________http://www.nfg.nl > _______________________________________________ > DBmail mailing list > [email protected] > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
