Is it Possible to Use Smartermail for SMTP only with the "full email usage" at Rackspace?

We have a client john@XYZ.com who uses Rackspace for IMAP and Exchange.

However, they cannot send transactional emails through Rackspace.

We are trying to configure XYZ.com on our smartermail server and set up john@xyz.com as a user account

We then want him to update Outlook to use our server "mail.smartermail.com" to be able to send all of his outbound email, and still use rackspace.com for his IMAP message downloading/storing

I added mail.smartermail.com to the SPF record

I gave him credentials and walked him through changing his SMTP

1. Any messages he sends to himself get held on my mail.smartermail.com and don't go out because it sees it as a local domain (my interpretation)

2. Any messages to other people @xyz.com don't go out (again, my interpretation, but mail.smartermail.com is seeing it as a local domain)

Is there any way to force Smartermail - on this domain - to act purely as an SMTP sender and nothing else? No not look locally for delivery to the same domain, and to not look to his own account for local delivery to messages he sends to himself?

Thank you

Employee Replied

9/7/2021 at 11:07 AM

Employee Post

Hi Chris,

You may be able to use the feature that allows you to host domains externally. SmarterMail will always deliver locally first. So if the users account exists on the SmarterMail server, then that is where emails will be sent first when he tries sending to himself. As the system administrator you'll need to edit the domain for your user, and in the Configuration tab > Email card change the "Inbound Message Delivery" option to either "External (use MX record)" or "External (use host address)". Once you select the option you want to use, there will be a setting that's automatically enabled called "Deliver locally if user exists". You'll want to disable this so emails will not be sent to that user in SmarterMail.

Keep in mind, this will affect any other users you have on that same domain.

Inbound Message Delivery- Administrators can specify the domain location for incoming email delivery. This allows you to specify whether the domain is hosted locally or partially/entirely on an external server. The following options are available:
Local - Select this option if the mail server is hosted locally.
External (use MX record) - Select this option if the mail server is hosted partially or entirely externally. Messages will be delivered based on an MX lookup. Select the option "Deliver locally if user exists" to perform a local delivery instead of external if the user exists locally.
External (use host address) - Select this option if the mail server is hosted partially or entirely externally. Messages will be delivered to the specified host address. The host address can either be entered as an IP address or the Fully Qualified Domain Name (FQDN), such as mail.yourdomain.com. Select the option "Deliver locally if user exists" to perform a local delivery instead of external if the user exists locally.

Let us know how this works out for you.

chris Replied

9/7/2021 at 2:55 PM

This sounds great. Any/all users doing this are doing it for the same person, with their mail/calendar on the other platform, using this just for SMTP sending. I'll implement tonight and let you know if there are any issues.

Thank you

Employee Replied

9/7/2021 at 3:03 PM

Employee Post

You're welcome, Chris!

3 Replies

Reply to Thread

Related Knowledge Base Articles

3 Replies

Reply to Thread

Tags

Related Knowledge Base Articles