Am 08.12.2012 23:17, schrieb Michael Heydekamp:
I'll try again to find a way to support both Envelope-to: and Delivered-To: for our own purpose by using copy&paste techniques ;-) , but due to lack of PHP skills, I'll not be able to safely support Received: as well.
I'm providing the diffs/patches attached, which now work for me with 0.9-git-master. When replying to a message in the Roundcube lists, the correct identity will be chosen automatically (in our case based on the "Envelope-to:" header).
Feel free to use/commit them.
Notes:
Typo in compose.inc corrected ("amtches" -> "matches")
Both "Envelope-to:" (Exim) and "Delivered-To:" (qmail, Postfix) should
be supported, although I could just test "Envelope-to:". The headers of the messages in the Roundcube mailing lists do in our case look like this:
Envelope-to: listuser@freexp.de Delivered-To: dev-at-lists-dot-roundcube-dot-net@lists.roundcube.net
I'm not sure what would happen if it would be vice versa and the "Delivered-To:" header would contain the recipient's address rather than the "Envelope-to:" header. But it should work, IMO.
- I'm also not sure what would happen if more than one "Envelope-to:"
and/or Delivered-to:" header would exist.
- The "Received:" header is not (yet) supported, as my PHP skills are not
sufficient for this purpose. But in the long run it should be supported, IMO.
And again: Even if this all will work at the end of the day, it still doesn't help for new messages. So an identity option in the addressbook would still be a good idea IMO.
Although I can very well imagine that this may get a bit complex, as all addressbook entries need to be checked and probably get updated if an identity is being changed or deleted.
Just a reminder. ;)
Cheers,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany