Am 27.12.20 um 21:12 schrieb Jeremy Harris via Exim-users:
> On 25/12/2020 13:01, Sagar Acharya via Exim-users wrote:
>> The central problem is however, that dig gives me the correct MX
>> record and nslookup doesn't. MX record exists, just exim is not able
>> to find it.
>>
>> I even tried this em
Hello,
I have used vexim, and edit this for my needs.
VIRTUAL_VACATION_DELIVERY_SUBJECT = SELECT vacationsubject FROM
veximusers, veximdomains WHERE localpart='${quote_pgsql:$local_part}'
AND domain='${quote_pgsql:$domain}' AND
veximusers.domain_id=veximdomains.domain_id
VIRTUAL_VACATION_D
Hello,
first of all some distribution use openssl and some use gnutls.
check this with 'exim -bV'
On 27.12.19 19:53, David Saez Padros via Exim-users wrote:
> Hi
>
> a remote server which was able to send us mail using
> P=esmtps X=TLSv1:DHE-RSA-AES256-SHA:256 , after upgrading to Exim 4.93 +
> O
Hello @list,
at the moment we use clamav and Avast for content scanning.
The local dealer of avast has raise prices up to over 200%.
Now we are looking for a alternative.
Any suggestions?
Best regards,
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at
when exim is the MTA it can not be false to have a backup / 2nd MX, not
only when the primary is down. when one of your user spam and the
primary is black listed for example. but that is only one reason to send
the outoing mail thow the 2'nd mx.
The MDA can be ha-cluster. but in my opinion HA
