Yes, Jeff, is correct.
# man qmail-smtpd
smtproutes
Artificial SMTP routes. Each route has the form
domain:relay, or domain:relay|user|password in case of authenticated
routes without any extra spaces. If domain matches
host, qmail-remote will connect to relay, as if host had
relay as its only MX. (It will also avoid doing any CNAME lookups on
recip.) host may include a colon and a port
number to use instead of the normal SMTP port, 25:
inside.af.mil:firewall.af.mil:26
:submission.myrelay.com:587|myuserid|mypasswd
relay may be empty; this tells qmail-remote to look up
MX records as usual. port value of 465 (deprecated smtps port) causes
TLS session to be started. smtproutes may
include wildcards:
.af.mil:
:heaven.af.mil
Here any address ending with .af.mil (but not af.mil
itself) is routed by its MX records; any other address is artificially
routed to heaven.af.mil.
The qmail system does not protect you if you create an
artificial mail loop between machines. However, you are always safe
using smtproutes if you do not accept mail from
the network. Note: authsender routes have precedence over
smtproutes.
domain:relay
domain is the destination domain. Any mail going to this domain will
user the specified relay whether IP address or fqdn. --Eric
On 8/20/2020 2:03 PM, Jeff Koch wrote:
I think the way it works is that domainname.com would be the domain
name of who the mail is going to.
For example if you wanted to route all emails to Comcast addresses
thru a mailserver at IP 74.28.22.16 via port 26 you would have a line
that says:
comcast.net:74.28.22.16:26
Jeff
On 8/20/2020 2:39 PM, Eric Broch wrote:
What version of qmail
On 8/20/2020 12:24 PM, Miguel Angel Amable Ventura wrote:
Hello everyone,
I have been trying to set up the smtproutes file in
/var/qmail/control/smtproutes
with the following information:
domainname.com:ip_address_dest:587
restarted qmail with:
qmailctl stop
qmailctl start
systemctl restart dovecot
But when I send an email from domainname.com it does not relay to
the ip_address_dest server, instead it goes directly to the
destination domain and does not do the smarthost function. Checking
the logs in /var/log/qmail/send/current it does not even try to
contact the smarthost! Maybe I am missing to restart any other
service related to qmail to read the new config file?
Do you know what i am missing here to get it work ok?
Have a nice day!
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]