Re: Tools to get a report of which folders have new mail?
On 2022-07-18 11:18 p.m., Steve Litt wrote: I use a Dovecot IMAP server on my Linux desktop computer, and I'm pretty good at writing shellscripts. Is there any way I could use doveadm or other tools to create a report that shows all my folders in a hierarchy? Also, is there a way to show only those with new mail? you could use "doveadm mailbox list" to build the list of folders and "doveadm search" to search each folder for appropriate IMAP flags https://wiki2.dovecot.org/Tools/Doveadm/SearchQuery e.g. doveadm mailbox list -u username | sort doveadm search -u username mailbox foldername UNSEEN (or NEW instead of UNSEEN)
Re: Ubuntu 22.04/Jammy repo coming soon ?
> On 15/07/2022 00:38 EEST Dean Carpenter wrote: > > > Is there any idea of when a repo for Ubuntu 22.04/Jammy will be built ? I've > tried a couple of test installs onto a 22.04 system using the 20.04/Focal > repo, but no luck yet. libssl issues etc. > -- > Dean Carpenter It will probably be made for the next major release, 2.4. For 2.3, we have no plans to provide ubuntu 22 support via repo.dovecot.org currently. Aki
Re: Tracing Sieve actions
Then you should probably look at ManageSieve protocol, available in Dovecot and some of clients, especially webmail ones and recently even discussed on this list. Aki > On 20/07/2022 09:55 EEST justina colmena ~biz wrote: > > > Thank you. I will have to look at "basic configuration" for sieving although > I don't want things crashing on production. > > I get too much mail at a publicly available address -- and while > SPF+DKIM+DMARC does cut down on the bulk of obvious spam -- the spam that > does get through is a little bit too "legitimate" to eliminate without > special sieving rules. > > This stuff really needs to be configurable per user without abusing root > privileges and without futzing at the command line, or else it just isn't > useful to the end user on the desktop or mobile device. Sieving needs to be > either an email client thing, or else a standard interface for rules that can > be configured and uploaded to Dovecot from the email client / reader software. > > https://doc.dovecot.org/configuration_manual/sieve/configuration/#basic-configuration > > > On July 19, 2022 10:35:40 PM AKDT, Aki Tuomi > wrote: > > > > > > > On 20/07/2022 09:34 EEST Doug Hardie wrote: > > > > > > > > > I encountered an interesting problem that one originator was being dumped > > > into the Deleted file directly by my sieve. The sieve file was quite > > > large and it was not obvious which entry was causing the issue. I recall > > > there was a way to get sieve-test to show what is going on and which > > > lines it used, but I could not replicate it tonight for anything. I > > > ended up having to change all the deliver to the Deleted files to > > > something else and test one at a time to find the offending entry. It > > > took a long time. How do you get sieve-test to show the actual path it > > > took through the file? > > > > > > -- Doug > > > > Hi Doug, take a loot at > > https://doc.dovecot.org/configuration_manual/sieve/configuration/#trace-debugging > > > > It might help. > > > > Kind regards, > > Aki > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: Tracing Sieve actions
Thank you. I will have to look at "basic configuration" for sieving although I don't want things crashing on production. I get too much mail at a publicly available address -- and while SPF+DKIM+DMARC does cut down on the bulk of obvious spam -- the spam that does get through is a little bit too "legitimate" to eliminate without special sieving rules. This stuff really needs to be configurable per user without abusing root privileges and without futzing at the command line, or else it just isn't useful to the end user on the desktop or mobile device. Sieving needs to be either an email client thing, or else a standard interface for rules that can be configured and uploaded to Dovecot from the email client / reader software. https://doc.dovecot.org/configuration_manual/sieve/configuration/#basic-configuration On July 19, 2022 10:35:40 PM AKDT, Aki Tuomi wrote: > >> On 20/07/2022 09:34 EEST Doug Hardie wrote: >> >> >> I encountered an interesting problem that one originator was being dumped >> into the Deleted file directly by my sieve. The sieve file was quite large >> and it was not obvious which entry was causing the issue. I recall there >> was a way to get sieve-test to show what is going on and which lines it >> used, but I could not replicate it tonight for anything. I ended up having >> to change all the deliver to the Deleted files to something else and test >> one at a time to find the offending entry. It took a long time. How do you >> get sieve-test to show the actual path it took through the file? >> >> -- Doug > >Hi Doug, take a loot at >https://doc.dovecot.org/configuration_manual/sieve/configuration/#trace-debugging > >It might help. > >Kind regards, >Aki -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: Tracing Sieve actions
Thanks, that's basically the same as the man page. I finally figured out that the way to do it is with: sieve-test -t - -Tlevel=tests .dovecot.sieve /xxx where /xxx is the test message. That gives the actual line numbers. I thought I tried that combination, but apparently not. Anyway, I am going to save that command line somewhere "in a safe spot" ;-) -- Doug > On 19 July 2022, at 23:35, Aki Tuomi wrote: > > >> On 20/07/2022 09:34 EEST Doug Hardie wrote: >> >> >> I encountered an interesting problem that one originator was being dumped >> into the Deleted file directly by my sieve. The sieve file was quite large >> and it was not obvious which entry was causing the issue. I recall there >> was a way to get sieve-test to show what is going on and which lines it >> used, but I could not replicate it tonight for anything. I ended up having >> to change all the deliver to the Deleted files to something else and test >> one at a time to find the offending entry. It took a long time. How do you >> get sieve-test to show the actual path it took through the file? >> >> -- Doug > > Hi Doug, take a loot at > https://doc.dovecot.org/configuration_manual/sieve/configuration/#trace-debugging > > It might help. > > Kind regards, > Aki
Re: Tracing Sieve actions
> On 20/07/2022 09:34 EEST Doug Hardie wrote: > > > I encountered an interesting problem that one originator was being dumped > into the Deleted file directly by my sieve. The sieve file was quite large > and it was not obvious which entry was causing the issue. I recall there was > a way to get sieve-test to show what is going on and which lines it used, but > I could not replicate it tonight for anything. I ended up having to change > all the deliver to the Deleted files to something else and test one at a time > to find the offending entry. It took a long time. How do you get sieve-test > to show the actual path it took through the file? > > -- Doug Hi Doug, take a loot at https://doc.dovecot.org/configuration_manual/sieve/configuration/#trace-debugging It might help. Kind regards, Aki
Tracing Sieve actions
I encountered an interesting problem that one originator was being dumped into the Deleted file directly by my sieve. The sieve file was quite large and it was not obvious which entry was causing the issue. I recall there was a way to get sieve-test to show what is going on and which lines it used, but I could not replicate it tonight for anything. I ended up having to change all the deliver to the Deleted files to something else and test one at a time to find the offending entry. It took a long time. How do you get sieve-test to show the actual path it took through the file? -- Doug
