hi,

I'm trying to relay a message through Xeams. All works well, until I try to include an attachment (3.8mb). The msg goes through SMTPConversation but I never see it in SMTPOuboundConversation. SmtpConversation reads (for a msg with an attachment):

2021-09-15 16:44:16,351 - [ 1300834] C --> EHLO tpweb01
2021-09-15 16:44:16,382 - [ 1300834] S <-- 250-217.xx.xx.xx. Pleased to meet you
2021-09-15 16:44:16,382 - [ 1300834] S <-- 250-SIZE 20971520
2021-09-15 16:44:16,382 - [ 1300834] S <-- 250-AUTH LOGIN PLAIN CRAM-MD5
2021-09-15 16:44:16,382 - [ 1300834] S <-- 250-AUTH=LOGIN PLAIN CRAM-MD5
2021-09-15 16:44:16,382 - [ 1300834] S <-- 250-STARTTLS
2021-09-15 16:44:16,382 - [ 1300834] S <-- 250 OK
2021-09-15 16:44:16,601 - [ 1300834] C --> MAIL FROM:<xxx@xxx.com>
2021-09-15 16:44:16,601 - [ 1300834] S <-- 250 OK
2021-09-15 16:44:16,616 - [ 1300834] C --> RCPT TO:<xxx@xxx.com>
2021-09-15 16:44:16,616 - [ 1300834] S <-- 250 OK
2021-09-15 16:44:16,632 - [ 1300834] C --> DATA
2021-09-15 16:44:16,632 - [ 1300834] S <-- 354 Start mail input; end with <CRLF>.<CRLF>
2021-09-15 16:44:17,584 - [ 1300834] S <-- 250 2.6.0 Queued mail for delivery

what could be the reasons for the messages not sending with attachments? I have another xeams server setup, and this one is working just fine

any help/ideas greatly appreciated!

thanks,

adrian

Do you see this message under Message Repository/View All Good?

If yes, the next place to check is Message Repository/Manage Outbound Queue to see if it is stuck in the queue. Additionally, check OutboundAuditTrailFailure.log file to see if it ran into an error.

ok -will try this when I get access again, thanks

hello -nothing in outbound queue, and nothing in the OutboundAuditTrailFailure log -there are other entries there though (for other emails). Also nothing in the Tools/Live Monitor

I'm able to send emails without an attachment. Am also able to send emails through another Xeams server without issue -I can't see what the difference is with this setup though (other than IP/domain)

do all failed sends result in an audit log entry?

and thank  you very much for getting back to me

Did you see the message in View All Good Messages?

I have a feeling that something is causing Xeams not even to attempt to send this message, as if it is a spam message. This is the reason I wanted to confirm if you see it in the Good messages.

You won't see it in any log if Xeams quarantines the message.

hello,

I've just done another test, and see it in the smtp conversation, and yes, I do not see it in "view all good" or in junk or possible junk (all that is turned off as outbound only) so where should I be looking for this message? How come it just disappears? I also don't see it when searching all messages. No other logs have updated, just SMTPConversation. Are there any other areas I can look at?

so all I see is:

2021-09-23 15:45:35,659 - [ 1323176] ************ New connection from: xx.xx.109.86:25
2021-09-23 15:45:35,659 - [ 1323176] C --> EHLO tpweb01
2021-09-23 15:45:35,659 - [ 1323176] S <-- 250-xx.xx.109.86. Pleased to meet you
2021-09-23 15:45:35,659 - [ 1323176] S <-- 250-SIZE 20971520
2021-09-23 15:45:35,659 - [ 1323176] S <-- 250-AUTH LOGIN PLAIN CRAM-MD5
2021-09-23 15:45:35,659 - [ 1323176] S <-- 250-AUTH=LOGIN PLAIN CRAM-MD5
2021-09-23 15:45:35,659 - [ 1323176] S <-- 250-STARTTLS
2021-09-23 15:45:35,659 - [ 1323176] S <-- 250 OK
2021-09-23 15:45:35,893 - [ 1323176] C --> MAIL FROM:<xx@domain.com>
2021-09-23 15:45:35,893 - [ 1323176] S <-- 250 OK
2021-09-23 15:45:35,909 - [ 1323176] C --> RCPT TO:<yy@domain.com>
2021-09-23 15:45:35,909 - [ 1323176] S <-- 250 OK
2021-09-23 15:45:35,925 - [ 1323176] C --> DATA
2021-09-23 15:45:35,925 - [ 1323176] S <-- 354 Start mail input; end with <CRLF>.<CRLF>
2021-09-23 15:45:37,440 - [ 1323176] S <-- 250 2.6.0 Queued mail for delivery
2021-09-23 15:47:15,665 - [ 1323176] C --> QUIT
2021-09-23 15:47:15,665 - [ 1323176] S <-- 221 Good bye. Hope to see you again
2021-09-23 15:47:15,665 - [ 1323176] ~~~~~~~~~~~~ Connection Terminated (100006:999999)

ah jeez -I'm sorry. I've just found the issue. You prompted my thinking talking about it never being processed. I had checked message size, which was fine. But looking today, more closely, it was maximum actionable size, and the action being "reject" for some reason....so anything over 1mb...rejected

apologies, again, and thank you so much for getting back to me so promptly -and thanks for delivering a great product

cheers,
adrian

I am glad to learn you found the problem.