Client’s are reporting issues connecting to SMTP, and also having 3-4 copies of each message delivered once it does connect. Also issues with time/date stamps - emails being received before they are sent!
SMTP issue on Mail1 and whatever server is 204.**.1*4.85
Have not seen any SMTP issues since the network issues resolved.
Are these recent or during a peroid 3 hours back to about 2 hours 30 minutes back when we had a DOS attack happening?
I sent a test mail from mail1 to hotmail. Received in 60 seconds. No multiple emails found of any sort.
As stephen suggested, we faced a minor DDOS attack and that could have resulted in the connectivity issues your clients faced.
Recent. IF you look at mail servers on Jodopulse, it looks like a Christmas tree with all the red in amongst the green.
Mail1 Praveen is checking SMTP on, the other server you gave was mail4, and it only had 2 failures back during the height of the DOS attack
Mail 4 is the one my client is on, and they are still having SMTP issues, and the repeating emails have occurred as recently as 30 minutes ago, as I received 3 duplicates from one client.
Was due to the DDOS attack.
The DDOS attacks were hours ago. The SMTP server, especially mail 1, has red marks through out it’s range from 10am to now.
Praveen is working on mail1 now. Mail4 has had no SMTP failures, the duplicate issue will be checked shortly.
Hi. This is the qmail-send program at mail4.******here.biz.
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.
gary @ g**er.com:
2**.14.1**.9 does not like recipient.
Remote host said: 553 sorry, that domain isn’t allowed to be relayed thru this MTA (#5.7.1)
Giving up on 2.14.1**.**9.
She then turned around and was able to forward the failure notice to the same address that was rejected, sending it from the same address as she did the rejected message.
Something ain’t right!
Mail1 SMTP errors resolved some time back but I waited to reply.
Having someone check this mail4 error you have there.
Remote host said: 553 sorry, that domain isn’t allowed to be relayed thru this MTA (#5.7.1)
This error usually occurs if you are doing POP3 before SMTP and didn’t pop3 before SMTP in a reasonable time frame. Just POP3 again and resend the email. If the error still occurs, put in a ticket and we’d check it out.
It is never really a global issue. But can happen occasionally.
Sorry about saying the Mail1 SMTP timeouts were caused by DDOS.. didn’t check the time frame.
As stephen mentioned, issue was solved. The server was reaching the max smtp connection limit due to a spammer. This spammer was blocked on old mail1, but not on the new mail1. Blocked him now.. and no more SMTP time outs since
Have no idea what is meant by this! LOL
Do you mean by “doing POP3” that I’m (or my client is) checking for new messages, and then “SMTP” is sending messages?
All I know is they use Outlook Express, have it set to send messages automatically, and every 10 minutes it checks the server for new mail and sends anything in the Outbox (which there shouldn’t be anything in the Outbox if it is sent automatically!).
Not sure if we have any email client experts here, but when sending emails does Outlook/Outlook Express, etc. wait for a confirmation signal from the mail server before it places a copy of the message in the “Sent” folder? If it can’t be sent, does the message sit in the Outbox waiting for the next send/receive cycle?
Maybe I can explain the SMTP/POP issues Yash stated.
Typically, a mail client (Outlook or Express) will ask for mail (POP) and send mail (SMTP), in that order. Because the server remembers the client when the send request hits (SMTP), there is typically no problem sending mail. Sometimes, a client will try to send mail before receiving it – several legit reasons this happens. In that case, the SMTP server does not know who the client is when it asks if it can send, so it gets rejected.
As Yash stated, just hitting send/receive again will normally do the trick, as the ‘receive’ aspect will reathenticate with the server.
A better option, however, would be to check “My Outgoing server (SMTP) requires authentication” under “more settings” then “outgoing” tab in Outlook '07 (slightly dif in other versions, but is there). This way, the server will always trust the sender, even if it does not remember it as the same client that just asked to receive mail a couple minutes prior…
Make sense?
Tim
Outlook '07?
yes – Outlook '07 (i do a lot of Betas…). It is the same place in Outlook/Office '03 (maybe slightly different terms).
All my client’s have the authentication option checked (I personally setup their email clients), so this should not be an issue. In fact, it’s one of the things that makes getting the SMTP errors so frustrating!