connections to spare.
Jan
On Mon, Sep 9, 2019 at 4:10 PM Phillip Carroll via Exim-users <
exim-users@exim.org> wrote:
my configuration has had something similar for years. Is there any
significant difference?
acl_check_mail:
# deny any mail without helo name
denymessage = HELO re
my configuration has had something similar for years. Is there any
significant difference?
acl_check_mail:
# deny any mail without helo name
denymessage = HELO required before MAIL
condition = ${if eq{$sender_helo_name}{} {1}}
(Yours obviously simpler to read)
On 9/6/2019
Because I was quite tardy in updating from 4.91 to 4.92, I am faced with
the the question as to best procedure for determining if anyone
successfully hacked into my Centos 7 server.
(I updated in late June, still oblivious to the existence of the CVE. A
week later I learn about the CVE.
On 7/23/2019 9:58 AM, Calum Mackay via Exim-users wrote:
hi Phillip,
If your Linux system was successfully hacked, you may see changes to:
/etc/cron.d/root
/etc/crontab
/root/.ssh/authorized_keys
/root/.ssh/known_hosts
(or the Centos equivalent, above was from a Debian system)
Hi Calum,
On 10/17/2019 2:11 PM, Andrew C Aitchison via Exim-users wrote:
On Thu, 17 Oct 2019, Nospam2k via Exim-users wrote:
I’ve installed 4.92.2 on CentOS 7.
There is an important security fix (for CVE-2019-16928)
in 4.92.3
In addition:
The CentOS 7 release-level package is available at epel
On 10/11/2019 2:55 AM, Jeremy Harris via Exim-users wrote:
The openssl_options are fed to the SSL_CTX_set_options() interface
(via some fairly-obvious processing). The tls_require_ciphers is
fed to SSL_CTX_set_cipher_list().
To the maintainers:
Help needed with a small grammar explanation.
At the moment I am interested in (at long last) making my exim.conf
somewhat aware of SPF/DKIM/DMARC in some regard, which has led me to
perusal of Chapter 58 of the exim 4.94 spec.
Coming from a world of Context-Free
On 7/16/2020 12:05 AM, Julian Bradfield via Exim-users wrote:
However, the DMARC example of 58.5 contains a construct that has me
totally stumped:
warn !domains = +screwed_up_dmarc_records
...
Presumably the left side of the "=" is negated in some manner, but that
is about as much as I
On 7/16/2020 11:56 AM, Jeremy Harris via Exim-users wrote:
On 16/07/2020 19:00, Phillip Carroll via Exim-users wrote:
warn !domains = +screwed_up_dmarc_records
control = dmarc_enable_forensic
Does precisely nothing because the control modifier appears AFTER the
failing "domains"
