Re: Do not working Vitual Flagged / All.

2024-12-11 Thread Bernardo Reino via dovecot
On Wed, 11 Dec 2024, yisuyong--- via dovecot wrote: Thanks Sirius! It's been resolved. [..] Please make sure you change your IMAP password as quickly as possible, as you have posted it with your logs. ___ dovecot mailing list -- dovecot@dovecot.o

Re: Sieve not working again

2024-12-11 Thread christian via dovecot
But what is never mentioned in the docs is where you have to enter this in the dovecot setup. Does this also affect the sieve scripts that only do things like mark as read or move to INBOX.stuff? Christian Am 11.12.2024 um 14:20 schrieb Aki Tuomi: https://doc.dovecot.org/2.3/settings/core/#co

Re: Sieve not working again

2024-12-11 Thread Aki Tuomi via dovecot
https://doc.dovecot.org/2.3/settings/core/#core_setting-sendmail_path and https://doc.dovecot.org/2.3/settings/core/#core_setting-submission_host Aki > On 11/12/2024 15:08 EET christian via dovecot wrote: > > > Where is this set up with submission_host and sendmail_path? I can't > find any

Re: Sieve not working again

2024-12-11 Thread christian via dovecot
Where is this set up with submission_host and sendmail_path? I can't find anything about this in dovecot. Christian Am 11.12.2024 um 13:58 schrieb Aki Tuomi via dovecot: Ok, then I would suggest checking your MTA logs to see if such attempt was ever made? Also I wonder if you have submission

Re: Sieve not working again

2024-12-11 Thread Aki Tuomi via dovecot
Ok, then I would suggest checking your MTA logs to see if such attempt was ever made? Also I wonder if you have submission_host or sendmail_path configured correctly? Aki > On 11/12/2024 14:45 EET christian via dovecot wrote: > > > sieve-test result > > sieve-test -c /etc/dovecot/dovecot.

Re: Sieve not working again

2024-12-11 Thread christian via dovecot
sieve-test result sieve-test -c /etc/dovecot/dovecot.conf /var/customers/sieve/postmas...@domain.info/filter.sieve /home/mail/domain/domain.info/postmaster/cur/'17 33920865.M944228P1768729.wwl10,S=6511,W=6637:2,' sieve-test(root)<1768869><>: Debug: Loading modules from directory: /usr

Re: Sieve not working again

2024-12-11 Thread Aki Tuomi via dovecot
Please try sieve-test, it comes with dovecot and you can use it to actually get pretty detailed information about what happens with your script. I cannot see anything in particular wrong with your config. Aki > On 11/12/2024 14:19 EET christian via dovecot wrote: > > > But it doesn't matter

Re: Sieve not working again

2024-12-11 Thread christian via dovecot
But it doesn't matter which email comes in. In the test case, every email that comes in should be forwarded. No Sieve action is written to the sieve.log. Something doesn't seem to be working properly. Can you take a look at my attached postconf -n to see if you can see anything? Am 11.12.202

Re: Sieve not working again

2024-12-11 Thread Aki Tuomi via dovecot
Have you tried with sieve-test? It could provide more information on what is happening with your script and email. Aki > On 11/12/2024 13:54 EET christian via dovecot wrote: > > > I have a typical line from the log that shows how a sieve script is > accessed. But it is not taken into accoun

Re: Sieve not working again

2024-12-11 Thread christian via dovecot
I have a typical line from the log that shows how a sieve script is accessed. But it is not taken into account. All user sieve scripts are not executed. All before.script entries are executed properly. Dec 11 12:45:26 lda(postmas...@domain.info)<1725352>: Debug: sieve: file storage: Relative

Re: Sieve not working again

2024-12-11 Thread Aki Tuomi via dovecot
It's hard to say exactly, can you consider posting it to the list? Make sure it does not contain anything you don't want to make public. Aki > On 11/12/2024 13:00 EET christian via dovecot wrote: > > > Hello Aki, > can you tell me what exactly I should be looking for? With the amount of > l

Re: Sieve not working again

2024-12-11 Thread christian via dovecot
Hello Aki, can you tell me what exactly I should be looking for? With the amount of log entries in the debug.log it is otherwise very difficult to find something if you don't know what to look for. Thanks Christian Am 11.12.2024 um 08:02 schrieb Aki Tuomi via dovecot: On 08/12/2024 14:37 EE

Re: Do not working Vitual Flagged / All.

2024-12-11 Thread yisuyong--- via dovecot
Thanks Sirius! It's been resolved. However, I solved it by adding a comment in the original settings. namespace inbox { inbox = yes location = mailbox 보낼편지함 { auto = subscribe } mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts }

Re: Do not working Vitual Flagged / All.

2024-12-11 Thread Sirius via dovecot
On ons, 2024/12/11 at 08:00:29 +, yisuyong--- via dovecot wrote: > I added "subscription = no" as you said > > namespace virtual { > hidden = yes > list = no > location = > virtual:/etc/dovecot/virtual:INDEX=~/.virtual:CONTROL=~/.virtual:VOLATILEDIR=~/.virtual/ > prefix = virtual/ >

Re: Do not working Vitual Flagged / All.

2024-12-11 Thread yisuyong--- via dovecot
Debugging log for Dovecot when I clicked Flagged. Dec 11 16:13:39 mail dovecot: auth: Debug: auth client connected (pid=271743) Dec 11 16:13:39 mail dovecot: imap-login: Debug: SSL: where=0x10, ret=1: before SSL initialization Dec 11 16:13:39 mail dovecot: imap-login: Debug: SSL: where=0x2001, re

Re: Do not working Vitual Flagged / All.

2024-12-11 Thread yisuyong--- via dovecot
I added "subscription = no" as you said namespace virtual { hidden = yes list = no location = virtual:/etc/dovecot/virtual:INDEX=~/.virtual:CONTROL=~/.virtual:VOLATILEDIR=~/.virtual/ prefix = virtual/ separator = / subscriptions = no type = private } And I done change ownership and