<p>I can do that for you, email me the info off list.<br>
-dc</p>
<div class="gmail_quote">On Apr 9, 2011 9:32 AM, "Matt" <<a href="mailto:matt@itwannabe.com">matt@itwannabe.com</a>> wrote:<br type="attribution">> My server, hosted by Dave at Internet solver, doesn't resolve properly. The only place this ever caused me problems was on craigslist, so I never bothered complaining about it. I'll get in touch with Dave, but I doubt it will be solved before Monday.<br>
> <br>> Matt, the IT Wannabe<br>> <a href="http://www.itwannabe.com/">http://www.itwannabe.com/</a><br>> <br>> On Apr 8, 2011, at 9:14 PM, Nicolai <<a href="mailto:nicolai-cialug@chocolatine.org">nicolai-cialug@chocolatine.org</a>> wrote:<br>
> <br>>> Hello all,<br>>> <br>>> This is a long message but you can skip over it if the following items<br>>> don't apply to you:<br>>> <br>>> 1. Forward-confirmed reverse DNS for your mailserver, which will soon be<br>
>> required for sending mail to <a href="http://cialug.org">cialug.org</a>. (Let me know if this applies<br>>> to you!)<br>>> <br>>> 2. A description of small changes I've made to the <a href="http://cialug.org">cialug.org</a> mail config.<br>
>> <br>>> 3. Posts from non-subscriber addresses. (Let me know if you do!)<br>>> <br>>> First, I want to remind folks that they will soon need to have proper<br>>> DNS records for machines sending mail to <a href="http://cialug.org">cialug.org</a>.<br>
>> <br>>> Who this mainly applies to: people who run their own mail servers. It<br>>> should not affect many people.<br>>> <br>>> This requirement will apply only to DNS records, not to your mail server<br>
>> config. And if you don't run your own mail server, it's exceedingly<br>>> unlikely this applies to you at all.<br>>> <br>>> What this entails:<br>>> <br>>> This means having matching PTR and A records, also known as<br>
>> Forward-confirmed reverse DNS. See:<br>>> <br>>> <a href="https://secure.wikimedia.org/wikipedia/en/wiki/Forward-confirmed_reverse_DNS">https://secure.wikimedia.org/wikipedia/en/wiki/Forward-confirmed_reverse_DNS</a><br>
>> <br>>> For example, your trusty <a href="http://cialug.org">cialug.org</a> server sits on 67.224.64.36, which<br>>> resolves to <a href="http://mail.cialug.org">mail.cialug.org</a>, which in turn resolves to 67.224.64.36. A<br>
>> perfect match. The great majority of spamcannons lack matching DNS<br>>> records, and virtually all legitimate mailservers have them. And any<br>>> legit server should be able to get them, if they don't already.<br>
>> <br>>> How to verify if your mail server has matching DNS records:<br>>> <br>>> 1. Find its (public, if necessary) IP address.<br>>> 2. Resolve it via the command dig -x <ip>, ie,<br>
>> <br>>> dig -x 67.224.64.36<br>>> <br>>> 3. Resolve the hostname you got from step #2, if applicable, via<br>>> dig <hostname>, ie,<br>>> <br>>> dig <a href="http://mail.cialug.org">mail.cialug.org</a><br>
>> <br>>> If the records match, you're good to go.<br>>> <br>>> However if you get NXDOMAIN for either query, or if the records don't<br>>> match, you'll need to talk to your ISP. Explain that you need<br>
>> Forward-confirmed reverse DNS to talk to <a href="http://cialug.org">cialug.org</a>, as described in RFC<br>>> 1912, specifically section 2.1:<br>>> <br>>> "Every Internet-reachable host should have a name. The consequences<br>
>> of this are becoming more and more obvious. Many services available<br>>> on the Internet will not talk to you if you aren't correctly<br>>> registered in the DNS. Make sure your PTR and A records match. For<br>
>> every IP address, there should be a matching PTR record in the<br>>> in-addr.arpa domain."<br>>> <br>>> If you don't know if this applies to you, send me a private mail with<br>>> your mail server's IP address and I'd be happy to check for you.<br>
>> <br>>> <br>>> SECOND, Postfix is now using <a href="http://sbl-xbl.spamhaus.org">sbl-xbl.spamhaus.org</a> and is blocking<br>>> significant amounts of spam. (Including messages from the forged bryan@<br>
>> botnet of recent fame.) We don't see this spam on the list but the list<br>>> admins get copies of it in our mailboxes and have to wade through it<br>>> while maintaining mailman. Currently it's 50 - 100 spam messages a day,<br>
>> every day, and would presumably grow much larger as spam levels return<br>>> to normal after post-Rustock botnet spam levels normalize.<br>>> <br>>> Third, I would prefer to simply discard all non-subscriber posts. Does<br>
>> anyone actually post from a non-subscriber address?<br>>> <br>>> Nicolai<br>>> _______________________________________________<br>>> Cialug mailing list<br>>> <a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>
>> <a href="http://cialug.org/mailman/listinfo/cialug">http://cialug.org/mailman/listinfo/cialug</a><br>> _______________________________________________<br>> Cialug mailing list<br>> <a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>
> <a href="http://cialug.org/mailman/listinfo/cialug">http://cialug.org/mailman/listinfo/cialug</a><br></div>