[exim] Re: Upgrading Exim to 4.94: $local_part vs. $local_part_data

On 2025-03-18, Yves Goergen via Exim-users wrote: > Hello, > > I'm upgrading Exim from 4.93 to 4.97 soon and read an entry in the > upgrading documentation [1]. It says I cannot use $local_part in > transports anymore and should consider $local_part_data. For some purposes you cannot use $local

[exim] Re: Exim as smtp client. Bad certificate ?

On 2025-01-08, Gandalf Corvotempesta via Exim-users wrote: > ### target.mail.server.example:login:password > 1.2.3.4:myu...@mydomain.net:xxx > > Tried with "*", the ip, the hostname and so on, it's always ignored Is 1.2.3.4 how you identify the smarthost? - it should be the name you use

[exim] Re: Why does this mail fail sender verification?

On 2025-01-04, Sebastian Nielsen via Exim-users wrote: > Ooh it actually does the DNS lookups too. > It’s a no-reply address so its not supposed to have any MX. > > Any way to disable the DNS lookups and only verify the literal format of the > header (I use verify = header_sender to ensure that

[exim] Re: how to test send email in command line under Linux ?

tldr: SWAKS > I'm new to exim and I'm trying to configure it correctly in my VPS so I can > use it for differents domains. > > I tried to send email (just to check if exim smtp works) using this command: > > *echo "Subject: teest" | /usr/sbin/exim4 -v rafn...@gmail.com >* > > And checking the resu

[exim] Re: disclaimer + DKIM does not work (reopened)

On 2024-11-13, brunoc68 via Exim-users wrote: > Dear all, > > I found out why DKIM signature did not work in my case. > > It comes from a bug in altermime as described here : > > * https://www.ijs.si/software/amavisd/release-notes.txt >

[exim] Re: How to forward certain error bounces to postmaster address

On 2024-10-25, Tapio Peltonen via Exim-users wrote: > I would like to set up exim to send recipient error 554 bounces to > postmaster (or another local address) in addition to the original > sender, but not other permanent errors. Any ideas how to configure > this? Assuming you mean 554 response

[exim] Re: Personalize MX

On 2024-10-23, Leonardo Boselli via Exim-users wrote: > [I am a long time user of this lists, but I retired and the work accound I > used > to use has been deleted - and i did not do any exim configuration since 2020] > So question is: how can i use, for certain domains, a specific MX: that is,

[exim] Re: Tainted filenames?

On 2024-08-22, Marco Gaiarin via Exim-users wrote: > > I'm 'de-tainting' my old exim config file, but i've found a trouble. > > I've a transport that have: > > dkim_private_key = ${if > exists{/etc/exim4/dkim/DKIM_DOMAIN-DKIM_SELECTOR-private.pem}{/etc/exim4/dkim/DKIM_DOMAIN-DKIM_SELECTOR-p

[exim] Re: sender verification details

On 2024-08-06, Ian Z via Exim-users wrote: > Does non-callout sender verification of nonlocal addresses, in the case of > a dnslookup router, determine the MX host of the sender domain? > > If yes, how can I access and log that information? So "verify = sender" That's going to activate the route

[exim] Re: event_action and "retry timeout exceeded"

On 2024-06-15, Viktor Ustiuhov via Exim-users wrote: > Hello. > > Please tell me how can I log "retry timeout exceeded" using event_action? > > I don't see any difference in the event for successful delivery of > messages and for "retry timeout exceeded". In both cases, the value of > $event_name

[exim] Re: Slightly OT - possible reasons for ending on Spamhaus blacklist

On 2024-04-18, Sebastian Arcus via Exim-users wrote: > This is slightly off-topic, but if anyone could shed some light, it > would be very much appreciated. A few days ago I started having issues > with the public IP address of one network I look after ending up on the > Spamhaus XBL and CSS bl

[exim] Re: How to restrict client login through IP whitelist

On 2024-03-26, TomNewChao via Exim-users wrote: > Thanks for your apply. >I have read your information about > `https://github.com/Exim/exim/wiki/BlockCracking`. The main purpose is to > modify the configuration to prevent user attacks through frequency limiting. > However, it doesn't meet

[exim] Re: tracing SMTP conversations

On 2024-02-24, graeme vetterlein via Exim-users wrote: > What I REALLY REALLY would like to do is watch the SMTP conversation > between my exim4 and its smarterhost > > (it's probably something I'm sending, so I want as much to see *my* side > of the conversation) > > I can see over many years

[exim] Re: Dynamic local_domains

On 2024-01-28, Jerry Stuckle via Exim-users wrote: > Hi, all, > > I saw a similar post on this server from last June but no solution as > far as i could tell. The only difference is I'm using MySQL instead of > PGSql and Debian instead of Ubuntu (although both use similar > configurations). E

[exim] Re: Reduce & inlist

On 2024-02-28, Slavko via Exim-users wrote: > Hi all, > > i found in ML archives recipe how to remove duplicates from list, > i tried it in that form in file used -be input: > > APPEND_ITEM = ${if def:value {$value,$item}{$item}} > INLIST = inlist{$item}{<,$value} > > ${reduce{<, item1

[exim] Re: Multiple servers , same mysql DB

On 2023-12-09, Gandalf Corvotempesta via Exim-users wrote: > Hi all > i need a simple advice > I have 3 mail servers that shares the same mysql with email accounts, > aliases and so on. > > Not all servers need to handle the full address list, in example, > domain "test1.it" is handled by server1

[exim] Re: Testing the GSASL authenticator with SCRAM-*-PLUS

On 2023-11-19, Martin Lambers via Exim-users wrote: > For archive completeness I'd like to mention that for SCRAM, the server > does not need to know the password itself, but just a salted and hashed > version of it, which can be set with server_skey instead of > server_password. For my simple

[exim] Re: Fwd: Upon applying 4.96-1 on test, "Tainted arg 2" appears

On 2023-11-09, Johnnie W Adams via Exim-users wrote: > No luck: basically tainted data is a case of you can't get there from here. There's no way to de-taint data. You have to start with untainted data. So given tainted data what you do is make some kind of lookup that returns an untainted dat

[exim] Re: Message ID length change: Expected?

On 2023-11-16, Jeremy Harris via Exim-users wrote: > On 16/11/2023 04:23, Jasen Betts via Exim-users wrote: >> for me 0..28 is not quite enough > > That's interesting info. How big a farm sharing a single spool > do you (indeed, anyone) think Exim ought to support?

[exim] Re: Message ID length change: Expected?

On 2023-11-14, Kris Oye via Exim-users wrote: > After re-reading the release notes, I see this footnote: > > "Notable changes: > > - The internal (but exposed in logs, Received: headers and Message-ID: > headers) > identifier used for messages is longer than in the previous release" > > I gue

[exim] Re: SEGV_MAPERR

On 2023-10-27, Jeremy Harris via Exim-users wrote: > On 27/10/2023 04:12, Julian Waters via Exim-users wrote: >> I haven’t raised a debian bug, I’m assuming it’s just my incompetence. > > That a segv can happen at all constitutes a bug, > however it was triggered. > >> Can you run with debug? > >

[exim] Re: Destination address in a transport

On 2023-10-26, Thomas Andrews via Exim-users wrote: > On 10/26/23 11:51, Jeremy Harris via Exim-users wrote: >> On 26/10/2023 10:11, Thomas Andrews via Exim-users wrote: >>> The external program is delivering the email to another server for >>> further processing. >> >> If that's all it is doing,

[exim] Re: Routing based on *recipient* IP address

On 2023-10-26, Gandalf Corvotempesta via Exim-users wrote: > Hi guys > > TL;DR: how can i route, to a specific smarthost, all email based on > the *recipient* mx IP address ? Yes, in your config use the dnslookup router for that smarthost use ignore_target_hosts with an inverted host list ( th

[exim] Re: disclaimer + DKIM does not work (reopened)

On 2023-10-24, Bruno CAPELETO via Exim-users wrote: > Le 24/10/2023 à 05:30, Jasen Betts via Exim-users a écrit : >> On 2023-10-19, brunoc68 via Exim-users wrote: >>> Dear all, >>> >>> In my organization I must configure Exim to add a disclaimer for every &g

[exim] Re: disclaimer + DKIM does not work (reopened)

On 2023-10-19, brunoc68 via Exim-users wrote: > Dear all, > > In my organization I must configure Exim to add a disclaimer for every > outgoing email, both text and html. > > Please do not argue that this should not be done blablabla... I have to > do this for administrative reasons, too long to

[exim] Re: Mitigation statement for CVE-2023-42119

On 2023-10-04, Slavko via Exim-users wrote: > Dňa 4. 10. o 8:45 Florian Zumbiehl via Exim-users napísal(a): > >> responses--however, if that recursive resolver is on a different machine >> than exim itself, which probably is a common setup, then an attacker with >> access to the same local network

[exim] Re: Is sender verification possible on a server that is used as a smarthost?

On 2023-10-04, Mario Emmenlauer via Exim-users wrote: > On 04.10.23 16:34, Chris Siebenmann wrote: >>> Now I would like to configure this server as a smarthost, so it will >>> forward emails from my desktop computers (without static IP or DNS). >>> Also, I'd like to have unique mailnames for each

[exim] Re: RFC822 Date format.

On 2023-09-25, Jasen Betts via Exim-users wrote: > I want to add a Resent-Date: header. Is there any way to access this > RFC822 timestamp using simple string expansion? so far this is my best candidate: ${run {/usr/bin/date --rfc-email}} -- Jasen. 🇺🇦 Слава Україні -- ## subscr

[exim] RFC822 Date format.

Exim generates correctly formatted Date headers when using control=submission *, and uses the same format in received headers. I want to add a Resent-Date: header. Is there any way to access this RFC822 timestamp using simple string expansion? (*) Control is submission seems somewhat Orwellian

[exim] Re: How to enable incoming DKIM check, ideally in Ubuntu/Debian?

On 2023-09-24, Slavko via Exim-users wrote: > --===1966052188431819066== > Content-Type: multipart/signed; boundary="Sig_/lzN9G3ASjGZEv5NTElT3kpN"; > protocol="application/pgp-signature"; micalg=pgp-sha256 > > --Sig_/lzN9G3ASjGZEv5NTElT3kpN > Content-Type: text/plain; charset=UTF-8 >

[exim] Re: Exim 4.97-RC0 released

On 2023-09-09, Andreas Metzler via Exim-users wrote: > On 2023-09-08 Jasen Betts via Exim-users wrote: > [...] >> https://packages.debian.org/search?keywords=libfile-fcntllock-perl >> seems to exist and have existed for several years. > >> It's a dependancy o

[exim] Re: Exim 4.97-RC0 released

On 2023-09-08, Ian Z via Exim-users wrote: > On Fri, Sep 08, 2023 at 12:39:57PM +0100, Jeremy Harris via Exim-users wrote: > >> Yup. On FreeBSD it seems to be called p5-File-FcntlLock, OpenSDB >> likewise (I think). > > On debian & derived, including ubuntu, the pattern would be > > libfile-fcntl

[exim] Re: No immediate delivery for emails locally submitted in systemd unit

On 2023-09-01, Andreas Metzler via Exim-users wrote: > On 2023-09-01 Slavko via Exim-users wrote: > [...] >> You have several options: > >> + use forking type unit (not appropriate in all cases) >> + disable kill in unit (not very good idea) >> + setup sendwait in mailx (not with bsd-mailx) >> +

[exim] Re: Looking for advice on Grey Listing vs outlook.com's behaviour

On 2023-08-22, Mark Elkins via Exim-users wrote: > Hi Exim Users, > > I'm looking for advice on Grey Listing vs outlook.com's behaviour of > retrying to send from multiple SMTP relays. > > Many years ago, we added Grey Listing as a feature to Exim. This delays > the receiving of new emails by 10

[exim] Re: Please untainted string

On 2023-08-21, Sławomir Dworaczek via Exim-users wrote: > Helo > Thank you for your answer > Unfortunately > failed to expand ACL string > "${if!eq{}{${lookup{{local_part}@${domain}}dsearch{/etc/exim": missing > lookup type Oops! Missing $ before {local_part} ${if!eq{}{${lookup{${l

[exim] Re: dmarc_history_file - incomplete data logged for spf and dkim

On 2023-08-20, Jeremy Harris via Exim-users wrote: > I could guess that "-" might be viable, by analogy with > the "rua" line coding, but that's not really sufficient. > The RFC standard for DMARC doesn't mention ARC. Is there > one somewhere? RFC8617 (experimental) https://datatracker.ietf.o

[exim] Re: fakereject and DSN

On 2023-08-19, Victor Ustugov via Exim-users wrote: > Hello. > > I have been using fakereject for many years. It allows me to deliver > emails to the recipients junk folder and return a permanent error code > to the sender's server. > > But when the sender requests a DSN, he receives a notificatio

[exim] Re: Please untainted string

On 2023-08-17, Sławomir Dworaczek via Exim-users wrote: > Helo > please untainted string > thank you and regards > deny > > message = "no no no" > > condition = ${if exists{/etc/exim/${local_part}@${domain}}{1}{0}} use lookup-dsearch condition = ${if!eq{}{${lookup{{local_part}@${domain}}dsear

[exim] Re: is UTF spamsenders now a thing?

On 2023-07-28, Cyborg via Exim-users wrote: > > ## No help required , this is just an info for you guys ## > > Hi, > > we have a new kind of spammer at our mailborder: > > 1qOF7T-002mUk-2Y H=(timesquareas.yachts) [216.9.227.107] Warning: > processing file "" for "To: X -> From: >

[exim] Re: Debian - dynamic local_domains?

On 2023-06-24, Ray O'Donnell via Exim-users wrote: > Hello, > > I'm new to this list, so apologies if this should be asked elsewhere - > please point me in the right direction if so. > > I run a small email server hosting a number of low-traffic virtual > domains (Exim + Dovecot). The OS is Debi

[exim] Re: delay not kicking in

On 2023-06-04, Slavko via Exim-users wrote: > --===5177538003882154364== > Content-Type: multipart/signed; boundary="Sig_/UlU3IJ5lalsyNpEcaEewzpE"; > protocol="application/pgp-signature"; micalg=pgp-sha256 > > --Sig_/UlU3IJ5lalsyNpEcaEewzpE > Content-Type: text/plain; charset=UTF-8 >

[exim] Re: delay not kicking in

On 2023-06-03, Jeremy Harris via Exim-users wrote: > On 03/06/2023 21:29, Julian Bradfield via Exim-users wrote: >> The delay on each recipient is triggered, but then cancelled because >> exim's smtp_out connection has been shut down. > > Thanks - that's the item of info I was missing and > hadn't

[exim] Re: Show regex capture group in logs?

On 2023-05-16, MRob via Exim-users wrote: > Hi, I want to capture part of a regex match (capture group) to put in > logs. This example using subject header works but is there a better way? > > warn set acl_c_temp = ${if match{$h_Subject:}{ group>}{$1}{none}} > !condition = ${if eq{$acl_c_te