Op 08/09/2018 om 20:13 schreef Stephan Bosch:

Op 07/09/2018 om 21:32 schreef Jan Nowak:

...

Hello,

we have a problem after updating the software with the operation of sieve scripts sending a copy of the e-mails, e-mails are not transferred.

Configuration: dovecot-2.3.2.1 + dovecot-pigeonhole-0.5.2 + FreeBSD 11.2

log: Sep 06 13:28:17 lda(XXX@XXX)<38615>: Info: sieve: msgid=XXX-XXX-XXX-7788-XXX@XXXXnet: stored mail into mailbox 'INBOX' Sep 06 13:28:17 lda(XXX@XXX)<38615>: Info: sieve: Execution of script /usr/home/XXX/mail/XXX@XXX/.dovecot.sieve failed, but implicit keep was successful (user logfile /usr/home/XXX/mail/XXX@XXX/.dovecot.sieve.log may reveal additional details)

.dovecot.sieve.log: error: msgid=XXX-XXX-XXX-7788-XXX@XXXXnet: failed to redirect message to XXXXX@XXXXXX.com: smtp(127.0.0.1:25 http://127.0.0.1:25): DATA failed: 552 Message header not CRLF terminated (permanent failure).

On old configuration: dovecot 2.2 + dovecot-pigeonhole- 0.4  + FreeBSD 11.2 we don't have problem.

Has anyone had a similar problem, knows the solution?

Can you send me a pcap log (e.g. using Wireshark) from the connection between Dovecot and the MTA? Does it happen for every message?

Never mind. I see the problem already. What MTA is this?

Regards,

Stephan.

We are using Exim 4.91.

sob., 8 wrz 2018 o 20:38 Stephan Bosch stephan@rename-it.nl napisał(a):

Op 08/09/2018 om 20:21 schreef Stephan Bosch:

Op 08/09/2018 om 20:13 schreef Stephan Bosch:

Op 07/09/2018 om 21:32 schreef Jan Nowak:

Hello,

we have a problem after updating the software with the operation of sieve scripts sending a copy of the e-mails, e-mails are not transferred.

Configuration: dovecot-2.3.2.1 + dovecot-pigeonhole-0.5.2 + FreeBSD 11.2

log: Sep 06 13:28:17 lda(XXX@XXX)<38615>: Info: sieve: msgid=XXX-XXX-XXX-7788-XXX@XXXXnet: stored mail into mailbox 'INBOX' Sep 06 13:28:17 lda(XXX@XXX)<38615>: Info: sieve: Execution of script /usr/home/XXX/mail/XXX@XXX/.dovecot.sieve failed, but implicit keep was successful (user logfile /usr/home/XXX/mail/XXX@XXX/.dovecot.sieve.log may reveal additional details)

.dovecot.sieve.log: error: msgid=XXX-XXX-XXX-7788-XXX@XXXXnet: failed to redirect message to XXXXX@XXXXXX.com XXXXX@XXXXXX.com: smtp(127.0.0.1:25): DATA failed: 552 Message header not CRLF terminated (permanent failure).

On old configuration: dovecot 2.2 + dovecot-pigeonhole- 0.4 + FreeBSD 11.2 we don't have problem.

Has anyone had a similar problem, knows the solution?

Can you send me a pcap log (e.g. using Wireshark) from the connection between Dovecot and the MTA? Does it happen for every message?

Never mind. I see the problem already. What MTA is this?

To confirm, can you still send me that PCAP log?

Regards,

Stephan.

Have you verified that it happens with dovecot 2.3.21 and pigeonhole 0.5.21?

Aki

On 12/08/2024 16:39 EEST skraw--- via dovecot dovecot@dovecot.org wrote:

And what was the proposed solution to this?

---

dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org

2.1.17 is way older than 2.3.2.1

Please try with 2.3.21 (latest version).

Aki

On 12/08/2024 17:11 EEST skraw--- via dovecot dovecot@dovecot.org wrote:

I see it happening with dovecot 2.1.17 in a setup that is complex to update. So I am interested in the cause and possible solutions to bring them into this old setup.

---

dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org

On 12/08/2024 19:06, skraw--- via dovecot wrote:

As I already said, this setup is way too complex to think about an update. The cause of this problem cannot be a problem of the same size. If somebody (probably you or Stephan) already found the cause I could concentrate on backporting a solution. And future readers of the thread may be interested as well ...

---

dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org

Hi

this is what I found

https://dovecot.org/list/dovecot/2019-April/115674.html

John

Ok, it seems the version I am having here is older than the cited patch allows. It is likely pigeonhole-0.4.21 from 2017 where the lib-smtp does not exist at all. So I am a bit stuck ...