Dear collegues,
my administration writes one(!) email with more than 3000 receipients
in the envelope. (Please, no discussion about the sense of this. Period.)
Receiving that mail takes about 2 two hours.
Delivering that mail is done very quick, as usual.
I started debugging this and I recogniz
ts, it's a Debian 10
buster OS
with an exim 4.94 from the Debian 11-backport
I will try your proposals and keep you informed.
Regards, Olaf
On 3/11/21 9:59 PM, Olaf Hopp (SCC) via Exim-users wrote:
Dear collegues,
my administration writes one(!) email with more than 3000 receipients
On 3/12/21 9:34 AM, Olaf Hopp (SCC) via Exim-users wrote:
Hi, folks,
thanks for your answers so far
Just a few more input:
There is no rate limiting, tar pitting or so .
I created a special "accept" ACL just at the beginning of my acl_smtp_rcpt
I created a special router at the begin
On 5/5/21 11:04 AM, Jeremy Harris via Exim-users wrote:
On 05/05/2021 00:56, Dan Egli via Exim-users wrote:
Hey everyone, quick question, more an idle thought. When exim looks up a mail
to be delivered via remote_smtp, it seems to always prefer to use IPv4 even
when a v6 address is available.
On 7/31/21 11:19 PM, Jeremy Harris via Exim-users wrote:
On 30/07/2021 22:40, Alain D D Williams via Exim-users wrote:
I do not think that I can do that here. The certificate is given to me by Let's
Encrypt (le). Le verifies the (SNI) name by asking the agent to upload a nonce
(a file with 86 ra
Dear all,
I am migrating from exim 4.92 to 4.94, so the tainted data "problem" comes into
the focus.
I have a transport:
uservacation:
driver = autoreply
file = /etc/exim4/autoreply/${domain}/${local_part}.msg
[...]
After fiddling around with dsearch I ended up with two nested dsearch'es
On 12/14/21 14:31, Jeremy Harris via Exim-users wrote:
On 14/12/2021 12:58, Olaf Hopp (SCC) via Exim-users wrote:
is there a more elegant solution ?
If the router calling that transport, or some previous router
in the chain preceding, happened to have done successful
domain= and/or
On 1/19/22 08:57, Jasen Betts via Exim-users wrote:
exim can be configured how long to retry for and when to warn,
you can set it to 6 months if you want (well, you might have to say
183 days I don't think exim understands months)
Maximum seems to bee weeks:
s seconds
m minutes
h
On 1/25/22 23:44, Marc MERLIN via Exim-users wrote:
It's been a long time since I've had to edit my exim4 config, so I'm
very rusty.
A bit of googling didn't show any results, seems that it's not a common
need?
Is there a known working way to prevent any user on my exim server to
send Email to
Dear collegues,
I'm facing a weired 'tainted data' problem under Debian Bullseye with
exim-4.94.2
Currently I am working around this using the option
"allow_insecure_tainted_data = yes"
but I want to understand it and resolve it.
Normally everything runs fine for thousands of mails per day, such
On 3/9/22 16:56, Jeremy Harris via Exim-users wrote:
On 09/03/2022 13:49, Jeremy Harris via Exim-users wrote:
I agree that queued and non-queued should behave the same.
For your router, the dommains= test will have set up $domain_data.
Use it.
You'd need to do a similar job for $local_part, b
On 3/11/22 12:23, Jeremy Harris via Exim-users wrote:
On 11/03/2022 10:44, Olaf Hopp (SCC) via Exim-users wrote:
Do you still want me to debug the asymmetric behaviour wether
the mail was in the queue or not ?
If you have the time, yes. The first part is "why didn't nonqueued
fa
Dear collegues,
I'm debugging a problem between sympa and exim.
To start the daemon in debug mode I start it as
/usr/sbin/exim4 -bd -q5m -d+all
and I see the flow from extern to exim and from there to the sympa.
So far so good.
When the mails comes out of the sympa list manager it
calls directly /
On 7/4/22 11:12, Evgeniy Berdnikov via Exim-users wrote:
Place a script wrapper instead of symlink on /usr/sbin/sendmail, which
could add some flags, like that:
#!/bin/sh
exec /path/to/exim -d+all "$@"
Tried that with redirecting that command to
I see the beginning of the debug o
Hello
(apologies for being slightly off topic. A similar question will go into the
sympa list)
Is there anybody using exim and sympa where DSN (delivery status notification)
is
switched on for a list within sympa ?
When DSN is switched off for a list sympa calls the exim with the args
-oi -odi
On 7/6/22 11:29, Odhiambo Washington wrote:
Out of curiosity, why do you need DSN for a mailing list?
One of the list owners asked for it.
Don't ask me why, I'm just running the exim.
Olaf
--
Karlsruher Institut für Technologie (KIT)
Steinbuch Centre for Computing (SCC)
Dipl.-Geophys. Olaf
Dear collegues,
we moved some internal domains from "olddomain.org" to "newdomain.org"
we have internal routing for the new and old domain
Now we want to get rid of the routing for "olddomain.org"
and I want to rewrite "olddomain.org" to "newdomain.org"
so "f...@sub.olddomain.org" should become "f
On 8/9/22 17:54, Andrew C Aitchison wrote:
On Tue, 9 Aug 2022, Olaf Hopp (SCC) via Exim-users wrote:
[...]
You have:
^(.*)@(.*)\.olddomain\.org $1@$2.newdomain.org TS
The examples suggest that:
*@*olddomain.org $1@$2.newdomain.org TS
would be sufficient.
When using '
On 8/10/22 09:51, Andrew C Aitchison wrote:
the command, including any surrounding angle brackets.
Argh, RTFM :(
So $1 *does* include the opening "<" which is why you had to add the ">"
The rule
^([^<]*)@(.*)\\.olddomain\\.org $1@$2.newdomain.org TS
seems to work for me.
I still had
#testrouter:
# driver = manualroute
# senders = import...@example.net
# domains = example.com
# transport = remote_smtp
# route_list = * 192.168.178.1
*This* will never run since the domain part of "senders" != "domains"
But maybe you redacted the domains and hoping, that they
are equal in your
On 1/5/23 19:08, Olaf Hopp (SCC) via Exim-users wrote:
#testrouter:
# driver = manualroute
# senders = import...@example.net
# domains = example.com
# transport = remote_smtp
# route_list = * 192.168.178.1
*This* will never run since the domain part of "senders" != "domains&
Dear list,
we want to ratelimit incomming mail bursts (e.g. due
to phishing attacks).
To get an idea of reasonable values I have
warn
ratelimit = 100 / 60s / strict / $sender_address
log_message = RATELIMIT EXCEEDED for $sender_address $sender_rate
messages / $sender_rate_period
B
On 3/9/23 21:08, Jeremy Harris via Exim-users wrote:
On 09/03/2023 19:30, Slavko via Exim-users wrote:
Dňa 9. marca 2023 16:08:08 UTC používateľ Jeremy Harris via Exim-users
napísal:
On 09/03/2023 15:47, Olaf Hopp (SCC) via Exim-users wrote:
"x recipients per distinct sender per
Hi,
for legal reasons I have a list of domains, where I *must* send via TLS
Currently, I have two routers and transports:
router_A:
domains: +domainlist-with-TLS-Domains
transport: tlssmtp
router_B:
domains: *
transport: smtp
tlssmtp:
hosts_require_tls = *
On 3/23/23 17:19, Jeremy Harris via Exim-users wrote:
On 23/03/2023 16:01, Jeremy Harris via Exim-users wrote:
allsmtp:
driver = smtp
hosts_require_tls = ${if match_domain{$domain}{+domainlist-with-TLS-Domains}
{*}{}}
multi_domain = false
Actually, better have
max_rcpt = 1
rather t
On 3/24/23 13:42, Jeremy Harris via Exim-users wrote:
On 24/03/2023 12:28, Olaf Hopp (SCC) via Exim-users wrote:
Do you think "multi_domain = false" is not worth for trying ?
Corrrect.
But seems to work:
<= olafh...@kit.edu
=> f...@example.com ... X=TLS... example.c
On 3/28/23 15:59, Mike Tubby via Exim-users wrote:
Hi Olaf,
outbound_force_tls:
driver = dnslookup
domains = +tls_force_remote_domains
transport = remote_smtp_force_tls
outbound_lookup:
driver = dnslookup
domains = ! +local_domains
transpo
Sorry for being a bit off topic:
recently we had incoming phishing mails which all had a BCC header line.
So I thought, that's easy to defend and I introduced a data ACL
deny condition = ${if def:h_BCC: {yes}{no}}
My logs revealed a lot of them and I was afraid of doing some overblocki
28 matches
Mail list logo
