I've been looking at various client fixes to add :from, but ultimately the better solution would be in sieve/managesieve as although I have a single webmail solution I'm also offering imap access.
A really simple solution (for me) would be for sieve to copy the :address to :from. I may even implement this as a hack and recompile...
Still doesn't fix responses to expanded system aliases. That's a whole different problem though, I suspect.
Peter.
-----Original Message----- From: dovecot-bounces+dovecot=peter-b.org@dovecot.org [mailto:dovecot-bounces+dovecot=peter-b.org@dovecot.org] On Behalf Of Gavin Hamill Sent: 22 October 2009 11:03 To: Stephan Bosch Cc: 'Dovecot Mailing List' Subject: Re: [Dovecot] simple steps with sieve
On Tue, 2009-10-20 at 17:34 +0200, Stephan Bosch wrote:
Peter Borg wrote:
I find it really hard to believe that Gavin and I are the only ones to hit this issue. That said I've probably been hacking at this particular system too long and am missing something very obvious....!
You're definitely not the only one. Finding a good solution is difficult however. The intention of this check within the vacation action is to prevent spurious vacation responses to for example Bcc:'ed deliveries (and perhaps multi-drop aliases).
For my own situation, I solved this issue entirely from the 'roundcube' webmail package. Help on the roundcubeforums site suggested changes to the 'sieverules' plugin so :addresses would always be included in a vacation rule. I extended this to the :from parameter.
Also used roundcube's new_user_identity plugin to populate the primary identity of a 'ar-wbim' username with 'wim.bim@ourdomain.com' so that the :from and :addresses are using the canonical format
Fairly ugly, but it works for us. I'll document the changes if I get a moment.
Cheers, Gavin.