SMTP: Multiple Hostnames/Interfaces Support
With the SMTP proxy able to handle mail for many domains, allow the proxy to be configured so that an admin can assign a hostname per profile, or have the proxy report different hostnames per outgoing interface. (and the ability to specify which domains/profiles go out which interface). Allows for easier management and adoption of many smtp domains on a single asg appliance.
I just want to echo everyone else below, this really is a much needed feature. I am new to Sophos and have only been using it for about 3 months now, but I can't believe such a basic function is missing and I'm surprised that nothing has been done since this has been a topic for 6 years.
Jan Quilitz commented
This feature has been requested for years now - when can we get that working?
Rolf Müller commented
Hey Sophos People, the request for better smtp implementation has been around for years now. It would be nice if you could improve this, please!
Mike Horwath commented
I'll agree with the DKIM issues, and policies per domain.
I don't agree with the binding to a different address per domain as there is no need - you can handle hundreds of thousands (millions!) of domains for email over any individual IP address.
Same with outbound, and if you keep a clean house then any worries about later RBL issues are zero.
Robert Šusta commented
I was disappointed, when I realized, than angry as this is really needed, and finally furious because it can be set-up on any handmade linux box... Really, come on... For that money? Such elementar feature missing?
realy need, would be awesome.
Klaus Hahn commented
Need this urgently!
Paul Glass commented
Really could do with this right now.....
Maximilian Pfister commented
Yes...different smarthosts would help a lot - also needed for failover of outgoing SMTP traffic maybe through different ISPs
Bob Alfson commented
In addition, it should be possible to indicate a different smart host if different than Global.
This is vital for proper tenant mail domains. A single TLS cert and DKIM key are both currently bound to all outbound mail. Until we can segregate outgoing mail traffic by sender domain, so each gets it's own DKIM profile and TLS cert, footer, postmaster address and upstream smarthost, we have to stick to NAT'd connections.
Luke H commented
I vote for this feature too- it would be great to allow each SMTP profile to have a unique banner/HELO !
Peter Mott commented
The UTM should not listen for SMTP on every interface. Please provide at least a global setting to bind SMTP service to a single interface.
Dan (Gonzzo) commented
Alex said it all..
I perhaps just add the need to define a smarthost with login information per SMTP profile...
Adam Werner commented
This would be a very useful feature so I hope it is being strongly considered. Many of us need to support multiple mail domains and therefore having the ability to easily map an outbound mail domain to a specific WAN interface and IP address [without dealing with complicated SNAT and/or Multipath rules] would be awesome.
Chris Haaser commented
Please consider this feature. I can't be that hard to implement binding Exim to another IP?
Rolf Müller commented
Beeing able to adjust the IP-Address of the SMTP deamon and more over supporting individual Domains on multiple SMTP configurations as mentioned by Gert and Alex would be features greatly improving the UTM
With multiple email domains hosted behind UTM with per domain email server
we need ability to configure setting per each individual email domain
Please consider in a future to add to
SMTP Profile sections:
- Advanced settings (Use Global settings or Use individual settings)
such as SMTP hostname in HELO and SMTP banner strings. The Postmaster address address, Max message size
From SMTP -> Advanced Tab -> Advanced settings
- SMTP Bound to Address (Use Uplink Interfaces /External WAN or Use individual settings)
Additional Address of External WAN interface or Group of Additional Addresses of Uplink Interfaces)
(Follow Global Uplink balancing settings or Use individual settings)
Right now we can use SNAT to replace External WAN IP with Additional IP for SMTP protocol, but it will apply to all email domains.
Ability to create Interface Group from Additional Address and bound SMTP traffic to such group per email domain
Being able to route the packets from a different interface (IP address) is crucial too.