I am having problems with emailing some people with accounts at BTConnect from your servers - apparently this has to do with whether your SMTP server will retry sending messages. BTConnect claim your mail servers are not set up right....
Do your SMTP servers retry sending messages? Can they be set to retry 2/3 times?
please see the transcript below for more information
-----
QUOTE
(Stewart) - 04/01/2005 02:08 PM
Thank you for your enquiry Mr Mulady
This is correct, the error 451 confirms that the ISP you are using is not RFC compliant. This is due to a security measure, which we have recently introduced on our mail servers to cut down the amount of spam received by our customers.
When another Internet Service Provider's server contacts our mail server to deliver email for one of our customers, our server will initially reject the request. Any standards-compliant mail server which is set up correctly will simply retry sending the email, upon which it will be accepted by our server (this only needs to be done the first time that each server attempts to deliver an email - subsequent emails will go through unimpeded), but automatic spam engines are generally unable to cope with this, and do not re-attempt delivery.
For the vast majority of other Internet Service Providers, this has not caused any problems. However, there are some ISP’s that are unable to send emails to our users, as they are not RFC compliant. We are still gathering information on this situation, however it does not appear at this stage that there is a fault with any of our servers.
Kind regards, Stewart Grassie
BT Business Support
Customer - 04/01/2005 01:58 PM
In what way does my choice of *INBOUND* SMTP route affect my ability to send mail to BTConnect customers?
The routing used by inbound mail has no bearing upon mail sent from our webserver to BTConnect customers. This mail hadn't even touched our mail system until it was returned to us as undeliverable.
You say that 123-Reg is not RFC compliant, which RFC and in what way are they not compliant? And how does this affect mail sent from a 3rd party webserver direct to the BTConnect MX servers?
Here is a sample of emails bounced back from Btconnect.com
**SNIP**
----------------------------
---------------------------- Original Message
----------------------------
From: "Mail Delivery System" <Mailer-Daemon@server26.fastbighost.com>
Date: Tue, March 29, 2005 8:51 am
To: kentbusi@server26.fastbighost.com
------------------------------------------------------------------------
--
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
terry.osborne@btconnect.com
SMTP error from remote mailer after RCPT
TO:<terry.osborne@btconnect.com>: host ibmr.btconnect.com
[194.73.73.216]: 451 <terry.osborne@btconnect.com>... Requested mail action not taken: mailbox unavailable: retry timeout exceeded
neil-hutchison@btconnect.com
SMTP error from remote mailer after RCPT
TO:<neil-hutchison@btconnect.com>: host ibmr.btconnect.com
[194.73.73.216]: 451 <neil-hutchison@btconnect.com>... Requested mail action not taken: mailbox unavailable: retry timeout exceeded
------ This is a copy of the message, including all the headers. ------
Return-path: <kentbusi@server26.fastbighost.com>
Received: from kentbusi by server26.fastbighost.com with local (Exim
4.44)
id 1DGCQD-0002xI-7g; Tue, 29 Mar 2005 08:50:01 +0000
To: admin@kentbusinessclub.co.uk
Date: Tue, 29 Mar 2005 08:50:01 +0000
From: KentBusinessClub Offers Update <auto@kentbusinessclub.co.uk>
Message-ID: <46983f0d6b4fd9bd3c34c851aa5c996a@localhost.localdomain>
X-Priority: 3
X-Mailer: PHPMailer [version 1.72]
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="b1_46983f0d6b4fd9bd3c34c851aa5c996a"
Sender: <kentbusi@server26.fastbighost.com>
--b1_46983f0d6b4fd9bd3c34c851aa5c996a
Content-Type: multipart/alternative;
boundary="b2_46983f0d6b4fd9bd3c34c851aa5c996a"
--b2_46983f0d6b4fd9bd3c34c851aa5c996a
Content-Type: text/plain; charset = "iso-8859-1"
Content-Transfer-Encoding: 8bit
KentBusinessClub.co.uk - you to the power of
--------------------------------------------
There have been no new offers in the past seven days, but we will let you know when there have been new offers added.
If you do not wish to recieve these emails anymore please log into the www.KentBusinessClub.co.uk site and change your profile settings.
--b2_46983f0d6b4fd9bd3c34c851aa5c996a
Content-Type: text/html; charset = "iso-8859-1"
Content-Transfer-Encoding: 8bit
**SNIP**
----------------------------
Can you please tell us why these emails are being bounced?, what needs changing to stop them bouncing?, and who's job it is to change it please?
-----Original Message-----
From: BT Business Support [mailto:business.support@btbusinessoffice.com]
Sent: 01 April 2005 12:10
To: iain mulady
website - www... [Incident: 050331-000033]
Thank you for contacting BT Business.
This message is being sent in response to your recent enquiry to our Technical Support team.
If you would like to contact the Technical Support team again, simply revisit BT Business Help & support, at:
http://www.btbusinessoffice.com/help.
Kind regards,
BT Business Support
Search results
---------------------------------------------------------------
Hiya, I work for a company that runs a small business community website
- www...
Discussion Thread
---------------------------------------------------------------
(Stewart) - 04/01/2005 11:09 AM
Thank you for your enquiry Mr Mulady
>From looking into this issue, I have found you are hosted with 123-REG.
The reason you are unable to send to btconnect.com customers may be due the ISP you are using to forward your emails is not RFC Compliant.
RFC is an acronym for Request For Comments. The Internet Engineering Task Force makes requests to administrators and users about things like how should a mail server interact with other mail servers. The responses are compiled into a standard that becomes known as a RFC. Specific RFC have a number, for example RFC 821 is that standard that governs how mail servers should interact.
Due to the fact that viruses often are programmed without re
==================== text File Attachment ==================== Attachment -1073787203.txt, 7446 bytes, discarded
(Stewart) - 04/01/2005 11:09 AM
Thank you for your enquiry Mr Mulady
From looking into this issue, I have found you are hosted with 123-REG. The reason you are unable to send to btconnect.com customers may be due the ISP you are using to forward your emails is not RFC Compliant.
RFC is an acronym for Request For Comments. The Internet Engineering Task Force makes requests to administrators and users about things like how should a mail server interact with other mail servers. The responses are compiled into a standard that becomes known as a RFC. Specific RFC have a number, for example RFC 821 is that standard that governs how mail servers should interact.
Due to the fact that viruses often are programmed without regard to RFC's and spammers tend to buy poorly made software that also fails to follow RFC's it has become common practice to refuse connections from mail servers that are not RFC compliant.
This is the scenario just now, it is purely a step to combat unsolicited spam appearing in your inbox.
The best course of action would be to contact your ISP to inform them of this problem.
If in the future you need further assistance please feel free to search the knowledge base or email our BT Business Support team again at www.btbusinessoffice.com/help.
Kind regards, Stewart Grassie
BT Business Support
Customer - 03/31/2005 09:13 AM
Hiya,
I work for a company that runs a small business community website - www.kentbusinessclub.co.uk - we are having great problems emailing users of @btconnect.com accounts
They are having no problems with their email otherwise so I was wondering if this is to do with junk-mail filters at your servers blocking our email address?
Any help much appreciated,
Regards,
Iain
iain@kentbusinessclub.co.uk
iain@broadbasemarketing.co.uk
Thank you for your enquiry Mr Mulady
This is correct, the error 451 confirms that the ISP you are using is not RFC compliant. This is due to a security measure, which we have recently introduced on our mail servers to cut down the amount of spam received by our customers.
When another Internet Service Provider's server contacts our mail server to deliver email for one of our customers, our server will initially reject the request. Any standards-compliant mail server which is set up correctly will simply retry sending the email, upon which it will be accepted by our server (this only needs to be done the first time that each server attempts to deliver an email - subsequent emails will go through unimpeded), but automatic spam engines are generally unable to cope with this, and do not re-attempt delivery.
For the vast majority of other Internet Service Providers, this has not caused any problems. However, there are some ISP’s that are unable to send emails to our users, as they are not RFC compliant. We are still gathering information on this situation, however it does not appear at this stage that there is a fault with any of our servers.
Kind regards, Stewart Grassie
BT Business Support
Customer - 04/01/2005 01:58 PM
In what way does my choice of *INBOUND* SMTP route affect my ability to send mail to BTConnect customers?
The routing used by inbound mail has no bearing upon mail sent from our webserver to BTConnect customers. This mail hadn't even touched our mail system until it was returned to us as undeliverable.
You say that 123-Reg is not RFC compliant, which RFC and in what way are they not compliant? And how does this affect mail sent from a 3rd party webserver direct to the BTConnect MX servers?
Here is a sample of emails bounced back from Btconnect.com
**SNIP**
----------------------------
---------------------------- Original Message
----------------------------
From: "Mail Delivery System" <Mailer-Daemon@server26.fastbighost.com>
Date: Tue, March 29, 2005 8:51 am
To: kentbusi@server26.fastbighost.com
------------------------------------------------------------------------
--
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
terry.osborne@btconnect.com
SMTP error from remote mailer after RCPT
TO:<terry.osborne@btconnect.com>: host ibmr.btconnect.com
[194.73.73.216]: 451 <terry.osborne@btconnect.com>... Requested mail action not taken: mailbox unavailable: retry timeout exceeded
neil-hutchison@btconnect.com
SMTP error from remote mailer after RCPT
TO:<neil-hutchison@btconnect.com>: host ibmr.btconnect.com
[194.73.73.216]: 451 <neil-hutchison@btconnect.com>... Requested mail action not taken: mailbox unavailable: retry timeout exceeded
------ This is a copy of the message, including all the headers. ------
Return-path: <kentbusi@server26.fastbighost.com>
Received: from kentbusi by server26.fastbighost.com with local (Exim
4.44)
id 1DGCQD-0002xI-7g; Tue, 29 Mar 2005 08:50:01 +0000
To: admin@kentbusinessclub.co.uk
Date: Tue, 29 Mar 2005 08:50:01 +0000
From: KentBusinessClub Offers Update <auto@kentbusinessclub.co.uk>
Message-ID: <46983f0d6b4fd9bd3c34c851aa5c996a@localhost.localdomain>
X-Priority: 3
X-Mailer: PHPMailer [version 1.72]
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="b1_46983f0d6b4fd9bd3c34c851aa5c996a"
Sender: <kentbusi@server26.fastbighost.com>
--b1_46983f0d6b4fd9bd3c34c851aa5c996a
Content-Type: multipart/alternative;
boundary="b2_46983f0d6b4fd9bd3c34c851aa5c996a"
--b2_46983f0d6b4fd9bd3c34c851aa5c996a
Content-Type: text/plain; charset = "iso-8859-1"
Content-Transfer-Encoding: 8bit
KentBusinessClub.co.uk - you to the power of
--------------------------------------------
There have been no new offers in the past seven days, but we will let you know when there have been new offers added.
If you do not wish to recieve these emails anymore please log into the www.KentBusinessClub.co.uk site and change your profile settings.
--b2_46983f0d6b4fd9bd3c34c851aa5c996a
Content-Type: text/html; charset = "iso-8859-1"
Content-Transfer-Encoding: 8bit
**SNIP**
----------------------------
Can you please tell us why these emails are being bounced?, what needs changing to stop them bouncing?, and who's job it is to change it please?
-----Original Message-----
From: BT Business Support [mailto:business.support@btbusinessoffice.com]
Sent: 01 April 2005 12:10
To: iain mulady
website - www... [Incident: 050331-000033]
Thank you for contacting BT Business.
This message is being sent in response to your recent enquiry to our Technical Support team.
If you would like to contact the Technical Support team again, simply revisit BT Business Help & support, at:
http://www.btbusinessoffice.com/help.
Kind regards,
BT Business Support
Search results
---------------------------------------------------------------
Hiya, I work for a company that runs a small business community website
- www...
Discussion Thread
---------------------------------------------------------------
(Stewart) - 04/01/2005 11:09 AM
Thank you for your enquiry Mr Mulady
>From looking into this issue, I have found you are hosted with 123-REG.
The reason you are unable to send to btconnect.com customers may be due the ISP you are using to forward your emails is not RFC Compliant.
RFC is an acronym for Request For Comments. The Internet Engineering Task Force makes requests to administrators and users about things like how should a mail server interact with other mail servers. The responses are compiled into a standard that becomes known as a RFC. Specific RFC have a number, for example RFC 821 is that standard that governs how mail servers should interact.
Due to the fact that viruses often are programmed without re
==================== text File Attachment ==================== Attachment -1073787203.txt, 7446 bytes, discarded
(Stewart) - 04/01/2005 11:09 AM
Thank you for your enquiry Mr Mulady
From looking into this issue, I have found you are hosted with 123-REG. The reason you are unable to send to btconnect.com customers may be due the ISP you are using to forward your emails is not RFC Compliant.
RFC is an acronym for Request For Comments. The Internet Engineering Task Force makes requests to administrators and users about things like how should a mail server interact with other mail servers. The responses are compiled into a standard that becomes known as a RFC. Specific RFC have a number, for example RFC 821 is that standard that governs how mail servers should interact.
Due to the fact that viruses often are programmed without regard to RFC's and spammers tend to buy poorly made software that also fails to follow RFC's it has become common practice to refuse connections from mail servers that are not RFC compliant.
This is the scenario just now, it is purely a step to combat unsolicited spam appearing in your inbox.
The best course of action would be to contact your ISP to inform them of this problem.
If in the future you need further assistance please feel free to search the knowledge base or email our BT Business Support team again at www.btbusinessoffice.com/help.
Kind regards, Stewart Grassie
BT Business Support
Customer - 03/31/2005 09:13 AM
Hiya,
I work for a company that runs a small business community website - www.kentbusinessclub.co.uk - we are having great problems emailing users of @btconnect.com accounts
They are having no problems with their email otherwise so I was wondering if this is to do with junk-mail filters at your servers blocking our email address?
Any help much appreciated,
Regards,
Iain
iain@kentbusinessclub.co.uk
iain@broadbasemarketing.co.uk