• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Emails are bouncing back

zed2007

Basic Pleskian
Server operating system version
CentOS Linux 7.9.2009 (Core)
Plesk version and microupdate number
Version 18.0.50 Update #2
Emails that should be order confirmation are returned back.
with the following error description:

Received: (qmail 31260 invoked for bounce); 21 Mar 2023 17:39:48 +0100
Date: 21 Mar 2023 17:39:48 +0100
From: [email protected]
To: [email protected]
Subject: failure notice
 

Attachments

  • BestB.JPG
    BestB.JPG
    151.5 KB · Views: 7
Could you please check if the log can be more complete for a single transaction? Normally there should be several lines per send attempt and at least one will give a clear error message why the mail cannot be transferred to the recipient's server.
 
Thanks you for the answer. Here are some more examples from the log.
 

Attachments

  • qmailLog1.JPG
    qmailLog1.JPG
    51.2 KB · Views: 10
  • qmailLog2.JPG
    qmailLog2.JPG
    209.8 KB · Views: 10
According to web.de:

"Emails will be rejected by our mail system if the information provided in the email header does not meet the specifications in RFC 5321 and RFC 5322.

This includes the following:

The following headers must be syntactically correct: Date, From, Sender, To
The headers BCC, CC, Date, From, Sender, Subject and To must not occur more than once.

Usually, in these cases, there is a syntax error in an e-mail address specified in the From or To field. A common cause is, for example, non-coded umlauts or semicolons instead of commas when specifying multiple addresses.

Therefore, please check the information provided by your system for correctness and contact the administrators of your system if necessary."
 
Back
Top