I make extensive use of recipient-delimiters (usually "+") when providing my email addresses. This requires manual entry each time I need to respond to an entity where I've provided my address in the "user+subaddress@domain.tld" format. Suggested enhancement -- in Folder->Properties->Compose, add: [ ] Sub-address ________________________________ which would allow any recipient-delimiter. i.e., enabling this feature and entering "+foo" would cause the resulting From address to automatically become "user+foo@domain.tld" rather than just "user@domain.tld" of the account.
This is surely something very particular to your own personal preference, is it not?
Only if one denies the existence of this format within multiple RFCs... a small sampling of grep'ing for this format: rfc1147.txt: sw0l+snmp@andrew.cmu.edu. ("sw0l" is "ess double-you rfc2130.txt: * Keith Moore <moore+charsets@cs.utk.edu> rfc3113.txt: EMail: Klensin+iab@jck.com rfc3467.txt: EMail: klensin+srch@jck.com rfc3598.txt: addressing" (e.g., "ken+sieve@example.org"), it is sometimes rfc3598.txt: "ken+sieve@example.org"). If no separator character exists, then rfc3696.txt: user+mailbox@example.com rfc3743.txt: EMail: Klensin+ietf@jck.com rfc3767.txt: Lawrence Greenfield (leg+@andrew.cmu.edu), rfc3777.txt: EMail: galvin+ietf@elistx.com rfc3798.txt: EMail: tony+rfc3798@maillennium.att.com rfc3885.txt: EMail: tony+msgtrk@maillennium.att.com rfc3887.txt: EMail: tony+msgtrk@maillennium.att.com rfc3888.txt: EMail: tony+msgtrk@maillennium.att.com
The existence of the plus sign in other people's addresses is not conclusive that they use it in the same way as you.
Well... it's a format that's been supported for years in Postfix: # ADDRESS EXTENSIONS (e.g., user+foo) # # The recipient_delimiter parameter specifies the separator between # user names and address extensions (user+foo). See canonical(5), # local(8), relocated(5) and virtual(5) for the effects this has on # aliases, canonical, virtual, relocated and .forward file lookups. # Basically, the software tries user+foo and .forward+foo before # trying user and .forward. # #recipient_delimiter = + Then, there's always the RFC itself... rfc5233[Jan/08] (which obsoletes rfc3598[Sep/03])
rfc5233 - now it makes more sense
Created attachment 782 [details] Example script for the Python plugin
With the Python plugin in CVS, you can script a workaround yourself in the meantime. I attached a quick & dirty example script that will modify any occurence of "berndth@gmx.de" in the From header to "berndth+foo@gmx.de" if the message was composed from the folder Mailinglisten/Claws-Mail/user. Similar replacements take place for the Bug (+bar) and Translators (+baz) folders. This script needs to be saved as $HOME/.claws-mail/python-scripts/auto/compose_any Of course, this solution is not perfect (e.g. you'll need to update the script when you rename a referenced folder), but maybe it's helpful to you.
WORKAROUND: This workaround does not track account changes; but works otherwise. Folder->Properties->Templates [Compose|Reply|Forward] [X] Use template when {composing new,replying to,forwarding} messages From: user+subaddress@domain.tld