Re: how to configure imapsieve to be used per user

2022-10-27 Thread Sebastian Bachmann
Okay, I could have enabled debug log earlier, than that would have been easy... Thanks for the hint. The key is to specify the sieve script inside the sieve directory without the .sieve suffix, i.e.: a SETMETADATA test (/shared/imapsieve/script "imap") which points to sieve/imap.sieve in the

Re: how to configure imapsieve to be used per user

2022-10-27 Thread Paul Kudla
ok fair enuff are you using a db to set the dir's there is a master sieve (all) directory that handles the entire server (message duplicate supression etc) mine is in [17:26:12] mail18.scom.ca [root:0] /usr/local/etc/dovecot/sieve # ll total 38 drwxr-xr-x 2 vmail vmail uarch4B Apr

Re: how to configure imapsieve to be used per user

2022-10-27 Thread Sebastian Bachmann
On 27.10.2022 13:54, Paul Kudla wrote: again may (probably not) what you are looking for but it at least gives another example(s) No, actually I was looking for something different. The TO and me were looking for imapsieve examples and how they can be configured on a per user & per mailbox

oauth2 + postgres = Panic: file http-client.c: line 646 (http_client_context_close)

2022-10-27 Thread Sebastiano Degan
I could to reply to the original thread: https://www.mail-archive.com/dovecot@dovecot.org/msg85204.html But I managed to get a stack trace of the error: root@mail:~ # lldb /usr/local/libexec/dovecot/auth (lldb) target create "/usr/local/libexec/dovecot/auth" Current executable set to '/usr/local/

Re: Mailing list IMAP archive.

2022-10-27 Thread Narcis Garcia
El 27/10/22 a les 18:04, dove...@ptld.com ha escrit: I am trying to use the IMAP mailing list archive described on https://www.dovecot.org/mailing-lists/ Is this feature still functioning? Using Thunderbird i get an error message that the connection was refused. Try using dovecot.org:imaps (po

Re: Mailing list IMAP archive.

2022-10-27 Thread dovecot
I am trying to use the IMAP mailing list archive described on https://www.dovecot.org/mailing-lists/ Is this feature still functioning? Using Thunderbird i get an error message that the connection was refused. Try using dovecot.org:imaps (port 993) Thanks, that worked. For others using Thun

Re: Mailing list IMAP archive.

2022-10-27 Thread Aki Tuomi
> On 27/10/2022 18:36 EEST dove...@ptld.com wrote: > > > I am trying to use the IMAP mailing list archive described on > https://www.dovecot.org/mailing-lists/ > > Is this feature still functioning? Using Thunderbird i get an error message > that the connection was refused. > I don't know i

Mailing list IMAP archive.

2022-10-27 Thread dovecot
I am trying to use the IMAP mailing list archive described on https://www.dovecot.org/mailing-lists/ Is this feature still functioning? Using Thunderbird i get an error message that the connection was refused. I don't know if Thunderbird isn't functioning properly (with handling no password) o

Re: how to configure imapsieve to be used per user

2022-10-27 Thread Paul Kudla
My apologies to the response eariler I was making the assumption that you were using pigeonholes it needs to be compiled seperately after making dovecot's server installs basically the pigeonholes has to be compiled against the dovecot version you are running after which my post info will

Re: how to configure imapsieve to be used per user

2022-10-27 Thread hi
On 2022-10-27 02:28, Stephan Bosch wrote: On 24-10-2022 12:00, Sebastian Bachmann wrote: according to the documentation, this has to be added to the IMAP METADATA dict per mailbox (https://doc.dovecot.org/configuration_manual/imap_metadata/): https://doc.dovecot.org/configuration_manual/sieve

Re: how to configure imapsieve to be used per user

2022-10-27 Thread Paul Kudla
ok a few things about sieve although it is a pain it is usually (on a per user basis) better to access the sieve scripting through thunderbird's plugin sieve or something similiar as it will sort out checksums, syntax etc. see : https://github.com/thsmi/sieve/ https://www.pair.com/support

Re: The end of Dovecot Director?

2022-10-27 Thread Jan Bramkamp
On 27.10.22 04:24, Timo Sirainen wrote: Director never worked especially well, and for most use cases it's just unnecessarily complex. I think usually it could be replaced with: * Database (sql/ldap/whatever) containing user -> backend table. * Configure Dovecot proxy to use this database a

Re: The end of Dovecot Director?

2022-10-27 Thread hi
On 2022-10-27 08:31, William Edwards wrote:  Op 27 okt. 2022 om 04:25 heeft Timo Sirainen het volgende geschreven: Director never worked especially well, and for most use cases it's just unnecessarily complex. I think usually it could be replaced with: * Database (sql/ldap/whatever) cont

Re: Catch all for Metadata storage in SQL database

2022-10-27 Thread Aki Tuomi
> On 03/05/2021 09:10 EEST Aki Tuomi wrote: > > > > On 30/04/2021 09:38 Steffen Kaiser wrote: > > > > > > Hi, > > > > the > > > > https://doc.dovecot.org/configuration_manual/imap_metadata/ > > > > sample uses > > > > mail_attribute_dict = file:%h/Maildir/dovecot-attributes > > > > w

Re: Catch all for Metadata storage in SQL database

2022-10-27 Thread Aki Tuomi
> On 03/05/2021 09:10 EEST Aki Tuomi wrote: > > > > On 30/04/2021 09:38 Steffen Kaiser wrote: > > > > > > Hi, > > > > the > > > > https://doc.dovecot.org/configuration_manual/imap_metadata/ > > > > sample uses > > > > mail_attribute_dict = file:%h/Maildir/dovecot-attributes > > > > w

Re: The end of Dovecot Director?

2022-10-27 Thread hi
On 2022-10-27 08:31, William Edwards wrote:  Op 27 okt. 2022 om 04:25 heeft Timo Sirainen het volgende geschreven: Director never worked especially well, and for most use cases it's just unnecessarily complex. I think usually it could be replaced with: * Database (sql/ldap/whatever) cont

Re: The end of Dovecot Director?

2022-10-27 Thread William Edwards
 > Op 27 okt. 2022 om 04:25 heeft Timo Sirainen het volgende > geschreven: > > Director never worked especially well, and for most use cases it's just > unnecessarily complex. I think usually it could be replaced with: > > * Database (sql/ldap/whatever) containing user -> backend table. > *