On 20.05.22 16:33, Gedalya via Exim-users wrote: > On 5/20/22 22:10, exim-users--- via Exim-users wrote:
>> I would check if it is possible to get rid of the smarthost style config completely and configure as "internet site; mail is sent and received directly
>> using SMTP". Exim will lookup MX for outgoing mail in DNS and take care of delivery without any manual configuration. You should implement the usual stuff
>> to get your mail properly accepted and not marked as SPAM (you should do that anyways). > These days, the network you're coming from is a very important factor. A subscriber network (business / residential) or so-called "cloud" networks are considered bad reputation, this often applies to the entire network and not to a specific IP address. It can be very difficult to get your mail through, even if you follow the recommendations wrt DKIM, DMARC etc.
> The motivation to use a smarthost is clear.
You are right with that (especially with the network reputation), however the OP might replicate that "send direct" setup. I think configuring a lot manual routes instead of one (or a low
number) of smarthosts is getting unhandy really fast. > The remote_smtp transport does not use password.client. remote_smtp_smarthost does.
>
> You can indeed use the hubbed hosts setup, it makes sense to edit /etc/exim4/hubbed_hosts rather than the main config file, but you'd just have to change the transport to remote_smtp_smarthost and then authentication would work.
Thanks for pointing that out, I indeed changed the transport for my hubbed_hosts setup (some time ago). I like the approach of route lookup, because I try to avoid editing the config file for
possibly regularly changing parts (and it helps on updates, if the main configuration does not have to many changes).
