Odomus, thank you for your answer.
I know the magic behind Reply Address Masking. I have tested deeply and I think I have found where the problem is.
If the account that sends the email message has a FROM that includes real name with accents (or non-ASCII Characters), Spamgourmet Server change the FROM field address to a string similar to this
From: "=?iso-8859-1?Q?Real Name with accents Fern=E1ndez?=
- busybodyemail@domain.com" <test.mysgusername.6913e966e5.busybodyemail#domain.com@ob.0sg.net>
<busybodyemail@domain.com> If the original FROM is pure ASCII the FROM field after going through Spamgourmet is similar to this
From: "Real Name without accents - busybodyemail@domain.com"
<test.mysgusername.6913e966e5.busybodyemail#domain.com@ob.0sg.net>In the first case, if you are using GMail (Web or Android tested), the message is sent to
busybodyemail@domain.com not to
test.mysgusername.6913e966e5.busybodyemail#domain.com@ob.0sg.net so the magic behind Reply Address Masking is being ignored, because the message is sent directly to the recipient not through Spamgourmet servers.
I think that Spamgourmet server is adding an additional email address at the end of FROM field when the real name has accents (or non-ASCII characters). The server is encoding the text in the FROM field (according to
RFC 2047) but is including the original email address after this. Gmail is using this last address instead of the masked address.
So, be careful if you use GMail, when you reply a message that has been encoded in this way you can be making public your real email address. This is not a consequence of a wrong setup in your email client, or in your Spamgourmet setup. This is a situation that can emerge when someone send you a message and has non-ASCII characters in their email address.
Admins, please review this case.
Regards.