custumer support of


New Email not delivers mail to their costumer coming from telecomitalia's mail service **** That mail returns to sender with message "delivery time expired"
Failed; 4.4.7 (delivery time expired) I have been asking 'costumer support' of several times to explain this issue to me, however they DO NOT REPLY.
What is going on ?
thanks for help
source code of returned mail hereafter ,
(user names replaced by *********) :

From - Sun Jun 02 08:10:28 2013 X-Account-Key: account2 X-UIDL: 12496 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 X-Mozilla-Keys: Return-Path: <> Received: from ( by ( id 51A621BA001C07B9 for *********; Sat, 1 Jun 2013 21:42:08 +0200 Received: by ( id 5123901C07BC8EC9 for ********; Sat, 1 Jun 2013 21:42:08 +0200 From: Mail Delivery Service <> Subject: Delivery Status Notification To: ********** Date: Sat, 1 Jun 2013 21:42:08 +0200 Message-ID: <> X-CP-Transaction-ID: 5123901C07BBD6F8 X-CP-For: ********* MIME-Version: 1.0 Content-Type: Multipart/Report; report-type=delivery-status; boundary="========/5123901C07BBD6F8/" X-Antivirus: avast! (VPS 130601-0, 01.06.2013), Inbound message X-Antivirus-Status: Clean This multi-part MIME message contains a Delivery Status Notification. If you can see this text, your mail client may not be able to understand MIME formatted messages or DSNs (see RFC 2045 through 2049 for general MIME information and RFC 1891 through 1894 for DSN specific information). --========/5123901C07BBD6F8/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit - These recipients of your message have been processed by the mail server: *******; Failed; 4.4.7 (delivery time expired) --========/5123901C07BBD6F8/ Content-Type: Message/Delivery-Status Original-Envelope-ID: <> Reporting-MTA: dns; Received-from-MTA: dns; [] ( Arrival-Date: Sat, 1 Jun 2013 20:41:27 +0200 Original-Recipient: rfc822;***** Final-Recipient: rfc822; ***** Action: Failed Status: 4.4.7 (delivery time expired) --========/5123901C07BBD6F8/ Content-Type: Message/RFC822 Return-Path: <***********> Received: from [] ( by ( (authenticated as *********** id 5123901C07BBD6F8 for *****; Sat, 1 Jun 2013 20:41:27 +0200 Message-ID: <> Date: Sat, 01 Jun 2013 20:41:25 +0200 From: =?ISO-8859-15?Q?************= <************> Reply-To: ************** User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: ***** Subject: test aus alice Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 130601-0, 01.06.2013), Outbound message X-Antivirus-Status: Clean test aus alice --========/5123901C07BBD6F8/

EQ Admin

EQ Forum Admin
Staff member
Re: costumer support of


Failed Status: 4.4.7 (delivery time expired) - It looks like is dropping connections from your IP address at a network / firewall or some other level that isn't rejecting the connection with a proper 4xx or 5xx smtp code. - MX Lookup Tool - Check your DNS MX Records online - MxToolbox - A good place to start is getting off the CBL which is used as part of the Spamhaus XBL. Fix this problem and it might fix your problem with delivering to It will definitely help with at least some other ISP's.

Did you change any of the IP addresses in the bounce message? I have a hard time believing something wrote an IP in the headers in the form x.x.060.x , that's unusual. It looks like I really need to be checking: 86235 IN A

Lots of blacklistings! - MX Lookup Tool - Check your DNS MX Records online - MxToolbox This better explains why you're flat out blocked. If many abuse reports and traffic came from your IP space it's easier to block the IP address(es) than waste computing resources content filtering the spam.

Focus on getting off SORBS SPAM first, then work on any others that are free and possible to get removed from. I do not recommend paying to get off a blacklist. Before you can get off SORBS you'll need to identify the source of the problem and fix it. Probable causes of the spam problem for an ISP SMTP relay include:

  • Compromised accounts being used to authenticate and relay spam
  • On network abusers and bulk email senders that are allowed to send spam because they have an IP owned by
  • Smart hosting of spam/bounces by your customers through your SMTP relays
  • Relaying of spam via compromised web site forms that are configured to use your SMTP relays as their outgoing mail server.
  • If you have never done a cleanup you might have some customers who are actually spammers and using your mail servers directly to send spam.
Also, make sure your SMTP auth isn't broken and allowing anyone to authenticate and relay spam through your relays.


New Email
hello popowich

thanks for your interest to my problem. However the technical details you describe are somehow above my knowledge and experience.

I have been trying several times to send a mail to my box at using my mailbox at which is telecomitalia. These mails returned with "Failed; 4.4.7 (delivery time expired)"
I then sent these bounced mails to support of asking for their reason of bouncing my mail back to sender. This was done in using another (clean) mailserver and confirmation of DELIVERY was given by But NO answer arrived from to my question.
Why don't they reply ?

The smtp servers of alice being used were,, All these resulted blacklisted days before. I checked again just now, and they result CLEAN !!!!!!

I did not change any IP address in the bounced mail, just cancelled names.
That strange leads to San Jose in the US, (possibly to what does that mean ?
and how is this related to alice smtp server ?). goes to of telecomitalia in Milano, this is correct.

All what I need is to get a response of saying why my mails were not deliverd to the given address at but returned to sender.
Can you provide for them responding to me ?

I am not experienced in looking deeper into the matter by using the MX-Toolbox-instruments.

thanks anyhow,

EQ Admin

EQ Forum Admin
Staff member
Hi Hans,

Apologies, for some reason I thought in your original reply that you represented Your ISP needs to do a better job of blocking and relaying spam. If that issue gets fixed, most likely your issue with sending to will be fixed.

If you did get a reply from, which I doubt would happen, they would most likely tell you that is blocked for allowing too much spam to sent through their mail servers.

I don't think it's directly related to your problem, but does not have good customer service feedback on this forum. You can leave customer service feedback for here if you hope they will read it someday, but like I said I believe the real issue is that needs to do a better job of not allowing spam to be sent through their mail servers.