[horde] Feature Request - allow envelope-sender to equal envelop-to on reply.

[Simon Brereton]

> -----Original Message-----
> From: Michael M Slusarz [mailto:slusarz at horde.org]
> Sent: Tuesday, June 14, 2011 5:22 PM
> Quoting Simon Brereton <simon.brereton at buongiorno.com>:
> 
> >> -----Original Message-----
> >> From: horde-bounces at lists.horde.org [mailto:horde-
> >> bounces at lists.horde.org] On Behalf Of Michael M Slusarz
> >>
> >> > My mail server (in common with several others) allows for a
> >> delimiting
> >> > character, everything after which is ignored (by default in
> postfix
> >> > it's a +, but you can change this)..  So that user at domain.com is
> >> the
> >> > same as user+identifier at domain.com
> >> >
> >> > I find myself using this more and more often, not just to file
> >> mail,
> >> > but also to track which sites are sharing my email address.
> >> > However, the value in this is nullified when I have to respond
> to
> >> an
> >> > email and the sender becomes user at domain.com
> >> >
> >> > Would it be possible to add a feature to IMP that says if you
> get
> >> an
> >> > email delivered to user at domain.com but envelope-to is
> >> > user+identifier at domain.com, that the envelope-sender
> automatically
> >> > becomes user+identifier at domain.com?
> >>
> >> This works just fine with IMP 5.  Responding, e.g., to a message
> from
> >> foo+bar at example.com correctly sets the To: address on the compose
> >> message to foo+bar at example.com.
> >>
> >> > Also, if it would be possible to specify what the delimiter is
> (in
> >> my
> >> > case it's non-standard).
> >>
> >> To the extent this doesn't already work, no.  Why would you need
> this
> >> anyway?  Such e-mail tags are meant to be transparent to everyone
> >> outside of the local MTA anyway.
> >
> > Because generally, I use this feature with shady sites/companies
> I'm
> > not yet sure I want to entrust my email address to.
> >
> > So for example, if I sign up to horde.org with user-
> horde at domain.com I
> > want to be able to respond to emails addressed to
> > user-horde at domain.com with that address to avoid revealing the real
> > address.  user-horde at domain.com can then be blocked later if needs
> to
> > be and I don't have to worry about them also having knowledge of
> > user at domain.com with which to continue their now unwanted
> > communications.
> 
> Setup an identity specifically for "user-foo at domain.com" in Horde's
> identities.

Probably, I should have mentioned that I am aware of that route - but with anything more than 5 such accounts, that would become unworkable (and I probably have 20-odd such strings out in the wild at the moment).

If it works for replying to email with foo+bar as the envelope sender (not that there isn't a valid reason why it shouldn't - unless I misunderstood your earlier point), why can't it work for replying to email with foo+bar as envelope-to?

Simon