Extra listener for client cert ?

2024-08-13 Thread Laura Smith via dovecot
Is it possible to, and (if yes) has anyone had experience with setting up an extra listener that requires client certs. The problem I've got is I still need to support Outlook clients.  Fortunately these are located in fixed locations on desktop computers. Meanwhile, I would like to harden the

Re: Debian Bookworm packages, please !

2024-06-27 Thread Laura Smith via dovecot
are not needed to buy pro licenses. Aki > On 27/06/2024 11:03 EEST Laura Smith via dovecot wrote: > > > Perhaps try reading my last post Scott. > > Perhaps especially the bit where I said OX were offered money but they were > not interested without megabucks being spent. &g

Re: Debian Bookworm packages, please !

2024-06-27 Thread Laura Smith via dovecot
Perhaps try reading my last post Scott. Perhaps especially the bit where I said OX were offered money but they were not interested without megabucks being spent. As others have said, take your cheap, unsubstatiated, attacks elsewhere chum. On Wednesday, 26 June 2024 at 21:24, Scott Q. via d

Re: Debian Bookworm packages, please !

2024-06-26 Thread Laura Smith via dovecot
> Why do you care about the repo then ? Use the patch locally, > publish it, etc. You care about OpenSSL 3.0 compatibility right ? What > do you care if it's in the public tree or not. Because Aki has been shouting from the rooftops here that "beware, its not that easy, Dovecot crashes with Open

Re: Debian Bookworm packages, please !

2024-06-26 Thread Laura Smith via dovecot
I do maintain a few open source projects > and am accustomed to people's expectations to get commercial grade > software...for free. > > Cheers > > On Wednesday, 26/06/2024 at 08:34 Laura Smith via dovecot wrote: > > > You are conflating OS with packages.  I don'

Re: Debian Bookworm packages, please !

2024-06-26 Thread Laura Smith via dovecot
ithout premium access. Since that's > what the OS has committed to, unless they pull a redhat and deprecate an OS > before initial EOL date. > > Sent from Outlook for iOS > > From: Laura Smith > Sent: Wednesday, June 26, 2024 2:06:44 PM > To: Lucas Rolff > Cc: Aki Tu

Re: Debian Bookworm packages, please !

2024-06-26 Thread Laura Smith via dovecot
ke other operating > systems, should probably be brought up with the Debian release and security > teams. > > Sent from Outlook for iOShttps://aka.ms/o0ukef > > ____________ > From: Laura Smith via dovecot dovecot@dovecot.org > > Sent: Wednesday, Ju

Re: Debian Bookworm packages, please !

2024-06-26 Thread Laura Smith via dovecot
ught up with the Debian release and security > teams. > > Sent from Outlook for iOS > > From: Laura Smith via dovecot > Sent: Wednesday, June 26, 2024 1:31:48 PM > To: Aki Tuomi > Cc: Laura Smith via dovecot ; Michael > Subject: Re: Debian Bookworm packages, please ! >

Re: Debian Bookworm packages, please !

2024-06-26 Thread Laura Smith via dovecot
The fundamental problem here is that this turns into a security problem, which in 2024 is not a nice thing to have. Yes, theoretically I could run the previous Debian release, 11 Bullseye which is now EOL but in LTS until 2026. However, the OpenSSL delivered with Bullseye is 1.1.1. Any LTS pat

Re: Debian Bookworm packages, please !

2024-06-26 Thread Laura Smith via dovecot
> > could you please elaborate on this? are there any security issues with > > using the debian version? what are the problems you are implicating with > > your above statement, that it's 'not fully working either'? > > > > greetings... > > > It can sometimes crash. > > Aki Does Dovecot eve

Re: Debian Bookworm packages, please !

2024-06-25 Thread Laura Smith via dovecot
> > We can already see that the Debian/RedHat patched 2.3 which is offered is > broken because there is more than just "making it compile" with things like > OpenSSL3, and yes, I can appreciate that it's not fully broken, but it's not > fully working either. Yeah, that's sort of what's hold

Re: Debian Bookworm packages, please !

2024-06-25 Thread Laura Smith via dovecot
On Tuesday, 25 June 2024 at 15:06, Aki Tuomi via dovecot wrote: > > On 25/06/2024 16:58 EEST Laura Smith via dovecot dovecot@dovecot.org wrote: > > > > Debian Bookworm (12) was released June 2023. > > > > It is therefore somewhat disappointing to see no B

Debian Bookworm packages, please !

2024-06-25 Thread Laura Smith via dovecot
Debian Bookworm (12) was released June 2023. It is therefore somewhat disappointing to see no Bookworm packages in  https://repo.dovecot.org/ce-2.3-latest/debian/ ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le.

Re: Replicator service in Dovecot 2.4 CE

2023-10-18 Thread Laura Smith via dovecot
> Are you completely removing support for 'replication-with-dsync' starting > from version 2.4? > Are there any plans for built-in tools to implement an active/active or > active/passive cluster in the community edition? kv See the long discussion "the future of SIS" (https://dovecot.org/m

Re: The future of SIS

2023-10-17 Thread Laura Smith via dovecot
--- Original Message --- On Tuesday, October 17th, 2023 at 15:27, Filip Hanes via dovecot wrote: > Other S3 implementation is Minio on top of any posix filesystem - you can > choose which fills your needs. Minio is great in general, the only thing I would say it its a little bit wei

Re: The future of SIS

2023-10-17 Thread Laura Smith via dovecot
--- Original Message --- On Tuesday, October 17th, 2023 at 06:46, Jean-Daniel Dupas wrote: > > If you are using Ubuntu, OpenZFS is readily available, and support > deduplication natively. I thought nobody sane actually used ZFS dedup because it eats RAM for breakfast, lunch and d

RE: The future of SIS

2023-10-16 Thread Laura Smith via dovecot
> Is s3 not to slow for this? > I think the clue is in the name "s3-compatible". Clearly calling out to "real" (AWS) S3 would be a non-starter. But a local installation of something like CEPH, MinIO or whatever on the same LAN ? I'd think that should be workable, no ? ___

RE: The future of SIS

2023-10-16 Thread Laura Smith via dovecot
> > Interesting, nice they use this rust, I am curious how they define this > scaling. What I don't get is why are they messing with smtp. I always get a > bad feeling when a company is trying to do everything. Good they are using rust and even better they've had an independent security audi

Re: The future of SIS

2023-10-16 Thread Laura Smith via dovecot
> > Well, so Laura is absolutely right ... > > > "Things like dsync will be GONE in the community version." > > That's not right, dsync is still there. Replicator is not, so dsync can't be > triggered automatically by dovecot after changes to the mailbox Well, to be fair : 1. I said what I

Re: The future of SIS

2023-10-16 Thread Laura Smith via dovecot
> > If that is the case, well then I have to find another way to keep mails in > sync between 2 mailservers. Hope the community will find a new solution! > I have been keeping one eye on Stalwart (https://stalw.art/) for a while now. I haven't tested it as yet, but I'm very much tempted to g

Re: The future of SIS

2023-10-13 Thread Laura Smith via dovecot
spread FUD that you made up. > > Dsync is not going anywhere, and we are not close-sourcing Dovecot Core. > There is not a trove of code going into Dovecot 3.0 that "never sees the > daylight". > > Thank you, > Aki > > > On 13/10/2023 21:10 EEST Laura Sm

Re: The future of SIS

2023-10-13 Thread Laura Smith via dovecot
TL;DR If you are a Dovecot Community user, don't waste your time reading the Dovecot Pro release notes. To expand: I think you have to understand that lots of things that are going into Dovecot 3 (Pro) will never see the light of day in the community edition. In addition, Dovecot have publicly

Outlook and IMAP Flags

2023-07-22 Thread Laura Smith via dovecot
Hi I've tried searching the internet, but the only thing I can find is a post on a MIcrosoft forum where a Microsoft reps claims flags are not supported on IMAP (I thought it was an RFC3501 feature ?). Anyway, I have a user who has Outlook/Windows on desktop and iOS (iPhone/iPad) for remote.

Any need to be worried about occasional dsync errors ?

2019-09-24 Thread Laura Smith via dovecot
I am occasionally (maybe every 4 hours or less frequently) seeing the following two errors appear in my logs. Are they any cause for concern ? Error: Timeout during state=sync_mails (send=done recv=mails) I/O has stalled, no activity for 600 seconds (last sent=mail_request (EOL)

dsync not replicatiing .dovecot.sieve

2019-07-03 Thread Laura Smith via dovecot
There was a post on this topic to the list Aug 06, 2018 to which Aki replied "Thank you for reporting this, we'll take a look at this.". But its not clear what (if anything) has happened since ? The problem still seems to exist in 2.3.3 (original report by previous poster was for 2.3.2.1) The s

Warning: Failed to do incremental sync

2019-07-03 Thread Laura Smith via dovecot
Setup dovecot sync along the lines of (https://wiki2.dovecot.org/Replication). I am doing one way replication. The initial full replication happened without issue, but now I'm seeing these errors on the slave server: doveadm: Warning: /data/mail/foo/bar/Maildir/dovecot-uidlist: Duplicate fil

mail_replica equivalent to replicator_host/replicator_port

2019-07-03 Thread Laura Smith via dovecot
Silly question but regarding https://wiki.dovecot.org/Replication, is the mail_replica parameter shown in the docs equivalent to replicator_host and replicator_port in 2.3.3 ? 2.3.3 doesn't seem to like the mail_replica param (and indeed doveconf -a doesn't show it as an option) Thanks !

Re: failed: read(/var/run/dovecot/dns-client)

2019-04-11 Thread Laura Smith via dovecot
‐‐‐ Original Message ‐‐‐ On Thursday, April 11, 2019 9:01 PM, John Fawcett via dovecot wrote: > On 11/04/2019 10:02, Laura Smith via dovecot wrote: > > > ‐‐‐ Original Message ‐‐‐ > > On Thursday, April 11, 2019 12:55 AM, John Fawcett via dovecot > > d

Re: auth-worker unknown user

2019-04-11 Thread Laura Smith via dovecot
On Thursday, April 11, 2019 5:49 PM, Aki Tuomi wrote: > > On 11 April 2019 17:56 Laura Smith via dovecot dovecot@dovecot.org wrote: > > On Thursday, April 11, 2019 3:07 PM, Aki Tuomi aki.tu...@open-xchange.com > > wrote: > > > > > > On 11 April 2019 16:

Re: auth-worker unknown user

2019-04-11 Thread Laura Smith via dovecot
On Thursday, April 11, 2019 3:07 PM, Aki Tuomi wrote: > > On 11 April 2019 16:45 Laura Smith via dovecot < dovecot@dovecot.org> wrote: > > > > On Thursday, April 11, 2019 2:02 PM, Aki Tuomi < > > aki.tu...@open-xchange.com> wrote: > > > >

Re: auth-worker unknown user

2019-04-11 Thread Laura Smith via dovecot
‐‐‐ Original Message ‐‐‐ On Thursday, April 11, 2019 3:07 PM, Aki Tuomi wrote: > > On 11 April 2019 16:45 Laura Smith via dovecot < dovecot@dovecot.org> wrote: > > > > On Thursday, April 11, 2019 2:02 PM, Aki Tuomi < > > aki.tu...@open-xchange.com&g

Re: auth-worker unknown user

2019-04-11 Thread Laura Smith via dovecot
On Thursday, April 11, 2019 2:02 PM, Aki Tuomi wrote: > PAM is trying to lookup user@domain while you probably only have user. PAM > driver does not yet support username_format.  > > Aki But /etc/dovecot/users file isn't pam ?   I don't need pam if if I'm using /etc/dovecot/users ?  Or am I u

auth-worker unknown user

2019-04-11 Thread Laura Smith via dovecot
pam(foo...@example.com,192.0.1.1,<9zMTUUCGNfHZzMpL>): unknown user (SHA1 of given password: ff75068c2f4d700a49dae204d56477a5ffa5d23d) The password is correct, i.e. 'echo -n 'passed' | openssl dgst -sha1' matches. The user is setup correctly in /etc/dovecot/users (the /etc/dovecot/users was cop

Re: failed: read(/var/run/dovecot/dns-client)

2019-04-11 Thread Laura Smith via dovecot
‐‐‐ Original Message ‐‐‐ On Thursday, April 11, 2019 9:05 AM, Aki Tuomi wrote: > > On 11 April 2019 11:02 Laura Smith via dovecot dovecot@dovecot.org wrote: > > ‐‐‐ Original Message ‐‐‐ > > On Thursday, April 11, 2019 12:55 AM, John Fawcett via dovecot >

Re: failed: read(/var/run/dovecot/dns-client)

2019-04-11 Thread Laura Smith via dovecot
‐‐‐ Original Message ‐‐‐ On Thursday, April 11, 2019 12:55 AM, John Fawcett via dovecot wrote: > On 11/04/2019 00:51, Laura Smith via dovecot wrote: > > > ‐‐‐ Original Message ‐‐‐ > > On Wednesday, April 10, 2019 11:48 PM, John Fawcett via dovecot >

Re: failed: read(/var/run/dovecot/dns-client)

2019-04-10 Thread Laura Smith via dovecot
‐‐‐ Original Message ‐‐‐ On Wednesday, April 10, 2019 11:48 PM, John Fawcett via dovecot wrote: > On 11/04/2019 00:18, Laura Smith via dovecot wrote: > > > ‐‐‐ Original Message ‐‐‐ > > On Wednesday, April 10, 2019 10:24 PM, Aki Tuomi aki.tu...@open-xcha

Re: failed: read(/var/run/dovecot/dns-client)

2019-04-10 Thread Laura Smith via dovecot
‐‐‐ Original Message ‐‐‐ On Wednesday, April 10, 2019 10:24 PM, Aki Tuomi wrote: > > On 10 April 2019 23:56 Laura Smith via dovecot < dovecot@dovecot.org> wrote: > > > > ‐‐‐ Original Message ‐‐‐ > > On Wednesday, April 10, 2019 9:14 PM, A

Re: failed: read(/var/run/dovecot/dns-client)

2019-04-10 Thread Laura Smith via dovecot
‐‐‐ Original Message ‐‐‐ On Wednesday, April 10, 2019 9:14 PM, Aki Tuomi wrote: > > On 10 April 2019 23:13 Laura Smith via dovecot dovecot@dovecot.org wrote: > > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ > > On Wednesday, April 10,

Re: failed: read(/var/run/dovecot/dns-client)

2019-04-10 Thread Laura Smith via dovecot
Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Wednesday, April 10, 2019 8:20 PM, Aki Tuomi wrote: > > On 10 April 2019 22:13 Laura Smith via dovecot dovecot@dovecot.org wrote: > > On Wednesday, April 10, 2019 7:57 PM, Aki Tuomi aki.tu...@open-xchange.co

Re: failed: read(/var/run/dovecot/dns-client)

2019-04-10 Thread Laura Smith via dovecot
On Wednesday, April 10, 2019 7:57 PM, Aki Tuomi wrote: > > On 10 April 2019 21:26 Laura Smith via dovecot dovecot@dovecot.org wrote: > > === > > dsync(foo...@example.com): Error: imapc(foobar.example.com:993): > > dns_lookup(foobar.example.com) failed: read(/va

Re: ssl_cert: Can't open file permission denied

2019-04-10 Thread Laura Smith via dovecot
‐‐‐ Original Message ‐‐‐ On Wednesday, April 10, 2019 1:08 PM, Michael Orlitzky via dovecot wrote: > On 4/10/19 6:39 AM, Dmitry Donskih via dovecot wrote: > > > `chmod -R 655 /etc/foobar/ssl' drops x attribute from`ssl' itself. > > Use `chmod -R 755' or`chmod +x' or similar. > > Your p

failed: read(/var/run/dovecot/dns-client)

2019-04-10 Thread Laura Smith via dovecot
=== dsync(foo...@example.com): Error: imapc(foobar.example.com:993): dns_lookup(foobar.example.com) failed: read(/var/run/dovecot/dns-client) failed: read(size=512) failed: Connection reset by peer dsync(foo...@example.com): Error: Failed to initialize user: imapc: Login to foobar.example.com f

Re: ssl_cert: Can't open file permission denied

2019-04-10 Thread Laura Smith via dovecot
On Wednesday, April 10, 2019 11:40 AM, Gerald Galster via dovecot wrote: > > Am 10.04.2019 um 11:59 schrieb Laura Smith via dovecot > > : > > > > On Wednesday, April 10, 2019 10:52 AM, Aki Tuomi via dovecot > > wrote: > > > > > On 1

Re: ssl_cert: Can't open file permission denied

2019-04-10 Thread Laura Smith via dovecot
On Wednesday, April 10, 2019 10:52 AM, Aki Tuomi via dovecot wrote: > On 10.4.2019 12.36, Laura Smith via dovecot wrote: > > > Dovecot 2.3.3 (dcead646b) > > openSUSE Leap 15.0 > > I am getting a weird error message: > > Fatal: Error in configuration file /

ssl_cert: Can't open file permission denied

2019-04-10 Thread Laura Smith via dovecot
Dovecot 2.3.3 (dcead646b) openSUSE Leap 15.0 I am getting a weird error message: Fatal: Error in configuration file /etc/dovecot/local.conf line 16: ssl_cert: Can't open file /etc/foobar/ssl/certbot.pem: Permission denied I have tried the following: - chmod -R 655 /etc/foobar/ssl (/etc/foobar i