Re: Malformed spam email gets through.

2018-01-03 Thread @lbutlr
On 03 Jan 2018, at 04:57, Matus UHLAR - fantomas wrote: > while it's "only" recommended that the right part is a domain name, but > there must be right part. Yes, there must be a left and a right and an ‘@‘ in-between. On 03 Jan 2018, at 12:36, Bill Cole wrote: > About 1.5% of my personal non-

Re: Malformed spam email gets through.

2018-01-03 Thread Ian Zimmerman
On 2018-01-03 14:36, Bill Cole wrote: > I have run an environment where each MTA node in the external gateway > layer would add a MID with its own FQDN to any message passing through > missing a MID. Those names could not be resolved in the world at > large, but they were absolutely valid and guar

Re: Malformed spam email gets through.

2018-01-03 Thread Bill Cole
On 2 Jan 2018, at 20:39, Alex wrote: Is it possible to at least enforce that the message-ID has a valid domain? Not reliably. About 1.5% of my personal non-spam email over the past 20 years has had "localhost" as the right hand side of the MID. This implies a de facto RFC violation because

Re: Malformed spam email gets through.

2018-01-03 Thread Matus UHLAR - fantomas
On 1 Jan 2018, at 10:47, Matus UHLAR - fantomas uh...@fantomas.sk> wrote: On 1 Jan 2018, at 11:41 (-0500), Matus UHLAR - fantomas wrote: the gross format in RFCs 822,2822 and 5322 describes message-id consisting of local and domain part, thus is must contain "@". On 01.01.18 12:17, Bill Cole

Re: Malformed spam email gets through.

2018-01-03 Thread Antony Stone
On Wednesday 03 January 2018 at 02:39:54, Alex wrote: > Hi, > > Is it possible to at least enforce that the message-ID has a valid domain? If by "enforce" you mean "require" (in other words, you look at whatever message-ID the incoming email has, and you decide that if it doesn't contain a val