Marc
I'm not convinced that it is dbmail or gmime adding a host part. Do you
have an
example of the full message headers?
John
Yes, I'm however pretty sure postfix does not change the from address. I
have furthermore spamassassin and clamavsmtp
running. But online the ones with a
Marc,
dbmail doesn't do this, afaict. The only set_header call we do during
normal delivery is for 'Return-Path'. What do the postfix logs tell you?
Marc Dirix wrote:
Marc
I'm not convinced that it is dbmail or gmime adding a host part. Do you
have an
example of the full message headers?
dbmail doesn't do this, afaict. The only set_header call we do during
normal delivery is for 'Return-Path'. What do the postfix logs tell you?
Nothing intelligible, the rcpt-to address (in the message envelope) is
correct.
I can't find an option for postfix where it enables / disables it
Marc Dirix wrote:
dbmail doesn't do this, afaict. The only set_header call we do during
normal delivery is for 'Return-Path'. What do the postfix logs tell you?
Nothing intelligible, the rcpt-to address (in the message envelope) is
correct.
I can't find an option for postfix where it
Oops. The README clearly states:
Rewrite user to u...@$myorigin
This feature is controlled by the boolean append_at_myorigin
parameter (default: yes). You should never turn off this feature,
because a lot of Postfix components expect that all addresses have the
form u...@domain.
Marc Dirix wrote:
Oops. The README clearly states:
Rewrite user to u...@$myorigin
This feature is controlled by the boolean append_at_myorigin
parameter (default: yes). You should never turn off this feature,
because a lot of Postfix components expect that all addresses have the
form
Marc Dirix wrote:
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.
Marc
I'm not convinced that it is dbmail or gmime adding a host part. Do you
have an
example of the
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
It's likely a bug of the sending client (probably a webmail service).
Shouldn't the from header contain only ascii encoding?
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
This is done because the us-ascii character set does not include support for
accented characters (José). This string also utilized quoted printable. I
would think that the decoding of this string should be handled not by the
server, but rather by the client. If this is something that DBMail
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.
Hi
I'm on 2.2.11.
Often some customers receive emails with incorrect (or strangely
encoded) From headers. This From header then gets mangled
at some point between reception and delivery.
The newly formed From header has been mangled, and
@host.domain of the mailserver has been added.
See here
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?
Aaron
On Wed, 6 May 2009 15:19:41 +0200, Marc Dirix m...@electronics-design.nl
wrote:
Hi
I'm on 2.2.11.
Often
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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?
Me too, but in a different way: Not the address but
2009 15:17
To: DBMail mailinglist
Subject: Re: [Dbmail] mysterious from-address
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
Although I could live with mis-encoding.
The addition of @host.domain is somewhat
annoying as it makes outlook think the email address is valid,
and does not complain to the user.
Marc
___
DBmail mailing list
DBmail@dbmail.org
16 matches
Mail list logo
