From ellie at fastmail.com Sun Mar 1 21:09:41 2020 From: ellie at fastmail.com (ellie timoney) Date: Mon, 02 Mar 2020 13:09:41 +1100 Subject: Cyrus IMAP 3.2.0-beta2 released Message-ID: <7d9a432f-b031-4984-b59a-5088b5475b45@www.fastmail.com> The Cyrus team is proud to announce the third beta release from the new Cyrus IMAP 3.2 series: 3.2.0-beta3 While 3.2 is still in beta, the main https://www.cyrusimap.org/ website will continue to be focused on the stable 3.0 series. The 3.2 website is available at https://www.cyrusimap.org/3.2/ I'm trialling hosting the release files using Github's releases feature. Please use the Github download links if possible, and advise if you have any problems! (It may even download faster due to Github's content delivery network.) Download URLs: https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.2.0-beta3/cyrus-imapd-3.2.0-beta3.tar.gz https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.2.0-beta3/cyrus-imapd-3.2.0-beta3.tar.gz.sig https://www.cyrusimap.org/releases/cyrus-imapd-3.2.0-beta3.tar.gz https://www.cyrusimap.org/releases/cyrus-imapd-3.2.0-beta3.tar.gz.sig Please consult the release notes and upgrade documentation before upgrading to 3.2: https://cyrusimap.org/3.2/imap/download/release-notes/3.2/x/3.2.0-beta3.html https://cyrusimap.org/3.2/imap/download/upgrade.html And join us on Github at https://github.com/cyrusimap/cyrus-imapd to report issues, join in the deliberations of new features for the next Cyrus IMAP release, and to contribute to the documentation. On behalf of the Cyrus team, Kind regards, ellie timoney From nprice at gibb.co.za Wed Mar 4 08:04:10 2020 From: nprice at gibb.co.za (Neil Price) Date: Wed, 4 Mar 2020 15:04:10 +0200 Subject: In-place upgrade 2.5.10 -> 3.08 (Debian) Message-ID: <7242362a-5311-fc83-5a69-bfec5f817f9d@gibb.co.za> I'm planning to upgrade Debian Stretch to Buster. Anyone done this on the same hardware? What cyrus related problems can I expect ? From heiler.bemerguy at cinbesa.com.br Mon Mar 16 11:13:39 2020 From: heiler.bemerguy at cinbesa.com.br (Heiler Bemerguy) Date: Mon, 16 Mar 2020 12:13:39 -0300 Subject: tcp keep alive? Message-ID: <1e510ff9-c6d9-a260-1c7b-3b19eea63880@cinbesa.com.br> An HTML attachment was scrubbed... URL: From ml at netfence.it Tue Mar 17 05:57:18 2020 From: ml at netfence.it (Andrea Venturoli) Date: Tue, 17 Mar 2020 10:57:18 +0100 Subject: Sendmail+Cyrus IMAP "Data format error" and bounces Message-ID: <9ef2e539-b264-d11b-fda2-5b42e92f67b3@netfence.it> Hello. I'm running sendmail 8.15.2, delivering to Cytus IMAP 3.0.13. From time to time, I receive some message that are refused and bounce. Do to possible blacklisting, I *really* want to avoid bounces. Here's a sample log: sm-mta[97841]: 00DI1r4x097841: from=, size=37059, class=0, nrcpts=1, msgid=, proto=UTF8SMTPS, daemon=MTA, relay=xxxxxxxxxxx.xxxxxxxx.net [37.148.183.222] sm-mta[97960]: AUTH=client, relay=localhost, mech=, bits=0 sm-mta[97960]: 00DI1r4x097841: to=xxxxxxxxxx, delay=00:00:11, xdelay=00:00:00, mailer=cyrusv2, pri=67551, relay=localhost, dsn=5.6.7, stat=Data format error sm-mta[97960]: 00DI1r4x097841: 00DI264w097960: DSN: Data format error sm-mta[97960]: 00DI264w097960: to=, delay=00:00:04, xdelay=00:00:04, mailer=esmtp, pri=30000, relay=mx1.slgnt.eu., dsn=5.1.2, stat=Host unknown (Name server: xxx.xxxxx.xx.: no data known) Most of these messages are spam/malware, but the above was a legitimate message from a service provider I use. I usually become aware of this, due to the second bounce (legitimate mail usually comes from a "noreply" address, while spam/malware of course from spoofed/inexistent addresses). There's nothing more in the sendmail logs and Cyrus logs nothing about this. I've searched the web, but found no explanation. I've asked the sendmail side and they suggested I ask on the Cyrus-side. Does anyone have any idea what might be the reason behind this "Data format error"? Any hint on how to avoid it? bye & Thanks av. From debbiep at polyfoam.com.au Tue Mar 17 06:58:31 2020 From: debbiep at polyfoam.com.au (Deborah Pickett) Date: Tue, 17 Mar 2020 21:58:31 +1100 Subject: Sendmail+Cyrus IMAP "Data format error" and bounces In-Reply-To: <9ef2e539-b264-d11b-fda2-5b42e92f67b3@netfence.it> References: <9ef2e539-b264-d11b-fda2-5b42e92f67b3@netfence.it> Message-ID: Hi Andrea, On 2020-03-17 20:57, Andrea Venturoli wrote: > From time to time, I receive some message that are refused and bounce. > Do to possible blacklisting, I *really* want to avoid bounces. > > Here's a sample log: > sm-mta[97841]: 00DI1r4x097841: from=, size=37059, > class=0, nrcpts=1, > msgid=, > > proto=UTF8SMTPS, daemon=MTA, relay=xxxxxxxxxxx.xxxxxxxx.net > [37.148.183.222] > sm-mta[97960]: AUTH=client, relay=localhost, mech=, bits=0 > sm-mta[97960]: 00DI1r4x097841: to=xxxxxxxxxx, delay=00:00:11, > xdelay=00:00:00, mailer=cyrusv2, pri=67551, relay=localhost, dsn=5.6.7, > stat=Data format error > sm-mta[97960]: 00DI1r4x097841: 00DI264w097960: DSN: Data format error > sm-mta[97960]: 00DI264w097960: to=, > delay=00:00:04, xdelay=00:00:04, mailer=esmtp, pri=30000, > relay=mx1.slgnt.eu., dsn=5.1.2, stat=Host unknown (Name server: > xxx.xxxxx.xx.: no data known) I don't use sendmail but I do use the same version of Cyrus that you do. The status 5.6.7 seems to be related to encodings.? It's defined in RFC 6531, SMTP Extension for Internationalized Email: When the SMTPUTF8-aware SMTP server supports enhanced mail system status codes [RFC3463], reply- code "X.6.7" [RFC5248] (see Section 4) is used, meaning "Non-ASCII addresses not permitted for that sender/recipient". [source: https://tools.ietf.org/html/rfc6531#section-3.5] Do all of the failures have proto=UTF8SMTP(S) in them, or just this example? For posterity, here is your post on the sendmail group, which I have read: https://groups.google.com/forum/#!topic/comp.mail.sendmail/5F2UZgAYrnI I agree with them that your anonymization of the log with xxx may have masked important information.? There may be temporary DNS failures going on but it's impossible to tell. -- Deborah Pickett System Administrator Polyfoam Australia Pty Ltd From a_s_y at sama.ru Tue Mar 17 08:31:32 2020 From: a_s_y at sama.ru (Sergey) Date: Tue, 17 Mar 2020 16:31:32 +0400 Subject: Sendmail+Cyrus IMAP "Data format error" and bounces In-Reply-To: <9ef2e539-b264-d11b-fda2-5b42e92f67b3@netfence.it> References: <9ef2e539-b264-d11b-fda2-5b42e92f67b3@netfence.it> Message-ID: <202003171631.32524.a_s_y@sama.ru> On Tuesday 17 March 2020, Andrea Venturoli wrote: > From time to time, I receive some message that are refused > and bounce. Do to possible blacklisting, I *really* want to > avoid bounces. I use Sendmail+Cyrus a very long time and I not remember this problem exactly. Cyrus is not receive messages in two cases: 1) message contains 8-bit symbols (not encoded to base64 or QP) in header; 2) message contains NUL character. The first is subject of reject8bit option in imapd.conf. About second look to https://groups.google.com/forum/#!topic/comp.mail.sendmail/xW7S5vXDNtY May be the first one causes the "Data format error" message. -- Regards, Sergey From ml at netfence.it Tue Mar 17 08:49:44 2020 From: ml at netfence.it (Andrea Venturoli) Date: Tue, 17 Mar 2020 13:49:44 +0100 Subject: Sendmail+Cyrus IMAP "Data format error" and bounces In-Reply-To: References: <9ef2e539-b264-d11b-fda2-5b42e92f67b3@netfence.it> Message-ID: On 2020-03-17 11:58, Deborah Pickett wrote: > Hi Andrea, Hello and thanks a lot for your interest. Finally I get some useful information on this! > The status 5.6.7 seems to be related to encodings.? It's defined in RFC > 6531, SMTP Extension for Internationalized Email: > > When the SMTPUTF8-aware SMTP > server supports enhanced mail system status codes [RFC3463], reply- > code "X.6.7" [RFC5248] (see Section 4) is used, meaning "Non-ASCII > addresses not permitted for that sender/recipient". > [source: https://tools.ietf.org/html/rfc6531#section-3.5] Please allow me to explain what I understand, then: _ sendmail is SMTPUTF8-aware (this is confirmed by EHLO); however Cyrus isn't? _ 5.6.7 means either the sender or the recipient is not ASCII: however I can see for sure that, at least in certain cases, the recipient is in fact ASCII (all my addresses are); possibly the sender isn't: altough in the logs I see an ASCII address, it might not be and it gets *represented* in ASCII? I'd find this strange, though; _ or, possibly, other headers are non ASCII: that's what I thought prior to your mail and it still seems more probable to me, but then I should see 5.6.9 (or 5.6.8?), not 5.6.7. Correct? In any case, I'm fine if these messages are plainly rejected; I'm not fine if they are accepted and then bounced. I guess this means the problem lies between sendmail and Cyrus, with the former accepting it and, only afterwards, the latter refusing it. Any way to configure one of the two to avoid this? > Do all of the failures have proto=UTF8SMTP(S) in them, or just this > example? Yes, they do. > I agree with them that your anonymization of the log with xxx may have > masked important information. Unfortunately I have to. If both ends were mine, I'd have no problem, but I cant' violate the privacy of others. > There may be temporary DNS failures going on but it's impossible to tell. I don't question this statement; however, this is irrelevant. AFAICT, the eventual DNS failure might cause the bounce to fail; however that's not my concern: I want to avoid the bounce in the first place. Or is something slipping me through? I can provide (alas anonymized) samples of logs where the bounce does not fail, if needed. bye & Thanks av. From ml at netfence.it Tue Mar 17 10:52:00 2020 From: ml at netfence.it (Andrea Venturoli) Date: Tue, 17 Mar 2020 15:52:00 +0100 Subject: Sendmail+Cyrus IMAP "Data format error" and bounces In-Reply-To: <202003171631.32524.a_s_y@sama.ru> References: <9ef2e539-b264-d11b-fda2-5b42e92f67b3@netfence.it> <202003171631.32524.a_s_y@sama.ru> Message-ID: On 2020-03-17 13:31, Sergey wrote: > On Tuesday 17 March 2020, Andrea Venturoli wrote: > >> From time to time, I receive some message that are refused >> and bounce. Do to possible blacklisting, I *really* want to >> avoid bounces. > > I use Sendmail+Cyrus a very long time and I not remember this > problem exactly. Cyrus is not receive messages in two cases: > 1) message contains 8-bit symbols (not encoded to base64 or > QP) in header; > 2) message contains NUL character. > > The first is subject of reject8bit option in imapd.conf. About second look > to https://groups.google.com/forum/#!topic/comp.mail.sendmail/xW7S5vXDNtY > > May be the first one causes the "Data format error" message. Thanks for pointing this out! I've been fighting the "NUL characters" problem on the sendmail side for a long time: it seems I won about some 10 months ago, since I don't see any more of these errors in the logs after May. I'm still seeing bounces, but, as you say, the reason is not the same! So, focusing on 1), I my imapd.conf I have: # If enabled, lmtpd rejects messages with 8-bit characters in the # headers. Otherwise, 8-bit characters are changed to `X'. (A proper # soultion to non-ASCII characters in headers is offered by RFC 2047 # and its predecessors.) # #reject8bit: no Also, https://www.cyrusimap.org/imap/reference/manpages/configs/imapd.conf.html#std:cyrusman-imapd.conf(5), says "reject8bit: 0" is the default. From this I understand my setup should NOT reject 8bit headers (but change non-ASCII characters to X). I'm now setting this explicitly and I'll see what happens. bye & Thanks av. P.S. Assuming I now receive such messages, what about settings munge8bit: 1? Any drawback or risk? From ml at netfence.it Tue Mar 17 15:13:48 2020 From: ml at netfence.it (Andrea Venturoli) Date: Tue, 17 Mar 2020 20:13:48 +0100 Subject: Sendmail+Cyrus IMAP "Data format error" and bounces In-Reply-To: References: <9ef2e539-b264-d11b-fda2-5b42e92f67b3@netfence.it> <202003171631.32524.a_s_y@sama.ru> Message-ID: <2f1aef32-4b1b-f37b-1a27-22cf9a6e067f@netfence.it> On 2020-03-17 15:52, Andrea Venturoli wrote: > Also, > https://www.cyrusimap.org/imap/reference/manpages/configs/imapd.conf.html#std:cyrusman-imapd.conf(5), > says "reject8bit: 0" is the default. > > From this I understand my setup should NOT reject 8bit headers (but > change non-ASCII characters to X). > > I'm now setting this explicitly and I'll see what happens. In fact, nothing changed. bye av. From debbiep at polyfoam.com.au Tue Mar 17 18:38:30 2020 From: debbiep at polyfoam.com.au (Deborah Pickett) Date: Wed, 18 Mar 2020 09:38:30 +1100 Subject: Sendmail+Cyrus IMAP "Data format error" and bounces In-Reply-To: References: <9ef2e539-b264-d11b-fda2-5b42e92f67b3@netfence.it> Message-ID: <7e34c529-2e12-74f1-5d5f-2dc82307f6cb@polyfoam.com.au> On 2020-03-17 23:49, Andrea Venturoli wrote: > _ sendmail is SMTPUTF8-aware (this is confirmed by EHLO); however > Cyrus isn't? Could be.? This option in imapd.conf might be relevant: rfc2047_utf8: 0 If enabled, imapd will parse any non-encoded character sequence in MIME header values as UTF8. This is useful for installations that either advertise the UTF8SMTP (RFC 5335) extension or receive mails with improperly escaped UTF-8 byte sequences. It is recommended that this option is left disabled unless there is good reason to do otherwise. [source: https://www.cyrusimap.org/imap/reference/manpages/configs/imapd.conf.html] > _ 5.6.7 means either the sender or the recipient is not ASCII: > ? however I can see for sure that, at least in certain cases, the > recipient is in fact ASCII (all my addresses are); > ? possibly the sender isn't: altough in the logs I see an ASCII > address, it might not be and it gets *represented* in ASCII? I'd find > this strange, though; > > _ or, possibly, other headers are non ASCII: that's what I thought > prior to your mail and it still seems more probable to me, but then I > should see 5.6.9 (or 5.6.8?), not 5.6.7. I wondered about that too.? I couldn't tell, and probably you can't either unless you can see all the headers in the messages that are being rejected.? I'd see this as an opportunity: now you can probably craft your own SMTP conversation to deliberately trigger the 5.6.7 rejection, and not have to wait for fate to deliver one to your server. It may also be instructive to temporarily disable UTF8SMTP in sendmail and see if that changes the rejection behaviour.? Do this carefully because you may reject more that you intended. > In any case, I'm fine if these messages are plainly rejected; I'm not > fine if they are accepted and then bounced. > I guess this means the problem lies between sendmail and Cyrus, with > the former accepting it and, only afterwards, the latter refusing it. > Any way to configure one of the two to avoid this? The config for that would be on the sendmail side, so I don't know.? Perhaps there's a way for sendmail to keep the connection from the sender open until it has attempted delivery to Cyrus; then sendmail could reject the sender's initial SMTP connection without having to generate a bounce message. Once you are armed with proof that Cyrus is rejecting these messages, you could take that back to the sendmail group and see if they can help. -- Deborah Pickett System Administrator Polyfoam Australia Pty Ltd From a_s_y at sama.ru Wed Mar 18 02:03:43 2020 From: a_s_y at sama.ru (Sergey) Date: Wed, 18 Mar 2020 10:03:43 +0400 Subject: Sendmail+Cyrus IMAP "Data format error" and bounces In-Reply-To: <2f1aef32-4b1b-f37b-1a27-22cf9a6e067f@netfence.it> References: <9ef2e539-b264-d11b-fda2-5b42e92f67b3@netfence.it> <2f1aef32-4b1b-f37b-1a27-22cf9a6e067f@netfence.it> Message-ID: <202003181003.43913.a_s_y@sama.ru> On Tuesday 17 March 2020, Andrea Venturoli wrote: > > I'm now setting this explicitly and I'll see what happens. > > In fact, nothing changed. I checked my Sendmail's log just in case and didn't find any "Data format error" messages. I keep a log for 1 month. About 200K messages were received by Cyrus at this time. But it is possible that bad messages are not accepted for some signs that I consider spam tags: about 80K messages were rejected. sendmail 8.16.0.41 (but 8.15.2 was used some years ago). Cyrus IMAP 2.5.15. I use 3.0.13 on experimental server but mail traffic too small here. Can You grab bad message before reject and send it to me? -- Regards, Sergey From miguel at prodemge.gov.br Wed Mar 18 10:23:15 2020 From: miguel at prodemge.gov.br (Miguel Mucio Santos Moreira) Date: Wed, 18 Mar 2020 11:23:15 -0300 Subject: Increasing metadata data In-Reply-To: <4297-5e722e80-1-522ce900@170685135> Message-ID: <285c-5e722f00-15-460ab180@19420509> Dear, We're upgrading our cyrus version from 2.4.16-5 on Debian 7 to 2.5.10-3 on Debian 9. Our environment is composed for backend, mupdate master and frontend servers in a Murder topology. Following the cyrus imap documentation we're creating new backend servers with that new version informed above. Even with some punctual issues, we're migrating mailboxes successfully to new backend server. However we diagnostic this new backend has a huge increasing in it's metadata data in comparison with the old ones. We are in doubt if it is a expected behaviour or not, and if not what could be the problem related to. Thanks in advance. Respectfully -- Miguel Moreira DTE/SRE/GRE - Ger?ncia de Redes +55(31)3339-1401 PRODEMGE - Companhia de Tecnologia da Informa??o do Estado de Minas Gerais Aviso: Esta mensagem ? destinada exclusivamente para a(s) pessoa(s) a quem ? dirigida, podendo conter informa??o sigilosa e legalmente protegida. O uso impr?prio ser? tratado conforme as normas da empresa e a legisla??o em vigor. Caso n?o seja o destinat?rio, favor notificar o remetente, ficando proibidas a utiliza??o, divulga??o, c?pia e distribui??o.? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ml at netfence.it Wed Mar 18 11:23:20 2020 From: ml at netfence.it (Andrea Venturoli) Date: Wed, 18 Mar 2020 16:23:20 +0100 Subject: Sendmail+Cyrus IMAP "Data format error" and bounces In-Reply-To: <7e34c529-2e12-74f1-5d5f-2dc82307f6cb@polyfoam.com.au> References: <9ef2e539-b264-d11b-fda2-5b42e92f67b3@netfence.it> <7e34c529-2e12-74f1-5d5f-2dc82307f6cb@polyfoam.com.au> Message-ID: On 2020-03-17 23:38, Deborah Pickett wrote: > On 2020-03-17 23:49, Andrea Venturoli wrote: >> _ sendmail is SMTPUTF8-aware (this is confirmed by EHLO); however >> Cyrus isn't? > > Could be.? This option in imapd.conf might be relevant: > > rfc2047_utf8: 0 > > If enabled, imapd will parse any non-encoded character sequence in MIME > header values as UTF8. This is useful for installations that either > advertise the UTF8SMTP (RFC 5335) extension or receive mails with > improperly escaped UTF-8 byte sequences. It is recommended that this > option is left disabled unless there is good reason to do otherwise. I'd be curious what damage this can do. In any case, activating it did not solve: I'm still getting "Data format error" and bounce. Still trying the other things. bye & Thanks av. From Hagedorn at uni-koeln.de Fri Mar 20 05:28:25 2020 From: Hagedorn at uni-koeln.de (Sebastian Hagedorn) Date: Fri, 20 Mar 2020 10:28:25 +0100 Subject: tcp keep alive? In-Reply-To: <1e510ff9-c6d9-a260-1c7b-3b19eea63880@cinbesa.com.br> References: <1e510ff9-c6d9-a260-1c7b-3b19eea63880@cinbesa.com.br> Message-ID: Have you enabled keepalive in imapd.conf? tcp_keepalive: 1 -- .:.Sebastian Hagedorn - Weyertal 121 (Geb?ude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universit?t zu K?ln / Cologne University - ? +49-221-470-89578.:. Am 16.03.20 um 16:13 schrieb Heiler Bemerguy: > Hey Guys, > > I have seen this on my Cyrus server 2.5.10, which is preventing new > users on IMAP: > > root at mailer:~# netstat -na |grep 177.194.176.48 |wc -l > 27 > root at mailer:~# netstat -na |grep 177.194.176.48 > tcp??????? 0????? 0 10.1.200.226:143??????? 177.194.176.48:56330??? ... > > Not even a single byte is sent to this IP (as seen on tcpdump), and this > Debian's tcp keepalive is set like: > > net.ipv4.tcp_keepalive_intvl = 5 > net.ipv4.tcp_keepalive_probes = 3 > net.ipv4.tcp_keepalive_time = 60 > > And there's an iptables rules like this: > > iptables -A INPUT -p tcp --syn --dport 143 -m connlimit > --connlimit-above 10 --connlimit-mask 32 -j REJECT > iptables -A INPUT -p tcp --syn --dport 143 -j ACCEPT > > Even though this user is multiple connected like that for HOURS....... > > -- > Best Regards, > > Heiler Bemerguy - CINBESA > Analista de Redes, Wi-Fi, > Virtualiza??o e Servi?os Internet > (55) 91 98151-4894 > > > ---- > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > -------------- next part -------------- A non-text attachment was scrubbed... Name: Hagedorn.vcf Type: text/x-vcard Size: 333 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5367 bytes Desc: S/MIME Cryptographic Signature URL: From daniel-oliveira at procergs.rs.gov.br Thu Mar 26 14:00:01 2020 From: daniel-oliveira at procergs.rs.gov.br (Daniel Soares de Oliveira) Date: Thu, 26 Mar 2020 15:00:01 -0300 Subject: Split users into specific partitions by username In-Reply-To: References: Message-ID: <4ca0084fd2fd32e2d87320d645c9a66c@expresso.rs.gov.br> Hello, I'm new to this world so I apologize if my question is in the wrong forum. ??? Is it possible to define user groups in cyrus and associate each group with a specific spool partition? Example: - Users with the first letter of the mailbox from A to D are created on partition A. - Users with the first letter of the mailbox from E to H are created on partition B. - Users with the first letter of the mailbox from I to Z are created on partition C. ??? And another question is whether a corresponding metadata partition is recommended for each spool partition? Best Regards Daniel S. Oliveira From ml at netfence.it Fri Mar 27 13:59:52 2020 From: ml at netfence.it (Andrea Venturoli) Date: Fri, 27 Mar 2020 18:59:52 +0100 Subject: Sendmail+Cyrus IMAP "Data format error" and bounces In-Reply-To: <2f1aef32-4b1b-f37b-1a27-22cf9a6e067f@netfence.it> References: <9ef2e539-b264-d11b-fda2-5b42e92f67b3@netfence.it> <202003171631.32524.a_s_y@sama.ru> <2f1aef32-4b1b-f37b-1a27-22cf9a6e067f@netfence.it> Message-ID: On 2020-03-17 20:13, Andrea Venturoli wrote: > On 2020-03-17 15:52, Andrea Venturoli wrote: > >> Also, >> https://www.cyrusimap.org/imap/reference/manpages/configs/imapd.conf.html#std:cyrusman-imapd.conf(5), >> says "reject8bit: 0" is the default. >> >> ?From this I understand my setup should NOT reject 8bit headers (but >> change non-ASCII characters to X). >> >> I'm now setting this explicitly and I'll see what happens. > > In fact, nothing changed. So, I made some tests. I prepared a text file with the following content (notice the non-ASCII character at the end of the Subject) and saved it as mail.txt: > Subject: Prova? > . "file mail.txt" says "mail.txt: UTF-8 Unicode text". Then I pushed this to my mailserver with curl: > curl --url 'smtp://myserver:25' --mail-from 'ml at netfence.it' --mail-rcpt 'ml at netfence.it' --upload-file mail.txt With "reject8bit: yes", sendmail refuses the message with "Message contains non-ASCII characters in headers". (Still don't know why it doesn't refuse it upfront, but bounces it!). With "reject8bit: no", I get the message and the subject is translated to "ProvaXX", as I would expect, since rfc2047_utf8 is, by default, off. Strangely, if I enable rfc2047_utf8, I still get "ProvaXX" as a subject. In any case, it seems that, at least for the subject, UTF-8 characters are handled (almost) as expected. *HOWEVER* curl does not use UTF8SMTPS, which is instead activated when I get mails that are bounced. Any idea for a similar tool which can use UTF8SMTPS, so I can repeat that tests? bye & Thanks av. P.S. I also tried tcpdump to get full data on a troublesome mail, but, unfortunately TLS was enabled and I was not able to get clear data. From eric at knudstrup.org Sat Mar 28 02:56:31 2020 From: eric at knudstrup.org (Eric Knudstrup) Date: Fri, 27 Mar 2020 23:56:31 -0700 Subject: Empty Trash on Thunderbird not getting propagated to replica Message-ID: <5a7a4a86-a549-3329-315d-6a8b0a376589@knudstrup.org> I have a 2.4.20 IMAP server I'm in the process of migrating to a 3.0.13 server on a different machine, using replication to move the database. This server was a 2.4.7 server until recently, when I upgraded it to 2.4.20 to make sure it was on the latest in its series. In order to get all of the data to replicate, I had to reconstruct all of the mailboxes on the 2.4.20 server. Then I moved all of the old messages out of a Trash folder into my Deleted Messages folder which has been delegated as the Trash folder.? To make Apple Mail happy. After I hit "Empty Trash" in Thunderbird, these messages were all expunged and apparently deleted from the 2.4.20 server. After letting it sit, I'm still not seeing that having propagated to the 3.0.13 system. What am I missing? From ellie at fastmail.com Mon Mar 30 00:13:16 2020 From: ellie at fastmail.com (ellie timoney) Date: Mon, 30 Mar 2020 15:13:16 +1100 Subject: Cyrus IMAP 3.2.0-beta4 released Message-ID: <5e7f1389-ca89-4d4a-9a45-41f5f00551b1@www.fastmail.com> The Cyrus team is proud to announce the fourth beta release from the new Cyrus IMAP 3.2 series: 3.2.0-beta4 While 3.2 is still in beta, the main https://www.cyrusimap.org/ website will continue to be focused on the stable 3.0 series. The 3.2 website is available at https://www.cyrusimap.org/3.2/ Download URLs: https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.2.0-beta4/cyrus-imapd-3.2.0-beta4.tar.gz https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.2.0-beta4/cyrus-imapd-3.2.0-beta4.tar.gz.sig Please consult the release notes and upgrade documentation before upgrading to 3.2: https://cyrusimap.org/3.2/imap/download/release-notes/3.2/x/3.2.0-beta4.html https://cyrusimap.org/3.2/imap/download/upgrade.html And join us on Github at https://github.com/cyrusimap/cyrus-imapd to report issues, join in the deliberations of new features for the next Cyrus IMAP release, and to contribute to the documentation. On behalf of the Cyrus team, Kind regards, ellie timoney From ellie at fastmail.com Tue Mar 31 18:36:44 2020 From: ellie at fastmail.com (ellie timoney) Date: Wed, 01 Apr 2020 09:36:44 +1100 Subject: Cyrus IMAP 3.2.0-beta4 released In-Reply-To: <5e7f1389-ca89-4d4a-9a45-41f5f00551b1@www.fastmail.com> References: <5e7f1389-ca89-4d4a-9a45-41f5f00551b1@www.fastmail.com> Message-ID: <56aced9c-dca7-4970-8fe3-eb09c33ee8e9@www.fastmail.com> Correction: https://www.cyrusimap.org/3.2/imap/download/release-notes/3.2/x/3.2.0-beta4.html https://www.cyrusimap.org/3.2/imap/download/upgrade.html On Mon, Mar 30, 2020, at 3:13 PM, ellie timoney wrote: > The Cyrus team is proud to announce the fourth beta release from the > new Cyrus IMAP 3.2 series: 3.2.0-beta4 > > While 3.2 is still in beta, the main https://www.cyrusimap.org/ website > will continue to be focused on the stable 3.0 series. The 3.2 website > is available at https://www.cyrusimap.org/3.2/ > > Download URLs: > > > https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.2.0-beta4/cyrus-imapd-3.2.0-beta4.tar.gz > > https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.2.0-beta4/cyrus-imapd-3.2.0-beta4.tar.gz.sig > > Please consult the release notes and upgrade documentation before > upgrading to 3.2: > > > And join us on Github at https://github.com/cyrusimap/cyrus-imapd to > report issues, join in the deliberations of new features for the next > Cyrus IMAP release, and to contribute to the documentation. > > On behalf of the Cyrus team, > > Kind regards, > > ellie timoney >