Email sent multiple times

I found a few threads with this same problem, but none had an answer.

I have an email with an attachment that my customer received over 20 times, yet it still showed in my outbox. This is really embarrassing. Even now that I’ve deleted it it is not showing in my outbox.

I’m running version 7.2.36908.0

As a Pro License user you can make use of your VIP support option and open a support ticket directly with eM Client. They will be able to help you further.

Your server is probably not completing the transaction correctly, so the message is being resent over and over. eM Client will retry until the server confirms it has received the message. You can look in Menu > Tools > Operations, and see if there is any SMTP error in the Log tab. You can quote that error to Support when you contact them.

Deleting the message from the Outbox will cease any further attempts to send the message.

Hi. I’ve been having the same problem for quite a long time, whenever sending emails with attachments.

It looks like eM Client is not waiting long enough for a response from the SMTP server, perhaps because it is also busy syncing folders at the same time, and also because i have high latency (on satellite).

Here’s the error:

10:32:38 PM xxx@columbiavalley.com [SMTP]  MailClient.Accounts.SocketException: Sending messages failed due to the following reason:
10:32:38 PM     “Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.”
10:32:38 PM    at MailClient.Protocols.Smtp.SmtpSendCommand.Execute(WorkerStatus status)
10:32:38 PM    at MailClient.Commands.Command.Process(WorkerStatus status)

eM Client seems to recover from this error and try again, because the email does get successfully sent. But once this error has been encountered, it looks like the outgoing email does not get removed from the outbox, resulting in the email being sent many times, sometimes dozens of times until i finally delete it from the outbox.

This looks really unprofessional when sending attachments to clients and colleagues.

Yes, what happens when you send a message, the client (eM Client) will wait for confirmation from the server that it has been received. If the server does not respond, then the client will try to send it again, until it gets a response.

So your server is not responding, and eM Client is trying again and again, just like it is supposed to.

You should contact your provider and ask for them to look into this for you.

This is not a problem with our server. The server responds promptly, but eM Client does not seem to wait long enough for clients on satellite internet.

On top of that, it’s clear that eM Client itself is causing some of this delay because it spends a lot of time synchronizing folders, which affects internet response time quite a bit. It’s synchronizing folders at the same time that it’s sending out emails, so it’s not a surprise that there would be some delay. But apparently the timeouts in eM Client are too short. That’s certainly what it looks like. But, as we both say, eventually the email does go out.

The actual problem is that multiple copies get sent, because apparently eM Client does not remove the email from the outbox after successfully sending it, because it has flagged an error. Perhaps that flag should be reset after the connection has been re-established and/or once the email has successfully been sent.

No, this is an issue with your server. You even quoted the error which said “A connection attempt failed because the connected party did not properly respond after a period of time , or established connection failed because connected host has failed to respond.”

Multiple copies will be sent because the server is not giving the correct response the first time. The message is sent, the server does not respond, eM Client sends again.

What did your provider say when you asked them about this?

The server is responding promptly, just not promptly enough for the timeouts of eM Client. eM Client does not even seem to take into account the delays that it, itself, causes by syncing folders at the same time as sending out email (that appears to be the case).

This is our own VPS, so we are our own provider and have already checked out the server side more than once. This server is on a dedicated box on a high-throughput enterprise-grade pipe and there are only a handful of email users, so i’m very confident that it’s not a mail-server response problem.

Exactly how long does eM Client wait before treating it as a non-response?

One thing that could be happening here is that eM Client sends out a large number of requests, most of which are for folder syncing, and then because it’s waiting for so many responses from the server it cannot get a fast enough response on outgoing mail to be within the timeout limitation.

This is not the only timeout issue i’m seeing. Filters commonly fail because the filter is running before incoming mail has completely downloaded.

As a Pro License user, please open a support ticket directly with eM Client. They will be able to assist you further.

I will do that.

When i said “retry” i was referring to the packet for which no response was received (soon enough). When using TLS there will be multiple attempts to send a packet if a problem is encountered. So unless all attempts fail, the packet transmission should succeed and there would be no need to flag the whole transmission as having failed.

I’m starting to wonder if eM Client has been tested on slower internet connections? Really, this program should be robust enough and flexible enough to gracefully handle the unexpected.