|
Home > Archive > IIS and SMTP > February 2007 > verizon.net rejecting mail
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
verizon.net rejecting mail
|
|
| geek-y-guy 2007-02-20, 1:17 pm |
| Hi All: I colo a 2003 Web Edition webserver for a client which has a static
IP and single domain on it. They send mail from the website using CDOSYS and
the SMTP Service. THere's a valid PTR record for the webserver's IP. The
domain has an MX record which has nothing to do with this server.
Verizon is consistently rejecting mail from the server, and sent me this
checklist to verify:
1.) Please ensure that your server is accepting mail from
206.46.252.0/24.
2.) Please ensure that your server accepts a Null Mail From: command
e.g. Mail From:<>.
3.) Please ensure your mail server responds to the SMTP commands within
30 seconds.
4.) Please ensure the from address used is a valid email address that is
accepted by the MX server for that domain.
5.) Please ensure you have a proper MX record.
Does any of this apply to the webserver? The SMTP Service wouldn't have
anything to do with the functionality above, right?
Do I need to use a smart host instead of sending directly from the server to
get around verizon's restrictions?
| |
| PeterD 2007-02-20, 7:16 pm |
| On Tue, 20 Feb 2007 12:22:03 -0500, "geek-y-guy" <noone@nowhere.org>
wrote:
>Hi All: I colo a 2003 Web Edition webserver for a client which has a static
>IP and single domain on it. They send mail from the website using CDOSYS and
>the SMTP Service. THere's a valid PTR record for the webserver's IP. The
>domain has an MX record which has nothing to do with this server.
>
>Verizon is consistently rejecting mail from the server, and sent me this
>checklist to verify:
>
>1.) Please ensure that your server is accepting mail from
>206.46.252.0/24.
>
>2.) Please ensure that your server accepts a Null Mail From: command
>e.g. Mail From:<>.
>
>3.) Please ensure your mail server responds to the SMTP commands within
>30 seconds.
>
>4.) Please ensure the from address used is a valid email address that is
>accepted by the MX server for that domain.
>
>5.) Please ensure you have a proper MX record.
>
>Does any of this apply to the webserver? The SMTP Service wouldn't have
>anything to do with the functionality above, right?
Huh? Aren't you asking why your SMTP doesn't work with Verizon
addresses? Or did I miss something?
Did you chekc each of these items?
>
>Do I need to use a smart host instead of sending directly from the server to
>get around verizon's restrictions?
>
What restrictions? All they say is have your email server setup
properly...
| |
| geek-y-guy 2007-02-20, 7:16 pm |
|
--
"PeterD" <peter2@hipson.net> wrote in message
news:2b3nt2hfev7f5ihn8ffh9cmg9l2o6mvqoe@
4ax.com...
> On Tue, 20 Feb 2007 12:22:03 -0500, "geek-y-guy" <noone@nowhere.org>
> wrote:
>
>
> Huh? Aren't you asking why your SMTP doesn't work with Verizon
> addresses? Or did I miss something?
>
> Did you chekc each of these items?
The webserver is not a mailserver. There's no incoming SMTP enabled, so it
wouldn't meet any of the requirements above. There's an MX record for the
domain, but it has nothing to do with this server.
>
>
> What restrictions? All they say is have your email server setup
> properly...
But this isn't the mailserver for the domain, it's just a webserver that
sends out emails when someone fills in a form on the website.
| |
| PeterD 2007-02-21, 1:18 pm |
| On Tue, 20 Feb 2007 19:35:28 -0500, "geek-y-guy" <noone@nowhere.org>
wrote:
| |
| PeterD 2007-02-21, 1:18 pm |
| On Tue, 20 Feb 2007 19:35:28 -0500, "geek-y-guy" <noone@nowhere.org>
wrote:
>
>
>--
>
>The webserver is not a mailserver. There's no incoming SMTP enabled, so it
>wouldn't meet any of the requirements above. There's an MX record for the
>domain, but it has nothing to do with this server.
>
Duh... did you think *HOW* the web server sends emails? It uses a SMTP
server, that's how!
>
>But this isn't the mailserver for the domain, it's just a webserver that
>sends out emails when someone fills in a form on the website.
>
And *WHAT* SMTP server is the web server using to send these emails?
| |
| geek-y-guy 2007-02-21, 1:18 pm |
| >>The webserver is not a mailserver. There's no incoming SMTP enabled, so it
>
> Duh... did you think *HOW* the web server sends emails? It uses a SMTP
> server, that's how!
I understand that...thanks for the LART.
>
>
> And *WHAT* SMTP server is the web server using to send these emails?
So if I understand you correctly, I would have to allow incoming SMTP on
TCP/IP 25 to the webserver, so that Verizon can verify the origination of
the email?
Up until now, the only ports allowed from the firewall to the IP of the
webserver are 80 and 443.
I'd rather keep my servers as locked down as possible, so it seems like I
would have to route mail from this server through a smarthost...no big deal,
but a PITA to manage since I have a lot of servers to deal with.
| |
| PeterD 2007-02-21, 7:16 pm |
| On Wed, 21 Feb 2007 10:58:01 -0500, "geek-y-guy" <noone@nowhere.org>
wrote:
>
>I understand that...thanks for the LART.
>
>So if I understand you correctly, I would have to allow incoming SMTP on
>TCP/IP 25 to the webserver, so that Verizon can verify the origination of
>the email?
You don't get it, and I'm not able to communicate this to you: THE WEB
SERVER IS NOT SENDING THE EMAIL, THE SMTP SERVER IS. Whichever SMTP
server your web server is tied to is the one you need to work on. Web
servers DO NOT SEND EMAIL. Ever.
>
>Up until now, the only ports allowed from the firewall to the IP of the
>webserver are 80 and 443.
>
>I'd rather keep my servers as locked down as possible, so it seems like I
>would have to route mail from this server through a smarthost...no big deal,
>but a PITA to manage since I have a lot of servers to deal with.
>
|
|
|
|
|