rMX and rDNS together make spamming more difficult ?
My idea is check senders (MTA s) ip and priviledges to use smtp, not using protocol headers or other content filtering method. My idea is control connection (ip) using reverse dns lookup database, not dns lookup. My proposal include also method to handle roaming mta. Mail sending is done from ip, not from domain. Reverse dns is mostly controlled by operators and "big companies", so we have less players as in domain structure and I believe that it is easier to make "operator blacklist" as domains. This idea is simple (too simple to be true ? That I m asking) to add every access control level : firewall, proxies, filters, wrappers, smtp servers, ... Proposal rMX using rDNS: http://www.awot.fi/sf/browser/showfile?cust=awkoulutus&subdir=dns&doc=reverse_mx I m waiting feedback, have I missed something ? -jukka- Jukka do.t Inkeri at Awot do.t Fi
My idea is check senders (MTA s) ip and priviledges to use smtp, not using
Hi Feedback: Your idea sounds just like any other blacklisting, except for that you want to deny anybody by default instead and add the ones you want to accept. Thats sounds like a huge project, maybe too huge. What would you really want to accept on your list? There are countries allowing spam, and there are countries partly allowing it. I do not want to block the "legal" spam. Would you add "legally" spamming companies? Spammers using compromised systems to spam is another thing. That sure is one annoying problem... I do not think you have the general solution, and I don't have any ideas for one either. But keep it brainstorming! Best regards, Joergen Hovland If you want to know how we try to stop spam: We are currently handling spam by blocking all known dialups/dhcp ranges. On top of that we block entire countries (or all countries except for the ones on the list) per emailaccount decided by the customer. This blocking is based on the IP-address of the remote-mailserver trying to send us the email. My own email blocks every country except UK, Netherlands, USA and Scandinavia. ----- Original Message ----- From: <use.signature.ripe@awot.fi> To: <dns-wg@ripe.net> Sent: Thursday, November 27, 2003 3:55 PM Subject: [dns-wg] rMX and rDNS together make spamming more difficult ? protocol headers or other content filtering method. My idea is control connection (ip) using reverse dns lookup database, not dns lookup. My proposal include also method to handle roaming mta.
Mail sending is done from ip, not from domain.
Reverse dns is mostly controlled by operators and "big companies", so we
have less players as in domain structure and I believe that it is easier to make "operator blacklist" as domains.
This idea is simple (too simple to be true ? That I m asking) to add every
access control level : firewall, proxies, filters, wrappers, smtp servers, ...
Proposal rMX using rDNS:
http://www.awot.fi/sf/browser/showfile?cust=awkoulutus&subdir=dns&doc=reverse_mx
I m waiting feedback, have I missed something ?
-jukka- Jukka do.t Inkeri at Awot do.t Fi
>> My idea is check senders (MTA s) ip and priviledges to use >> smtp, not using protocol headers or other content filtering >> method. My idea is control connection (ip) using reverse dns >> lookup database, not dns lookup. I'm confused. How do you propose to use the reverse DNS database without doing a DNS lookup? Please explain. Oh, and please use a real email address on this list. IIRC postings are only permitted from list members which means the list should be spam-free. Putting garbage in the From: header is not appreciated.
I m waiting feedback, have I missed something ? Probably. The dns-wg is about dns, not about anti-spam. Maybe you should take your ideas to the antispam group first. jaap
participants (4)
-
Jaap Akkerhuis -
Jim Reid -
Jørgen Hovland -
use.signature.ripe＠awot.fi