On Wed, Jun 01, 2022 at 04:55:18PM +0100, Jeremy Harris via Exim-users wrote:
> On 01/06/2022 16:46, Evgeniy Berdnikov via Exim-users wrote:
> > Strace of Debian bsd-mailx (my version is 8.1.2-0.20180807cvs-2)
> > shows that it does not append newline writing to MTA child process,
> > it only
Evgeniy Berdnikov via Exim-users writes:
> On Wed, Jun 01, 2022 at 04:15:18PM +0200, Kamil Jońca via Exim-users wrote:
>> %dpkg -S /usr/bin/bsd-mailx
>> bsd-mailx: /usr/bin/bsd-mailx
>
> Strace of Debian bsd-mailx (my version is 8.1.2-0.20180807cvs-2)
> shows that it does not append newline wri
On 01/06/2022 16:46, Evgeniy Berdnikov via Exim-users wrote:
Strace of Debian bsd-mailx (my version is 8.1.2-0.20180807cvs-2)
shows that it does not append newline writing to MTA child process,
it only converts "\n" to "\r\n".
Is bsd-mailx talking SMTP-on-TCP to exim, or stdin?
If the lat
On Wed, Jun 01, 2022 at 04:15:18PM +0200, Kamil Jońca via Exim-users wrote:
> %dpkg -S /usr/bin/bsd-mailx
> bsd-mailx: /usr/bin/bsd-mailx
Strace of Debian bsd-mailx (my version is 8.1.2-0.20180807cvs-2)
shows that it does not append newline writing to MTA child process,
it only converts "\n" to
Jeremy Harris via Exim-users writes:
> On 01/06/2022 04:42, Kamil Jońca via Exim-users wrote:
>> - "mail" command is the same in both cases.
>
> Obviously since one case runs exim and the other postfix, they cannot be.
--8<---cut here---start->8---
%which mail
On 01/06/22, Jeremy Harris via Exim-users (exim-users@exim.org) wrote:
> On 01/06/2022 12:05, Rory Campbell-Lange via Exim-users wrote:
>
> Possibly another case of
> https://lists.exim.org/lurker/message/20220429.095648.83dbd9f7.en.html
>
> - for which the workaround was
>hosts_try_fasto
On 2022-06-01 11:05, Rory Campbell-Lange wrote:
> My company's servers are having some curious issues sending some email to
google, running exim on Debian.
>
>
> The error seems unique to sending to google; we are sending around 12.5k
messages/day to a wide variety of recipients.
>
> Any though
On 01/06/2022 12:05, Rory Campbell-Lange via Exim-users wrote:
Exim version 4.94.2 #2 built 13-Jul-2021 16:04:57
The error seems unique to sending to google; we are sending around 12.5k
messages/day to a wide variety of recipients.
The error is along the following lines:
2022-06-01
My company's servers are having some curious issues sending some email to
google, running exim on Debian.
Exim version 4.94.2 #2 built 13-Jul-2021 16:04:57
The error seems unique to sending to google; we are sending around 12.5k
messages/day to a wide variety of recipients.
The error is al
will try to put this in and monitor it.
On 01/06/2022 09:45, Jeremy Harris via Exim-users wrote:
On 01/06/2022 09:14, Laura Williamson via Exim-users wrote:
remote_forwarded_smtp defer (-1): Failed to expand return path
"${srs_encode {thepassword} {$return_path} {$original_domain}}":
empty add
On 31.05.2022 13:40, Heiko Schlichting via Exim-users wrote:
> Jarland Donnell wrote:
>> A new variable was added in 4.95: message_linelength_limit
>>
>> This defaults to RFC spec which is 998 characters, but that's not where the
>> conversation should end. Absolutely no one out there is creating s
On 01/06/2022 09:14, Laura Williamson via Exim-users wrote:
remote_forwarded_smtp defer (-1): Failed to expand return path "${srs_encode
{thepassword} {$return_path} {$original_domain}}": empty address
Is it possible you are forwarding a message with an empty return_path
(a bounce) ?
If that'
On 1.06.2022 10:39, Arkadiusz Miśkiewicz wrote:
> On 31.05.2022 13:40, Heiko Schlichting via Exim-users wrote:
>> Jarland Donnell wrote:
>>> A new variable was added in 4.95: message_linelength_limit
>>>
>>> This defaults to RFC spec which is 998 characters, but that's not where the
>>> conversatio
Having an issue with this
remote_forwarded_smtp:
driver = smtp
max_rcpt = 1
return_path = ${srs_encode {SRS_SECRET} {$return_path}
{$original_domain}}
error:
remote_forwarded_smtp defer (-1): Failed to expand return path
"${srs_encode {thepassword}
On 01/06/2022 04:42, Kamil Jońca via Exim-users wrote:
- "mail" command is the same in both cases.
Obviously since one case runs exim and the other postfix, they cannot be.
But given this:
But there is another thing:
Normally, when message is delivered I use pipe transport:
--8<
bad internal_store_malloc request (2147483632 bytes) from string_catn 1167
I get this (now not with the many if contains in the filter file)
On 23/05/2022 15:36, Jeremy Harris via Exim-users wrote:
On 23/05/2022 15:10, Laura Williamson via Exim-users wrote:
bad memory allocation requested (2
16 matches
Mail list logo
