TagRFC5321/5322

Null sender address

A question came up on the email geeks slack channel about empty from addresses. I asked if they meant the 5321 or 5322 from address which prompted a question about if you could even have a null 5321 from. Yes, you can and it’s commonly used for some types of email. 5321.from is the bounce address, and the domain used in SPF authentication. Null addresses, literally <>, are used for email...

8 things that make your mail look like spam

In the comments of last week’s Wednesday question John B. asked Can you elaborate on specifics of “configure machines to not look like spam ware”? There are a lot of things that spamware does that is different from a lot of standard MTAs. Here are a list of things that may make your mail look like it is running spamware to a receiving server. Using weird values for HELO/EHLO, like a bare IP...

Six best practices for every mailer

People get into all sorts of details when talking about best practices. But so much of email depends on the type of email and the target market and the goals of the sender. It’s difficult to come up with universal best practices. I’ve said in the past that I think that best practices are primarily technical. I don’t believe there is a best frequency or a best time to send mail...

Email Standards Updated

This morning I received notification that the IETF had approved RFC5321 and RFC5322. These two RFCs are standards track and are updating the current email standards RFC821/822 and RFC2821/2822. MailChannels has a description of the changes between 2821/2822 and 5321/5322. While the new RFCs obsolete the old ones, they are more a clarification than actual changes to the protocols. Dave Crocker had...

Recent Posts

Archives

Follow Us