Re: A request to all mail admins

From: Nils Petter Vaskinn (no_at_spam.for.me.invalid)
Date: 08/28/03


Date: Thu, 28 Aug 2003 15:09:19 GMT

On Thu, 28 Aug 2003 14:20:56 +0000, Jem Berkes wrote:

> One suggestion that has been well formulated is the RMX resource record
> in DNS. A domain owner would list all mail servers authorized to send
> mail on behalf of the domain name. Mail servers that support RMX
> checking would do a type=RMX lookup on the domain name in the From
> field, and get back a list of authorized relay IPs for the domain. Then
> it's a simple check; is the connecting mail relay one of these
> authorized IPs?

That's a great idea. And the really good thing is that it can be
introduced gradually without breaking anything.

Step 1: reject messages if RMX exists and the sender doesn't match.
Step 1b: Insert extra header indicating there was no RMX to make it easy
for spam filters.
Step 2. Bounce and/or require resending to whitelist if there is no RMX
Step 3. Reject if there is no RMX

In step 1 everything will work as it has now. When RMX record have become
more common step 2 will mean the mail still gets there, but cause pressure
on late movers. step 3 is for when close to everyone is using this.

As I said a good idea that can make email useful again.

regards
NPV



Relevant Pages

  • Re: A request to all mail admins
    ... A domain owner would list all mail servers authorized ... I don't know exactly how RMX will be ... It won't stop people from sending spam from their own domains, ...
    (comp.os.linux.networking)
  • Re: A request to all mail admins
    ... A domain owner would list all mail servers authorized ... I don't know exactly how RMX will be ... It won't stop people from sending spam from their own domains, ...
    (comp.os.linux.security)
  • Re: A request to all mail admins
    ... A domain owner would list all mail servers authorized to send ... Mail servers that support RMX ... and get back a list of authorized relay IPs for the domain. ... reject messages if RMX exists and the sender doesn't match. ...
    (comp.os.linux.networking)