Re: Can't figure out why managesieve (pigeonhole) can't connect

2022-11-23 Thread PGNet Dev
i don't understand why it can't connect, this seems to work fine: fine ? you're manually overriding at least one problem with your certs/config ... - Status: The certificate is NOT trusted. The name in the certificate does not match the expected. *** PKI verification of server certificate fa

Re: Can't figure out why managesieve (pigeonhole) can't connect

2022-11-22 Thread PGNet Dev
Original Message From: justina colmena ~biz [mailto:just...@colmena.biz] Sent: Tuesday, November 22, 2022 at 12:44 PM EST To: Subject: Can't figure out why managesieve (pigeonhole) can't connect On Tuesday, November 22, 2022 8:25:19 AM AKST, PGNet Dev wrote: firs

Re: Can't figure out why managesieve (pigeonhole) can't connect

2022-11-22 Thread PGNet Dev
first, confirm that you can connect/authenticate to Dovecot's managesieve server without Roundcube in the picture. e.g., show the output of a successful 'openssl s_client ...' sieve authentication session Subject line says it all?  I am using Roundcube, and every time i click on "filters" i

Re: adding caldav/carddav next to dovecot

2022-10-14 Thread PGNet Dev
I don't have exp with 10k users, but I switched from radicale (which worked great!) to Nextcloud which has cloud functionality in addition to Card/CalDav interfaces too. Perhaps Nextcloud might fit your requirements. https://nextcloud.com/globalscale/ NextCloud's a fine solution. but, the OP'

Re: adding caldav/carddav next to dovecot

2022-10-14 Thread PGNet Dev
I have seen that one, don't you think that the performance difference between an interpreted language vs compiled language comes into play with 10k users? i'm sure it does. and that's a subjective decision about an objective measure. i've ~ 2K users, with radicale running alongside dovecot/f

Re: adding caldav/carddav next to dovecot

2022-10-14 Thread PGNet Dev
fyi here, to date, https://radicale.org/v3.html is very well behaved.

Re: Thunderbird can't connect to Dovecot (bad certificate: SSL alert number 42)

2022-09-14 Thread PGNet Dev
cert had an invalid/incorrect hostname fyi, https://kb.mozillazine.org/Files_and_folders_in_the_profile_-_Thunderbird ... cert_override.txt This is an optional file used to store a security exception. It appears to store the hos

Re: tika 2.4.1 'Text extraction failed' errors when dovecot+fts 2.3.19.1 passes embedded *.eml (message/rfc822) files ; org.apache.tika.parser.mail.RFC822Parser or dovecot ?

2022-08-01 Thread PGNet Dev
ached/embedded *.eml ... On Sat, Jul 30, 2022 at 7:51 PM PGNet Dev mailto:pgnet@gmail.com>> wrote: i'm running         dovecot 2.3.19.1 + fts         tika-server-standard 2.4.1 dovecot is feeding tika backend via fts_tika when dovecot passes data with *.eml atta

tika 2.4.1 'Text extraction failed' errors when dovecot+fts 2.3.19.1 passes embedded *.eml (message/rfc822) files ; org.apache.tika.parser.mail.RFC822Parser or dovecot ?

2022-07-30 Thread PGNet Dev
i'm running dovecot 2.3.19.1 + fts tika-server-standard 2.4.1 dovecot is feeding tika backend via fts_tika when dovecot passes data with *.eml attachments embedded, tika fails to correctly parse/extract content not clear if the issue is with tika, or what dovecot's passing in

Re: large search indexer tasks, submitted to flatcurve+tika+tesseract backend for attachment scanning, timeout even with "fts_index_timeout = 0"; how to increase/remove timeouts?

2022-07-28 Thread PGNet Dev
On 7/27/22 3:15 PM, Michael Slusarz wrote: where do I set that timeout to not fail, as above, on large index tasks? You need to change the source, as Tika has a hardcoded 60 second HTTP request limit. https://github.com/dovecot/core/blob/release-2.3.19/src/plugins/fts/fts-parser-tika.c#L76

large search indexer tasks, submitted to flatcurve+tika+tesseract backend for attachment scanning, timeout even with "fts_index_timeout = 0"; how to increase/remove timeouts?

2022-07-23 Thread PGNet Dev
i'm running dovecot 2.3.19.1 search indexing is enabled, via fts_flatcurve (dovecot23_fts_flatcurve) attachment processing is via fts_tika, with tika-server-standard-2.4.2 backend & tesseract5 OCR i'm working getting this optimized on a smaller, 4-core server that opt includes capping tessera

Re: verify dovecot 2.3.19.1 + fts_tika + tika-server 2.4.1 attachment scanning?

2022-07-19 Thread PGNet Dev
On 7/19/22 2:33 AM, Aki Tuomi wrote: Jul 18 21:28:23 mx-test tika[18970]: DEBUG [qtp977522995-24] 21:28:23,264 org.apache.tika.parser.pdf.PDFParser File: /tmp/apache-tika-9115808773791090696.tmp, length: 104932, md5: 092bf24b2cac33fac27965549c99613a You can see if this matches with your PDF f

Re: verify dovecot 2.3.19.1 + fts_tika + tika-server 2.4.1 attachment scanning?

2022-07-18 Thread PGNet Dev
On 7/18/22 7:20 AM, PGNet Dev wrote: On 7/18/22 5:53 AM, Aki Tuomi wrote: Can you provide logs & doveconf -n? referencing prior mention of a tika ML thread, ... tika upstream enabled a DEBUG build debugging receipt via fts-tika, with that build, of the failed-to-scan PDF is discussed

Re: verify dovecot 2.3.19.1 + fts_tika + tika-server 2.4.1 attachment scanning?

2022-07-18 Thread PGNet Dev
On 7/18/22 5:53 AM, Aki Tuomi wrote: On 17/07/2022 18:30 EEST PGNet Dev wrote: 1st Q: can anyone _here_ verify successful (no error/fail) PDF attachment scanning using dovecot 2.3.19.1 + fts_tika, with tika-server 2.4.1 Can you provide logs & doveconf -n? apart from continuing to d

Re: verify dovecot 2.3.19.1 + fts_tika + tika-server 2.4.1 attachment scanning?

2022-07-18 Thread PGNet Dev
On 7/18/22 5:53 AM, Aki Tuomi wrote: Can you provide logs & doveconf -n? referencing prior mention of a tika ML thread, https://dovecot.org/pipermail/dovecot/2022-July/125024.html latest tika logs, as part of the ongoing thread there, are, https://tika.markmail.org/message/e2

verify dovecot 2.3.19.1 + fts_tika + tika-server 2.4.1 attachment scanning?

2022-07-17 Thread PGNet Dev
debugging a reproducible tika-server fail with fts_tika has proved a bit challenging, upstream 1st Q: can anyone _here_ verify successful (no error/fail) PDF attachment scanning using dovecot 2.3.19.1 + fts_tika, with tika-server 2.4.1 ? i'm seeing issues with any/all PDF attachments. this

dovecot 2.3.19.1 + tika-server 2.4.1 failed attachment scanning -- ERROR: 'corrupt stream'?

2022-07-15 Thread PGNet Dev
i'm running dovecot 2.3.19.1 + fts_tika for attachment scanning, with tika-server 2.4.1 submitting a PDF attachment DIRECTLY to tika, via curl, there's no issue -- scan's OK on mail receipt in dovecot, the attachment is submitted to tika via fts, but scanning fails with a 'corrupt stream' ERR

Re: enable/control fts-tika debug logging in Dovecot 2.3.18 + Tika Server 2.4.0?

2022-05-23 Thread PGNet Dev
On 5/23/22 8:16 PM, Michael Slusarz wrote: Unfortunately, Tika has not yet been converted to events/categories with the ability to more granularly enable debugging just for this component. Aha! Thx. It's probably easier to just look at tika's debugging logs. The default log level (at least

enable/control fts-tika debug logging in Dovecot 2.3.18 + Tika Server 2.4.0?

2022-05-23 Thread PGNet Dev
i run dovecot-2.3.18-1.fc36.x86_64 i've installed Apache Tika, v 2.4.0 ls -al tika-server-standard-2.4.0.jar -rw-r--r-- 1 root root 59M May 2 09:53 tika-server-standard-2.4.0.jar tika's listening telnet 127.0.0.1 9998 Trying 127.0.0.1...

Re: Message attachments, relocated with Tbird in Dovecot maildir store, not openable; reversible by moving BACK to inbox?

2022-05-19 Thread PGNet Dev
On 5/19/22 3:12 AM, Virgo Pärna wrote: Check https://bugzilla.mozilla.org/show_bug.cgi?id=1589649 It seems to be some problem with current codepage of Thunderbird. Only in my case it also failed to open in application. And it creates magic 27 byte files.. thx for the link. of course, @ bug, "

Re: Message attachments, relocated with Tbird in Dovecot maildir store, not openable; reversible by moving BACK to inbox?

2022-05-18 Thread PGNet Dev
On 5/18/22 4:23 PM, Joseph Tam wrote: On Wed, 18 May 2022, PGNet Dev wrote: checking ls -altr /tmp/pid-59993/SomeFile.pdf     -r+ 1 pgnd pgnd   27 May 18 07:46 'SomeFile.pdf' This may or may not get you closer to the solution After enabling the memory cache

Re: Message attachments, relocated with Tbird in Dovecot maildir store, not openable; reversible by moving BACK to inbox?

2022-05-18 Thread PGNet Dev
On 5/18/22 9:51 AM, Virgo Pärna wrote: ls -al manual_13542AE.pdf -rw-r--r-- 1 pgnd pgnd 27 Apr 1 06:01 manual_13542AE.pdf Try enabling memory cache and setting memory cache size larger, then attachment size. That 27 byte file size is familiar. in Tbird, I

Re: Message attachments, relocated with Tbird in Dovecot maildir store, not openable; reversible by moving BACK to inbox?

2022-05-18 Thread PGNet Dev
On 5/18/22 8:00 AM, PGNet Dev wrote: 4/1/22 I see same symptoms when opening a mail in thunderbird 2 or 3 weeks after I received it, without moving it in another folder. But using "repair folder" in TB, I get it back, so for me it looks more like a TB cache problem. I've st

Re: Message attachments, relocated with Tbird in Dovecot maildir store, not openable; reversible by moving BACK to inbox?

2022-05-18 Thread PGNet Dev
4/1/22 I see same symptoms when opening a mail in thunderbird 2 or 3 weeks after I received it, without moving it in another folder. But using "repair folder" in TB, I get it back, so for me it looks more like a TB cache problem. I've still not managed to solve for this problem; 'repair' does

Re: dovecot-fts-solr Solr9 support

2022-05-17 Thread PGNet Dev
r.common.SolrException: Error loading class 'solr.FastLRUCache' /var/log/solr/solr.log.6:Caused by: java.lang.ClassNotFoundException: solr.FastLRUCache ... I can come up with a new config that should work in 8.x, 9.x, and the current dev branch by almost anyone. CaffeineCache _shoul

dovecot-fts-solr Solr9 support

2022-05-17 Thread PGNet Dev
I run dovecot-2.3.18 , & am deploying Solr search with 'dovecot-fts-solr' I run Solr standalone. When creating a dedicated 'dovecot' core, cp'ing from Dovecot's included solr schemas ls -al /usr/share/doc/dovecot/solr-* -rw-r--r-- 1 root root 12K Dec 3 06:48

Re: Message attachments, relocated with Tbird in Dovecot maildir store, not openable; reversible by moving BACK to inbox?

2022-04-01 Thread PGNet Dev
I see same symptoms when opening a mail in thunderbird 2 or 3 weeks after I received it, without moving it in another folder. Burt using "repair folder" in TB, I get it back, so for me it looks more like a TB cache problem. hm. 'repair' here does nothing for me. looking at my current TBird

Message attachments, relocated with Tbird in Dovecot maildir store, not openable; reversible by moving BACK to inbox?

2022-04-01 Thread PGNet Dev
I run dovecot --version 2.3.17.1 (476cd46418) on lsb_release -rd Description:Fedora release 35 (Thirty Five) Release:35 mail store is maildir mail_location = maildir:/data/vmail/%d/%n/Maildir:CONTROL=/data/vm

Re: 2FA/MFA with IMAP & postfix/submission

2021-07-14 Thread PGNet Dev
On 7/14/21 8:08 PM, Alex wrote: Hi, I have a dovecot-2.3.13 system on fedora34 with a few hundred IMAP4 accounts, as well as postfix users using submission. Clients are using primarily Outlook on Windows and old squirrelmail. Are there multi-factor options available? google roundcube + 2FA nu

Re: How to prevent, or change priority, of dovecot's FAILed relay-submission to relay's IPv6 address, and submit ONLY/first to IPv4?

2021-04-09 Thread PGNet Dev
Ah, well, I suggest you write your own patch and implement it then, since you have no interest in any explanations at all having already made up your mind. You din't come here for help or information, you came to argue. right. that's it.

Re: How to prevent, or change priority, of dovecot's FAILed relay-submission to relay's IPv6 address, and submit ONLY/first to IPv4?

2021-04-09 Thread PGNet Dev
then the software is entirely correct in deciding to use any of those addresses in whatever order it wants. Complete and utter malarkey. But believe what you like. Might wanna READ the code before going on about the "additional burden" http://dovecot.2317879.n4.nabble.com/how-to-set-smtp-clie

Re: How to prevent, or change priority, of dovecot's FAILed relay-submission to relay's IPv6 address, and submit ONLY/first to IPv4?

2021-04-09 Thread PGNet Dev
On 4/9/21 12:55 PM, @lbutlr wrote: On 09 Apr 2021, at 08:29, PGNet Dev wrote: And it's a bad assumption that since the host is dual-stack that all services on it will be. If a hostname resolves to both an A and record, it should provides services on both. Says who/what? The

Re: How to prevent, or change priority, of dovecot's FAILed relay-submission to relay's IPv6 address, and submit ONLY/first to IPv4?

2021-04-09 Thread PGNet Dev
And it's a bad assumption that since the host is dual-stack that all services on it will be. If a hostname resolves to both an A and record, it should provides services on both. Says who/what? There is no should/must/shall in any internet standard that suggest/implies/requires that.

Re: How to prevent, or change priority, of dovecot's FAILed relay-submission to relay's IPv6 address, and submit ONLY/first to IPv4?

2021-04-09 Thread PGNet Dev
On 4/9/21 8:08 AM, @lbutlr wrote: On 08 Apr 2021, at 06:08, PGNet Dev wrote: whereas other services listen at both IPv4 & IPv6 addresses, with IPv6 preferred over IPv4, postfix listens ONLY on IPv4, Do you mean that YOUR postfix only listens to ipv4? Yep. If so, wouldn't the so

Re: How to prevent, or change priority, of dovecot's FAILed relay-submission to relay's IPv6 address, and submit ONLY/first to IPv4?

2021-04-08 Thread PGNet Dev
rred over IPv4, postfix listens ONLY on IPv4, I don't intend to use it for POSTFIX. And therefore, neither for Dovecot. In _exactly_ the same manner/sense as dovecot's already-existing option to limit it's OWN listeners (inet_listener ) to IPv4 only. On 08/04/2021 14:45 PGN

Re: How to prevent, or change priority, of dovecot's FAILed relay-submission to relay's IPv6 address, and submit ONLY/first to IPv4?

2021-04-08 Thread PGNet Dev
How do you turn OFF, or reduce priority of, IPv6 connect attempts by submission relay? On 4/3/21 8:03 PM, PGNet Dev wrote: my server is a linux, dual-stack IPv4/IPv6 host it runs multiple services, including, but not limited to, postfix & dovecot the hostname is internal.mx.example

How to prevent, or change priority, of dovecot's FAILed relay-submission to relay's IPv6 address, and submit ONLY/first to IPv4?

2021-04-03 Thread PGNet Dev
my server is a linux, dual-stack IPv4/IPv6 host it runs multiple services, including, but not limited to, postfix & dovecot the hostname is internal.mx.example.com its DNS config, host internal.mx.example.com internal.mx.example.com has address 10.1.1.15

Re: set up for Dovecot redundancy -- store on edge server only if link to backofc server is down, otherwise deliver to final dest?

2021-01-04 Thread PGNet Dev
On 1/4/21 10:00 AM, Frank-Ulrich Sommer wrote: Perhaps I misunderstood the constraints, but (for a low nunber od accounts) what would be wrong with simply fetching the mail on the local server from dovecot1 and delivering it to dovecot2 with IMAP idle to prevent delays? Hm. I'd (only) been t

set up for Dovecot redundancy -- store on edge server only if link to backofc server is down, otherwise deliver to final dest?

2021-01-04 Thread PGNet Dev
I run Postfix + Dovecot. Currently, I've got a cloud-instance of Postfix that handles all the anti-spam/auth/routing. On successful 'pass', it resends email -- over a VPN link -- to a *local* Postfix instance, which then LMTP-delivers to a Dovecot instance on the same box. Works great. I'd l

Re: Dovecot alternatives with good i18n support?

2020-11-22 Thread PGNet Dev
On 11/22/20 6:59 AM, David Bürgin wrote: Hello! I’m interested in exploring alternative IMAP servers that have good support for internationalised email, such as support for SMTPUTF8, IDN mail domains, Unicode local-part, etc. etc. If you used to use Dovecot, and found an alte

Re: [patch] enhancement for tika server protected by user/password basic auth

2020-11-15 Thread PGNet Dev
On 11/15/20 1:29 PM, John Fawcett wrote: atm, listening on localhost, with Dovecot -> Tika direct, no proxy. similarly fragile under load. throwing ~10 messages with .5-5MB attachments at it at once causes all sorts of complaints. frequently, like this Nov 15 15:59:40 test.loc tika[35696]:

Re: [patch] enhancement for tika server protected by user/password basic auth

2020-11-15 Thread PGNet Dev
On 11/15/20 12:21 PM, John Fawcett wrote: I'm using tika-server.jar installed as a service yup. same here. atm, listening on localhost, with Dovecot -> Tika direct, no proxy. similarly fragile under load. throwing ~10 messages with .5-5MB attachments at it at once causes all sorts of compla

Re: [patch] enhancement for tika server protected by user/password basic auth

2020-11-15 Thread PGNet Dev
On 11/15/20 11:13 AM, John Fawcett wrote: Just a couple of updates about Tika and Solr together. 1. On mass reindexing I'm seeing panics - see below. These are present with Dovecot 2.3.10 and 2.3.11.3. Seem to go away with the fix which was previously posted on this list by Josef 'Jeff' Sipek, w

Re: [patch] enhancement for tika server protected by user/password basic auth

2020-11-15 Thread PGNet Dev
On 11/15/20 6:33 AM, John Fawcett wrote: I've configured a tika server behind an apache proxy which enforces basic auth, but sending basic auth credentials for a tika server is not currently supported by Dovecot. i was _just_ setting up a tika instance behind a nginx proxy with basicauth in pl

Re: dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?

2020-11-13 Thread PGNet Dev
I guess you didn't need to enclose username and password in quotes, i.e. fts_solr = url=https://myuser:my%40p...@solr.example.com:8984/solr/dovecot/ use_libfts soft_commit=yes batch_size=250 On 11/13/20 12:56 PM, John Fawcett wrote: I guess you didn't need to enclose username and password in

Re: dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?

2020-11-13 Thread PGNet Dev
On 11/13/20 11:37 AM, John Fawcett wrote: still dunno why the 401. :-/ So I just did a quick check of running dovecot with a standalone solr-8.7.0 instance and I'm not seeing any issues. +1 I confirm I haven't configured anything for indexer or indexer-worker in dovecot, just left the defau

Re: dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?

2020-11-13 Thread PGNet Dev
On 11/13/20 9:56 AM, PGNet Dev wrote: (2) see here: https://wiki.dovecot.org/Plugins/FTS/Solr two useful settings are debug and rawlog_dir=whatever to be added in the same line as fts_solr with fts_solr = ... debug line #35 @ https://pastebin.com/9ecLQspD _looks_ like the 401&#

Re: dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?

2020-11-13 Thread PGNet Dev
On 11/13/20 9:46 AM, John Fawcett wrote: (1) Can anyone yet verify Doveoct/fts-solr working with solr 8.7.x?>> (2) What logging config in Dovecot gets me more/detailed output for the fts_solr fail? (3) Any obvious clues as to what, specifically, is the source of this prob? (1) I can't, I'm sti

dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?

2020-11-13 Thread PGNet Dev
I've built a new dovecot + fts-solr instance; I've now picked up & am running the recently released solr 8.7.0. In a test account, I've one message -- in the 'Drafts' folder. On exec of fts 'index' doveadm index -u testu...@example.com -q '*' I get a 401 unauthorized indexin

Re: how to set smtp-client -> submission_relay_host for IPv4 only?

2020-11-11 Thread PGNet Dev
ref https://dovecot.org/pipermail/dovecot/2020-October/120226.html On 10/15/20 10:13 PM, Aki Tuomi wrote: I'm asking how/where to 'tell', via config, Dovecot's smtp-CLIENT, that's making to connection to the submission_relay_host, to use _only_ IPv4. There is currently no (other) way to d

Re: Recommended Protocols?

2020-11-10 Thread PGNet Dev
On 11/10/20 7:07 AM, Raymond Herrera wrote: I don't believe Thunderbird provides such capability (??). It does; works fine. fyi https://www.helmholtz-berlin.de/zentrum/locations/it/email/sig/cert-tbird_en.html If that is the case, how do I configure Dovecot to not ask for a client certific

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]

2020-11-02 Thread PGNet Dev
On 11/2/20 9:03 AM, John Fawcett wrote: the panic on doveadm fts lookup is to be expected and solved by my previous patch. snip all noted. atm, I've managed to get solr-backend indexing, and cmd-line searchable with doveadm, correctly finding the unfolded, accented characters in my 'test'. s

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]

2020-11-02 Thread PGNet Dev
On 11/1/20 10:35 AM, John Fawcett wrote: Yes, getting more data about any potential problem would be useful. Just to clarify: I have a fully working search setup for some time now over various dovecot releases, so no patches needed to get it working. My setup does use fts plugin and fts-solr pl

removing 'use_libfts' from dovecot fts_solr config; docs/examples of solr-backend-only tokenizer config for dovecot?

2020-11-02 Thread PGNet Dev
given existing problems with fts_solr = ... use_libfts ... i've rm'd it from dovecot config, and am moving all tokenization to solr config. iiuc, in dovecot + solr context, that's correctly config'd in solr/data/dovecot/conf/schema.xml dovecot release ships with 'starter confi

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]

2020-11-02 Thread PGNet Dev
On 11/2/20 5:13 AM, Aki Tuomi wrote: So what's the recommendation? use use_libfts, or not? It's a choice. You can let solr perform the tokenization etc. or you can let dovecot do it. There is no recommendation when using solr. atm, my fts plugin conf is plugin { fts

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]

2020-11-02 Thread PGNet Dev
On 11/2/20 12:44 AM, Aki Tuomi wrote: you should try removing use_libfts from your config line and let solr do that part. sry, i'm a bit confused. you'd suggested I _add_ it, https://dovecot.org/pipermail/dovecot/2020-October/120258.html I can reproduce your problem with the `fts l

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]

2020-11-01 Thread PGNet Dev
On 11/1/20 1:56 AM, John Fawcett wrote: At the moment I don't see other corrections needed in dovecot apart from command line doveadm fts which is not a show stopper. Via doveadm search I confirm - on my simple config - that search for accented or non accented characters works correctly as it doe

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]

2020-10-31 Thread PGNet Dev
On 10/31/20 9:55 AM, John Fawcett wrote: I can contribute a patch that solves the segfault. Unfortunately though fts search may be more broken than this. It does not give me search results, even though I see it querying solr and getting hits. Thx -- hopefully it moves this in the right directio

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-30 Thread PGNet Dev
On 10/18/20 10:28 PM, Aki Tuomi wrote: doveadm(myu...@example.com): Panic: file mail-storage.c: line 2112 (mailbox_get_open_status): assertion failed: (box->opened) ... I can reproduce your problem with the `fts lookup` command. Luckily it's equivalent to running `doveadm search`. I'

Re: Sieve filter script EXECUTION FAILED

2020-10-30 Thread PGNet Dev
On 10/30/20 10:11 AM, @lbutlr wrote: So, I have the sieve working up to the point that it calls the script, and the script is called (I get different errors if the script is not there, for example). filter action execute program `darkmode.sh' [[EXECUTION ABORTED]] The

how to enable automatic sharing of folders added/created in an already shared folder hiearchy?

2020-10-30 Thread PGNet Dev
I'm running dovecot --version 2.3.11.3 (502c39af9) folder sharing is enabled & working. as long as I manually enable enable sharing for each folder/subfolder. e.g., if I enable sharing for each of: sharedtopfolder subfolder1 subf

Re: Sieve_before

2020-10-21 Thread PGNet Dev
On 10/21/20 2:12 PM, @lbutlr wrote: Do I HAVE to have a default.sieve, that's the only thing that I can think the has changed in that folder. RE: compile, fyi note @ https://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts https://wiki2.dovecot.org/Pi

Re: Sieve_before

2020-10-21 Thread PGNet Dev
On 10/21/20 1:10 PM, @lbutlr wrote: I have trace logs enabled for user scripts, but I think only error get logged for upper level, and only along the lines of "could not compile ". verify that you can compile the scripts manually, even as root then double-check your perms on your sieve/ dir,

Re: Restrictions on default.sieve

2020-10-21 Thread PGNet Dev
On 10/21/20 10:55 AM, @lbutlr wrote: For the record, the first version with no conditions should work, right? it does here ...

Re: Restrictions on default.sieve

2020-10-21 Thread PGNet Dev
On 10/21/20 10:29 AM, @lbutlr wrote: Are there actions that default.sieve cannot take? I tried adding redirect :copy "backup+...@local.example.com" do you have an explicit require ["copy"]; in your .sieve?

Re: modify dovecot user/pass_queries to deliver to local aliases via dovecot submission, with postfixadmin/sqlite3 tables?

2020-10-20 Thread PGNet Dev
as usual, the problem's seldom where you 1st look. *NO* need for _any_ changes to queries. the source of the problem was my local postfix submission instance's config -- connected to, as submission_relay_host, by dovecot. it was doing exactly what I'd told it to do ... NOT expanding alias addr

modify dovecot user/pass_queries to deliver to local aliases via dovecot submission, with postfixadmin/sqlite3 tables?

2020-10-20 Thread PGNet Dev
I run dovecot + postfix with postfixadmin/sqlite3 I'm set up for all/only virtual users. All outbound mail submits via dovecot submission port. My current dovecot pass/user db queries are password_query = \ SELECT \ username as user, \ password, \ '/data

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-19 Thread PGNet Dev
On 10/19/20 1:03 PM, John Fawcett wrote: For libicu support in dovecot during the build process the libicu-devel package needs to be available. The following should be added to the dovecot.spec file BuildRequires: libicu-devel It's not necessary to specify --with-icu configure option but doing

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-19 Thread PGNet Dev
for any interested, let's see how far this gets: TBird "search on server" doesn't -- no comm with backend IMAP/SOLR; appears to be local-only search? https://groups.google.com/g/mozilla.dev.apps.thunderbird/c/SP-r2OEMZ24

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-19 Thread PGNet Dev
exec'ing search from Roundcube client, instead of TBird, accented-text search WORKS in both cases, "subject = aausdfrhyétdwgyatrdf" only, 2020-10-19 17:28:17.847 INFO (qtp1533985074-18) [ x:dovecot] o.a.s.c.S.Request [dovecot] webapp=/solr path=/select params={q={!lucene+q.op%3DAN

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-19 Thread PGNet Dev
On 10/19/20 10:04 AM, Peter wrote: you should trace the IMAP stream. With TB perform (crlt-shift-F) a server-side-search (checkbox in the dialog) - even if encrypted, the number of packets alon shows if there is any traffic. A server side search should also take considerably longer, esp. when

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-19 Thread PGNet Dev
On 10/19/20 9:48 AM, John Fawcett wrote: --with-icu should be sufficient, actually on centos 7 I got libuci compiled in without setting the explicit flag. Here's my ldd, which is under /usr/local/lib/dovecot ldd /usr/local/lib/dovecot/libdovecot-fts.so noted. as suspected. thx. config.log

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-19 Thread PGNet Dev
On 10/19/20 9:38 AM, Peter wrote: A network trace will show you, it TB actually requests something for your header search. Might be quicker that was my earlier quick-check ... abs nada from tcpdump -i lo port 8984 on the server, when doing any -- header, body -- TBird search to the serv

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-19 Thread PGNet Dev
On 10/19/20 9:15 AM, Peter wrote: If I remember correctly, that is an issue with TB - it only does body serches serverside, regardless of what you request, there should be an entry in their bugzilla, I'm too lazy right now. this is a very old bug https://groups.google.com/forum/#!top

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-19 Thread PGNet Dev
On 10/19/20 8:24 AM, John Fawcett wrote: Depending how solr has been setup you could see the logging in the web server access log. My access log is where I configured it in /var/log/httpd/servername.access_log, yours may be different. here, not running a standalone webserver/proxy in front of

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-19 Thread PGNet Dev
On 10/19/20 1:18 AM, John Fawcett wrote: I would recommend you to redo the tests after correcting the configuration. To be doubly sure you can include accented and unique non accented text in the same email and search for both. If the non accented text is found you know you've searching against t

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-19 Thread PGNet Dev
On 10/19/20 1:18 AM, John Fawcett wrote: notable/odd that subject searches are OK, but not body. The explanation for the different behaviour between headers and bodies is the following setting: fts_enforced = body I believe your header searches are not being sent to solr. See the following fo

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-19 Thread PGNet Dev
On 10/18/20 10:28 PM, Aki Tuomi wrote: Dovecot FTS tokenization is not done, unless you have `use_libfts` in fts_solr setting, in your case fts_solr = url=https://solr.example.com:8984/solr/dovecot/ use_libfts changing - fts_solr = url=https://solr.example.com:8984/solr/dovecot/ soft_

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-19 Thread PGNet Dev
On 10/18/20 10:28 PM, Aki Tuomi wrote: I can reproduce your problem with the `fts lookup` command. Luckily it's equivalent to running `doveadm search`. I'll open a bug about this. thx! Dovecot FTS tokenization is not done, unless you have `use_libfts` in fts_solr setting, in your case fts_s

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-18 Thread PGNet Dev
re-reading your mail ... On 10/18/20 2:58 PM, Shawn Heisey wrote: I do not use the fts-solr plugin, because my mail host in AWS does not have enough memory for that. is it that you're not using the dovecot plugin, but _DO_ have solr search setup? by what method/mean? or that you're avoid

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-18 Thread PGNet Dev
I've since rebuilt/reconfig'd all parts of my setup from scratch; some good cleanup along the way. Atm, my entire system for send/recv, store/retrieve, + rules & search is working as I intend. Ok, mostly ... Except for this accented-character search mystery. I've got a _lot_ of mail with

Re: how to set smtp-client -> submission_relay_host for IPv4 only?

2020-10-16 Thread PGNet Dev
On 10/15/20 10:13 PM, Aki Tuomi wrote: >> I'm asking how/where to 'tell', via config, Dovecot's smtp-CLIENT, that's >> making to connection to the submission_relay_host, to use _only_ IPv4. > > There is currently no (other) way to do this than using /etc/hosts or > specifying IPv4 address for th

Re: how to set smtp-client -> submission_relay_host for IPv4 only?

2020-10-15 Thread PGNet Dev
On 10/15/20 2:02 PM, jeremy ardley wrote: >> how/where do I configure (just) the dovecot smtp-client -> >> submission_relay_host to only connect IPv4? > > It appears your host has A and records in your DNS. The clients will try > IPV6 first if they see an record. > > If you don't need

how to set smtp-client -> submission_relay_host for IPv4 only?

2020-10-15 Thread PGNet Dev
In dovecot conf, for submission relay, I've config'd submission_relay_host = lan.example.com submission_relay_port = 465 hostname -- not IP -- must be used, to inform relay for cert verification match. Here, host lan.example.com lan.example.co

where to specify dovecot v2.3.11.3 SSL configs for fts solr indexer/backend connection?

2020-10-11 Thread PGNet Dev
I'm running. dovecot --version 2.3.11.3 (502c39af9) solr -version 8.6.3 solr's configured to use SSL. dovecot correctly uses SSL for transport fts_solr = url=https://solr.example.com:8984/solr/dovecot/ adding solr-side SSL client auth,

v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)

2020-10-11 Thread PGNet Dev
I'm running, dovecot --version 2.3.11.3 (502c39af9) solr -version 8.6.3 uname -rm 5.8.13-200.fc32.x86_64 x86_64 grep _NAME /etc/os-release PRETTY_NAME="Fedora 32 (Server Edition)" CPE

dovecot 2.3.11.3 namespace/ACL shared folder not accessible in sharing-user's Mail folder tree? have a working config?

2020-10-06 Thread PGNet Dev
I'm running dovecot --version 2.3.11.3 (502c39af9) I'm setting up folder sharing. Following https://wiki.dovecot.org/SharedMailboxes/Shared I've configured a folder to be shared, but it's not seen/accessible in the target user's Mail folder tree. My config inc

Re: BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."

2020-10-01 Thread PGNet Dev
On 10/1/20 8:52 AM, JEAN-PAUL CHAPALAIN wrote: > In my Centos-8 server, it was not necessary using  "Options = > ServerPreference" parameter. sry, then i'm unclear re: the point you're trying to make. this issue is ONLY about the problem re: THAT parameter's use, not re: general SSL error messa

Re: BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."

2020-10-01 Thread PGNet Dev
hi, On 10/1/20 12:21 AM, JEAN-PAUL CHAPALAIN wrote: > I had the same problem when migrating from Dovecot V2.2.36 on, Centos-7 to  > Dovecot v2.3.8 on Centos-8 My report is specifically/solely about the addition/use of the Options = ServerPreference parameter. I don't see that in your

Re: managesieve script 'redirect' fails @ "Error: sieve: ... aborted due to temporary failure; Error: smtp-server: ... failed: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong ve

2020-09-28 Thread PGNet Dev
On 9/27/20 2:07 PM, PGNet Dev wrote: > so the problem appears not to be the result of a general sieve-processing > fail, > but rather tied to the the redirect action/transaction For anyone interested, having dovecot sieve submit to its own submission proxy appears to be causal. Spe

Re: managesieve script 'redirect' fails @ "Error: sieve: ... aborted due to temporary failure; Error: smtp-server: ... failed: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong ve

2020-09-27 Thread PGNet Dev
adding a second, non-redirect action to the sieve rule in order to test, + require ["copy","fileinto"]; # rule:[SIEVETEST] if header :contains "subject" "SIEVETEST" { + fileinto :copy "testing"; redirect "us...@example2.co

Re: managesieve script 'redirect' fails @ "Error: sieve: ... aborted due to temporary failure; Error: smtp-server: ... failed: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong ve

2020-09-27 Thread PGNet Dev
i've been able to consistently reproduced the issue. no luck ID'ing the specific cause, yet. fyi, i've asked as well @ http://postfix.1071664.n5.nabble.com/local-postfix-re-delivery-of-dovecot-sieve-redirected-mail-fails-normal-direct-deliveries-are-OK-td107691.html with slightly simple conf

managesieve script 'redirect' fails @ "Error: sieve: ... aborted due to temporary failure; Error: smtp-server: ... failed: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong versio

2020-09-26 Thread PGNet Dev
I run dovecot --version 2.3.10.1 (a3d0e1171) postconf mail_version mail_version = 3.5.7 with three valid accounts on the server, us...@example1.net us...@example2.net ad...@mx.example.com I can send/receive from each -- bo

Re: dovecot warns (non-fatal) "invalid EHLO response line: Unexpected character in EHLO keyword" connecting to submission relay ?

2020-09-26 Thread PGNet Dev
On 9/26/20 6:45 AM, Alec Moskvin wrote: >> what's specifically invalid about >> >> 250 mail.messagingengine.com PIPELINING SIZE 7300 AUTH DIGEST-MD5 >> CRAM-MD5 NTLM LOGIN PLAIN AUTH=DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN >> ENHANCEDSTATUSCODES 8BITMIME >> >> by dovecot's 'measure'? > > T

maildir -> sdbox migration command for _all_ accounts, with split maildir/CONTROL/INDEX locations?

2020-09-25 Thread PGNet Dev
in a recent post, sven made a clear/cogent arg for sdbox vs maildir > While Maildir seems to be an obvious choice, it has some hidden > performance impacts, namely it relies heavily on information encoded in > the filename, which results in a big overhead in meta-operations, >

dovecot warns (non-fatal) "invalid EHLO response line: Unexpected character in EHLO keyword" connecting to submission relay ?

2020-09-25 Thread PGNet Dev
I'm setting up an alternative submission relay host for dovecot. Atm, it's pointing @ fastmail.com. with dovecot config, submission_relay_host = smtp.fastmail.com submission_relay_port = 465 submission_relay_ssl= smtps submission_relay_ssl_ver

Re: dovecot TSL 1.3 config option 'ssl_ciphersuites' causes fatal error on launch. not supported, bad config, or bug?

2020-09-24 Thread PGNet Dev
On 9/23/20 11:29 PM, Aki Tuomi wrote: > The config option is still missing, but it's in our backlog along with other > stuff we would like to add. Is that pegged to any version/milestone yet? In the meantime, what state is Dovecot's cipher support IN? What behavior should be expected when (all o

Re: BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."

2020-09-23 Thread PGNet Dev
On 9/23/20 7:27 AM, PGNet Dev wrote: > I'll see if I can reduce this to a simple demonstrator ... well, i can confirm that a CLEAN, minimal install works OK with the /etc/pki/tls/openssl.cnf spec'd above but my full/production instance FAILs. :-/ still, only on/with Dovecot subm

dovecot TSL 1.3 config option 'ssl_ciphersuites' causes fatal error on launch. not supported, bad config, or bug?

2020-09-23 Thread PGNet Dev
I've installed grep PRETTY /etc/os-release PRETTY_NAME="Fedora 32 (Server Edition)" dovecot --version 2.3.10.1 (a3d0e1171) openssl version OpenSSL 1.1.1g FIPS 21 Apr 2020 iiuc, Dovecot has apparently had support for setting

Re: BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."

2020-09-23 Thread PGNet Dev
On 9/23/20 2:14 AM, Aki Tuomi wrote: > I tried to reproduce this with the config you provided. I made sure openssl > uses the configuration, but alas, it works just fine for me. ugh. well, good to know. with my my full-blown configs, it's definitely reproducible here. I'll see if I can reduce

  1   2   3   >