Unspecified recipient | MDaemon Technologies Community Forum
  1. Forum
  2. MDaemon
  3. Unspecified recipient

Unspecified recipient

  • R

    Hi,

    an employee has send two messages. Short time later the mail comes back: unspecified recipient.

    But if i look in the sent mails, ther is an recipient....whats the problem?

     

     Echtheitsbestätigung für c.k@mxx-partner.de wird durchgeführt...
    Tue 2023-12-19 15:33:57.620: 01: Authenticated as c.k@mxx-partner.de
    Tue 2023-12-19 15:33:57.620: 03: --> 235 2.7.0 Authentication successful
    Tue 2023-12-19 15:33:57.627: 02: <-- MAIL FROM:<c.k@mxxpartner.de>
    Tue 2023-12-19 15:33:57.633: 03: --> 250 2.1.0 Sender OK
    Tue 2023-12-19 15:33:57.634: 02: <-- RCPT TO:<cm@web.de>
    Tue 2023-12-19 15:33:57.634: 03: --> 250 2.1.5 Recipient OK
    Tue 2023-12-19 15:33:57.634: 02: <-- DATA
    Tue 2023-12-19 15:33:57.635: 03: --> 354 Enter mail, end with <CRLF>.<CRLF>
    Tue 2023-12-19 15:33:57.647: 01: Message size: 126800 bytes
    Tue 2023-12-19 15:33:57.655: 03: --> 550 5.7.0 Authentication rejected
    Tue 2023-12-19 15:33:57.655: 01: Anmeldedaten für Echtheitsbestätigung stimmen nicht mit Adresse aus Absenderkopfzeile FROM überein
    Tue 2023-12-19 15:33:57.656: 02: <-- QUIT

     

    We use "send as", because we need this. How can i solve the problem?

     

    Thanks. Raimund.

    0 likes
  • A

    You can adjust the settings by going to Security / Sender Authentication / SMTP Authentication

    You can find more information in the help file at:

    https://help.mdaemon.com/MDaemon/en/security--smtp_authentication.html

    --
    Arron Caruth

    0 likes
  • R

    Thanks Arron, i hab disabled this now...because this are internal senders. No one other sends mails in the network.

     

    Thanks again, Raimund.

    0 likes
  • R

    Sorry Arron: But why works this 200 times a day and then randomly comes the auth-check-message for this two mails?

    Is this depending on the recipient?"

     

    Do you think i can make a check mark on "Do not allow authentication on the SMTP port", to have no problems with authentication?

     

    Thanks, Raimund

    0 likes
  • A

    Sorry Arron: But why works this 200 times a day and then randomly comes the auth-check-message for this two mails?

    It is comparing the authenticated user withe the email address in the return-path and the From header. 

    Looking at the log snippet you provided previously, it is not random, the authenticated user and the MAIL FROM value do not match, so the return-path probably also does not match.

    Tue 2023-12-19 15:33:57.620: 01: Authenticated as c.k@mxx-partner.de
    Tue 2023-12-19 15:33:57.627: 02: <-- MAIL FROM:<c.k@mxxpartner.de>

    Notice the authenticated user is using mxx-partner.de while the MAIL FROM value is using mxxpartner.de

    You say you have "disabled this now", which check box(es) did you uncheck? If you don't want MDaemon to check the return-path or From address, uncheck both boxes.  

    If an inbound SMTP session was active when the settings were changed, the previous settings will apply.  That "should" clear itself pretty quickly unless there is an SMTP session that remained active for a long time.  You can ensure this doesn't happen by restarting MDaemon. 

    Do you think i can make a check mark on "Do not allow authentication on the SMTP port", to have no problems with authentication?

    No.

    If you check the box for "Do not allow authentication on the SMTP Port" then all clients will need to use port 587 for sending messages, Authentication will not be an option when connecting on port 25.  In most configurations you will find clients trying to authenticate on port 25, even though the standard is port 587.  

    It sounds like you may be wanting to configure MDaemon to not require authentication.  While this is possible it is NOT reccomended because it leaves your server vulnerable.  If this is what you want, let me know and I'll tell you how to do it.

    --
    Arron Caruth

    0 likes
Please login to reply to this topic!

Participants