Expand my Community achievements bar.

SOLVED

Unable to send email deliveries from ACC instance

Avatar

Level 1

Hi,

 

I recently set up ACC within an AWS ec2 instance. Also set up postfix on this which is working. However, when creating a delivery within the ACC console the email delivery is showing as sent but is never received. The relay I set up seems to be working as I am seeing the successful connection within maillog, mta logs and mta child logs. From searching the only clue I have at the moment is the following error in my mta child log: 

 

 

2020-05-01 18:26:31.603Z	00000FC4	00000FC4	  1	info	log	Starting an MTA child (pid=4036, tid=4036)...
2020-05-01 18:26:35.761Z	00000FC4	00000FC4	  1	info	log	MTA-740014 '<removed email>' sent
2020-05-01 18:26:41.720Z	00000FC4	00000FC4	  1	error	log	IOB-090007 Network error (recv(), errno=2: No such file or directory) (iRc=-61)
2020-05-01 18:28:02.725Z	00000FC4	00000FC4	  1	info	log	MTA-740013 Message(s) waiting: 0, active session(s): 0.
2020-05-01 18:28:02.725Z	00000FC4	00000FC4	  1	info	log	Stopping MTA child (pid=4036, tid=4036)...

 

 

 I've searched around and can't seem to find solutions by going through my config files or anything online. I can provide more info on my config files if needed.

 

Any help would be appreciated, thanks!

1 Accepted Solution

Avatar

Correct answer by
Level 1

Forgot to update this thread with the answer we found. Turns out all it took was unchecking a box within the delivery template properties "Test SMTP delivery". We continue to get the same error messages but they do not appear to affect our deliveries in any way.

View solution in original post

3 Replies

Avatar

Employee

Hello Liam,

 

The log 

log	MTA-740014 '<removedemail>' sent

indicate that the message has been sent successfully assuming this is the email you sent the email to.

Now there are in broad 2 reasons for an email not reaching the user.

 

1. Landing in spam / junk folder - have you ruled this out that the email is not in spam

2. Can be blocked by ISP/ Mail provider / Spam filters - If this is an internal org domain try with a public domain like gmail.com or hotmail.com and if you get the email on them , check with IT to see if communications from the relay server are getting blocked.

 

Regards,

Adhiyan 

Avatar

Level 1
Thanks for the reply. I updated this thread with a post containing our answer. Turns out we had the "Test SMTP delivery" box checked under the delivery template properties.

Avatar

Correct answer by
Level 1

Forgot to update this thread with the answer we found. Turns out all it took was unchecking a box within the delivery template properties "Test SMTP delivery". We continue to get the same error messages but they do not appear to affect our deliveries in any way.