On 2023-05-22 03:56, Markus Reschke via Exim-users wrote:
Hi!
On 2023-05-20 01:20, James via Exim-users wrote:
I use:
condition = ${if and
{{>{$rcpt_count}{2}}{>{${eval:$rcpt_count-$recipients_count}}{2}}}{yes}{no}}
Nice refinement!
On Sun, 21 May 2023, Alexander Carver via Exim-users
I was searching through the lists and reading the documentation but I'm
coming up short on blocking IP only senders.
I've seen ACLs checking sender_helo_name using isip{} but that doesn't
seem to do anything for the case of a literal IP:
H=([185.17.76.25])
What's the proper way to check for
On 2023-05-28 01:29, Cyborg via Exim-users wrote:
Am 28.05.23 um 04:04 schrieb AC via Exim-users:
I was searching through the lists and reading the documentation but
I'm coming up short on blocking IP only senders.
I've seen ACLs checking sender_helo_name using isip{} but that doe
On 2023-05-28 03:10, Slavko via Exim-users wrote:
Dňa 28. mája 2023 9:35:07 UTC používateľ AC via Exim-users
napísal:
Thanks, I already did check localhost but it appears what I was after was
actually sender_host_name being empty which, from what I understand, is what
H=([ip]) actually
I have one primary Exim installation that is my main mail server visible
to both the internal hosts and as a public host so TLS is enabled on it.
My internal hosts are using Exim in smarthost mode to handle sending
daemon mail to the main server. All of this is working fine, I just get
messag
On 2023-10-07 18:55, Ian Z via Exim-users wrote:
On Sat, Oct 07, 2023 at 04:10:24PM -0700, AC via Exim-users wrote:
The internal hosts are running self-signed certificates. So is there
a way to either make the self-signed certificates acceptable to the
main Exim server or otherwise disable the
On 2023-10-07 21:44, Viktor Dukhovni via Exim-users wrote:
On Sat, Oct 07, 2023 at 08:52:24PM -0700, AC via Exim-users wrote:
The error message on the main server is:
TLS error on connection from [host] (recv): A TLS fatal alert has been
received.: Certificate is bad
You've misunderstoo
On 2023-10-07 22:10, Viktor Dukhovni via Exim-users wrote:
On Sat, Oct 07, 2023 at 09:53:25PM -0700, AC via Exim-users wrote:
As for misunderstanding the error, perhaps it could be modified to better
explain which side is causing the message since I obviously assumed that a
message in the
On 2025-06-07 17:23, AC via Exim-users wrote:
I want to block any connection that doesn't have a successful rDNS (logs
report "no host name found") but searching around results in so many
different variants of an ACL rule to do this.
What is the proper way (likely in acl_smtp
08 00:30, Slavko via Exim-users wrote:
Ahoj,
Dňa Sat, 7 Jun 2025 23:44:50 -0700 AC via Exim-users
napísal:
Because according to the documentation that variable is set if it's
more than just no rDNS but also a mismatch with a forward DNS query.
Unless I'm misreading the below docume
okup failed for host $sender_host_address
On 6/7/25 5:23 PM, AC via Exim-users wrote:
I want to block any connection that doesn't have a successful rDNS (logs
report "no host name found") but searching around results in so many
different variants of an ACL rule to do this.
Wha
I want to block any connection that doesn't have a successful rDNS (logs
report "no host name found") but searching around results in so many
different variants of an ACL rule to do this.
What is the proper way (likely in acl_smtp_connect if I'm not mistaken)
that will simply reject any con
s.com. 2025060801 1800 900 604800 86400
On 2025-06-08 13:35, Jeremy Harris via Exim-users wrote:
On 2025/06/08 8:58 PM, AC via Exim-users wrote:
It can be a PTR, an A/, an MX, doesn't matter to me.
You said "rDNS lookup". That implies PTR.
--
## subscription configurati
13 matches
Mail list logo
