Eric Johnson
My feedback
4 results found
-
34 votes
An error occurred while saving the comment -
7 votes
-
752 votes
An error occurred while saving the comment Strictly speaking, there is a way to do this, but it is a bit of a pain in the neck.
You can reply to an e-mail that came to an alias and it uses that address in the reply.
So send yourself an e-mail to that alias. Then whenever you want to send an e-mail using that aliases as the sender, reply to the mail you sent yourself and change the title and recipients name and get rid of the text in the message you sent yourself.
Try it. Suppose your address is example@proton.me. Send yourself an e-mail to example+3.141592653589793238462643383279502884197169399375105820974944592307816406286208998628034825342117067982148086513282306647093844609550582231725359408128481117450284102701938521105559644622948954930381964428810975665933446128475@proton.me. Then use reply to send a message to a friend.
Note that one downside to using aliases is that the PGP encryption no longer works. Each '+' alias you use would need its own PGP key. If you could identify '+' addresses that you would like to use for encrypted e-mail, it would be nice to be able to select those '+' addresses and create a PGP key for each of them.
-
36 votes
An error occurred while saving the comment Filter on the header (I just posted about this)
if header :comparator "i;unicode-casemap" :contains "X-Original-To" "example+0623nat@pm.me"
{
addflag "\\Flagged";
fileinto "Reference/News";
fileinto "Nature";
stop;
}where News is a subfolder of Rference and Nature is a label/tag.
Using header ... "X-Original-To" ..., also filters properly if the sender puts the address as part of a BCC.
It's best to leave the catchall turned off. With catchall turned on, if someone sends an e-mail to a non-existent address, it looks to them like it went through to the intended recipient. Leave it turned off so the sender gets back a response telling them that they made a mistake with the address.