Issues Trying to Smart Host Mail

randym

Verified User
Joined
Feb 19, 2006
Messages
10
Location
Las Vegas, Nevada USA
** I AM WILLING TO FINANCIALLY COMPENSATE ANYONE WHO HELPS ME FIX THIS -- UPON SATISFACTORY COMPLETION OF COURSE **

Hello to all of my fellow DirectAdmin Friends! :)

I have a customer who wants all of their mail (inbound and outbound) to first go to something called Xeams (xeams.com) They have Xeams configured as follows:

Spam firewall - Acts as a spam firewall that sits in front of another email server. Processes every email and sends good message to another server, such as Microsoft Exchange, Sendmail, Lotus Dominos or any other SMTP server. User mailboxes are not created on Xeams.

For them, in their own words, this also acts as a email archival system... I have tried the following:


Following are the contents of the file that I created as directed by the smart host docs:

Code:
smart_route_forward:
    driver = manualroute
    domains = ! +local_domains
    ignore_target_hosts = 127.0.0.0/8
    condition = ${if !eq{$original_domain}{$domain}}
    condition = ${if !eq{$original_domain}{}}
    condition = "${perl{check_limits}}"

    transport = remote_smtp_forward_transport

    route_list = * nospam.powerpbx.co
    no_more

smart_route:
    driver = manualroute
    domains = ! +local_domains
    ignore_target_hosts = 127.0.0.0/8
    condition = "${perl{check_limits}}"

    transport = remote_smtp

    route_list = * nospam.powerpbx.co
    no_more

After creating the above file, I tested just by trying to send an email inbound and outbound, and almost instantly received the following bounce-back in Roundcube:

This message was created automatically by mail delivery software.

Code:
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  E-MAIL ADDRESS REDACTED
    host nospam.powerpbx.co [45.38.157.21]
    SMTP error from remote mail server after RCPT TO:<EMAIL ADDRESS REDACTED>:
    550 5.7.1 <EMAIL ADDRESS REDACTED>... Relaying denied
Reporting-MTA: dns; da.powerpbx.co

Action: failed
Final-Recipient: rfc822;EMAIL ADDRESS REDACTED
Status: 5.0.0
Remote-MTA: dns; nospam.powerpbx.co
Diagnostic-Code: smtp; 550 5.7.1 EMAIL ADDRESS REDACTED... Relaying denied
Subject    test
From    EMAIL ADDRESS REDACTED
To    REDACTED
Date    Today 07:52
another one. tuesday 07:52

If you can please help me fix this, it would be most appreciated!

** I AM WILLING TO FINANCIALLY COMPENSATE ANYONE WHO HELPS ME FIX THIS -- UPON SATISFACTORY COMPLETION OF COURSE **
 
how did you install your Xeams ?
which edition and which method of operation was set?
it seems you did not set it up as a proxy, that's why its rejecting your proxy connections.
 
Xeams was installed with the typical Spam Firewall options. I have told Xeams to accept incoming mail from the DirectAdmin Server, but mail is not flowing in either direction.
 
mail relay is deprecated according to Xeams documentations, however,
It is still possible to enable mail relay and connect the DA server outgoing mail for your domain to flow towards the proxy.

Is your installation self hosted or cloud hosted by them ?

Only in case it's self hosted it will be possible to enable mail relay.
 
Hi Everybody,

Thanks so much for your input. I can confirm that Xeams is not the culprit in this case. It has to be something with either DirectAdmin, or the smarthosting file. I can say this confidently because when I moved the domains mail,pop and smtp records to point to another one of our mail servers simply by adding an A record both the new mail server and Xeams work together harmoniously.

This is not to say that I am not doing something incorrectly, but just following the docs for DirectAdmin, it's not working as it should.

I do indeed host my own as well as several other companies Xeams servers. I would say that we have been using Xeams since around the time of the Pandemic. If it has ever been the fault of Xeams, their support fixes whatever issues very rapidly.

I am open to thoughts, suggestions or even testing things out, but at this moment, the client's emails are on one of my Windows Mail Servers and everything is just purring away!

Thoughts?
 
exim configuration or server configuration, cant tell exactly.
this should be troubleshooted while looking at the whole system logs and mail logs.
the answer should be in the exim logs i guess,
the fact it works with windows does not mean there is no misconfiguration,
because you are getting 550, it means you are not allowed\authenticated.
might be the IP address is not set correctly on the closed relay server configuration.

telnet to the relay from your DA machine and send commands manually so you will know if it's an exim issue or a connection issue first.

about the configurations, the relevant doc would be this one https://www.exim.org/exim-html-current/doc/html/spec_html/ch-the_manualroute_router.html

also, make sure you are using the latest versions for both exim and exim.conf on the server.

if you would like me to have a closer look for you, send me a DM.
 
Are we trying to setup Split Delivery with Xeams and other mail exchange providers?
 
Back
Top