Wrong "from" address chosen in some cases
I have several identities configured for my default email account: let's call these "x@zzz.com", "y@zzz.com", "z@zzz.com" and "joe.bloggs@mailserver.com". The actual email provider is "mailserver.com" - that's what I log in to to send and receive mail - and the login details are the last address as a username (plus a password, of course); however, the first address - x@zzz.com - is set as my default identity. Incoming messages to any of these addresses are forwarded to the last one, but the "to" address on the message is displayed as the one that it was originally sent to.
If I create a new message, the "from" address is set to x@zzz.com as it should be. If I reply to an email, then it's set to whatever address that email was sent to, which again is correct. However, if I get a message from, for example, a mailing list, so that none of my email addresses appear in the "to" field, then when I reply the "from" address is set to "joe.bloggs@mailserver.com", which isn't correct. This is even if the headers show that the mailing list actually sent the message to one of the other identities, for example y@zzz.com. Can anyone explain what's going on here, please, and how to overcome it. I would have thought that if none of my identities appeared in the "to" or "cc" fields of an incoming message, any response should use my default sending idnetity.
Semua Balasan (2)
Are you talking about email where you are BCC'ed that is different to a mailing list, but I think it is what you mean.
Actually it's both. I don't know how the mailing lists actually work; the messages display as either:
From: xxx To: undisclosed-recipients Reply to: yyy
or:
From: xxx To: abc@def.com [where that's the address of the mailing list server, i.e. what the sender would have addressed it to] Reply to: yyy
It may be that there actually was a BCC header, but I don't get to see it (whereas I sometimes get other messages which display as:
From: xxx To: xxx BCC: [my address]
that were presumably also BCC'd to others as well). However, the behaviour is the same in all cases.