Bingo!

Pardon my earlier post. Did not know you knew about these.
If you can implement all three, then your email should flow with assurance and w/o restrictions. (But see my comments about (e.g.) Yahoo! and other carriers. What can be done? I have no idea.)


On 8/23/26 1:09 AM, Brian Westerman wrote:
One thing I forgot to mention is that the email address that receives the email 
from the user can (and should) also be able to limit who is allowed to send 
them email and from where, and do the validation of the SPF, DKIM, and DMARC 
records, etc.  So a lot of the filtering out of spam and bogus users can, and 
will be done there.

So much of the security controls are fairly simple to implement, and while I can stress 
that they should be in use, I can't really force anyone to do it.  It becomes that old 
"lead a horse to water..." thing.

Security-wise, I think it's okay, I was wondering more about how you think 
people would use it or like to use it, so that I can make sure that I handle 
those aspects before I publish it for use.

Brian

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

--
-- R; <><

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to