Outgoing email problem

zappaDPJ · Apr 21, 2009, 05:19:13

I've trying to send out some emails and although I think one or two got through (at least I hope they did), the majority are producing the following error.

QuoteThe message could not be sent. The authentication setting might not be correct for your outgoing e-mail [SMTP] server. For help solving this problem, go to Help, search for "Troubleshoot Windows Mail", and read the "I'm having problems sending e-mail" section. If you need help determining the proper server settings, please contact your e-mail service provider.

The rejected e-mail address was '********@idnet.com'. Subject 'Test Mail', Account: 'pop3.idnet.com', Server: 'smtp.idnet.com', Protocol: SMTP, Server Response: '452 4.3.1 Insufficient system storage', Port: 25, Secure(SSL): No, Server Error: 452, Error Number: 0x800CCC78

The fact that a couple got through seems to indicate this is a problem with IDNet's mail server. I'd be grateful if someone could take a look at this as a matter of urgency.

Glenn · Apr 21, 2009, 06:41:35

Zappa, if the problem is still ongoing, then I would suggest that you give support a call when they open.

Glenn · Apr 21, 2009, 07:30:56

My mails are taking approximately 50 minutes to arrive.

Rik · Apr 21, 2009, 08:51:45

No delays here now. Martin was working on the servers around 4am, so it's possible that there was a deluge of spam which he's cleared.

Sebby · Apr 21, 2009, 13:07:16

So he still hasn't got himself a desk?

Simon · Apr 21, 2009, 13:50:26

I'm more worried that he hasn't got himself a bed!

zappaDPJ · Apr 21, 2009, 14:52:50

It appears the problem has been fixed.

zappaDPJ · Apr 21, 2009, 17:41:06

Or maybe not. The test mail that I sent to myself at around 5.30am this morning (as per the error message posted above) has just arrived!

There seems to be some very odd times displayed in the mail details.

QuoteReturn-Path: <********@idnet.com>
Delivered-To: ********@idnet.com
Received: from smtp-out.idnet.com (smtp.idnet.com [212.69.36.238])
   by mail.idnet.com (Postfix) with ESMTP id 8D9D411B838
   for <********@idnet.com>; Tue, 21 Apr 2009 14:01:47 +0100 (BST)
Received: from localhost (unknown [127.0.0.1])
   by smtp-out.idnet.com (Postfix) with ESMTP id 8313316F9D2
   for <********@idnet.com>; Tue, 21 Apr 2009 13:01:47 +0000 (UTC)
X-Virus-Scanned: amavisd-new at idnet.com
Received: from smtp-out.idnet.com ([127.0.0.1])
   by localhost (smtp-out.idnet.com [127.0.0.1]) (amavisd-new, port 10024)
   with LMTP id J+SlSKA+VMDA for <zappadpj@idnet.com>;
   Tue, 21 Apr 2009 14:01:43 +0100 (BST)
Received: from zappaDPJ1 (cust215-dsl91-135-7.idnet.net [91.135.7.215])
   by smtp-out.idnet.com (Postfix) with SMTP id BA71D16FB82
   for <********@idnet.com>; Tue, 21 Apr 2009 14:00:35 +0100 (BST)
Message-ID: <16995ECF484F4676A21A992E94DD95D1@zappaDPJ1>
From: "zappaDPJ" <********@idnet.com>
To: <********@idnet.com>
Subject: Test Mail
Date: Tue, 21 Apr 2009 05:06:55 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
   boundary="----=_NextPart_000_003F_01C9C23E.FDADDA80"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049

It's getting a bit late in the day now so I'll give IDNet a ring in the morning.

Simon · Apr 21, 2009, 17:47:12

That may just have been a symptom of what was happening this morning, Zap, as the problems seem to have now cleared, but I'm only guessing.

zappaDPJ · Apr 21, 2009, 17:50:42

That does make some sense. Nobody else seems to have had any major issues and I doubt many users choose to send mail out in the early hours like me. I'll keep an eye on it tonight

Rik · Apr 21, 2009, 17:59:14

They are there until 6:30, Zappa.

Simon_idnet · Apr 21, 2009, 19:46:45

Quote from: zappaDPJ on Apr 21, 2009, 17:41:06
Or maybe not. The test mail that I sent to myself at around 5.30am this morning (as per the error message posted above) has just arrived!

There seems to be some very odd times displayed in the mail details.

It's getting a bit late in the day now so I'll give IDNet a ring in the morning.

Hi zappaDPJ

From those headers I can see that we received this mail from you at 14:00:35 and that it was processed ready for collection by 14:01:47

Regards
Simon

Lance · Apr 21, 2009, 22:42:41

Simon, are you saying that the message wasn't actually recieved at idnet until this afternoon, even though it was sent this morning?

Sebby · Apr 21, 2009, 23:00:45

Quote from: Simon on Apr 21, 2009, 13:50:26
I'm more worried that he hasn't got himself a bed!

Good point!

zappaDPJ · Apr 22, 2009, 02:51:08

Quote from: Lance on Apr 21, 2009, 22:42:41
Simon, are you saying that the message wasn't actually recieved at idnet until this afternoon, even though it was sent this morning?

I guess there's a problem at my end but I can't for the life of me work out what. If I'm waiting on an incoming email I keep the client open and it's set to auto send/receive at quite short intervals.

Poking around I've found that the test mail that caused the error in my first post did eventually get sent (as a result of auto send) at 05:06. As Simon has said, from IDNet's point of view the mail was received and ready for collection at 14.00 approx. However it was not received by me until around 17.30. This would obviously occur if I had shut my email client down but as far as I remember it's been running in the background for the last 48 hours or more.

Unfortunately I've deleted the incoming test mail but I do still have the out going mail and you can see that it was sent hours before it was logged by IDNet.

Any ideas?

[attachment deleted by admin]

g7pkf · Apr 22, 2009, 09:31:00

what av program are you using (please don't say norton)

Rik · Apr 22, 2009, 09:53:12

I think it would be best to talk to IDNet direct, Zappa, they can take a look at the server logs and see if there's a clue there.

zappaDPJ · Apr 22, 2009, 13:16:32

I probably will, I just want to eliminate the chance of it being something at my end first.

Quote from: g7pkf on Apr 22, 2009, 09:31:00
what av program are you using (please don't say norton)

I use Avira