Harald, Sounds valid - some RFC that defines this behavior would be nice though.
Fixing this like you propose is trivial. Currently dbmail uses g_mime_object_set_header(), but instead this could be changed to g_mime_object_prepend_header() We might even get aways with *always* prepend any header we add, but adding a separate call to do that explicitely seems like the safer choice. On 03-12-16 16:32, Reindl Harald wrote: > on our server running postfix "Return-Path" is always at bottom and > missing the <> but looking on servers running postfix+dovecot as well as > gmail it's always on top and looks like Return-Path: <a...@aon.at> > > Return-Path: users-return-114109-lists=rhsoft....@spamassassin.apache.org > Content-Type: text/plain > > that's ciritical in case of content-filters because the position of > received and other headers is the classification if it's trusted or not > and in case dbmail is the reason that would explain why it's so > difficult to pipe a message from the inbox to spamassassin and get the > same results as at recieve time > > again: > it is a MUST that every relay places it's headers ON TOP and if it also > adds a received-header any other headers are placed above > _______________________________________________ > DBmail mailing list > DBmail@dbmail.org > http://lists.nfg.nl/mailman/listinfo/dbmail > -- ________________________________________________________________ Paul J Stevens pjstevns @ gmail, twitter, github, linkedin _______________________________________________ DBmail mailing list DBmail@dbmail.org http://lists.nfg.nl/mailman/listinfo/dbmail
