On Thursday, March 8 at 02:27 PM, quoth Russel Oliver:
I have a recent problem sending mail to verizon.net. This all
started about a month ago and I am getting nowhere at all trying to
deal with verizon. (surprising I know)
Oh, fun. I've had the displeasure of dealing with them before. Good
luck!
I know verizon connects back to check if it can deliver to the
senders account before it accepts any mail
They do? That's new.
and I have that functionality in place ...
?
Unless I'm missing something, I would certainly hope so.
2007-03-08 14:40:52.069083500 delivery 138542: deferral:
Connected_to_206.46.232.11_but_sender_was_rejected./Remote_host_said:_450_Requested_mail_action_not_taken-Try_later:sv22pub.verizon.net/
Read that carefully. They're not saying they couldn't verify the
sender by talking to YOUR server, they're saying that 206.46.232.11
didn't like the sender for some reason, and unless you own
relay.verizon.net (aka 206.46.232.11), that's not you.
In general, this message from them usually means "we think your
message is spam, so why don't you keep it." (Say it in a snooty voice,
and you'll get the sentiment a bit more accurately.) It doesn't mean
something simple like "we couldn't verify your sender when we
contacted your server", it means "somewhere in the bowels of our
anti-spam heuristics, this message triggered a no-no rule."
The only real useful information I can give you is that Verizon places
HUGE amounts of stock in SPF, so you may be able to help yourself
somewhat by publishing SPF records for your sender's domain (assuming
you own that domain).
The only way I ever got results was by having my client, who was also
a Verizon client, spend an afternoon climbing through their
tech-support chain of command.
Good luck!
~Kyle
--
As we enjoy great Advantages from the Inventions of others we should
be glad of an Opportunity to serve others by any Invention of ours,
and this we should do freely and generously.
-- Benjamin Franklin
pgp3bhUIGPxIh.pgp
Description: PGP signature
|