dovecot 3.16 replicator Problem?

2021-08-18 Thread Günther J . Niederwimmer
Hello list,
I have a problem with the replicator (config) I mean it doesn't work anymore 
since version 3.16?

How can you turn up the log level with this tool? I think the full sync is 
still possible to some extent. I deleted a test user who was restored after a 
day.

Question: has something changed in the config so that the whole thing works 
again

Thanks for a answer,
-- 
mit freundlichen Grüßen / best regards

  Günther J. Niederwimmer




Odd config problem in Debian Bullseye / dovecot 2.3.13

2021-08-18 Thread Perry E. Metzger

Hi all!

For a long time, I've been running this out of cron as user "perry":

/usr/bin/doveadm expunge -u perry mailbox SPAM not seen before 7d

After upgrading to 2.3.13 as a result of a debian upgrade, this broke. I 
now am suddenly getting:


doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf 
line 132: ssl_key: Can't open file 
/etc/ssl/private/ssl-cert-snakeoil.key: Permission denied


Attempting things like setting "-o ssl_key=/dev/null" and the like don't 
work.


I could of course run this as root but I'd strongly prefer not to.

Anyone have any ideas?

Perry




Re: Odd config problem in Debian Bullseye / dovecot 2.3.13

2021-08-18 Thread Aki Tuomi


> On 18/08/2021 19:21 Perry E. Metzger  wrote:
> 
>  
> Hi all!
> 
> For a long time, I've been running this out of cron as user "perry":
> 
> /usr/bin/doveadm expunge -u perry mailbox SPAM not seen before 7d
> 
> After upgrading to 2.3.13 as a result of a debian upgrade, this broke. I 
> now am suddenly getting:
> 
> doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf 
> line 132: ssl_key: Can't open file 
> /etc/ssl/private/ssl-cert-snakeoil.key: Permission denied
> 
> Attempting things like setting "-o ssl_key=/dev/null" and the like don't 
> work.
> 
> I could of course run this as root but I'd strongly prefer not to.
> 
> Anyone have any ideas?
> 
> Perry


Hi!

this is a known issue, you can workaround it for now with

ssl=no
!try_include /etc/dovecot/ssl.conf

then put in /etc/dovecot/ssl.conf

ssl=yes
ssl_cert=<...
ssl_key=<...

etc.

and chmod 0400 /etc/dovecot/ssl.conf

Aki


Re: Snarf plugin retirement

2021-08-18 Thread John Stoffel
> "Brent" == Brent Busby  writes:

Brent> I wondered if it's possible to get the Snarf plugin back, if not in the
Brent> official Dovecot distribution, then at least to somehow build the plugin
Brent> source on a modern release...because:

Brent> Though the documented purpose for Snarf was to ease migration
Brent> off of UW-IMAP, that's not the only thing it was useful for.
Brent> Unfortunately, every mailreader that I've seen that can run
Brent> within Emacs -- and I've tried Gnus, VM, and RMAIL -- all
Brent> _require_ the use of a ~/mbox file when pulling from a local
Brent> mail spool on the same machine.  (This does not affect IMAP
Brent> usage of those mailreaders, only local file access.)

I'm confused... since I'm using VM to read and write these emails, I'm
trying to understand your issue.  Basically, when I moved to IMAP for
my personal domain, I made the concious choice to only allow IMAP
access, since I wanted proper locking from both Phones, mutt, and
other IMAP clients.  So I had to stop using local email spools to get
email.

So if you're offering IMAP access to mail, just turn off the local
mail spool completely. 

Brent> Non-Emacs mailreaders like Alpine and Mutt have sufficiently
Brent> robust file-locking safety that they can work on the local mail
Brent> spool in /var/spool/mail or /var/mail or what have you directly
Brent> without copying your mail somewhere else first, so for Alpine
Brent> and Mutt, use of ~/mbox is possible but not necessary.  But it
Brent> seems that for every mailreader that does run within Emacs, if
Brent> the mail source is local rather than IMAP, there is no other
Brent> way to operate the program than to have it copy your mail from
Brent> the spool to ~/mbox.  On a system where there are users who
Brent> sometimes work that way, doing local mail access in Emacs, and
Brent> other times use IMAP via Dovecot, you have a mess without the
Brent> Snarf plugin.

You have a mess period.  Don't do this.  It's a really bad idea and
trying to make it work is just too painful.  Now I *do* use a mix of
IMAP and local mbox format folders, where once I save it locally via
mbox, I can't acces those folders using my IMAP only clients.  But
that's an accepted and known limitation.

Brent> I realize this is a peculiar situation, so I don't expect Snarf
Brent> to necessarily be put back into Dovecot.  I was wondering how
Brent> it might be possible to build it today though...for any out
Brent> there who may use Emacs for mail most of the time...but
Brent> occasionally also want Dovecot IMAP on the same machine where
Brent> they're normally using an ~/mbox file for Emacs' sake.  UW-IMAP
Brent> may be dead...but long live GNU Emacs!

Just don't use VM without IMAP as your main mailbox any more.  And
also accept that once you get over a thousand or so emails, or lots of
large emails, then VM inside emacs really starts to suck.

I'd move to Mutt, but I haven't spent the time to re-create the VM
keybindings in mutt yet, which is what's holding me back.

And if you have users who want both types of access, just tell them
no.  It's *not* worth the hassle, and things *will* break.

John