Re: Dovecot auth-worker error after cram-md5 auth

Are you still trying to authenticate using cram-md5? Aki On 01.02.2017 09:51, Poliman - Serwis wrote: > It still use: > passdb { > driver = passwd-file > args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd > } > > When I delete above and delete "cram-md5" in auth_mechanisms it still not >

Re: Dovecot auth-worker error after cram-md5 auth

It still use: passdb { driver = passwd-file args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd } When I delete above and delete "cram-md5" in auth_mechanisms it still not working. 2017-02-01 8:45 GMT+01:00 Aki Tuomi : > You are probably wanting to do > passdb { >

Re: Dovecot auth-worker error after cram-md5 auth

It was only for testing purposes. That's why I want change it back to default settings. ;) I will check above lines and give response asap. 2017-02-01 8:45 GMT+01:00 Aki Tuomi : > You are probably wanting to do > passdb { > driver = passwd-file > args = scheme=cram-md5

Re: Dovecot auth-worker error after cram-md5 auth

You are probably wanting to do passdb { driver = passwd-file args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd } passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } Why you want to use cram-md5 is beyond me, because using SSL is much more safer. Aki On 01.02.2017 09:41, Poliman

Re: Dovecot auth-worker error after cram-md5 auth

Default it was: "auth_mechanisms = plain login" and I added cram-md5. After restart all work perfectly. But after I added: driver = passwd-file args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd I can't set default lines because I got error. Please tell me which lines should be changed to

Re: quota-status returns quota_status_success when email would put user over quota

Forgot to add the postfix config: smtpd_recipient_restrictions = ... check_policy_service inet:localhost:12340 Aki On 01.02.2017 09:34, Aki Tuomi wrote: > Steps to setup quota with status: > > mail_plugins = $mail_plugins quota > > protocol imap { >mail_plugins = $mail_plugins

Re: Dovecot auth-worker error after cram-md5 auth

Because cram-md5 needs the user's password for calculating responses, it cannot work with hashed passwords (one-way encrypted). The only supported password schemes are PLAIN and CRAM-MD5. Aki On 01.02.2017 09:33, Poliman - Serwis wrote: > I always restart dovecot after change config. ;) Sure, I

Re: quota-status returns quota_status_success when email would put user over quota

Steps to setup quota with status: mail_plugins = $mail_plugins quota protocol imap { mail_plugins = $mail_plugins imap_quota } service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 # You can choose any port you want } client_limit =

Re: Sieve removeflag Action

* Stephan Bosch 2017.01.31 21:31: > This slipped my attention for the moment. Will look at this soon... Thanks. signature.asc Description: Digital signature

Re: Dovecot auth-worker error after cram-md5 auth

I always restart dovecot after change config. ;) Sure, I commented out added two lines by me, restarted dovecot and here it is: # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS auth_mechanisms = plain login cram-md5 listen = *,[::] log_timestamp =

Re: Dovecot auth-worker error after cram-md5 auth

On 01.02.2017 08:18, Poliman - Serwis wrote: > This is debug log files in syslog: > Feb 1 07:10:25 vps342401 dovecot: auth: Debug: client passdb out: > CONT#0112#011PDAxODg3ODIzMTUwMzgxNzMuMTQ4NTkyOTQyNUB2cHMzNDI0MDEub3ZoLm5ldD4= > Feb 1 07:10:26 vps342401 dovecot: auth: Debug: client in: CONT

Re: Dovecot auth-worker error after cram-md5 auth

This is debug log files in syslog: Feb 1 07:10:25 vps342401 dovecot: auth: Debug: client passdb out: CONT#0112#011PDAxODg3ODIzMTUwMzgxNzMuMTQ4NTkyOTQyNUB2cHMzNDI0MDEub3ZoLm5ldD4= Feb 1 07:10:26 vps342401 dovecot: auth: Debug: client in: CONT Feb 1 07:10:26 vps342401 dovecot: auth-worker(27069):

Re: quota-status returns quota_status_success when email would put user over quota

Am 31. Jänner 2017 16:36:35 MEZ schrieb Kristian Pedersen : >Hi list, > >We still did not manage to get quota-status working. >We're hoping someone can provide some feedback/ideas on how we may >investigate this issue further? >Is it likely to be a bug fixed in a newer

dovecot 2.2.27 welcome plugins script

Hello everyone, I am trying to send a mail to newly autocreated users, using the welcome plugins, however, i am get unable to pipe user information correctly to the script, acording to the wiki the scripts are called just as the quota warnig scripts. Also, every time that a try something

Re: Vacation Sending To Root

Thanks for the response, I did manage to resolve this, however I ended up using a custom procmail recipe which handles (creates) the vacation responses. This was included (INCLUDERC) before the call to $DELIVER. On 31 January 2017 at 20:36, Stephan Bosch wrote: > Op

Re: mail_location in userdb inconsistent with imap and pigeonhole

Op 12/10/2016 om 7:11 PM schreef Ladislav Laska: > Hi! > > I'm still fighting with lost mails and what I think is a locking > problem. > > As I've lost some pretty important mails already, I decided to mitigate > my troubles by moving to maildir format, which should not be susceptible > to these

Re: Vacation Sending To Root

Op 12/16/2016 om 2:53 PM schreef Shaun Forsyth: > Dovecot Version 2.0.9 > > I am having an issue where all vacation messages are being sent to root. Is > any one able to advise. > > Dovecot Log Shows :- > Sieve: msgid=< > camd5tviw0ssiggm8jy5wov0ros1udcjfnvb9vo-rzcnn74e...@mail.xx.com>: sent >

Re: Sieve removeflag Action

Op 1/19/2017 om 10:43 AM schreef Thomas Leuxner: > * Stephan Bosch 2017.01.19 10:32: > >> Could you provide a more detailed example? > Sure. Personal script v This slipped my attention for the moment. Will look at this soon... Regards, Stephan.

Re: Sieve & Public folders issue (2nd episode)

Op 1/31/2017 om 7:05 PM schreef dovecot@avv.solutions: > Hello Community, > > Getting back to my previous post, here a a complement: > > - Having enabled sieve, I can store mails and create folder under the > recipient > - Having enabled public folders, I can move mail into them using a > client

Re: Is it possible to use sieve when delivering via pipe to the dovecot deliver command ?

Op 1/21/2017 om 7:12 PM schreef Thomas Carrié: > Hello, > > I am using Exim with this delivery configuration: > > virtual_delivery: > driver = pipe > command = /usr/lib/dovecot/deliver -d $local_part@$domain -f > ... > > I have enabled manage-sieve and uploaded a simple sieve script that I

Sieve & Public folders issue (2nd episode)

Hello Community, Getting back to my previous post, here a a complement: - Having enabled sieve, I can store mails and create folder under the recipient - Having enabled public folders, I can move mail into them using a client (eg Thunderbird); security is therefore ok (actually I gave full

Re: panic when doveadm sieve put between multiple hosts

This bug has been fixed in 2.2.26 with https://github.com/dovecot/core/commit/65a8a3c66787f164a94b67adf38da33b0c2aa519 and https://github.com/dovecot/core/commit/d83aa942767d377dadce82bb25a46aa96959b42b Aki On 2017-01-10 00:11, Tyler Jachetta wrote: Dovecot version: 2.2.25 (7be1766) I’m

Re: quota-status returns quota_status_success when email would put user over quota

Hi list, We still did not manage to get quota-status working. We're hoping someone can provide some feedback/ideas on how we may investigate this issue further? Is it likely to be a bug fixed in a newer version? Regards, Kristian On 2017-01-24 09:25, Kristian Pedersen wrote: Hi list, I

dovecot 2.2.18 replication I/O Timeout

Dear list, I am having an issue like this http://www.dovecot.org/list/dovecot-cvs/2014-September/024898.html with my current dovecot 2.2.18 Concret: doveadm -Dv replicator replicate -p high -f info throws an I/O Timeout error and the only thing I can see are some lock issues: Error:

Auth cache does not take %real_rip into account

I run a Director setup with a webmail in front, the webmail is in login_trusted_networks and sends IMAP-ID x-original-ip to log the client IP. If I enable auth_debug on the director, I see that the cache key contains the client IP, and not the %real_rip. This is causing problems because in

Re: dovecot mdbox never fix broken indexes

On 31.01.2017 12:39, Andrey Melnikov wrote: > 2017-01-31 13:03 GMT+03:00 Aki Tuomi : >>> On January 30, 2017 at 10:53 AM Andrey Melnikov >>> wrote: >>> >>> >>> 2017-01-30 11:43 GMT+03:00 Aki Tuomi : Hi! Please

UPD: 2.2.27 : accessing "mdbox_deleted" content destroys indexes

Just to say this bug is still present in 2.2.27 (1:2.2.27-2~bpo8+1 jessie-backports Debian package). # dovecot --version 2.2.27 (c0f36b0) mail_location = mdbox:~/mdbox:DIRNAME=_@@_dbox-Mails_@@_ Please let me know if you want me to transmit our "doveconf -n" output. Regards, Le 25/01/2017 à

Re: dovecot mdbox never fix broken indexes

2017-01-31 13:03 GMT+03:00 Aki Tuomi : > >> On January 30, 2017 at 10:53 AM Andrey Melnikov wrote: >> >> >> 2017-01-30 11:43 GMT+03:00 Aki Tuomi : >> > Hi! >> > >> > Please send these to dovecot@dovecot.org instead of us directly.

Re: dovecot mdbox never fix broken indexes

> On January 30, 2017 at 10:53 AM Andrey Melnikov wrote: > > > 2017-01-30 11:43 GMT+03:00 Aki Tuomi : > > Hi! > > > > Please send these to dovecot@dovecot.org instead of us directly. Thank you. > Ok, added to cc. > > > Also, did you try