English
Chinese (Simplified)
French
German
Italian
Japanese
Russian
Spanish
Vietnamese
unknown user
-
Hi,
i have migrated from exchange zu mdaemon the last two days.
If we send a message to an external client an a CC to an internal employee, the message comes back with "unknown user". The internal employee does not get the message.
Whats the problem?
Thanks, Raimund.
-
Arron Staff
Does the account for the internal employee exist in MDaemon or in a different email system?
What does MDaemon's inbound SMTP log show is happening? Can you post the session that shows the message being received?
What does the Routing log show is happening? Can you post the snippets that show the message being processed?
The log files can be found in the MDaemon\Logs directory.
-
yes, its an internal mdaemon user user. Former we used Exchange, but the service is disabled.
We have one connector-account and one active sync account. The Problem is the active sync account. Here comes the message.
smtp message, when sending a message to external people with internal CC:
Mon 2023-12-18 07:28:59.150: 05: Session 00000685; child 0001
Mon 2023-12-18 07:28:59.150: 05: Accepting SMTP connection from 192.168.99.159:58413 to 192.168.99.16:25
Mon 2023-12-18 07:28:59.150: 03: --> 220 owa.mxxh-partner.de ESMTP Mon, 18 Dec 2023 07:28:59 +0100
Mon 2023-12-18 07:28:59.167: 02: <-- EHLO DESKTOP-3RO30E4.mlxxp.intern
Mon 2023-12-18 07:28:59.167: 03: --> 250-owa.mxxh-partner.de Hello DESKTOP-3RO30E4.mlkp.intern [192.168.99.159], pleased to meet you
Mon 2023-12-18 07:28:59.167: 03: --> 250-ETRN
Mon 2023-12-18 07:28:59.167: 03: --> 250-AUTH LOGIN PLAIN
Mon 2023-12-18 07:28:59.167: 03: --> 250-8BITMIME
Mon 2023-12-18 07:28:59.167: 03: --> 250-ENHANCEDSTATUSCODES
Mon 2023-12-18 07:28:59.167: 03: --> 250-PIPELINING
Mon 2023-12-18 07:28:59.167: 03: --> 250-CHUNKING
Mon 2023-12-18 07:28:59.167: 03: --> 250-STARTTLS
Mon 2023-12-18 07:28:59.167: 03: --> 250 SIZE
Mon 2023-12-18 07:28:59.168: 02: <-- AUTH PLAIN
Mon 2023-12-18 07:28:59.168: 03: --> 334
Mon 2023-12-18 07:28:59.168: 02: <-- ******
Mon 2023-12-18 07:28:59.168: 01: Echtheitsbestätigung für s.hart@mxxh-partner.de wird durchgeführt...
Mon 2023-12-18 07:28:59.175: 01: Authenticated as s.hart@mxxh-partner.de
Mon 2023-12-18 07:28:59.175: 03: --> 235 2.7.0 Authentication successful
Mon 2023-12-18 07:28:59.182: 02: <-- MAIL FROM:<s.hart@mxxh-partner.de>
Mon 2023-12-18 07:28:59.192: 03: --> 250 2.1.0 Sender OK
Mon 2023-12-18 07:28:59.192: 02: <-- RCPT TO:<USER8B78C79A@mxxh-partner.de>
Mon 2023-12-18 07:28:59.192: 01: Absender hat versucht, eine Nachricht an eine unbekannte Adresse zuzustellen
Mon 2023-12-18 07:28:59.192: 03: --> 550 5.1.1 Recipient unknown <USER8B78C79A@mxxh-partner.de>
Mon 2023-12-18 07:28:59.193: 02: <-- QUIT
Mon 2023-12-18 07:28:59.193: 03: --> 221 2.0.0 See ya in cyberspace
Mon 2023-12-18 07:28:59.193: 04: SMTP session terminated (Bytes in/out: 186/441)outbound works to the external user:
8 07:27:50.593: 03: --> MAIL From:<muenchen@mxxh-partner.de> SIZE=406630
Mon 2023-12-18 07:27:50.593: 03: --> RCPT To:<hnes@vixxxnic.de>
Mon 2023-12-18 07:27:50.593: 03: --> DATA
Mon 2023-12-18 07:27:50.595: 02: <-- 250 OK
Mon 2023-12-18 07:27:50.595: 02: <-- 250 Accepted
Mon 2023-12-18 07:27:50.595: 02: <-- 354 Enter message, ending with "." on a line by itself
Mon 2023-12-18 07:27:50.595: 01: Sending <c:\mdaemon\queues\remote\pd3501000000067.msg> to [192.168.99.1]
Mon 2023-12-18 07:27:50.625: 01: Transfer Complete
Mon 2023-12-18 07:27:51.435: 02: <-- 250 OK id=1rF76V-0005lL-13
Mon 2023-12-18 07:27:51.435: 03: --> QUIT
Mon 2023-12-18 07:27:51.455: 02: <-- 221 owa.mxx-partner.de closing connection
Mon 2023-12-18 07:27:51.455: 01: SMTP session successful (Bytes in/out: 2429/410063)In the route i found nothing at this time.
Thanks, Raimund
-
Arron Staff
If you send a message directly USER8B78C79A@yourdomain.com, instead of CCing the user, does the same thing happen?
If you go to Accounts / Account Manager, is the USER8B78C79A account shown?
If you select the account and click Edit, Is the "Account is Enabled" radio button selected in the Account Status section of the Account Details?
-
yes, i can send a message from outside to the user:
15:45:10.541: <-- RCPT TO:<user8b78c79a@mxxh-partner.de>
Mon 2023-12-18 15:45:10.541: --> 250 2.1.5 Recipient OK
Mon 2023-12-18 15:45:10.541: <-- DATA
Mon 2023-12-18 15:45:10.542: --> 354 Enter mail, end with <CRLF>.<CRLF>
Mon 2023-12-18 15:45:10.543: Message size: 6904 bytes
Mon 2023-12-18 15:45:10.555: Outbreak Protection: Processing skipped. Trusted IP found.
Mon 2023-12-18 15:45:10.577: Erstellung der Nachricht successful: c:\mdaemon\queues\inbound\md5001000000303.msg
Mon 2023-12-18 15:45:10.577: --> 250 2.6.0 Ok, message saved <Message-ID: <027301da31c0$c60c07d0$52241770$@mdaemon-admin.de>>
Mon 2023-12-18 15:45:10.577: <-- QUIT
Mon 2023-12-18 15:45:10.577: --> 221 2.0.0 See ya in cyberspace
Mon 2023-12-18 15:45:10.577: SMTP session successful (Bytes in/out: 7568/4563)No, i cant find a user with this name. The accounts are all enabled. The CC-user works, receive and sends emails...
Thanks, Raimund
-
Arron Staff
If no user account exists for user8b78c79a and there is no alias, or mailing list (or something else in MDaemon to make the address valid), then the message is not to a valid local user and should be rejected.
It is not rejected in the last example because the session was from a trusted IP address.
Create an account for user8b78c79a by going to Accounts / Account Manager / New, are you then able to send to the user like you want?
-
I have to correct myself, I have received an e-mail to the administrator account that the user does not exist.
But the employee only writes the CC address, which she always writes. Not this user user8b78c79a. Its a real name and adress.
Greetings.
-
Arron Staff
But the employee only writes the CC address, which she always writes. Not this user user8b78c79a. Its a real name and adress
I'm not sure I understand. Are you saying that user8b78c79a is not the real account that the user is CCing mail to? If that is the case, please repeat all the steps above with the correct address. Does the account exist in MDaemon under Accounts / Account Manager?
Can you post log snippets that show what happens when the user tries to send to the real address? You can change the address in the log snippet if you want, it doesn't matter to me what the address is, I just need to see what MDaemon is doing.
Can you send to the account directly, instead of sending to it via CC?
-
Yes, the user8b78c79a ist not a user of us. Our user, we name him Meyer has the real adress h.meyer@mxx....
But if the sekretary add the real user in CC, we get the message, that user8b78c79a does not exist.
I thought that was an internal designation in mdaemon...
I will try to get the logs...
Thanks, Raimund
-
Arron Staff
That is very strange. I would also check the scretary's autocomplete and contact lists to make sure that a contact with user8b78c79a@domain.com as the email address does not exist. The easiest way to do this is to compose a new email on the secretary's computer and add Meyer to the recipient list. Then once added, check the real name and address in the To field to make sure it is the correct name and email address.
Then I'd check the sent items folder in Outlook to make sure previous messages were also sent to the correct address. If outlook shows the h.meyer@ address, then we'll need to see the MDaemon logs to figure out what is happening.
-
Now i have this user in the defect queue:
Zusammenfassung der Defekt-Warteschlange von MDaemon
An Von Betreff Art Nachrichten-ID Datum
USER8B78C79A@mxxhpartner.de
muenchen@mxxpartner.de
user from extern message to unknown local user <4ead01da31bf$c94640b0$5bd2c210$@mxxpartner.de>
Mon, 18 Dec 2023 15:37:54 +0100
user8b78c79a@mxxpartner.deI must find out, who is this user....
-
Arron Staff
I'd start by checking the inbound SMTP logs to see what IP address the messages are coming from. And then take a look at he email clients running on those IP addresses. Perhaps this was a valid address in Exchange that did not get moved over to MDaemon.
If you want MDaemon to start accepting the messages, create an account for the user. You can then login to webmail as that user and see what type of mail is being sent to the user and who is sending it.
If you'd prefer a more formal means of support to help you work through the issues, all of our support options can be found at https://mdaemon.com/pages/support-options. If you'd like a local contact for support, we also have a distributor in German, https://www.mdaemon.de/ that can assist.
