Chris and others,From what I've been reading on other mailing lists, not all is sweet-smelling roses as far as migrating mailing-list(s) to Mailman using Yahoo.com addresses.A big thorn with using Yahoo.com is its "DMARC badness" as Rick put it in his conspire mailing-list post '(forw) [skeptic] me.com is shooting Skeptic subscribers in the foot w/DMARC (was: I have questions...)' at http://linuxmafia.com/pipermail/conspire/2021-April/011582.htmlDirectly quoting Rick from that post:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~DMARC is a badly designed antiforgery method designed by Yahoo that is built atop an equally badly designed earlier antiforgery method named DKIM. DKIM allows an individual user to cryptographically sign the composed contents of his/her message, including many of the internal SMTP headers. DMARC is a metastandard that includes DKIM, and adds a method (SPF) to determine whether the IP address attempting to deliver mail ostensibly from a claimed sending domain is among the IP addresses predeclared as authorised to issue mail from that domain onto the Internet.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a standard email authentication method. DMARC helps mail administrators prevent hackers and other attackers from spoofing their organization and domain. Spoofing is a type of attack in which the From address of an email message is forged. A spoofed message appears to be from the impersonated organization or domain.
DMARC also lets you request reports
from email servers that get messages from your organization or domain.
These reports have information to help you identify possible
authentication issues and malicious activity for messages sent from your
domain.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Three other sections of that 'About DMARC' link are
o - Spooofing and Phishing
o - How DMARC prevents spoofing (including relevant expanded "zippys"; 'Authenticates messages (DMARC alignment)', 'Manages messages that fail authentication (receiver policy)', and 'Sends you reports so you can monitor and change your policy' )
o - What you need to do
Use the DomainKeys Identified Mail (DKIM) standard to help prevent spoofing on outgoing messages sent from your domain.
Email spoofing is when email content is changed to make the message appear from someone or somewhere other than the actual source. Spoofing is a common unauthorized use of email, so some email servers require DKIM to prevent email spoofing.
DKIM adds an encrypted signature to the header of all outgoing messages. Email servers that get signed messages use DKIM to decrypt the message header, and verify the message was not changed after it was sent.
If you want more email security, we recommend setting up these security methods along with DKIM:
Using
Sender Policy Framework (SPF), you can protect your domain from
spoofing and help ensure that your messages are delivered correctly. You
use SPF to authenticate email and specify the mail servers authorized
to send email for your domain. Mail servers use SPF to verify that
messages that appear to come from your domain actually are from your
domain.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~