Qmail
[Top] [All Lists]

Re: (OT)Verizon problems

To: qmail list <qmail@list.cr.yp.to>
Subject: Re: (OT)Verizon problems
From: Matt Simpson <net-qmlist@jmatt.net>
Date: Fri, 9 Mar 2007 10:27:05 -0500
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-qmail@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list qmail@list.cr.yp.to
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=jmatt.net; b=Yf/58vVFPzeGokDk8+LWVnwseGXqtA+CZ3oaD6uUud8Wp9Oejtnmy6/lEnpkiaIs4jGZ+nn5eBTTX/cBK7j/8QuBNTPKOKJzNxIMZkYPzMQtlRfnexrVGucwUmkcRS2Id1i/5pBS3vyNF3CliHG+pGQ0u2iJRYiXgZoDngeIb4M=; h=Received:Mime-Version:Message-Id:In-Reply-To:References:Date:From:Subject:Mime-Version:Content-Type;
Domainkey-status: bad
In-reply-to: <1173451090.45f17152d723a@www.techsane.com>
Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
References: <1173382026.45f0638abc48d@www.techsane.com> <20070308202117.GR2924@c-76-18-79-168.hsd1.nm.comcast.net> <45F0F96F.6030903@techsane.com> <p06240601c2170c06429b@chowder.foxhunters.org> <1173451090.45f17152d723a@www.techsane.com>
At 9:38 AM 3/9/07, Russel Oliver wrote:
But .. if I tell you that
in order to send mail to me you must allow certain access to your server you
are ok with that demand?

Depends on what the "certain access" is. But at this point, you don't even know if Verizon is demanding that. All you know is they're "demanding" something and not telling you what it is. I agree that's pretty moronic.

It's possible that they are trying to do some kind of check on your server to determine the validity of the sender. I may or may not be "OK" with that, depending on what kind of check they're doing, and what the definition of "OK" is.

I see quite a few ISPs that connect back to my server and initiate an SMTP transaction (MAIL FROM and RCPT TO) to check the sender validity. I think that's stupid, and it annoys me a little, but I'm "OK" with it if "OK" means I'm not actively trying to prevent it. I'm not "OK" with it if it means I have to make changes on my server to make it work.

For example, I do SPF checking on my server. I've seen ISPs do their validity checking from an IP address that's not in their published SPF records. So when they connect to my server and initiate their dummy SMTP transaction, I reject it because their sending server is not a valid server for the domain in their FROM address. I'm not going to turn off my SPF checking so their brain-dead scheme will work.

Another example: I use a GREETDELAY patch which also drops servers that try to send data before the greeting. I have a mailing list with a couple of users whose ISPs connect back to mine for every message, and get dropped for sending data too soon. So I'm "OK" with them checking the validity of senders if they do it correctly (even though I still think it's stupid), but I'm not "OK" with allowing them to break the SMTP rules to do it.

I am going to get a dump of the session and try to figure out what it is looking
for.

That might help. It might not. It's a good place to start. But, as Kyle pointed out, it's still possible that they're rejecting your message for some other reason unrelated to anything your server tells them. That's the really frustrating part. Good luck.

<Prev in Thread] Current Thread [Next in Thread>