On 6 June 2019 17:21:41 BST, Marc Haber via Exim-users
wrote:
>That would be legal syntax as in
>
>|local_domains =
>@:localhost:${extract{1}{.}{$primary_hostname}}:other.domain.example
>
>?
That's how I read the docs on list-expansion;
they're string-expanded first.
As always, test.
--
On Thu, 06 Jun 2019 18:21:41 +0200, Marc Haber via Exim-users
wrote:
>That would be legal syntax as in
>
>|local_domains =
>@:localhost:${extract{1}{.}{$primary_hostname}}:other.domain.example
>
>?
Indeed, and it even makes its way through Debian's magic scripts,
making
On Thu, 6 Jun 2019 16:05:14 +0100, Jeremy Harris via Exim-users
wrote:
>On 06/06/2019 15:07, Marc Haber via Exim-users wrote:
>> Am I doing things wrong by adding the short host name to
>> local_domains?
>
>If it works, it's hard to call it wrong.
It's a matter of personal style, I know, and I
On 06/06/2019 15:07, Marc Haber via Exim-users wrote:
> in Debian, local_domains gets seeded with "@:localhost" plus whatever
> the local administrator has entered to augment the list of
> local_domains.
>
> I am usually entering the short hostname of the host in that list, so
> that my
Hi,
in Debian, local_domains gets seeded with "@:localhost" plus whatever
the local administrator has entered to augment the list of
local_domains.
I am usually entering the short hostname of the host in that list, so
that my local_domains usually ends up being like "@:localhost:myhost",
knowing
Am 06.06.19 um 14:07 schrieb Heiko Schlittermann via Exim-users:
> Hi,
>
> Cyborg via Exim-users (Do 06 Jun 2019 13:24:21 CEST):
>> As the Advisiory is a bit unspecific for a protection, shouldn't a check
>> for "$" in
>>
>> deny message = Restricted characters in address
>>
Am 06.06.19 um 14:25 schrieb Spencer Marshall via Exim-users:
> why is this only being applied to +local_domains? why not everything?
> denymessage = Restricted characters in address
>local_parts = ^[.] : ^.*[\$@%!/|]
>
>
Because there are two Restricted Char rules,
On 6 Jun 2019, at 13:25, Spencer Marshall via Exim-users
wrote:
> why is this only being applied to +local_domains? why not everything?
> denymessage = Restricted characters in address
> local_parts = ^[.] : ^.*[\$@%!/|]
Primarily because you’re not in control of what
why is this only being applied to +local_domains? why not everything?
denymessage = Restricted characters in address
local_parts = ^[.] : ^.*[\$@%!/|]
Hi,
Cyborg via Exim-users (Do 06 Jun 2019 13:24:21 CEST):
> As the Advisiory is a
On 06/06/2019 12:56, Cyborg via Exim-users wrote:
>> exim -bV | grep -i support
> Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc OpenSSL
> Content_Scanning DKIM DNSSEC Event OCSP PRDR TCP_Fast_Open
>
> Does that "Event" mean, the code is in it or is it part of another string?
It means
Hi Jeremy,
Exim is connecting via 127.0.0.1:783 to SA, so it is just glancing at
it, not messing around with it (as far as I understand). And since
headers are already missing in SA, cyrus can be ruled out.
Best regards, --- Jan.
Am 06.06.19 um 14:00 schrieb Jeremy Harris via Exim-users:
> On
Hi,
Cyborg via Exim-users (Do 06 Jun 2019 13:24:21 CEST):
> As the Advisiory is a bit unspecific for a protection, shouldn't a check
> for "$" in
>
> deny message = Restricted characters in address
> domains = +local_domains
> local_parts = ^[.] :
On 06/06/2019 12:43, Jan Kriesten via Exim-users wrote:
> Occasionally, the inbound header is stripped (no to, from, subject)
Any pattern you can see among the occurrences?
As well as SA being involved, you seem to be delivering via cyrus,
so there are multiple possible places for breakage. Is
Hi Jeremy,
Am 06.06.19 um 13:40 schrieb Jeremy Harris via Exim-users:
> exim -bV | grep -i support
Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc OpenSSL
Content_Scanning DKIM DNSSEC Event OCSP PRDR TCP_Fast_Open
Does that "Event" mean, the code is in it or is it part of another
On 06/06/2019 12:24, Cyborg via Exim-users wrote:
> As the Advisiory is a bit unspecific for a protection, shouldn't a check
> for "$" in
>
> deny message = Restricted characters in address
> domains = +local_domains
> local_parts = ^[.] :
Hey!
I've got something quite strange going on with our exim installation:
Occasionally, the inbound header is stripped (no to, from, subject) and
the only thing left is like following:
===
Return-Path:
Received: from service ([unix socket])
by service (Cyrus v2.4.20) with LMTPA;
Am 05.06.19 um 17:17 schrieb Heiko Schlittermann via Exim-users:
> The fix for CVE-2019-10149 is public now.
>
As the Advisiory is a bit unspecific for a protection, shouldn't a check
for "$" in
deny message = Restricted characters in address
domains =
El mié, 05-06-2019 a las 17:17 +0200, Heiko Schlittermann via Exim-
users escribió:
> The fix for CVE-2019-10149 is public now.
>
>
>
> https://git.exim.org/exim.git
>
> Branch exim-4_91+fixes.
>
>
>
> Thank you to
>
> - Qualys for reporting it.
>
> - Jeremy for fixing it.
Am 06.06.2019 10:28, schrieb Niels Dettenbach via Exim-users:
Hi Niels
Do you have
-lspf2
in
LOOKUP_LIBS
too? It seems, i need this.
You may even try to enable.
EXPERIMENTAL_SPF=yes
SUPPORT_SPF=yes
Got it! ;)
I added "-l spf2" in LOOKUP_LIBS and "EXPERIMENTAL_SPF=yes" and
Am Donnerstag, 6. Juni 2019, 10:09:20 CEST schrieb Luca Bertoncello via Exim-
users:
> I have these lines in Local/Makefile:
>
> SUPPORT_SPF=yes
> CFLAGS += -I/usr/include
> LDFLAGS += -L/usr/lib -lspf2
>
> and of course I have libspf2 (and dev...) installed.
> I'm using a Debian Jessie.
Do
Hi list!
I'm trying to compile Exim 4.92, but I get this error:
gcc -o exim
drtables.o: In function `init_lookup_list':
drtables.c:(.text+0x20e): undefined reference to
`spf_lookup_module_info'
collect2: error: ld returned 1 exit status
Makefile:645: recipe for target 'exim' failed
make[1]:
21 matches
Mail list logo
