[Alpine-info] email+TAG@domain

[via Alpine-info]

>> In order to use say emails like myemail+TAG at domain when subscribing to 

>> some newsletter or service, I'm currently having a handful of roles, 

>> one per service(TAG).

>> 

>> But by doing so, for each new service I have to define a new role, 

>> which is rather tedious.




> I have set

> 	copy-to-address-to-from-if-it-is-us

> and

> 	 alt-addresses=email.*@domain


Same; I always use tear-off addresses for everything, and with these two 
settings, *most* of the time it just Does The Right Thing without needing 
to use roles or per-list/per-service hardcoded setup.

Most of the time... because:



> For some newsletters this works, but or others it does not.


Some email lists/newsletters Bcc: all recipients, so that your email 
address does not appear in the To: or Cc: field.  In this case, the 
"copy-to-address-to-from-if-it-is-us" setting doesn't work.

A possible workaround might be to add a similar option that matches on 
Delivered-To: headers, applies a sed(1)-style transform, and copies the 
result to the From: field.

Eduardo: any interest in adding such a feature?



> (I use email.TAG at domain, not sure whether the . and + are magic in this 

> case).


The ".*" in your "alt-addresses" setting is not for the "." in 
"email.TAG", it's a(n extended) regular expression.

In a regular expression, "." matches any single character, and "*" means 
"zero or more instances of the previous item."  (If you're used to 
shell-style globs, just remember to put ".*" anyplace that you would 
ordinarily put just plain "*" and it will probably do what you want.)

TL;DR: if you set "alt-addresses=alice.*@example.com", it will match 
alice.foo at example.com, alice+bar at example.com, alice-baz at example.com, 
alicebob at example.com, etc.


  -Jason