Re: [exim] Unable to send or receive mails, Tainted not permitted
The directory must be present beforehand
On 2022-02-13, necktwi via Exim-users wrote:
> It failed with
> 2022-02-13 12:01:02 1nJ8PW-0003xM-O7 == neck...@ferryfair.com R=localuser
> T=local_delivery defer (-1): Expansion of "${lookup {$local_part}
> dsearch,ret=full {/home}{$value/.maildir}fail}" (file or directory name for
> local_delivery transport) failed: "lookup" failed and "fail” requested
>
>
>> On 12-Feb-2022, at 6:29 PM, Jasen Betts via Exim-users
>> wrote:
>>
>> On 2022-02-12, necktwi via Exim-users wrote:
>>> I fixed it by setting
>>> directory = ${home}/.maildir
>>>
>>> But I want it to work with
>>> directory = /home/$local_part/.maildir
>>
>> use something like this instead.
>>
>> directory = ${lookup {$local_part} dsearch,ret=full
>> {/home}{$value/.maildir}fail}
>>
>>
>> --
>> Jasen.
>>
>> --
>> ## List details at https://lists.exim.org/mailman/listinfo/exim-users
>> ## Exim details at http://www.exim.org/
>> ## Please use the Wiki with this list - http://wiki.exim.org/
>
>
--
Jasen.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] message has lines too long for transport
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..}, I think.
It does not matter. This will not solve the "message has lines too long
for transport" issue because the value of max_received_linelength
remains the same after removing the long header and adding the folder
header.
In other words, the value of max_received_linelength will still be
greater than the value of ob->message_linelength_limit.
To my mind, it is necessary to recalculate the value of
max_received_linelength in the smtp_transport_entry function, taking
into account acl_removed_headers and acl_added_headers.
> Nevertheless, I'd like to have it as default behaviour of Exim,
> maybe with some global option as header_line_limit=998 (default)
> and 0 as "do not touch".
>
--
Best wishes Victor Ustugov
mailto:vic...@corvax.kiev.ua
JID: vic...@corvax.kiev.ua
public GnuPG/PGP key: https://victor.corvax.kiev.ua/corvax.asc
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] message has lines too long for transport
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..}, I think.
Nevertheless, I'd like to have it as default behaviour of Exim,
maybe with some global option as header_line_limit=998 (default)
and 0 as "do not touch".
--
Eugene Berdnikov
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] message has lines too long for transport
On 13/02/2022 17:48, Evgeniy Berdnikov via Exim-users wrote: Yes, my experiments confirm it: add_header option in ACLs produces a single-line header, and attempt to split it artificially by "\n" results in stripping the tail of line (after "\n") into X-ACL-Warn: header. That was asking to add two headers, the second with a default header name. Not one multiline header. The docs say: Leading and trailing newlines are removed from the data for the add_header modifier; if it then contains one or more newlines that are not followed by a space or a tab, it is assumed to contain multiple header lines. Each one is checked for valid syntax; X-ACL-Warn: is added to the front of any line that is not a valid header line. Try it with a newline, whitespace (i.e. tab or space) sequence, to get a multiline header. -- Cheers, Jeremy -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] message has lines too long for transport
On 2022-02-13 at 12:48:52 UTC-0500 (Sun, 13 Feb 2022 20:48:52 +0300) Evgeniy Berdnikov via Exim-users is rumored to have said: On Fri, Feb 11, 2022 at 08:48:33PM +0200, Victor Ustugov via Exim-users wrote: Evgeniy Berdnikov via Exim-users wrote on 19.11.2021 09:16: ... There are several variants to try: 1. Use header add/remove directives in ACLs and/or routers to "reinstall" problematic "References:" header if its length is too high, in hope Exim would fold it correctly. Exim doesn't fold such headers correctly. Yes, my experiments confirm it: add_header option in ACLs produces a single-line header, and attempt to split it artificially by "\n" results in stripping the tail of line (after "\n") into X-ACL-Warn: header. Proper splitting would add "\r\n " (any whitespace after the linebreak works, and it is essential.) -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] message has lines too long for transport
On Fri, Feb 11, 2022 at 08:48:33PM +0200, Victor Ustugov via Exim-users wrote: > Evgeniy Berdnikov via Exim-users wrote on 19.11.2021 09:16: ... > > There are several variants to try: > > > > 1. Use header add/remove directives in ACLs and/or routers to "reinstall" > > problematic "References:" header if its length is too high, in hope > > Exim would fold it correctly. > > Exim doesn't fold such headers correctly. Yes, my experiments confirm it: add_header option in ACLs produces a single-line header, and attempt to split it artificially by "\n" results in stripping the tail of line (after "\n") into X-ACL-Warn: header. IMHO, processing of add_header have better to be improved, to produce lines up to 78 characters, as recommended by RFC. -- Eugene Berdnikov -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
