similar to: Client Cert Auth Problem

Hello, I am new to Dovecot but installation was quite easy, so there is one more LDAP authenticated, Dovecot / Postfix mailbox online, but there is one question left: I would like to set up a configuration, which encrypts every user mail with a unique key. If user logs in, private key should be decrypted with user password and every mail user requests should be decrypted with users private key.

Hello, I ran into problems to get Dovecot running on FreeBSD. Steps for reproduction. Start Docot with dovecot -F (same result if started by rc script) telnet 192.168.116.38 110 Trying 192.168.116.38... Connected to freebsd. Escape character is '^]'. -ERR Disconnected: Auth process broken Connection closed by foreign host. logfile shows following: May 22 11:41:24 freebsd dovecot:

On 21 Feb 2023, at 10:12 pm, James Brown <jlbrown at bordo.com.au> wrote: > > The new one has Dovecot compiled with same configure options, same configuration files, but fails to authenticate: > > Feb 21 21:51:03 master: Info: Dovecot v2.3.20 (80a5ac675d) starting up for imap, pop3 (core dumps disabled) > Feb 21 21:51:33 auth-worker(11701): Error: conn unix:auth-worker

http://dovecot.org/releases/1.2/dovecot-1.2.2.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.2.tar.gz.sig Found and fixes several v1.2-specific bugs. Hopefully it's now stable for most people's usage. * GSSAPI: More changes to authentication. Hopefully good now. * lazy_expunge plugin: Drop \Deleted flag when moving message. + dovecot -n/-a now outputs also lda settings. +

http://dovecot.org/releases/1.2/dovecot-1.2.2.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.2.tar.gz.sig Found and fixes several v1.2-specific bugs. Hopefully it's now stable for most people's usage. * GSSAPI: More changes to authentication. Hopefully good now. * lazy_expunge plugin: Drop \Deleted flag when moving message. + dovecot -n/-a now outputs also lda settings. +

> On 22/02/2023 07:00 EET James Brown <jlbrown at bordo.com.au> wrote: > > > On 21 Feb 2023, at 10:12 pm, James Brown <jlbrown at bordo.com.au> wrote: > > > > > > > The new one has Dovecot compiled with same configure options, same configuration files, but fails to authenticate: > > > > Feb 21 21:51:03 master: Info: Dovecot v2.3.20

Hi all, One thing that's always itching when I think about mail-servers, is the storage of e-mail messages in (rather) plain-text. Meaning, any administrator with sufficient privileges would be able to read messages not meant for them. Of course, PGP alike solutions exist, but that's not for the masses. In my opinion I would like to have e-mail messages stored encrypted using a (strong)

Hello, it seems there there is an issue regarding "TLS-Certtificate" authentication in Thunderbird and Dovecot. Obviously client certificate is recognized by Dovecot: Apr 25 14:29:01 dovecot dovecot: imap-login: Valid certificate: /emailAddress=christian.felsing at example.net/CN=Christian Felsing (Test)/OU=CF Certificates/O=example.net/C=DE AFAIK Dovecot always requires IMAP login,

Hello, there is a problem between Dovevot 1.2 Managesieve 0.11.7 and Horde webmail 1.2.2 (possibly also in 1.2.3) in imap4flags $ telnet localhost 2000 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. "IMPLEMENTATION" "dovecot" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric

Hi, ok, I'm am developing a new solution that includes dovecot, and will be wanting to use the latest sieve implementation, so I have chosen to start with 1.2 as the base. I had a working install of 1.1.8 installed, and got a checkpassword setup working properly with it to authenticate a user. I used the passdb to call checkpassword, and the prefetch userdb to tell it to use the values that

Dovecot 1.07rc1 on ubuntu 6.04 I get the following problem: root 26375 0.0 0.2 5548 2240 ? Ss Sep15 1:39 /usr/sbin/dovecot root 26376 0.0 0.3 7896 3364 ? S Sep15 0:31 \_ dovecot-auth root 26378 0.0 0.3 8304 3824 ? S Sep15 0:34 \_ dovecot-auth root 26379 0.0 0.4 8668 4152 ? S Sep15 0:38 \_ dovecot-auth root

Hi After upgrading to dovecot 1.0.7 I noticed that the actual username is no longer logged, but rather the system user (in my case 'vmail') under which my virtual set-up runs. Now I'm unable to see which virtual users log in. Any pointers on how to configure dovecot to log the actual username given during the IMAP dialogue would be appreciated. My dovecot.conf includes the following:

I'm interested in using authentication via a UNIX socket as documented at http://wiki2.dovecot.org/AuthDatabase/Dict. (We are currently using a checkpassword script to enable us to authenticate against a django app that stores passwords in pbkdf2 format, but I'm concerned about scalability as we grow - specifically the comment about performance on

Hi! Dovecot is now a nearly 20 year old product, and during that time it has accumulated many different features and plugins in its core repository. We are starting to gradually remove some of these parts, which are unused, untested or deprecated. We will provide advance notification before removing anything. To start, the following features are likely to be removed in next few releases of

Hi! Dovecot is now a nearly 20 year old product, and during that time it has accumulated many different features and plugins in its core repository. We are starting to gradually remove some of these parts, which are unused, untested or deprecated. We will provide advance notification before removing anything. To start, the following features are likely to be removed in next few releases of

I need some help. I have compiled dovecot (1.0-rc15) with --with-mysql option, when I execute the binary with --build-options I get this: Build options: ioloop=poll notify=dnotify ipv6 openssl SQL drivers: Passdb: checkpassword passwd passwd-file shadow Userdb: checkpassword passwd prefetch passwd-file static In this case, when I execute dovecot I get this error: dovecot: Jan 03 03:48:47 Error:

can you try : smbclient //SERVER.DOMAIN.TLD/netlogon -k bet that works.. Louis >-----Oorspronkelijk bericht----- >Van: heinz.hoelzl at gvcc.net >[mailto:samba-bounces at lists.samba.org] Namens Heinz H?lzl >Verzonden: dinsdag 14 april 2015 10:55 >Aan: samba at lists.samba.org >CC: pug at felsing.net; schnaggy at schnaggy.de >Onderwerp: Re: [Samba] samba 4.2 RDP

I have an interesting case here ? Virtual mailboxes, domain/username/aliases stored in MySQL, authentication done using PAM. PAM authenticates through Kerberos, which are internal realms and not the email domains ? for example, my username would be laz at PARAVIS.LOCAL <mailto:laz at PARAVIS.LOCAL> and my email address would be laz at paravis.net <mailto:laz at paravis.net>. All of

Hi there, As of Dovecot 2.2.9, it's possible to enable passwordless authentication using client certificates [1]: ssl_ca = </etc/ssl/ca.pem ssl_verify_client_cert = yes auth_ssl_username_from_cert = yes (Password checking can be bypassed by returning the extra fields ?password= nopassword? in the passdb when the variable ?%k? expands to "valid".) However this

Hi, I'm trying to get apache, sendmail , and dovecot to use SSL certs signed by my own CA. I've got the apache certs working fine. However, dovecot ( I haven't even tried sendmail yet) doesn't seem to accept any of the certificates that I create for it. There is a script that comes with dovecot that creates self-signed certificates for you but, I need certificates signed by my own