On 20 Mar 2018, at 12:03, Konstantin Boyandin via Exim-users
wrote:
> However, the cases I mention do not print anything like above to
> main.log (and MX records are normally resolved at that moment, both
> manually and via output of 'exim -bt u...@example.com').
Just a thought: if it's only one
Hello Graeme,
When there were (quite rare) actual connectivity issues, I saw the
messages like
2018-03-19 12:58:22 1exnoM-0004qJ-Bn ** us...@example.net
: all relevant MX records point to non-existent hosts
However, the cases I mention do not print anything like above to
main.log (and MX records
On 20/03/2018 08:57, Ted Cooper via Exim-users wrote:
> On 20/03/18 12:24, Rob Gunther via Exim-users wrote:
>> [snip]
>> I did this little bit of research because I actually want to accept
>> different max message sizes with Exim - BASED ON THE RECIPIENT DOMAIN.
>>
>> If my Exim server answers,
On 20/03/18 12:24, Rob Gunther via Exim-users wrote:
> [snip]
> I did this little bit of research because I actually want to accept
> different max message sizes with Exim - BASED ON THE RECIPIENT DOMAIN.
>
> If my Exim server answers, issues a size of 157286400 is there any way I
> can (must be R
