Re: 209.196.45.44
"Alexey Lobanov (dsbl)" <[email protected]> Fri, 22 Dec 2006 13:38:16 +0300
| Newsgroups | gmane.mail.spam.dsbl.admin |
|---|---|
| Organization | DSBL volunteer |
| Message-ID | <[email protected]> |
Hello. On 22/12/06 08:29, [email protected] wrote: > Hello, > > Godaddy.com is the biggest internet company in the world for > hosting/email/domains. Your system is not capable of sending emails to > Godaddy.com. In opposite, we can see that it is perfectly capable. http://dsbl.org/listing?209.196.45.44 2006/Dec/22 01:44:29 UTC Removal Confirmation Sent EMail address: [email protected] Requestor IP: 75.19.59.200 Message Report: 64.202.166.12 accepted message. Remote host said: 250 ok 1166751874 qp 26043 by pre-smtp21-02.prod.mesa1.secureserver.net > Godaddy.com says that your emails do not meet RFC > standards, which is why they are being rejected. They are not rejected. If they would be rejected, you and we could analyze the rejection message and, possibly, change something. But we see that the GoDaddy server said "ok". > Yes, they say that > the dsbl.org emails are not compliant. > > It is very difficult for a third party (me) to coordinate efforts > between DSBL and Godaddy. It is much easier for you to contact Godaddy > and resolve your issues. GoDaddy technicians are welcome in this maillist at any time. Even in the Christmas night :-) > Isn't it in your best interest to coordinate > efforts with the biggest provider? For sure. And the coordination method is perfectly known: The Standards. DSBL still believes that the DSBL test messages are compliant to the current e-mail standard. If GoDaddy technician disagree, they must prove it. > > There is a saying: "The road to hell is paved with good intentions." > > > Any spam company can easily change their IP's and/or have the > resources to set up their own mail servers so that they can comply with > your rules. DSBL does not even try to say that any listed server belongs to a "spam company". > It is much easier for a spammer to get off of your list > than the regular guy. Think about this. And "regular guys" should not deal with DSBL delisting at all. Public network security incidents must be investigated and solved by a competent technical person, not by a "regular guy". > > You know that the server is configured correctly and not sending out > spam. Your tools are able to detect this. Absolutely unable. I ensure you that DSBL is not affiliated with CIA/KGB/FSB/Mossad et al and is not able to intercept and analyze your Internet traffic unless it is addressed to DSBL. > I am pleading for you to > fix this. You know that we only have good intentions. Yet, you are > unwilling to remove our IP from your list. Your company is causing > grief to the same people who you are trying to protect. This is my > last plead to remove my IP from your list. If you truly care about > good people then you would comply with my plea. If not, I will have to > figure something else out. In your place I would stop use the e-mail service applying undocumented censorship rules to your business e-mail. You just cannot know what other messages addressed to you were accepted by GoDaddy and killed silently in same way. Alexey DSBL voluneer > > Regards, > Rick Paul > > -------- Original Message -------- > Subject: RE: [DSBL-Contact] 209.196.45.44 > From: Bert Driehuis <[email protected]> > Date: Thu, December 21, 2006 6:21 pm > To: [email protected] > Cc: [email protected] > > [ Note: I do not represent DSBL. I just track [email protected] to keep > abreast > of possible issues that might affect my use of DSBL, and occasionally I > help > out with questions. You may get responses from other subscribers to > [email protected], possibly even with dissenting opinions. ] > > On Thu, 21 Dec 2006, [email protected] wrote: > >> There has got to be a reason that I do not receive your confirmation >> emails. The e-mail gets lost before it goes to my mailbox. I have >> tested it over and over again and do not receive any emails. > > I completely sympathize with your plight, but that won't help you, I'm > afraid. > > Any postmaster worth his salt can trace an e-mail message. An SMTP > server at 64.202.166.12 accepted the message on 2006/Dec/22 01:44:29 UTC > > and said "250 ok 1166751874 qp 26043 by > pre-smtp21-02.prod.mesa1.secureserver.net". All part of the record at > http://dsbl.org/listing?209.196.45.44 , by the way. That should be > sufficient information for your provider to track this down. Don't let > them off the hook until they either informed you (with an NTP calibrated > > time stamp and all technical detail) of when and how they handed off the > > message to you and thus prove you must have lost it since, or they come > clean and tell you why they discarded the message and what they will do > to prevent recurrence, or they retrieved it from a quaranteen folder. As > > a paying customer, there is no fourth option. And #2, silently ditching > your e-mail is not an option ISPs should get away with, as I'm sure > you'll agree. > > Please note that rejecting e-mail is fine; it's promising to deliver it > and then sweeping it under the carpet that is the problem here. >