On 2017-07-27 13:08, Rupert Gallagher wrote: > The rfc prescribes (MUST) the use of your public domain in the domain > part of your mid.
If you mean RFC 5322, this is not true. Section 3.6.4: The message identifier (msg-id) itself MUST be a globally unique identifier for a message. The generator of the message identifier MUST guarantee that the msg-id is unique. There are several algorithms that can be used to accomplish this. Since the msg-id has a similar syntax to addr-spec (identical except that quoted strings, comments, and folding white space are not allowed), a good method is to put the domain name (or a domain literal IP address) of the host on which the message identifier was created on the right-hand side of the "@" (since domain names and IP addresses are normally unique), and put a combination of the current absolute date and time along with some other currently unique (perhaps sequential) identifier available on the system (for example, a process id number) on the left-hand side. Though other algorithms will work, it is RECOMMENDED that the right-hand side contain some domain identifier (either of the host itself or otherwise) such that the generator of the message identifier can guarantee the uniqueness of the left-hand side within the scope of that domain. Or do you mean some other RFC, which one? > So the dns tests are just the first in the queue. The dimain must also > match early in the Reveived list. Huh? Even corrected for the obvious typos, this doesn't make sense. We're talking about the Message-ID here. > If you fail with it, then you have problems with every rfc-compliant > smtp server world-wide. This filter is especially useful against > scripts, spamming programs, and web-based mailers. You're free to lose any incoming mail you like, including mine :-) Though apparently you do get my messages, so I am confused about what your filter actually does. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. Do obvious transformation on domain to reply privately _only_ on Usenet.
