On 2019-03-04, jan-jun.2019--- via Exim-users wrote:
> Hi Andrew,
> $ grep -ir x-relay-user /etc/exim4
> grep: /etc/exim4/passwd.client: Permission denied
> $
passwd.client is just a database of smarthost passwords, the lack of
other output is a pretty good indication that exim's not adding that
jan-jun.2019--- via Exim-users (Mo 04 Mär 2019 19:32:53
CET):
> > $ exim -bV
> > Exim version 4.92 #3 built 11-Feb-2019 21:35:34
>
> "Mine" / the version my hoster is running is:
>
> $ exim --version
> Exim version 4.82 #3 built 10-Feb-2018 19:43:33
ohoh, from Exim's perspective this is quite ol
Hi Andrew,
>> "Mine" / the version my hoster is running is:
>>
>> $ exim --version
>> Exim version 4.82 #3 built 10-Feb-2018 19:43:33
>> Copyright (c) University of Cambridge, 1995 - 2013
>> (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007
>> -
>> 2013
>> Berkeley DB: Berkel
On Mon, 4 Mar 2019, jan-jun.2019--- via Exim-users wrote:
Try
exim -bP config | grep -i x-relay-user
and check, if this header is part of your Exim configuration at all.
$ exim -bV
Exim version 4.92 #3 built 11-Feb-2019 21:35:34
"Mine" / the version my hoster is running is:
$ exim --
> Try
>
> exim -bP config | grep -i x-relay-user
>
> and check, if this header is part of your Exim configuration at all.
Hi, not clear what you mean by "config",
>>> The actual literal word 'config', which is one of the possible
>>> arguments
>>> to "exim -bP"
>>>
>>
Am 04.03.19 um 17:53 schrieb jan-jun.2019--- via Exim-users:
Try
exim -bP config | grep -i x-relay-user
and check, if this header is part of your Exim configuration at all.
>>> Hi, not clear what you mean by "config",
>> The actual literal word 'config', which is one of
>>> Try
>>>
>>> exim -bP config | grep -i x-relay-user
>>>
>>> and check, if this header is part of your Exim configuration at all.
>>
>> Hi, not clear what you mean by "config",
>
> The actual literal word 'config', which is one of the possible arguments
> to "exim -bP"
>
> See
> https://www.e
On 4 Mar 2019, at 9:27, jan-jun.2019--- via Exim-users wrote:
Heiko Schlittermann via Exim-users :
What directive you're talking about?
Sorry, forgot to mention this -- I meant
squirrel/config/config_local.php +=
define('hide_squirrelmail_header', 1);
Ok, but this doesn't explain the exis
jan-jun.2019--- via Exim-users (Mo 04 Mär 2019 15:27:31
CET):
> > Try
> >
> > exim -bP config | grep -i x-relay-user
> >
> > and check, if this header is part of your Exim configuration at all.
>
> Hi, not clear what you mean by "config", but just
> "exim -bP | grep -i relay"
> leads to e
Heiko Schlittermann via Exim-users :
>> > What directive you're talking about?
>>
>> Sorry, forgot to mention this -- I meant
>>
>> squirrel/config/config_local.php +=
>> define('hide_squirrelmail_header', 1);
>
> Ok, but this doesn't explain the existence/non-existence of the
> X-Releay-User head
Markus Robert Kessler via Exim-users (Mo 04 Mär 2019
01:04:04 CET):
> Hi Heiko,
> >
> > > When accessing /usr/sbin/exim4 locally, then Squirrel email client is
> > > able to write the header without "X-Relay-User" info. But,
> >
> > So, probably Squirrel isn't the origin of this header.
> >
> >
Hi Heiko,
> jan-jun.2019--- via Exim-users (So 03 Mär 2019
17:10:10 CET):
> > I want to prevent exim from sending out the "X-Relay-User" header line.
>
> In the first place I'd try to find the origin of this line.
> Exim doesn't know about any such line, the X- prefix indicates, that
> this isn't
12 matches
Mail list logo