Error Sending to Gmail Account

BobMc98
Posts: 2
Joined: Wed Sep 13, 2017 2:58 am

Error Sending to Gmail Account

Postby BobMc98 » Wed Sep 13, 2017 3:07 am

I recently upgraded to the latest MailEnable version, and am currently experiencing difficulty sending to a Gmail account. I get repeated bounceback messages about a delivery delay, with the following explanation:

MailEnable: Message delivery has been delayed.

Message is waiting at <mymailserver> for delivery to gmail-smtp-in.l.google.com.

The message will be retried for another 29 hours.

Reason: ME-E0029: [<hash?>] DATA Command Failed. Transmit File: Communications Error Transmitting File to gmail.com.

Message headers follow:



Can anyone provide some information regarding how to track down the source of the issue?

MailEnable-Ian
Site Admin
Posts: 8439
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: Error Sending to Gmail Account

Postby MailEnable-Ian » Thu Sep 14, 2017 1:05 am

Hi,

What do the SMTP log files report in regards to the SMTP transaction with the Gmail server? From the bounce message details it looks like there problem is the transmitting of the message data. Are you sending from a client machine using a third a party email client? I.e: Outlook? Does the client machine have Antivirus email scanning options enabled? If so try and disable them and then try to resend. If you the client routes via firewall/proxy then this may also be the problem where the connection maybe dropped by the firewall/proxy because of the data being transmitted.
Regards,

Ian Margarone
MailEnable Support

BobMc98
Posts: 2
Joined: Wed Sep 13, 2017 2:58 am

Re: Error Sending to Gmail Account

Postby BobMc98 » Thu Sep 14, 2017 4:07 am

MailEnable-Ian wrote:Hi,

What do the SMTP log files report in regards to the SMTP transaction with the Gmail server? From the bounce message details it looks like there problem is the transmitting of the message data. Are you sending from a client machine using a third a party email client? I.e: Outlook? Does the client machine have Antivirus email scanning options enabled? If so try and disable them and then try to resend. If you the client routes via firewall/proxy then this may also be the problem where the connection maybe dropped by the firewall/proxy because of the data being transmitted.


Ian, the log files didn't reveal much. The SMTP protocol traffic looks alright, up until the last two lines, which appear to unexpectedly quit, as shown below.

DATA DATA 354 Start mail input; end with <CRLF>.<CRLF> 46 6
QUIT QUIT 221 Service closing transmission channel 42 6


Here's the strange thing - I rebooted the server for some OS updates, and it released the message. Weird. I'm not sure what was blocking it but the reboot appears to have corrected it.

Thanks for the help.

Who is online

Users browsing this forum: No registered users and 1 guest