Topic: Email issues

[geoff]

Hi, All,

I am getting errors as below. Any ideas?

Hi. This is the qmail-send program at netsupport.net.au.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<another@theirdomain.com.au>:
Connected to 203.12.160.34 but connection died. (#4.4.2)
I'm not going to try again; this message has been in the queue too long.

Any suggestions welcomed

[chris burnat]

You need to tell us more about what you are trying to do, what you expect,  and how is your system/network set up:
- How is your server configured? 
- How do you send this type of email ?

Note: netsupport.net.au MX records are with TPG, an ISP in Australia, so I assume that your server is not operating as a mail server, and that this message comes from qmail-sent at TPG.   The recipient also appears to be an account somewhere at TPG according to the IP address included in the message, pointing to an issue with this ISP perhaps?

[geoff]

TPG have just come back to me to tell me my IP address has been blacklisted!!

I have no idea why, nor do they. My SMEServer has not been relaying, nor have I been sending bulk emails or spam, and I am at a complete loss as to why I am on the blacklist.

Thank you for taking the time to reply.

Another lost morning .......

[chris burnat]

Another lost morning .......

Not really, at least now you know what the score is.
I am with TPG myself, and know for a fact that a number of their IP range are included in a number of RBL Lists.  This may be your problem.   Do you have a static or dynamic address?   Best would be to purchase a range of static IP addresses (you can get them in lot of 4, check their site) and pin down your server in safe water.  If you do this, ensure that NAT is disabled in their ADSL router/modem, this is because their WAN address may be listed, but the static IP address you will assign to your server will most likely be clean.  I have recently setup 6 clients in this way and there has ben no issues (after I disabled NAT that is...)
We learn something everyday.

[geoff]

I have a Static IP which continues to get the 'connection died' error when I send through TPG, but a few emails are getting out, albeit slowly,  when I try to send direct.

The following was received from TPG:

From the information provided in our mail logs (sample has been provided
above), we believe that the problem is relating to timeout settings as
configured on your mail server. Either they are too short or the messages
are taking too long to be sent.

Could you please check the configuration of your mail server so that it
conforms to the minimum required timeout values as per RFC 2821? They are
provided below:

Initial 220 Message: 5 minutes
MAIL Command: 5 minutes
RCPT Command: 5 minutes
DATA Initiation: 2 minutes
Data Block: 3 minutes
DATA Termination: 10 minutes.
An SMTP server SHOULD have a timeout of at least 5 minutes while it
   is awaiting the next command from the sender.


As my SME Server is 'out of the box' and has no mods at all, I can only assume that it conforms with TPG's requirements, particulalry as it has always 'just worked' up until about a week and a half ago.

Any help or comments appreciated.

[chris burnat]

Time to go to the Bugtracker, please fill a report at Bugzilla and outline what is your problem, including the information received from your ISP.  Also provide details of your server, version number and date of last update if applicable.    The Devs will follow-up I am sure.
Thanks for doing this.
chris

[geoff]

Thanks, Chris, really appreciated.

At this stage I don't think this is an SME issue. I went into Spamhaus.Org and removed my IP from the RBL list and reconfigured SME to send out directly which seems successful except for the Optus-like people who will not accept email directly from a dynamic address. (I know I have a 'Static' IP but it is a dynamic address that does not change ....  )

I still have 98 messages in the queue, down from 144. If I use the TPG MailServers the error message changes to "421 4.3.2 Too many open connections". Once the MailQueue gets down to manageable proportions I'll go back through TPG and report.

Thanks again for your help.