Slavko via Exim-users wrote on 12.04.2023 22:38:
Hi, I have a variable to extract the email address in from header set like
this:
${lc:${address:$h_From:}}
>>>
>>> Header is valid, but after decoding it contains comma without
>>> qoutes, the comma is address separator and thus
Jasen Betts via Exim-users wrote on 13.04.2023 10:07:
> On 2023-04-12, Victor Ustugov via Exim-users wrote:
>> Slavko via Exim-users wrote on 12.04.2023 20:42:
>>> Dňa 12. apríla 2023 16:50:29 UTC používateľ MRob via Exim-users
>>> napísal:
>>>> Hi,
Slavko via Exim-users wrote on 12.04.2023 20:42:
> Dňa 12. apríla 2023 16:50:29 UTC používateľ MRob via Exim-users
> napísal:
>> Hi, I have a variable to extract the email address in from header set like
>> this:
>>
>> ${lc:${address:$h_From:}}
>
> Header is valid, but after decoding it contain
Jeremy Harris via Exim-users wrote on 09.04.2023 22:29:
> On 09/04/2023 17:58, David Siebörger via Exim-users wrote:
>> The default settings for CC and USE_DB for FreeBSD seem to be
>> out-of-date.
>
> I'd like to hear from the FreeBSD package maintainer their preferences,
> even though you're tal
Jeremy Harris via Exim-users wrote on 15.03.2023 01:21:
> On 14/03/2023 13:17, Victor Ustugov via Exim-users wrote:
>> Office365 OAutn2 access token response size is over 4K)
>
> You are seriously stretching the original intent of Exim's
> string-handling with this.
Don&#
Yves Goergen via Exim-users wrote on 15.03.2023 00:02:
> Hello,
Hello
> I'd like to hide the IP address of authenticated users sending their
> messages over my SMTP server. The address always appears in the
> "Received" header and remains there for the final recipient.
You may set the value of r
Jeremy Harris via Exim-users wrote on 14.03.2023 14:18:
>> exim: length limit exceeded (386 > 256) for: recipient
>
> Yes, I've run into that (just this week!)
>
> I assume the "-be " was a retrofit after the use
> of a trailing arg for a mail recipient, and just uses the same
> machinery.
>
>
Hello.
I need to check if the HTTP response is a JSON.
I did not find a function like isjson, so I decided to check HTTP
response with a regular expression.
When I tried to run exim with a long value of -be option, I got an error:
exim: length limit exceeded (386 > 256) for: recipient
But there
Jeremy Harris via Exim-users wrote on 14.03.2023 00:00:
> On 12/03/2023 21:51, Victor Ustugov via Exim-users wrote:
>> Rather, the lack of SNI support does not prevent me from getting
>> response to access token refresh request. But Exim puts certificate
>> verification error
Victor Ustugov via Exim-users wrote on 12.03.2023 23:32:
>>>>> Is it possible to use SNI with ${readsocket?
>>>> No.
>>>
>>> Do you plan to implement this functionality?
>>
>> It's not currently on the radar. Glancing round the
>&g
Jeremy Harris via Exim-users wrote on 12.03.2023 20:06:
> On 12/03/2023 17:31, Victor Ustugov via Exim-users wrote:
>> Jeremy Harris via Exim-users wrote on 12.03.2023 19:09:
>>> On 12/03/2023 16:25, Victor Ustugov via Exim-users wrote:
>>>> Is it possible to use
Jeremy Harris via Exim-users wrote on 12.03.2023 19:09:
> On 12/03/2023 16:25, Victor Ustugov via Exim-users wrote:
>> Is it possible to use SNI with ${readsocket?
> No.
Do you plan to implement this functionality?
--
Best wishes Victor Ustugov
mailto:vic...@corvax.kiev.ua
public G
ael via Exim-users wrote on 12.03.2023 18:27:
> On Sun, Mar 12, 2023 at 03:10:54PM +0200, Victor Ustugov via Exim-users wrote:
>> https://packages.debian.org/source/sid/exim4 to it. I mean 75_*.patch
>>
>> Script get_oauth2_access_token-v.corvax.t...@gmail.com.sh is based on
Victor Ustugov via Exim-users wrote on 12.03.2023 15:10:
> Later, I'm going to make requests to get an access token using
> ${readsocket. In this case, I won't need to call ${run and curl.
Is it possible to use SNI with ${readsocket?
In other words, is it possible to make HTT
Andrew C Aitchison via Exim-users wrote on 12.03.2023 13:38:
>> without ${expand:
>>
>> # exim -be
>> '${lookup{smtp.gmail.com<@>v.corvax.t...@gmail.com<@>oauth2}lsearch*{/usr/local/etc/exim/smtpauthdb}{$value}fail}'
>>
>> ${run{/bin/sh -c
>> /usr/local/bin/get_oauth2_access_token-v.corvax.t...@gm
> Andreas Metzler via Exim-users wrote on 12.03.2023 08:55:
>> On 2023-03-11 Victor Ustugov via Exim-users wrote:
>> [...]
>>> client_send = ${lookup{$host<@>$sender_address<@>oauth2}\
>>>lsearch*{CONFDIR/smtpauthdb}{${expand:$value}}fail}
>&
Andreas Metzler via Exim-users wrote on 12.03.2023 08:55:
> On 2023-03-11 Victor Ustugov via Exim-users wrote:
> [...]
>> client_send = ${lookup{$host<@>$sender_address<@>oauth2}\
>>lsearch*{CONFDIR/smtpauthdb}{${expand:$value}}fail}
> [...]
>
> Hello
Hello.
# uname -sr
FreeBSD 13.1-RELEASE-p6
# pkg info -E exim
exim-4.96
exim compiled with all the patches from exim4_4.96-14
https://packages.debian.org/source/sid/exim4
I try to setup OAuth2 client authenticator:
client_oauth2:
driver = plaintext
public_name = XOAUTH2
client_sen
Hello.
exim 4.95, example 1:
# exim -be '${if match{abc}{\N^(\S+)\s*(\S.+)*$\N}{$1}{}}'
abc
That is ok
exim 4.95, example 2:
# exim -be '${if match{abc}{\N^(\S+)\s*(\S.+)*$\N}{$2}{}}'
That is ok
exim 96, example 1:
# exim -be '${if match{abc}{\N^(\S+)\s*(\S.+)*$\N}{$1}{}}'
abc
That is ok
Andrew C Aitchison wrote on 13.09.2022 13:44:
>> Or you may use source package from Debian repo:
>>
>> wget http://deb.debian.org/debian/pool/main/e/exim4/exim4_4.96-3.dsc
>> wget
>> http://deb.debian.org/debian/pool/main/e/exim4/exim4_4.96.orig.tar.xz
>> wget
>> http://deb.debian.org/debian/pool/
Mike Tubby via Exim-users wrote on 12.09.2022 00:27:
>
>>> Compiling Exim 4.96 fails on Devuan 4.0 Chimaera (basically Debian
>>> but without systemd).
...
>> # apt show libpcre2-8-0
>> ... ...
>> This package contains the 8 bit runtime library, which operates on
>> ASCII and UT
Evgeniy Berdnikov via Exim-users wrote on 13.02.2022 21:02:
> On Sun, Feb 13, 2022 at 06:31:23PM +, Jeremy Harris via Exim-users wrote:
>> Try it with a newline, whitespace (i.e. tab or space) sequence, to get a
>> multiline
>> header.
>
> This way works, yes. And may be programmed with ${sg
Evgeniy Berdnikov via Exim-users wrote on 19.11.2021 09:16:
>>> Yes, "References:" has 1018 octets while RFC limit is 998.
>>> This is known bug for several Outlook versions.
>>>
Not sure how to mitigate this one. Maybe I should truncate/remove the
header - and possibly break the thread
Heiko Schlittermann via Exim-users wrote on 05.05.2021 23:48:
> Victor Ustugov via Exim-users (Mi 05 Mai 2021 22:29:32
> CEST):
>>>> git clone --branch exim-4.94.2+fixes https://github.com/Exim/exim.git
>>>
>>> Sorry my fault, far too many branches, merges,
Heiko Schlittermann via Exim-users wrote on 05.05.2021 21:36:
> Victor Ustugov via Exim-users (Mi 05 Mai 2021 20:01:56
> CEST):
>> Heiko Schlittermann via Exim-users wrote on 05.05.2021 19:11:
>>
>>> In case you didn't notice. We've added a new but alre
Heiko Schlittermann via Exim-users wrote on 05.05.2021 19:11:
> In case you didn't notice. We've added a new but already deprecated main
> config option:
>
> allow_insecure_tainted_data = yes
>
> For this option you need to get exim-4.94.2+fixes. This option isn't
> part of 4.94.2!
Did
Victor Ustugov via Exim-users wrote on 05.05.2021 17:14:
> Heiko Schlittermann via Exim-users wrote on 05.05.2021 16:16:
>>>>>> I'd just refuse to create a bloated 4.94+fixes, instead of releasing
>>>>>> 4.95 as soon as possible.
>>>>>
Heiko Schlittermann via Exim-users wrote on 05.05.2021 16:16:
> Victor Ustugov via Exim-users (Mi 05 Mai 2021 14:48:20
> CEST):
>> Heiko Schlittermann via Exim-users wrote on 05.05.2021 14:57:
>>> Victor Ustugov via Exim-users (Mi 05 Mai 2021
>>> 13:21:55 CEST):
&
Heiko Schlittermann via Exim-users wrote on 05.05.2021 14:57:
> Victor Ustugov via Exim-users (Mi 05 Mai 2021 13:21:55
> CEST):
>>> I'd just refuse to create a bloated 4.94+fixes, instead of releasing
>>> 4.95 as soon as possible.
>>
>> Yesterday I
Heiko Schlittermann via Exim-users wrote on 05.05.2021 01:39:
> Jeremy Harris via Exim-users (Mi 05 Mai 2021 00:11:59
> CEST):
>> Having made me go and look... that is what I did, in b8514d1960
>> (which is since 4.94). A comma-sep option "file=/foo" after
>> the word "sqlite".
>
> Yes, that's
Heiko Schlittermann via Exim-users wrote on 04.05.2021 20:34:
>>> I cannot find any reference to the syntax you're using.
>>> Maybe I'm stupid.
>>
>> https://lists.exim.org/lurker/message/20200606.183617.325a7016.en.html
>>
>> https://git.exim.org/exim.git/commitdiff/b8514d1960e259d49ab2c84c89eba5
Heiko Schlittermann via Exim-users wrote on 04.05.2021 19:29:
> Heiko Schlittermann via Exim-users (Di 04 Mai 2021
> 17:44:23 CEST):
>> Odhiambo Washington via Exim-users (Di 04 Mai 2021
>> 17:00:36 CEST):
>>> On Tue, May 4, 2021 at 4:52 PM Heiko Schlittermann via Exim-users <
>>> temporarily r
Victor Ustugov via Exim-users wrote on 24.12.2019 22:56:
> Why the value of addr->message is different in warning messages sent by
> queue runner and warning messages sent by exim manually executed with -v
> -M options?
>
>
> This is a piece of warning message sent by ex
Victor Ustugov via Exim-users wrote on 24.12.2019 22:56:
> Hello
>
> Why the value of addr->message is different in warning messages sent by
> queue runner and warning messages sent by exim manually executed with -v
> -M options?
exim version 4.92.3
--
Best wis
Hello
Why the value of addr->message is different in warning messages sent by
queue runner and warning messages sent by exim manually executed with -v
-M options?
This is a piece of warning message sent by exim -v -M:
t...@mx.org.ua
host mail2.itsupport.kiev.ua [91.197.146.24]
Delay
Marco Gaiarin via Exim-users wrote on 28.09.2018 15:30:
> Mandi! Victor Ustugov via Exim-users
> In chel di` si favelave...
>
>> Try to use $mime_anomaly_level and $mime_anomaly_text
>
> Bingo! I've wrote:
>
> deny
> message = Serious MIME
Marco Gaiarin via Exim-users wrote on 13.09.2018 18:45:
> Mandi! Lena--- via Exim-users
> In chel di` si favelave...
>
>> No way I think. I'm curious: how often did you see messages triggering
>> this rejection?
>
> Oh, probably never... but indeed seems good to reject messages with a
> defecti
t;
Filtering did not set up a significant delivery.
Normal delivery will occur.
Please, show the content of your filter and the headers of your test
message.
> On 28 March 2018 at 04:46, Victor Ustugov via Exim-users <
> exim-users@exim.org> wrote:
>
>> Amjad Qasem via Exi
Amjad Qasem via Exim-users wrote on 27.03.2018 21:01:
> Thanks for your reply
>
> I have tested the below but it' didn't work
> if $h_from: contains "x...@example.com"
> then
> headers add X-Spam-Score: 100
> endif
untested:
if
"${if
forany{${addresses:$rh_from:}}{eq{$item}
Heiko Schlittermann via Exim-users wrote on 09.03.2018 12:06:
> Heiko Schlittermann (Fr 09 Mär 2018 11:02:01 CET):
> …
>> Good, then the error message could improved :) Thank you. I'll check if
>> we can fix it.
>
> Filed a wishlist item (bug#2252)
This is a simple fix to workaround the problem:
Marco Gaiarin wrote on 05.12.2017 22:45:
> Mandi! Viktor Dukhovni
> In chel di` si favelave...
>
>> What's motivation behind this thread? Are you trying to expand a
>> group whose members are listed indirectly as member DNs? If so,
>
> Exactly. If tehre's a group that hame email 'groupname@my
41 matches
Mail list logo
