On 4/11/19 8:26 PM, Patrick wrote:
bob+megac...@example.com is only published to MegaCorp, so any non-MegaCorp email received at bob+megac...@example.com implies that MegaCorp has an email privacy issue.
I get the logic. I've done similar for about 15 years.
Filter the old token then issue a new one to MegaCorp when that happens?
*Reset* *Moment*
The subaddress delimiter is MTA specific, i.e. ymmv. ;)
ACK
Nice. The subaddress can encode assertions regarding the sender, e.g. bob+dkimMegaCorp.com requires the email to be signed by MegaCorpWere this format well-known, then MegaCorp would know that 3rd party contact is forbidden and it has to broker the email transaction.
I get the idea.But what happens if MegaCorp farms out bob+MegaCorp.com@ or the entity they farm it out to recognizes the format and removes the dkim. ;-)
There really should be some sort of checksum / signature that you know that isn't easily guessable.
Sure. Any non-compliant email below a rate-limit is filtered to spam?
Sure. You could do that. Or—presuming you're running SpamAssassin—you could artificially add something to the Spam Score. So clean messages that have 3.5 points added will still come in under 5. Conversely a spam message that might have 4 points by itself is now at 7.5, thus tagged as spam. }:-)
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
