What’s the difference between technical standards and ethical guidelines?

Think of it this way. Technical standards are the rules that keep email working at all. Ethical guidelines are the rules that keep email worth having.

Technical standards cover the infrastructure layer. SMTP defines how mail servers talk to each other. MIME defines how message content is structured. SPF, DKIM, and DMARC define how senders prove they are who they say they are. Break these and your email simply stops working. It bounces, gets rejected, or sits in a queue going nowhere.

Ethical guidelines live one layer up. They cover consent (did this person actually ask to hear from you?), transparency (is the subject line honest about what's inside?), and respect (can someone easily leave your list?). Break these and the email still technically sends. It just shouldn't.

The gray area is where things get interesting. Here are four real scenarios to make this concrete:

• Compliant and ethical. You authenticate your domain with SPF, DKIM, and DMARC, you only email people who explicitly opted in, and your unsubscribe link is in plain sight. This is where every sender should be.
• Compliant but ethically questionable. Your authentication passes perfectly, but you bought a list, pre-ticked the consent checkbox, or wrote a subject line designed to trick people into opening. The mail delivers. The damage to your reputation (and the recipient's trust) builds quietly.
• Non-compliant but well-intentioned. You genuinely earned your list, your content is honest, but you never set up DMARC. Your domain is vulnerable to spoofing, and your reputation can be hijacked by someone else. Good intentions don't protect you here.
• Non-compliant and unethical. Purchased list, no authentication, misleading subject line. This is where spam filters, blocklists, and mailbox providers like Gmail and Outlook step in hard.

The reason both matter together is that spam filters don't just check your authentication. They also factor in complaint rates, engagement patterns, and sending behavior. A technically perfect email from a sender with a dirty list and a clickbait subject line still gets filtered. The filters have learned to read ethics, even if they can't articulate them the way a human can.

Your actual responsibility as a sender sits in both columns. Technical compliance gets you in the door. Ethical practice keeps you there.

Not sure where your setup stands? Our free SPF checker covers the technical side in about 30 seconds. If you want a second opinion on the ethical side of your program, our SOS hotline is free and judgment-free.