|
|
You're in the
iis smtp nntp
group:SMTP delivery problem
iis smtp nntp:
mail only. This machine serves as a development machine for .NET, several databases, and software. The machine name is "asiolywadev" and the fully qualified domain name "asiolywadev.mydomain.net" is defined in SMTP's virtual properties. This machine resides at my location. We do have a valid MX record defined for our mail.mydomain.net mail sever at a completely different IP address at a different location in another state. The billing package builds an email and writes it to the "\mailroot\Pickup" directory. The email includes a CC: address. All seems to work fine except for some email addresses. In testing, att.net wouldn't accept email and it just sits in the queue, although the email was delivered to the TO: address. When I switch the addresses the att.net address never gets delivered. A look at the event logs show: +-----------------------------------+ Message delivery to the host '12.102.240.23' failed while delivering to the remote domain 'att.net' for the following reason: An SMTP protocol error occured. +------------------------------------+ The header of the email, built by the dbms application, looks like: Received: from mail pickup service by asiolywadev.mydomain.net with Microsoft SMTPSVC; Wed, 8 Nov 2006 00:30:37 -0800 Date: Wed, 08 Nov 2006 00:30 From: support@mydomain.net Subject: Statement from LAKEWOOD VIEW TWNHOME ASSN To: myaddress@mydomain.net Cc: myaddress@att.net MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-ID: <ASIOLYWADEVFRaqbC8w00000003@asiolywadev.mydomain.net> X-OriginalArrivalTime: 08 Nov 2006 08:30:37.0156 (UTC) FILETIME=[2A8C8240:01C70310] I ran the SMTPDiag tool and get: C:\Documents and Settings\me>d:\utilities\smtpdiag\smtpdiag "myaddress@my domain.net" "myaddress@att.net" /v Searching for Exchange external DNS settings. Computer name is ASIOLYWADEV. Failed to connect to the domain controller. Error: 8007054b Checking SOA for att.net. Checking external DNS servers. Checking internal DNS servers. Checking TCP/UDP SOA serial number using DNS server [4.2.2.2]. TCP test succeeded. UDP test succeeded. Serial number: 143 SOA serial number match: Passed. Checking local domain records. Starting TCP and UDP DNS queries for the local domain. This test will try to validate that DNS is set up correctly for inbound mail. This test can fail for 3 reasons. 1) Local domain is not set up in DNS. Inbound mail cannot be routed to local mailboxes. 2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail, but will affect outbound mail. 3) Internal DNS is unaware of external DNS settings. This is a valid configuration for certain topologies. Checking MX records using TCP: mydomain.net. MX: MAIL.mydomain.net (10) Checking MX records using UDP: mydomain.net. MX: MAIL.mydomain.net (10) Both TCP and UDP queries succeeded. Local DNS test passed. Checking remote domain records. Starting TCP and UDP DNS queries for the remote domain. This test will try to validate that DNS is set up correctly for outbound mail. This test can fail for 3 reasons. 1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows 2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP queries first, then fall back to TCP queries. 2) Internal DNS does not know how to query external domains. You must either use an external DNS server or configure DNS server to query external domains. 3) Remote domain does not exist. Failure is expected. Checking MX records using TCP: att.net. MX: gateway2.att.net (5) MX: gateway1.att.net (5) Checking MX records using UDP: att.net. MX: gateway1.att.net (5) MX: gateway2.att.net (5) Both TCP and UDP queries succeeded. Remote DNS test passed. A: gateway2.att.net [12.102.240.23] A: gateway1.att.net [204.127.134.23] Checking MX servers listed for myaddress@att.net. Connecting to gateway1.att.net [204.127.134.23] on port 25. Received: 550 unauthorized interface for 67.160.83.167 on mtiwmxc16 Error: Expected "220". Server is not accepting connections. Failed to submit mail to gateway1.att.net. Connecting to gateway2.att.net [12.102.240.23] on port 25. Received: 550 unauthorized interface for 67.160.83.167 on mtiwmxc18 Error: Expected "220". Server is not accepting connections. Failed to submit mail to gateway2.att.net. So, there seems to be some kind of problem with ATT.NET accepting email from our development server. I can't figure out why? Our production servers, running on Linux and using sendmail from within the local network where our corporate mail server resides, are able to send billings with CC:s to my att.net address without problems. Can anyone help? Thanks, Bill
http://forums.openhosting.com/viewtopic.php?p=708&sid=03a058d3793cb255c73178cae11763bc Seem to some weird blocking they are using. Apparently they think it's funny to to try and cause trouble instead of showing an error message when they block. Your best bet is trying to contact them and ask them about this. KL. "Bill H" <you@notreally.com> skrev i meddelandet news:RYKdnRMaovCOAczYnZ2dnUVZ_qGdnZ2d@comcast.com... [quoted text, click to view] > I've set up a Win 2K3 machine with the SMTP service running for outgoing > mail only. This machine serves as a development machine for .NET, several > databases, and software. The machine name is "asiolywadev" and the fully > qualified domain name "asiolywadev.mydomain.net" is defined in SMTP's > virtual properties. This machine resides at my location. > > We do have a valid MX record defined for our mail.mydomain.net mail sever > at a completely different IP address at a different location in another > state. > > The billing package builds an email and writes it to the > "\mailroot\Pickup" directory. The email includes a CC: address. All > seems to work fine except for some email addresses. In testing, att.net > wouldn't accept email and it just sits in the queue, although the email > was delivered to the TO: address. When I switch the addresses the att.net > address never gets delivered. > > A look at the event logs show: > > +-----------------------------------+ > Message delivery to the host '12.102.240.23' failed > while delivering to the remote domain 'att.net' for the > following reason: An SMTP protocol error occured. > +------------------------------------+ > > The header of the email, built by the dbms application, looks like: > > Received: from mail pickup service by asiolywadev.mydomain.net with > Microsoft SMTPSVC; > Wed, 8 Nov 2006 00:30:37 -0800 > Date: Wed, 08 Nov 2006 00:30 > From: support@mydomain.net > Subject: Statement from LAKEWOOD VIEW TWNHOME ASSN > To: myaddress@mydomain.net > Cc: myaddress@att.net > MIME-Version: 1.0 > Content-Type: text/plain; charset="iso-8859-1" > Message-ID: <ASIOLYWADEVFRaqbC8w00000003@asiolywadev.mydomain.net> > X-OriginalArrivalTime: 08 Nov 2006 08:30:37.0156 (UTC) > FILETIME=[2A8C8240:01C70310] > > I ran the SMTPDiag tool and get: > > C:\Documents and Settings\me>d:\utilities\smtpdiag\smtpdiag "myaddress@my > > domain.net" "myaddress@att.net" /v > > > > Searching for Exchange external DNS settings. > > Computer name is ASIOLYWADEV. > > Failed to connect to the domain controller. Error: 8007054b > > > > Checking SOA for att.net. > > Checking external DNS servers. > > Checking internal DNS servers. > > > > Checking TCP/UDP SOA serial number using DNS server [4.2.2.2]. > > TCP test succeeded. > > UDP test succeeded. > > Serial number: 143 > > SOA serial number match: Passed. > > > > Checking local domain records. > > Starting TCP and UDP DNS queries for the local domain. This test will try > to > > validate that DNS is set up correctly for inbound mail. This test can fail > for > > 3 reasons. > > 1) Local domain is not set up in DNS. Inbound mail cannot be routed to > > local mailboxes. > > 2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound > mail, > > but will affect outbound mail. > > 3) Internal DNS is unaware of external DNS settings. This is a valid > > configuration for certain topologies. > > Checking MX records using TCP: mydomain.net. > > MX: MAIL.mydomain.net (10) > > Checking MX records using UDP: mydomain.net. > > MX: MAIL.mydomain.net (10) > > Both TCP and UDP queries succeeded. Local DNS test passed. > > > > Checking remote domain records. > > Starting TCP and UDP DNS queries for the remote domain. This test will try > to > > validate that DNS is set up correctly for outbound mail. This test can > fail for > > 3 reasons. > > 1) Firewall blocks TCP/UDP queries which will block outbound mail. > Windows > > 2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP > > queries first, then fall back to TCP queries. > > 2) Internal DNS does not know how to query external domains. You must > > either use an external DNS server or configure DNS server to query > external > > domains. > > 3) Remote domain does not exist. Failure is expected. > > Checking MX records using TCP: att.net. > > MX: gateway2.att.net (5) > > MX: gateway1.att.net (5) > > Checking MX records using UDP: att.net. > > MX: gateway1.att.net (5) > > MX: gateway2.att.net (5) > > Both TCP and UDP queries succeeded. Remote DNS test passed. > > A: gateway2.att.net [12.102.240.23] > > A: gateway1.att.net [204.127.134.23] > > > > Checking MX servers listed for myaddress@att.net. > > Connecting to gateway1.att.net [204.127.134.23] on port 25. > > Received: > > 550 unauthorized interface for 67.160.83.167 on mtiwmxc16 > > > > Error: Expected "220". Server is not accepting connections. > > Failed to submit mail to gateway1.att.net. > > Connecting to gateway2.att.net [12.102.240.23] on port 25. > > Received: > > 550 unauthorized interface for 67.160.83.167 on mtiwmxc18 > > > > Error: Expected "220". Server is not accepting connections. > > Failed to submit mail to gateway2.att.net. > > > > > So, there seems to be some kind of problem with ATT.NET accepting email > from our development server. I can't figure out why? Our production > servers, running on Linux and using sendmail from within the local network > where our corporate mail server resides, are able to send billings with > CC:s to my att.net address without problems. > > Can anyone help? > > Thanks, > > Bill >
I'm checking with AT&T right now. Hopefully they'll come up with an answer.
Thanks, Bill [quoted text, click to view] "KL" <noname@nowhere.com> wrote in message news:%23p4EJ%23xAHHA.4212@TK2MSFTNGP02.phx.gbl... > > http://forums.openhosting.com/viewtopic.php?p=708&sid=03a058d3793cb255c73178cae11763bc > > Seem to some weird blocking they are using. Apparently they think it's > funny to to try and cause trouble instead of showing an error message when > they block. > > Your best bet is trying to contact them and ask them about this. > > KL. > > > "Bill H" <you@notreally.com> skrev i meddelandet > news:RYKdnRMaovCOAczYnZ2dnUVZ_qGdnZ2d@comcast.com... >> I've set up a Win 2K3 machine with the SMTP service running for outgoing >> mail only. This machine serves as a development machine for .NET, >> several databases, and software. The machine name is "asiolywadev" and >> the fully qualified domain name "asiolywadev.mydomain.net" is defined in >> SMTP's virtual properties. This machine resides at my location. >> >> We do have a valid MX record defined for our mail.mydomain.net mail sever >> at a completely different IP address at a different location in another >> state. >> >> The billing package builds an email and writes it to the >> "\mailroot\Pickup" directory. The email includes a CC: address. All >> seems to work fine except for some email addresses. In testing, att.net >> wouldn't accept email and it just sits in the queue, although the email >> was delivered to the TO: address. When I switch the addresses the att.net >> address never gets delivered. >> >> A look at the event logs show: >> >> +-----------------------------------+ >> Message delivery to the host '12.102.240.23' failed >> while delivering to the remote domain 'att.net' for the >> following reason: An SMTP protocol error occured. >> +------------------------------------+ >> >> The header of the email, built by the dbms application, looks like: >> >> Received: from mail pickup service by asiolywadev.mydomain.net with >> Microsoft SMTPSVC; >> Wed, 8 Nov 2006 00:30:37 -0800 >> Date: Wed, 08 Nov 2006 00:30 >> From: support@mydomain.net >> Subject: Statement from LAKEWOOD VIEW TWNHOME ASSN >> To: myaddress@mydomain.net >> Cc: myaddress@att.net >> MIME-Version: 1.0 >> Content-Type: text/plain; charset="iso-8859-1" >> Message-ID: <ASIOLYWADEVFRaqbC8w00000003@asiolywadev.mydomain.net> >> X-OriginalArrivalTime: 08 Nov 2006 08:30:37.0156 (UTC) >> FILETIME=[2A8C8240:01C70310] >> >> I ran the SMTPDiag tool and get: >> >> C:\Documents and Settings\me>d:\utilities\smtpdiag\smtpdiag "myaddress@my >> >> domain.net" "myaddress@att.net" /v >> >> >> >> Searching for Exchange external DNS settings. >> >> Computer name is ASIOLYWADEV. >> >> Failed to connect to the domain controller. Error: 8007054b >> >> >> >> Checking SOA for att.net. >> >> Checking external DNS servers. >> >> Checking internal DNS servers. >> >> >> >> Checking TCP/UDP SOA serial number using DNS server [4.2.2.2]. >> >> TCP test succeeded. >> >> UDP test succeeded. >> >> Serial number: 143 >> >> SOA serial number match: Passed. >> >> >> >> Checking local domain records. >> >> Starting TCP and UDP DNS queries for the local domain. This test will try >> to >> >> validate that DNS is set up correctly for inbound mail. This test can >> fail for >> >> 3 reasons. >> >> 1) Local domain is not set up in DNS. Inbound mail cannot be routed to >> >> local mailboxes. >> >> 2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound >> mail, >> >> but will affect outbound mail. >> >> 3) Internal DNS is unaware of external DNS settings. This is a valid >> >> configuration for certain topologies. >> >> Checking MX records using TCP: mydomain.net. >> >> MX: MAIL.mydomain.net (10) >> >> Checking MX records using UDP: mydomain.net. >> >> MX: MAIL.mydomain.net (10) >> >> Both TCP and UDP queries succeeded. Local DNS test passed. >> >> >> >> Checking remote domain records. >> >> Starting TCP and UDP DNS queries for the remote domain. This test will >> try to >> >> validate that DNS is set up correctly for outbound mail. This test can >> fail for >> >> 3 reasons. >> >> 1) Firewall blocks TCP/UDP queries which will block outbound mail. >> Windows >> >> 2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP >> >> queries first, then fall back to TCP queries. >> >> 2) Internal DNS does not know how to query external domains. You must >> >> either use an external DNS server or configure DNS server to query >> external >> >> domains. >> >> 3) Remote domain does not exist. Failure is expected. >> >> Checking MX records using TCP: att.net. >> >> MX: gateway2.att.net (5) >> >> MX: gateway1.att.net (5) >> >> Checking MX records using UDP: att.net. >> >> MX: gateway1.att.net (5) >> >> MX: gateway2.att.net (5) >> >> Both TCP and UDP queries succeeded. Remote DNS test passed. >> >> A: gateway2.att.net [12.102.240.23] >> >> A: gateway1.att.net [204.127.134.23] >> >> >> >> Checking MX servers listed for myaddress@att.net. >> >> Connecting to gateway1.att.net [204.127.134.23] on port 25. >> >> Received: >> >> 550 unauthorized interface for 67.160.83.167 on mtiwmxc16 >> >> >> >> Error: Expected "220". Server is not accepting connections. >> >> Failed to submit mail to gateway1.att.net. >> >> Connecting to gateway2.att.net [12.102.240.23] on port 25. >> >> Received: >> >> 550 unauthorized interface for 67.160.83.167 on mtiwmxc18 >> >> >> >> Error: Expected "220". Server is not accepting connections. >> >> Failed to submit mail to gateway2.att.net. >> >> >> >> >> So, there seems to be some kind of problem with ATT.NET accepting email >> from our development server. I can't figure out why? Our production >> servers, running on Linux and using sendmail from within the local >> network where our corporate mail server resides, are able to send >> billings with CC:s to my att.net address without problems. >> >> Can anyone help? >> >> Thanks, >> >> Bill >> > >
It seems AT&T requires any email sent to them be legitimate. Their
definition of legitimate is: 1) The "FROM:" address domain has to have a valid MX record associated with it; mail.mydomain.com will work fine for me@mydomain.com. 2) The IP address that the email is originating from has to match the main address of the A record for the above domain. So, my development SMTP server sent the email from 67.123.123.123 using the "FROM:" address of me@mydomain.com. However, the MX record for our company points to mail.mydomain.com and our A record for mail.mydomain.com points to IP address 209.123.123.123. Therefore, any emails from me@mydomain.com must come from an IP address of 209.123.123.{whatever}. [quoted text, click to view] "Bill H" <you@notreally.com> wrote in message ...
> I'm checking with AT&T right now. Hopefully they'll come up with an > answer. > > Thanks, > > Bill > > "KL" <noname@nowhere.com> wrote in message > news:%23p4EJ%23xAHHA.4212@TK2MSFTNGP02.phx.gbl... >> >> http://forums.openhosting.com/viewtopic.php?p=708&sid=03a058d3793cb255c73178cae11763bc >> >> Seem to some weird blocking they are using. Apparently they think it's >> funny to to try and cause trouble instead of showing an error message >> when they block. >> >> Your best bet is trying to contact them and ask them about this. >> >> KL. >> >> >> "Bill H" <you@notreally.com> skrev i meddelandet >> news:RYKdnRMaovCOAczYnZ2dnUVZ_qGdnZ2d@comcast.com... >>> I've set up a Win 2K3 machine with the SMTP service running for outgoing >>> mail only. This machine serves as a development machine for .NET, >>> several databases, and software. The machine name is "asiolywadev" and >>> the fully qualified domain name "asiolywadev.mydomain.net" is defined in >>> SMTP's virtual properties. This machine resides at my location. >>> >>> We do have a valid MX record defined for our mail.mydomain.net mail >>> sever at a completely different IP address at a different location in >>> another state. >>> >>> The billing package builds an email and writes it to the >>> "\mailroot\Pickup" directory. The email includes a CC: address. All >>> seems to work fine except for some email addresses. In testing, att.net >>> wouldn't accept email and it just sits in the queue, although the email >>> was delivered to the TO: address. When I switch the addresses the >>> att.net address never gets delivered. >>> >>> A look at the event logs show: >>> >>> +-----------------------------------+ >>> Message delivery to the host '12.102.240.23' failed >>> while delivering to the remote domain 'att.net' for the >>> following reason: An SMTP protocol error occured. >>> +------------------------------------+ >>> >>> The header of the email, built by the dbms application, looks like: >>> >>> Received: from mail pickup service by asiolywadev.mydomain.net with >>> Microsoft SMTPSVC; >>> Wed, 8 Nov 2006 00:30:37 -0800 >>> Date: Wed, 08 Nov 2006 00:30 >>> From: support@mydomain.net >>> Subject: Statement from LAKEWOOD VIEW TWNHOME ASSN >>> To: myaddress@mydomain.net >>> Cc: myaddress@att.net >>> MIME-Version: 1.0 >>> Content-Type: text/plain; charset="iso-8859-1" >>> Message-ID: <ASIOLYWADEVFRaqbC8w00000003@asiolywadev.mydomain.net> >>> X-OriginalArrivalTime: 08 Nov 2006 08:30:37.0156 (UTC) >>> FILETIME=[2A8C8240:01C70310] >>> >>> I ran the SMTPDiag tool and get: >>> >>> C:\Documents and Settings\me>d:\utilities\smtpdiag\smtpdiag >>> "myaddress@my >>> >>> domain.net" "myaddress@att.net" /v >>> >>> >>> >>> Searching for Exchange external DNS settings. >>> >>> Computer name is ASIOLYWADEV. >>> >>> Failed to connect to the domain controller. Error: 8007054b >>> >>> >>> >>> Checking SOA for att.net. >>> >>> Checking external DNS servers. >>> >>> Checking internal DNS servers. >>> >>> >>> >>> Checking TCP/UDP SOA serial number using DNS server [4.2.2.2]. >>> >>> TCP test succeeded. >>> >>> UDP test succeeded. >>> >>> Serial number: 143 >>> >>> SOA serial number match: Passed. >>> >>> >>> >>> Checking local domain records. >>> >>> Starting TCP and UDP DNS queries for the local domain. This test will >>> try to >>> >>> validate that DNS is set up correctly for inbound mail. This test can >>> fail for >>> >>> 3 reasons. >>> >>> 1) Local domain is not set up in DNS. Inbound mail cannot be routed >>> to >>> >>> local mailboxes. >>> >>> 2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound >>> mail, >>> >>> but will affect outbound mail. >>> >>> 3) Internal DNS is unaware of external DNS settings. This is a valid >>> >>> configuration for certain topologies. >>> >>> Checking MX records using TCP: mydomain.net. >>> >>> MX: MAIL.mydomain.net (10) >>> >>> Checking MX records using UDP: mydomain.net. >>> >>> MX: MAIL.mydomain.net (10) >>> >>> Both TCP and UDP queries succeeded. Local DNS test passed. >>> >>> >>> >>> Checking remote domain records. >>> >>> Starting TCP and UDP DNS queries for the remote domain. This test will >>> try to >>> >>> validate that DNS is set up correctly for outbound mail. This test can >>> fail for >>> >>> 3 reasons. >>> >>> 1) Firewall blocks TCP/UDP queries which will block outbound mail. >>> Windows >>> >>> 2000/NT Server requires TCP DNS queries. Windows Server 2003 will use >>> UDP >>> >>> queries first, then fall back to TCP queries. >>> >>> 2) Internal DNS does not know how to query external domains. You must >>> >>> either use an external DNS server or configure DNS server to query >>> external >>> >>> domains. >>> >>> 3) Remote domain does not exist. Failure is expected. >>> >>> Checking MX records using TCP: att.net. >>> >>> MX: gateway2.att.net (5) >>> >>> MX: gateway1.att.net (5) >>> >>> Checking MX records using UDP: att.net. >>> >>> MX: gateway1.att.net (5) >>> >>> MX: gateway2.att.net (5) >>> >>> Both TCP and UDP queries succeeded. Remote DNS test passed. >>> >>> A: gateway2.att.net [12.102.240.23] >>> >>> A: gateway1.att.net [204.127.134.23] >>> >>> >>> >>> Checking MX servers listed for myaddress@att.net. >>> >>> Connecting to gateway1.att.net [204.127.134.23] on port 25. >>> >>> Received: >>> >>> 550 unauthorized interface for 67.160.83.167 on mtiwmxc16 >>> >>> >>> >>> Error: Expected "220". Server is not accepting connections. >>> >>> Failed to submit mail to gateway1.att.net. >>> >>> Connecting to gateway2.att.net [12.102.240.23] on port 25. >>> >>> Received: >>> >>> 550 unauthorized interface for 67.160.83.167 on mtiwmxc18 >>> >>> >>> >>> Error: Expected "220". Server is not accepting connections. >>> >>> Failed to submit mail to gateway2.att.net. >>> >>> >>> >>> >>> So, there seems to be some kind of problem with ATT.NET accepting email
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |