- dovecot - dovecot.org

Re: Auth Policy Server/wforce/weakforced
by Daniel Miller 08 Aug '17

08 Aug '17

On 8/4/2017 12:48 PM, Daniel Miller wrote: > On 8/3/2017 6:11 AM, Teemu Huovila wrote: >> >> On 02.08.2017 23:35, Daniel Miller wrote: >>> Is there explicit documentation available for the (probably trivial) >>> configuration needed for Dovecot and Wforce? I'm probably missing >>> something that should be perfectly obvious... >>> >>> Wforce appears to start without errors. I added a file to dovecot's >>> conf.d: >>> >>> 95-policy.conf: >>> auth_policy_server_url = http://localhost:8084/ >>> auth_policy_hash_nonce = this_is_my_super_secret_something >>> >>> Looking at the Wforce console I see: >>> >>> WforceWebserver: HTTP Request "/" from 127.0.0.1:45108: Web >>> Authentication failed >>> >>> In wforce.conf I have the (default): >>> >>> webserver("0.0.0.0:8084", "--WEBPWD") >>> >>> Do I need to change the "--WEBPWD"? Do I need to specify something >>> in the Dovecot config? >> You could try putting an actual password, in plain text, where >> --WEBPWD is. Then add that base64 encoded to dovecot setting >> auth_policy_server_api_header. >> > I knew it would be something like that. I've made some changes but > I'm still not there. I presently have: > > webserver("0.0.0.0:8084", "--WEBPWD ultra-secret-secure-safe") > in wforce.conf (and I've tried with and without the --WEBPWD) > > and > > auth_policy_server_api_header = Authorization: Basic > dWx0cmEtc2VjcmV0LXNlY3VyZS1zYWZl > in 95-policy.conf for dovecot > > Obviously I'm still formatting something wrong. > I think I've got something working a little better. I'm using: webserver("0.0.0.0:8084", "ultra-secret-secure-safe") (so I remove the --WEBPWD - that's a placeholder, not a argument declaration) and for dovecot, the base64 encoding needs to be "wforce:password" instead of just the password. Now I have to see what else needs to be tweaked. Daniel

2 1

[master-2.2] 4118e86
by Armin Tüting 08 Aug '17

08 Aug '17

quota-status.c: In function ‘client_handle_request’: quota-status.c:98:10: warning: passing argument 4 of ‘message_detail_address_parse’ from incompatible pointer type [enabled by default] &detail); ^ In file included from quota-status.c:14:0: ../../../src/lib-mail/message-address.h:38:6: note: expected ‘const char **’ but argument is of type ‘char *’ void message_detail_address_parse(const char *delimiter_string, ^ quota-status.c:98:10: error: too many arguments to function ‘message_detail_address_parse’ &detail); ^ In file included from quota-status.c:14:0: ../../../src/lib-mail/message-address.h:38:6: note: declared here void message_detail_address_parse(const char *delimiter_string,

2 1

Dovecot infrastructure
by Simone Marx :: Edinet Srl 08 Aug '17

08 Aug '17

Hi, I would need some suggestion for a dovecot based mail infrastructure. Actually, only one server (with dovecot sendmail amavis spamassassin clamav etc etc) is no longer enouth, so I thought I would put on a more complex infrastructure on different servers. But I do not know a few things. I was thinking about partitioning users on 3-4 servers with dovecot (imap / pop3) and dovecot-lda (no networked filesystem between them) and then configuring 1-2 servers with dovecot director and 1-2 servers for SMTP with postfix. It is not clear how the director will map user -> server to be used and, in a user virtualization context (maybe on MySQL) what is the owner / permissions I should give to home folders where I will store mail Thank you. Simone.

3 3

IMAP From sort uses only local-part
by Paul 08 Aug '17

08 Aug '17

As far as I can tell, when I ask Dovecot to sort an IMAP mailbox by the >From address, it ignores the part of the address after the '@'. So, for instance, mails from info(a)abc.org, info(a)xyz.org, and info(a)ghi.org are all mingled together in arrival order. Is there a way to change this? Thanks!

2 1

dovecot 2.2.28 password auth with openldap
by Markus Rosjat 07 Aug '17

07 Aug '17

Hi there, I desperatly trying to store a BLF-CRYPT password hash in an LDAP userPassword Attribute and get dovecot to authenticate against it. I use a thunderbird as client and send the password plain with starttls. what worked so far but is kinda problematic for my smtp authenticaton was to store the has with the prefix {CRYPT} or {BLF-CRYPT}. Is there a way to get dovecot to authenticate without storing the prefix in the LDAP attribute ? regards -- Markus Rosjat fon: +49 351 8107223 mail: rosjat(a)ghweb.de G+H Webservice GbR Gorzolla, Herrmann Königsbrücker Str. 70, 01099 Dresden http://www.ghweb.de fon: +49 351 8107220 fax: +49 351 8107227 Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT

3 2

Re: dovecot Digest, Vol 172, Issue 8
by Ken Zachreson 06 Aug '17

06 Aug '17

Help Thank You, Ken Zachreson On Aug 6, 2017 2:00 AM, dovecot-request(a)dovecot.org wrote: ATTENTION: This email was sent from someone outside of GCRC. Always use caution when opening attachments or clicking links, and when receiving unexpected emails. Send dovecot mailing list submissions to dovecot(a)dovecot.org To subscribe or unsubscribe via the World Wide Web, visit https://dovecot.org/mailman/listinfo/dovecot or, via email, send a message with subject or body 'help' to dovecot-request(a)dovecot.org You can reach the person managing the list at dovecot-owner(a)dovecot.org When replying, please edit your Subject line so it is more specific than "Re: Contents of dovecot digest..." Today's Topics: 1. Re: Corrupted SSL parameters file in state_dir: ssl-parameters.dat (Terry Jones) 2. Using Dovecot for IMAP/POP and SMTP (Kenneth Ulrich) 3. Re: Using Dovecot for IMAP/POP and SMTP (Larry Rosenman) 4. Re: Using Dovecot for IMAP/POP and SMTP (Randy Bush) ---------------------------------------------------------------------- Message: 1 Date: Sat, 5 Aug 2017 11:55:49 +0100 From: Terry Jones <r.a.n.domdev4+dovecot(a)gmail.com> To: Joseph Tam <jtam.home(a)gmail.com> Cc: dovecot(a)dovecot.org Subject: Re: Corrupted SSL parameters file in state_dir: ssl-parameters.dat Message-ID: <CA+HuS5GLWxSq6fxh8pg4RXsYOOUBa0gLqTQ-Pt0Xs-fC1pfmYQ(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" > > > Your timestamps suggest you did this the other way around. > > Aki mentioned that issue is/will be fixed, but DH parameters can take a > *very* long time to generate if you're unlucky, so maybe it's a timing > issue (using the service before the DH parameters was ready.) > I think I would ask you to ignore the timestamps in this instance. I can tell you from fact that I deleted the old .dat file, restarted dovecot, and waited for it to regenerate the file (i.e. there was nothing there, and then there was ...). So I can guarantee you that the file there at the moment very much is a new file, and that I waited for that new file before testing again. ------------------------------ Message: 2 Date: Sat, 5 Aug 2017 20:14:57 -0500 From: Kenneth Ulrich <ulrichkenneth(a)gmail.com> To: dovecot(a)dovecot.org Subject: Using Dovecot for IMAP/POP and SMTP Message-ID: <CACSvXraiWV_JkJ=bZmnNV6Axs8ziWb_8ywN0beyB1fkRJ3RLSg(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" All, I was wondering if it is possible to use Dovecot as both incoming and outgoing. I have a friend that I am helping build a server, and he plans on using Dovecot for POP/IMAP and Postfix for SMTP and mailbox storage. If I understand right, Dovecot can handle both services and that is the path I would like him to take for easier maintenance. Can someone confirm this? ------------------------------ Message: 3 Date: Sat, 5 Aug 2017 20:18:18 -0500 From: Larry Rosenman <larryrtx(a)gmail.com> To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: Using Dovecot for IMAP/POP and SMTP Message-ID: <CA+S=X75hvJU+Y5tiUCcLAC9kDLsDQhOwqMu7Q7Em6oXD_sG8YQ(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" No. Dovecot is JUST an IMAP/Pop3 server. SMTP *MUST* be handled via an MTA (Mail transport agent). Exim, Postfix, Sendmail, qmail, others are MTA's for SMTP. On 8/5/17, Kenneth Ulrich <ulrichkenneth(a)gmail.com> wrote: > All, > > I was wondering if it is possible to use Dovecot as both incoming and > outgoing. > > I have a friend that I am helping build a server, and he plans on using > Dovecot for POP/IMAP and Postfix for SMTP and mailbox storage. > > If I understand right, Dovecot can handle both services and that is the > path I would like him to take for easier maintenance. > > Can someone confirm this? > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ------------------------------ Message: 4 Date: Sun, 06 Aug 2017 10:48:58 +0900 From: Randy Bush <randy(a)psg.com> To: Kenneth Ulrich <ulrichkenneth(a)gmail.com> Cc: dovecot(a)dovecot.org Subject: Re: Using Dovecot for IMAP/POP and SMTP Message-ID: <m2tw1lihyt.wl-randy(a)psg.com> Content-Type: text/plain; charset=US-ASCII > I was wondering if it is possible to use Dovecot as both incoming and > outgoing. no. but if it was systemd it would, and pick up the paper post too. randy ------------------------------ Subject: Digest Footer _______________________________________________ dovecot mailing list dovecot(a)dovecot.org https://dovecot.org/mailman/listinfo/dovecot ------------------------------ End of dovecot Digest, Vol 172, Issue 8 ***************************************

1 0

Using Dovecot for IMAP/POP and SMTP
by Kenneth Ulrich 06 Aug '17

06 Aug '17

All, I was wondering if it is possible to use Dovecot as both incoming and outgoing. I have a friend that I am helping build a server, and he plans on using Dovecot for POP/IMAP and Postfix for SMTP and mailbox storage. If I understand right, Dovecot can handle both services and that is the path I would like him to take for easier maintenance. Can someone confirm this?

3 2

Re: Corrupted SSL parameters file in state_dir: ssl-parameters.dat
by Joseph Tam 05 Aug '17

05 Aug '17

> But if I enable SSL, the doveadm backup on the remote machine hangs. > And the destination machine prints the following two massages in the > logs : > > Aug 4 17:10:31 bbb dovecot: doveadm: Error: Corrupted SSL parameters > file in state_dir: ssl-parameters.dat - disabling SSL 360 > Aug 4 17:10:31 bbb dovecot: doveadm: Error: Couldn't initialize SSL > parameters, disabling SSL > > > BUT : > > (1) /var/lib/dovecot/ssl-parameters.dat *DOES* exist. > and > (2) If I delete it and restart dovecot, it successully re-creates it, as per > Aug 4 17:02:32 bbb dovecot: ssl-params: Generating SSL parameters > Aug 4 17:06:58 bbb dovecot: ssl-params: SSL parameters regeneration completed Your timestamps suggest you did this the other way around. Aki mentioned that issue is/will be fixed, but DH parameters can take a *very* long time to generate if you're unlucky, so maybe it's a timing issue (using the service before the DH parameters was ready.) Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: Doveadm-sync SSH practicalities
by Joseph Tam 05 Aug '17

05 Aug '17

Terry Jones wrote: > The documentation is somewhat silent on this subject. If you mean https://wiki.dovecot.org/Tools/Doveadm/Sync the answers seem implicit to what's been stated. > What permissions does the SSH user need ? To be able to run the doveadm executable (or a wrapper script that eventually runs doveadm) on the remote side. > How associated does it need to be with things like dovecot directory > ownership etc ? It will take uid/gid directly from the login privileges unless you use a wrapper script that changes UID/GID. This may be necessary if you use remote-prefix option for remapping virtual users and user@domain to another UID/GID. > Obviously my dovecot daemon processes are running as restricted users > with "nologin" shells etc., and I don't really want to go opening > them up if I don't have to. It doesn't seem possible: you'll need to be able to set up the other endpoint of communication. You may be able to lock down the shell by replacing it with a fixed doveadm and arguments, or perhaps by fiddling with keys and the forced command feature of ssh, after working out the security issues. Depending on your use-case, you might be better off using one of the other transport methods. Do you actually need per-user syncing? Joseph Tam <jtam.home(a)gmail.com>

2 2

Auth Policy Server/wforce/weakforced
by Daniel Miller 04 Aug '17

04 Aug '17

Is there explicit documentation available for the (probably trivial) configuration needed for Dovecot and Wforce? I'm probably missing something that should be perfectly obvious... Wforce appears to start without errors. I added a file to dovecot's conf.d: 95-policy.conf: auth_policy_server_url = http://localhost:8084/ auth_policy_hash_nonce = this_is_my_super_secret_something Looking at the Wforce console I see: WforceWebserver: HTTP Request "/" from 127.0.0.1:45108: Web Authentication failed In wforce.conf I have the (default): webserver("0.0.0.0:8084", "--WEBPWD") Do I need to change the "--WEBPWD"? Do I need to specify something in the Dovecot config? -- Daniel

2 2