DKIM and reply address masking issue
Posted: Wed Jan 25, 2017 12:42 am
Hey everyone - Syskoll warned me about this, and I guess I knew it anyway, but the enforcement of DKIM that is currently going into place with providers like google/gmail is *not* compatible with spamgourmet's reply address masking feature -- that is, when we go in and change the "from" address to be one that will come back to spamgourmet instead of to the sender (so that we can change your from address to be the disposable address you were using), that breaks the integrity check that the DKIM enforcement runs later on -- sort of like, "this email says in its DKIM headers that it's from example.com (or somewhere), but the 'from' address is [something]@spamgourmet.com - somethings's not right, so REJECT. If this happens, you probably won't get any error message or any indication that the message has been sent.
I'm probably going to need some time to figure out an elegant way to make things work, but in the meantime, turning off reply address masking temporarily could help if you're expecting an email and it's not arriving (you probably have to click 're-send' wherever it was that sent it).
This only happens when both: 1) the sender has implemented DKIM rules, and 2) your email provider is enforcing them. So currently it won't happen very often, but probably it will happen more as time goes on.
So... this sucks, yes. But DKIM enforcement is a Good Thing, in my opinion. If we had things like that around a long time ago, probably there would be no need for spamgourmet.
I'll keep you posted.
I'm probably going to need some time to figure out an elegant way to make things work, but in the meantime, turning off reply address masking temporarily could help if you're expecting an email and it's not arriving (you probably have to click 're-send' wherever it was that sent it).
This only happens when both: 1) the sender has implemented DKIM rules, and 2) your email provider is enforcing them. So currently it won't happen very often, but probably it will happen more as time goes on.
So... this sucks, yes. But DKIM enforcement is a Good Thing, in my opinion. If we had things like that around a long time ago, probably there would be no need for spamgourmet.
I'll keep you posted.