Am 08.07.2013 20:13, schrieb Michael Heydekamp:
Am 08.07.2013 08:19, schrieb A.L.E.C:
On 07/06/2013 10:58 PM, Michael Heydekamp wrote:
The main difference between these two messages is the order of the "Envelope-To:" headers. But apparently that doesn't make any difference at all, as when replying to these messages, the identity "identity1@test.de" is being used as the sender in the "From:" header in both cases. Hmm...?!?
See line 1905-1812 of steps/mail/func.inc (git-master).
Yep, afterwards I did find this place. Originally this code was in steps/mail/compose.inc.
As I'm able to create any custom header right before delivery, how can I make sure that this - and only this - custom header will be respected with regards to identity selection, disregarding any other headers/addresses and the entire rest of the logic...?
This would be a private patch, of course. Any help and hint appreciated, for I'm a noob in terms of PHP (= I have an idea of the logic, but just can't code it).
Maybe a hook for plugin at the end of rcmail_identity_select() function would be the best solution for you. I'd call it 'identity_select' or 'message_compose_identity'.
Sounds like a perfect idea - and a lot better than to patch the existing code in func.inc, as the daily git-pull will then often run into conflicts and abort the merge.
The problem just is: As I said, I'm a PHP noob and have no clue what I have to do to create/use such a hook with a plugin. I may probably be able to patch the existing code in func.inc, but that's it. Even though the plugin code will most likely be pretty similar to the code in func.inc.
Contact me once the hook is present (myroundcube [at] mail4us [dot] net). Such a plugin isn't a big thing.
If anyone of the Roundcube and/or plugin developers want to help me, you're welcome. A fair and tax-free ;-) compensation is granted.
Cheers,