Reject 550 is not allowed access from your loc... | MDaemon Technologies Community Forum
  1. Forum
  2. MDaemon
  3. Reject 550 <username> is not allowed access from your location

Reject 550 <username> is not allowed access from your location

  • B

    Hello, 

    Just configuring MDaemon and Gateway to take over from an old Exchange system.

    I get the 550 not allowed access error from the smart hosted Gateway (logs) when trying to send from an account on MDaemon. 

    Any suggestions what I might have missed?

    0 likes
  • A

    Are you using SecurityGateway and is it returning the 550 error?  If you are and it is returning the error, by default SecurityGateway only accepts  messages from local users that are from IPs configured as domain mail servers.   You can configure a domain mail server by going to Setup / Users | Mail Configuration | Domain Mail Servers.

    If that is not it, log snippets that show the error occurring and a better undertanding of the mail routing that is causing issues would be helpful.

    --
    Arron Caruth

    0 likes
  • B

    Thanks Arron, that got me pointed in the right direction. We used a FQDN to allow the MDaemon to talk to SecurtiyGateway but the DMZ record wasn't pointing to the correct IP. Changing to the explicit Trusted IP it worked.

    Exchange is now forwarding inbound mail to the SecurityGateway if it doesn't find the user mailbox. The message is delivers to MDaemon. Great.

    Now the second part of this is trying to get local Exchange users to be able to send mail to other local domain users residing on MDaemon. We will take another look at this tomorrow.  It seems to be redirecting out the front door from the SecurityGateway...

     

    Tue 2025-01-14 17:09:43: --> MAIL From:<user1@dougallmedia.com> SIZE=6821
    Tue 2025-01-14 17:09:43: <-- 250 2.1.0 Sender OK
    Tue 2025-01-14 17:09:43: --> RCPT To:<user2@dougallmedia.com>
    Tue 2025-01-14 17:09:43: <-- 250 2.1.5 Recipient OK
    Tue 2025-01-14 17:09:43: --> DATA
    Tue 2025-01-14 17:09:43: <-- 354 Start mail input; end with .
    Tue 2025-01-14 17:09:43: Sending <C:\Program Files\MDaemon Technologies\SecurityGateway\Temp\49ddec30454b4da08453780c66c85c4c.tmp> to [192.168.1.14]
    Tue 2025-01-14 17:09:43: <-- 250 2.6.0 <CH2PR01MB6054FE7688A2F5362C4116BFAB182@CH2PR01MB6054.prod.exchangelabs.com> [InternalId=7247] Queued mail for delivery
    Tue 2025-01-14 17:09:43: ----------
     
    0 likes
  • A

    If dougallmedia.com is configured as a domain in SecurityGateway, it should be sending it to the domain mail servers that are configured.  Does user2@dougallmedia.com exist in SecurityGateway?  

    Is the user configured to use the domain mail server for the domain or have you configured a domain mail server for that user account?  (Setup / Users | Accounts | Select a domain | Users | Select a User | Edit, scroll down and you will see the mail delivery section that allows you to specify a domain mail server to be used for that user account)

    What does the rest of the transcript show is happening?

    --
    Arron Caruth

    0 likes
  • B

    To be clear, there is no problem with sending external mail in or out though Exchange which hands it off to SGW then MDaemon server mailbox.

    Yes the user is listed on within the domain on MDaemon and SecurityGateway (SGW). It may be an order of operations thing to some extent. Both servers are listed in the Mail Delivery list and 'use domain mail servers' was selected by default. The Exchange server was listed first.

    If we change the Mail Delivery to 'Deliver mail using specified mail server' and just select MDaemon Mail Server..  Test from Exchange server from the same domain to a user (on the same domain) on DMaemon we get a 550 5.7.1 Sender unknown. We tried adding the domain name to the Allow list using both *@domain.com and the 'specific domain' allow entering the FQDN of the exchange server. Once that was done we got an Authentication required message. The sending user on the Exchange machine does not have a user account on the MDaemon servers.

    It looks like MDaemon just looks to itself since is thinks it has that domain to itself.

    Wed 2025-01-15 11:58:49: Attempting TCP connection to [192.168.1.146 : 25]
    Wed 2025-01-15 11:58:49: Socket connection established (192.168.204.72 : 54662 -> 192.168.1.146 : 25)
    Wed 2025-01-15 11:58:49: Waiting for protocol initiation...
    Wed 2025-01-15 11:58:49: <-- 220 mail3.dougallmedia.com ESMTP Wed, 15 Jan 2025 11:58:27 -0500
    Wed 2025-01-15 11:58:49: --> EHLO dougallmedia.com
    Wed 2025-01-15 11:58:49: <-- 250-mail3.dougallmedia.com Hello dougallmedia.com [192.168.204.72], pleased to meet you
    Wed 2025-01-15 11:58:49: <-- 250-ETRN
    Wed 2025-01-15 11:58:49: <-- 250-AUTH LOGIN PLAIN
    Wed 2025-01-15 11:58:49: <-- 250-8BITMIME
    Wed 2025-01-15 11:58:49: <-- 250-ENHANCEDSTATUSCODES
    Wed 2025-01-15 11:58:49: <-- 250-PIPELINING
    Wed 2025-01-15 11:58:49: <-- 250-CHUNKING
    Wed 2025-01-15 11:58:49: <-- 250-STARTTLS
    Wed 2025-01-15 11:58:49: <-- 250 SIZE
    Wed 2025-01-15 11:58:49: --> STARTTLS
    Wed 2025-01-15 11:58:49: <-- 220 2.7.0 Ready to start TLS
    Wed 2025-01-15 11:58:49: SSL negotiation successful (TLS 1.2, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)
    Wed 2025-01-15 11:58:49: --> EHLO dougallmedia.com
    Wed 2025-01-15 11:58:49: <-- 250-mail3.dougallmedia.com Hello dougallmedia.com [192.168.204.72], pleased to meet you
    Wed 2025-01-15 11:58:49: <-- 250-ETRN
    Wed 2025-01-15 11:58:49: <-- 250-AUTH LOGIN PLAIN
    Wed 2025-01-15 11:58:49: <-- 250-8BITMIME
    Wed 2025-01-15 11:58:49: <-- 250-ENHANCEDSTATUSCODES
    Wed 2025-01-15 11:58:49: <-- 250-PIPELINING
    Wed 2025-01-15 11:58:49: <-- 250-CHUNKING
    Wed 2025-01-15 11:58:49: <-- 250-REQUIRETLS
    Wed 2025-01-15 11:58:49: <-- 250 SIZE
    Wed 2025-01-15 11:58:49: --> MAIL From:<User1@dougallmedia.com> SIZE=2778
    Wed 2025-01-15 11:58:49: <-- 550 5.7.1 Sender unknown
    Wed 2025-01-15 11:58:49: ----------
     
    I have mailbox on both systems and sending from exchange to a mailbox user with only a mailbox on MDaemon I'm rejected with 530 5.7.0  Authentication required
     
    Wed 2025-01-15 12:09:57: --> 250 Ok, message saved
    Wed 2025-01-15 12:09:57: <-- QUIT
    Wed 2025-01-15 12:09:57: --> 221 See ya in cyberspace
    Wed 2025-01-15 12:09:57: SMTP session successful (Bytes in/out: 34119/398)
    Wed 2025-01-15 12:09:57: ----------
    Wed 2025-01-15 12:09:57: Attempting TCP connection to [192.168.1.146 : 25]
    Wed 2025-01-15 12:09:57: Socket connection established (192.168.204.72 : 54965 -> 192.168.1.146 : 25)
    Wed 2025-01-15 12:09:57: Waiting for protocol initiation...
    Wed 2025-01-15 12:09:57: <-- 220 mail3.dougallmedia.com ESMTP Wed, 15 Jan 2025 12:09:35 -0500
    Wed 2025-01-15 12:09:57: --> EHLO dougallmedia.com
    Wed 2025-01-15 12:09:57: <-- 250-mail3.dougallmedia.com Hello dougallmedia.com [192.168.204.72], pleased to meet you
    Wed 2025-01-15 12:09:57: <-- 250-ETRN
    Wed 2025-01-15 12:09:57: <-- 250-AUTH LOGIN PLAIN
    Wed 2025-01-15 12:09:57: <-- 250-8BITMIME
    Wed 2025-01-15 12:09:57: <-- 250-ENHANCEDSTATUSCODES
    Wed 2025-01-15 12:09:57: <-- 250-PIPELINING
    Wed 2025-01-15 12:09:57: <-- 250-CHUNKING
    Wed 2025-01-15 12:09:57: <-- 250-STARTTLS
    Wed 2025-01-15 12:09:57: <-- 250 SIZE
    Wed 2025-01-15 12:09:57: --> STARTTLS
    Wed 2025-01-15 12:09:57: <-- 220 2.7.0 Ready to start TLS
    Wed 2025-01-15 12:09:57: SSL negotiation successful (TLS 1.2, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)
    Wed 2025-01-15 12:09:57: --> EHLO dougallmedia.com
    Wed 2025-01-15 12:09:57: <-- 250-mail3.dougallmedia.com Hello dougallmedia.com [192.168.204.72], pleased to meet you
    Wed 2025-01-15 12:09:57: <-- 250-ETRN
    Wed 2025-01-15 12:09:57: <-- 250-AUTH LOGIN PLAIN
    Wed 2025-01-15 12:09:57: <-- 250-8BITMIME
    Wed 2025-01-15 12:09:57: <-- 250-ENHANCEDSTATUSCODES
    Wed 2025-01-15 12:09:57: <-- 250-PIPELINING
    Wed 2025-01-15 12:09:57: <-- 250-CHUNKING
    Wed 2025-01-15 12:09:57: <-- 250-REQUIRETLS
    Wed 2025-01-15 12:09:57: <-- 250 SIZE
    Wed 2025-01-15 12:09:57: --> MAIL From:<user1_withmailboxesonbothserver@dougallmedia.com> SIZE=34253
    Wed 2025-01-15 12:09:57: <-- 250 2.1.0 Sender OK
    Wed 2025-01-15 12:09:57: --> RCPT To:<user2_withmailboxonMDaemonOnly@dougallmedia.com>
    Wed 2025-01-15 12:09:57: <-- 530 5.7.0 Authentication required
    Wed 2025-01-15 12:09:57: ----------
     
    0 likes
  • A

    MDaemon, by default, expects there to be a mailbox for all users of a domain.  So if you hadd mydomain.com, then MDaemon expects it knows about all email addresses for mydomain.com.  You can work around that in a couple of different ways.  

    1. Create all an account in MDaemon for every address.  If the address exists in exchange, tell MDaemon to forward the message to exchange or SecurityGateway and let them route the mail.  

    2. Tell MDaemon to route mail for unknown addresses to another mail server, in this case I would choose SecurityGateway.  Setup / Server Settings / Unknown mail, check the box for "forwarded to another mail server" and uncheck the options for "returned to sender", "sent to postmaster", and "sent to the bad message folder".  In the field for Send the message to this host, enter the host name or IP address of the server to send the messages to. You'll also have to adjust the Account verification settings found at Security / Security Settings / Relay Control so that messages to/from unknown local users will be accepted.  There are a number of different ways you could do it, you could trust local IPs, you could require authentication, or you could just turn the checks off completely.  Its up to you.  If you decide to exclude the check for authenticated sessions, you'll have to configure SecurityGateway and/or Exchange to authenticate when sending to MDaemon.

    If you configure MDaemon this way you should proceed with caution. If MDaemon is available on the internet and you turn off the Account verification checks it will accept mail to any address on local domains and will generate lots of unwanted traffic.

    By default MDaemon requires authentication when mail is sent from local accounts. You can adjust these settings by going to Security / SMTP Authentication. Or you could configure SecurityGateway and/or Exchange to authenticate with MDaemon when sending mail to it.

     

    --
    Arron Caruth

    0 likes
  • B

    I'll check that out Arron, thank you.

    The whole reason in trying to get this to work is then we can move peoples mailboxes off of Exchange ad-hoc or per department. Moving everything over in one shot (which would be ideal) is going to take way to much time so being without an messaging servers. That's based on our initial test moves per mailbox. Then theres a synconization issue with the one or two Public Folders/Calendars.

    0 likes
  • B

    @Arron I'm back on this but I'm bumping up on a couple of items that I might not be understanding in your comments.

    You can adjust these settings by going to Security / SMTP Authentication.

    I can not seem to find that menu item. All I see in Security > Landing Page > Allowlists (i've tried adding the specific domain name and tried just a test addresss).

    Or you could configure SecurityGateway and/or Exchange to authenticate with MDaemon when sending mail to it.

    Not sure how to set that up in SGW.

    At the moment we have all our DNS records pointing to our Exchange server. MDaemon mail server is set on the trusted side and SGW is in the DMZ. All working fine as above thread suggests, except for this issue exchange passing off to SGW from an internal user and getting 5.7.0 Authentication required.

    I'll look at it again with fresh eyes in the morning.

     

    0 likes
  • A

    You can adjust these settings by going to Security / SMTP Authentication.

    Sorry, the menu is actually Security / Sender Authentication / SMTP Authentication and its in the MDaemon Remote Administration UI. 

    Or you could configure SecurityGateway and/or Exchange to authenticate with MDaemon when sending mail to it.

    To do this, you would need to loging to SecurityGateway and go to Setup / Users | Mail Configuration | Domain Mail Servers, select the domain mail server that is configured and points to MDaemon and then click Edit.  Check the box for "Requires SMTP Authentication" and then enter a valid username and password.  Then every time SecurityGateway tries to send a message to MDaemon, it will attempt to use the credentials provided to authenticate during the SMTP session.

    except for this issue exchange passing off to SGW from an internal user and getting 5.7.0 Authentication required.

    Is the 5.7.0 Authentication required error being returned by SecurityGateway or is SecurityGateway getting the error when its trying to send the message to MDaemon? If its when trying to send to MDaemon, you can use the information above to adjust the configurations so that it will work.

    --
    Arron Caruth

    0 likes
  • B

    So close!

    Mail from Exchange local mailbox user (mydomain.com) to an MDaemon mailbox user (same mydomain.com - but no user mailbox on the exchange server) now works by disabling SMTP Auth 'is always required'

    Now I'm getting DMeamon 550 5.1.1 Recipient unknown, when trying to send the other way. MDaemon mailbox user to Exchange mailbox user in the same domain.  I've tried adding the Exchange server IP or FQDN to (Security Manager) Trusted Host and Trusted IPs. Added Exchange to as a Smart Host. Server Settings > Delivery I have tried setting to "Send all email directly first, and then to smart host if problems, and seeing the Smart host here to the Exchange Server. But I can see that's counter to setting the Smarthost under the Domain Manager (mydomain.com), smarthost is set to the SGW so MDaemon mail server can send out email.

    So not sure if there is some routing that can be done the same way Exchange is able to 'relay' to another mail server.

    OR.. would it be better to remove the SGW from the equation altogether just using the Exchange Server as MDeamons Smarthost until all the mailboxes are migrated from Exchange to MDaemon. Assuming this might solved the 550 5.1.1 errors?

    0 likes
  • A

    Which server is responding with 550 5.1.1 Recipient Unknown?  If its not MDaemon, what server is it?

    If it is MDaemon, MDaemon, by default, expects there to be a mailbox for all users of a domain.  So if you have mydomain.com setup in MDaemon, then MDaemon expects it knows about all email addresses for mydomain.com.  If you attempt to send to user@mydomain.com and MDaemon does not have a user@mydomain.com mailbox, alias, mailing list, etc, it will respond with 550 Recipient Unknown. You can work around that in a couple of different ways.  

    1. Create all an account in MDaemon for every address.  If the address exists in exchange, tell MDaemon to forward the message SecurityGateway and let it route the mail.  

    2. Tell MDaemon to route mail for unknown addresses to another mail server, in this case I would choose SecurityGateway.  Setup / Server Settings / Unknown mail, check the box for "forwarded to another mail server" and uncheck the options for "returned to sender", "sent to postmaster", and "sent to the bad message folder".  In the field for Send the message to this host, enter the host name or IP address of the server to send the messages to. You'll also have to adjust the Account verification settings found at Security / Security Settings / Relay Control so that messages to/from unknown local users will be accepted.  There are a number of different ways you could do it, you could trust local IPs, you could require authentication, or you could just turn the checks off completely.  Its up to you.  If you decide to exclude the check for authenticated sessions, you'll have to configure SecurityGateway and/or Exchange to authenticate when sending to MDaemon.

    If you configure MDaemon to not require the MAIL and RCPT addresses to exist you should proceed with caution. If MDaemon is available on the internet and you turn off the Account verification checks it will accept mail to any address on local domains and will generate lots of unwanted traffic.

    Just trusing the IP addresses is not enough, you also have to open the MDaemon UI and go to Security/ Security Settings / Relay Control, and check the boxes for unless sent from a trusted IP address.  When you do this, it only allows the IP addresses in the trusted list to send to uknown recipients.   If a mail client is sending to MDaemon and try to send user user2@my.domain.com and user2 is not a valid recipient, then MDaemon will return an error.  You can avoid this by trusting all IP addresses clients might send from (this is a bad idea), or by checking the box for unless sent via authenticated SMTP session.  And then require all clients to authenticate when sending mail. 

    >OR.. would it be better to remove the SGW from the equation altogether just using the Exchange Server as MDeamons Smarthost until all the mailboxes are migrated from Exchange to MDaemon. Assuming this might solved the 550 5.1.1 errors?

    In my opinion, its easier to configure SecurityGateway as the smart host, but what is easier for you?  Also, you can use SecurityGateway to archive mail, it keeps a rolling 14 days of email that users can access them selves, and customers tend to like getting the quarantine reports vs looking at their spam folder.

    --
    Arron Caruth

    0 likes
  • B

    I can't seem to get this to find or route using the same domain. It still fails to find a recipient at the MDaemon level users mailbox.

    Option 1 - do you mean from within the users Mdaemon mailbox settings use Enable Forwarding? If so this doesn't seem to make sense given its an incoming based forwarding rule?

    Option 2 - trying to send a message from an MDaemon user only on MDaemon to a user with a mailbox on the Exchange server only (same domain name). Seems to route off of MDaemon server to SWG server..  but then hangs up on RCTP is a local domain, however is not a vaild user. If I send to an off domain it works no problem. So MDaemon will not route off itself is it has the same domain locally.

    Log from SGW:

    Accepting SMTP connection from [192.168.1.146 : 59509] on port 25
    Tue 2025-01-28 12:49:55: # Sender is a local domain mail server (MDaemon Email Server)
    Tue 2025-01-28 12:49:55: ========== Processing IP scripts
    Tue 2025-01-28 12:49:55: -- Executing: Blocklist --
    Tue 2025-01-28 12:49:55: -- End: Blocklist (0.000019 seconds) --
    Tue 2025-01-28 12:49:55: -- Executing: Location Screening --
    Tue 2025-01-28 12:49:55: Geolocation entry not found for IP address [192.168.1.146]
    Tue 2025-01-28 12:49:55: -- End: Location Screening (0.005737 seconds) --
    Tue 2025-01-28 12:49:55: -- Executing: PTR DNS lookup --
    Tue 2025-01-28 12:49:55: -- End: PTR DNS lookup (0.000002 seconds) --
    Tue 2025-01-28 12:49:55: ========== End IP scripts
    Tue 2025-01-28 12:49:55: --> 220 dougallmedia.com ESMTP SecurityGateway 10.5.2 UNREGISTERED; Tue, 28 Jan 2025 12:49:55 -0500
    Tue 2025-01-28 12:49:55: <-- EHLO mail3.dougallmedia.com
    Tue 2025-01-28 12:49:55: ========== Processing HELO scripts
    Tue 2025-01-28 12:49:55: -- Executing: Blocklist --
    Tue 2025-01-28 12:49:55: # Sender is on allowlist (Host global)
    Tue 2025-01-28 12:49:55: -- End: Blocklist (0.000027 seconds) --
    Tue 2025-01-28 12:49:55: -- Executing: HELO DNS lookup --
    Tue 2025-01-28 12:49:55: -- End: HELO DNS lookup (0.000009 seconds) --
    Tue 2025-01-28 12:49:55: ========== End HELO scripts
    Tue 2025-01-28 12:49:55: --> 250-dougallmedia.com Hello mail3.dougallmedia.com, pleased to meet you
    Tue 2025-01-28 12:49:55: --> 250-8BITMIME
    Tue 2025-01-28 12:49:55: --> 250-AUTH LOGIN PLAIN
    Tue 2025-01-28 12:49:55: --> 250 SIZE 0
    Tue 2025-01-28 12:49:55: <-- MAIL From:<user-on-MDaemon@dougallmedia.com> SIZE=1962
    Tue 2025-01-28 12:49:55: Found user: <user-on-MDaemon@dougallmedia.com>
    Tue 2025-01-28 12:49:55: ========== Processing AUTH scripts
    Tue 2025-01-28 12:49:55: -- Executing: Secure and authenticated port rules --
    Tue 2025-01-28 12:49:55: -- End: Secure and authenticated port rules (0.000004 seconds) --
    Tue 2025-01-28 12:49:55: -- Executing: Dynamic Screening --
    Tue 2025-01-28 12:49:55: -- End: Dynamic Screening (0.000003 seconds) --
    Tue 2025-01-28 12:49:55: ========== End AUTH scripts
    Tue 2025-01-28 12:49:55: ========== Processing MAIL scripts
    Tue 2025-01-28 12:49:55: # Executing outbound scripts
    Tue 2025-01-28 12:49:55: -- Executing: Invalid Sender --
    Tue 2025-01-28 12:49:55: -- End: Invalid Sender (0.000003 seconds) --
    Tue 2025-01-28 12:49:55: -- Executing: MAIL DNS Lookup --
    Tue 2025-01-28 12:49:55: -- End: MAIL DNS Lookup (0.000002 seconds) --
    Tue 2025-01-28 12:49:55: -- Executing: SMTP Authentication Required --
    Tue 2025-01-28 12:49:55: -- End: SMTP Authentication Required (0.000020 seconds) --
    Tue 2025-01-28 12:49:55: ========== End MAIL scripts
    Tue 2025-01-28 12:49:55: --> 250 <user-on-MDaemon@dougallmedia.com>, Sender ok
    Tue 2025-01-28 12:49:55: <-- RCPT To:<user-on-Exchange@dougallmedia.com>
    Tue 2025-01-28 12:49:55: Found expired negative cache entry for user
    Tue 2025-01-28 12:49:55: Performing Minger lookup (192.168.1.146:4069 for user-on-Exchange@dougallmedia.com)
    Tue 2025-01-28 12:49:55: User not found: <user-on-Exchange@dougallmedia.com>
    Tue 2025-01-28 12:49:55: ========== Processing RCPT scripts for recipient: user-on-Exchange@dougallmedia.com
    Tue 2025-01-28 12:49:55: ** RCTP is a local domain, however is not a valid user
    Tue 2025-01-28 12:49:55: ** Sieve scripts for the rcpt domain will not be executed
    Tue 2025-01-28 12:49:55: ** Message will be routed directly to domain's MX host
    Tue 2025-01-28 12:49:55: # Executing outbound scripts
    Tue 2025-01-28 12:49:55: -- Executing: Blocklist --
    Tue 2025-01-28 12:49:55: -- End: Blocklist (0.000009 seconds) --
    Tue 2025-01-28 12:49:55: -- Executing: Tarpitting --
    Tue 2025-01-28 12:49:55: -- End: Tarpitting (0.000003 seconds) --
    Tue 2025-01-28 12:49:55: -- Executing: Relaying Denied --
    Tue 2025-01-28 12:49:55: -- End: Relaying Denied (0.000002 seconds) --
    Tue 2025-01-28 12:49:55: -- Executing: Invalid Recipient --
    Tue 2025-01-28 12:49:55: ** Reject 550 <user-on-Exchange@dougallmedia.com>, Recipient unknown
    Tue 2025-01-28 12:49:55: -- End: Invalid Recipient (0.000010 seconds) --
    Tue 2025-01-28 12:49:55: ========== End RCPT scripts
    Tue 2025-01-28 12:49:55: --> 550 <user-on-Exchange@dougallmedia.com>, Recipient unknown
    Tue 2025-01-28 12:49:55: <-- QUIT
    Tue 2025-01-28 12:49:55: --> 221 See ya in cyberspace

    On the SGW I have tried to set up delivery options to send through the Exchange server with Authentication but the message is not making it off of SGW when sending to the same domain name.

    I'm stumped, and the trail license is running out.  

    0 likes
  • A

    The log snippet shows that the only user verification source is pointing to MDaemon.  The user-on-Exchange@dougallmedia.com account does not exist in MDaemon so SecurityGateawy is rejecting the message.  You can see in the log here:

    Found expired negative cache entry for user
    Tue 2025-01-28 12:49:55: Performing Minger lookup (192.168.1.146:4069 for user-on-Exchange@dougallmedia.com)
    Tue 2025-01-28 12:49:55: User not found: <user-on-Exchange@dougallmedia.com>

    There are three choices to fix the issue. 

    1. Create the account in MDaemon, conifgure the account in MDaemon to forward messages to Exchange or SecurityGateway.  If you forward it to SecurityGateway you'll have to add a user specific domain mail server that points at Exchange. 
    2. Manually create the account in SecurityGateway and configure SecurityGateway to send the message to exchange by setting a user specific domain mail server for the account
    3. Configure a second user verification source for the domain in SecurityGateway and point it at the exchange server.  You'll also have to set a user specific domain mail server for the account.

    Option 1 - do you mean from within the users Mdaemon mailbox settings use Enable Forwarding? If so this doesn't seem to make sense given its an incoming based forwarding rule?

    If you have an account in MDaemon that receives mail and you want that mail to end up in Exchange, you can tell MDaemon to send it to Exchange by configuring MDaemon to forward the mail to another server.  Enter the IP address of the other server in the Domain, [Host], or IP field.  

    Option 2 - trying to send a message from an MDaemon user only on MDaemon to a user with a mailbox on the Exchange server only (same domain name). Seems to route off of MDaemon server to SWG server..  but then hangs up on RCTP is a local domain, however is not a vaild user. If I send to an off domain it works no problem. So MDaemon will not route off itself is it has the same domain locally.

    This is occurring because SecurityGateway doesn't know about the users on the Exchange server.  I've provided 3 potential solutions at the top of this message.

     the trail license is running out.  

    You can request an extension from our customer service team (sales @ help.mdaemon.com).  Be sure to provide them with your trial registration key, do not post your license to the forums, and let them know you are still working on configuring it.

    --
    Arron Caruth

    0 likes
  • B

    Just to update for anyone that my follow - We have used the forwarding method mentioned to allow mail to flow from MDaemon to on prem exchange server using the same domain names. We are now in the midst of migrating over Exchange user mailboxes to MDaemon on a schedule that works for us in a live environment. Thanks to Aaron for all the assistance on this. We have purchased all the necessary licenses and support being confident this is a great self hosted replacement product for our needs moving forward.

  • A

    I'm glad we could help.  Thank you for sharing the update.

    --
    Arron Caruth

    0 likes
Please login to reply to this topic!

Participants