testing sieve/pigeonhole, auth errors

2024-01-15 Thread Joe Acquisto
A small SOHO system, of installed perhaps a year.  Seems to be working and wished to add pigeonhole/sieve. Per Pigeonhole/sieve troubleshooting in the docs, set on mail_debug = yes and this is what I see, upon launching Thunderbird as the client.  Thought that "unknown user" and "permission denied"

Re: testing sieve/pigeonhole, auth errors

2024-01-18 Thread Joe Acquisto
On 1/15/24 15:13, Joe Acquisto wrote: A small SOHO system, of installed perhaps a year.  Seems to be working and wished to add pigeonhole/sieve. Back to attempting to configure this.  No doubt simple for one more familiar with dovecot and sundry stuff. One thing I find unclear is

CRe: testing sieve/pigeonhole, auth errors

2024-01-18 Thread Joe Acquisto
On 1/18/24 15:34, Joe Acquisto wrote: On 1/15/24 15:13, Joe Acquisto wrote: A small SOHO system, of installed perhaps a year.  Seems to be working and wished to add pigeonhole/sieve. Back to attempting to configure this.  No doubt simple for one more familiar with dovecot and

managesieve server not answering?

2024-01-18 Thread Joe Acquisto
Trying to connect to managesieve server configured to port 4190. No go. Roundcube is configured (thunderbird apparently having nothing current), but selecting "Add Filter" (new since re-configured for managesieve) produces "unable to connect to server". Port 4190 does not seem to answer or be

Re: managesieve server not answering?

2024-01-18 Thread Joe Acquisto
managesieve protocol: protocols = $protocols sieve # Service definitions On Thu, Jan 18, 2024 at 5:30 PM Joe Acquisto wrote: Trying to connect to managesieve server configured to port 4190. No go. Roundcube is configured (thunderbird apparently having nothing current), but

Re: managesieve server not answering?

2024-01-18 Thread Joe Acquisto
look at conf.d/20-managesieve.conf? notably the below top of that file. ❯ more 20-managesieve.conf ## ## ManageSieve specific settings ## # Uncomment to enable managesieve protocol: protocols = $protocols sieve # Service definitions On Thu, Jan 18, 2024 at 5:30 PM Joe Acquisto wrote

Re: managesieve server not answering?

2024-01-18 Thread Joe Acquisto
ay wish to double-check that file (all of it) and 90-sieve.conf as well On Thu, Jan 18, 2024 at 6:08 PM Joe Acquisto wrote: Yes.  It is uncommented as shown there below.  Service was restarted. joe a On 1/18/24 18:33, Larry Rosenman wrote: > Did you look at conf.d/20-man

Re: managesieve server not answering?

2024-01-18 Thread Joe Acquisto
Sure.  Thanks.  I can post mine here, I suppose in  a bit joe a. On 1/18/24 20:29, Larry Rosenman wrote: I could send your a dovecot -n of my setup, which works with RoundCube, if you want. On Thu, Jan 18, 2024 at 6:46 PM Joe Acquisto wrote: They look fine to me, questions remails if many

Re: managesieve server not answering?

2024-01-19 Thread Joe Acquisto
The problem of managesieve server/service not taking hold of port 4190 remains.  Perhaps the service is not being loaded/running at all?   Pardon any terminology faux pas On 1/18/24 18:30, Joe Acquisto wrote: Trying to connect to managesieve server configured to port 4190. No go. Roundcube

lda or lmtp for sieve?

2024-01-19 Thread Joe Acquisto
I noticed that many places in the documentation and in examples gleaned from the wilderness, refer to the LDA protocol when discussing sieve. The documentation also mentions that lmtp is preferred over lda, and seems to say in places that sieve will operate without issue in either case. Does

Re: lda or lmtp for sieve?

2024-01-19 Thread Joe Acquisto
Thanks for the reassurance.  It was a reach, hoping for some straw to grasp regarding the managesieve 4190 failure to bind. On 1/19/24 18:28, Joe Acquisto wrote: I noticed that many places in the documentation and in examples gleaned from the wilderness, refer to the LDA protocol when