• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question What could be causing this?

tkalfaoglu

Silver Pleskian
A customer complained that some of the mail they send from gmail never reaches their mailbox at our server.

I'm looking at the logs I hope these are all related.. (customer domain replaced with XXX)
Oct 4 09:36:04 ocean postfix/smtpd[26646]: connect from mail-wr1-f53.google.com[209.85.221.53]
Oct 4 09:36:04 ocean postfix/smtpd[26646]: TLS SNI mail.XXXX.com from mail-wr1-f53.google.com[209.85.221.53] not matched, using default chain
Oct 4 09:36:04 ocean postfix/smtpd[26646]: Anonymous TLS connection established from mail-wr1-f53.google.com[209.85.221.53]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
Oct 4 09:36:04 ocean postfix/smtpd[26646]: D42DD11E1228: client=mail-wr1-f53.google.com[209.85.221.53]
Oct 4 09:36:04 ocean psa-pc-remote[58664]: D42DD11E1228: from=<[email protected]> to=<[email protected]>
Oct 4 09:36:04 ocean psa-pc-remote[58664]: 7A5ED11E1224: py-limit-out: stderr: INFO:__main__:No SMTP AUTH and not running in sendmail context (incoming or unrestricted outgoing
mail). SKIP message.
Oct 4 09:36:04 ocean psa-pc-remote[58664]: 7A5ED11E1224: py-limit-out: stderr: SKIP
Oct 4 09:36:04 ocean psa-pc-remote[58664]: 7A5ED11E1224: spf: stderr: PASS
Oct 4 09:36:04 ocean psa-pc-remote[58664]: 7A5ED11E1224: check-quota: stderr: SKIP

What could be causing that No SMTP AUTH... line? I assume it is related to mail from [email protected] to [email protected]..
 
To me this looks like 2 unrelated mail transactions:
The message with the queue-id D42DD11E1228 is the incoming mail from Google and the message with the queue-id 7A5ED11E1224 looks like another mail (outgoing mail, sent through your server).

Can you grep for "D42DD11E1228" in your maillog and post the results here?
 
What could be causing that No SMTP AUTH... line? I assume it is related to mail from [email protected] to [email protected]..
Even if it is related, stderr: INFO means what it says, no action, just informative, SKIP means that a check was skipped because it is not relevant.
The other outcomes are PASS (what e.g. spf says), DEFER (greylisting uses this), STOP (message sent to spam), REJECT (sender in blacklist, SPF failed), DATA (more information), ERROR.
 
Hello tkalfaoglu
The log you've provided refers to 2 separated emails, please pay attention to queue_id written by postfix (D42DD11E1228 and 7A5ED11E1224).

Please collect full log for the message you're interested in: from `postfix/smtpd[...]: $TRACE_ID: ...` to last entry which is usual is `postfix/qmgr[...]: $TRACE_ID: removed`.
 
Back
Top