similar to: AUTH PLAIN fails while AUTH LOGIN succeeds with Exim -> Dovecot SASL auth

Hello, i've found an old thread [1] where it was stated that a whole mailbox can be made read-only only setting the according permissions on the filesystem side. [1] http://www.mailinglistarchive.com/html/dovecot at dovecot.org/2011-12/msg00300.html i'd like to check if it's still the only option we have with dovecot v2.0.18 . Regards, -- Sandro Tosi Product Engineer Shared

Hello, we're setting up a weird platform where every incoming email is passed from the MTA directly to a tool that then uses dovecot LMTP to deliver the message into the user mailbox. We are legally *not* allowed to run antispam on all the incoming messages, but only on some of them, as they are recognized by the aforementioned tool; but given that tool directly uses LMTP to delivers the

Hello, we're scouting if it's possible to use Pigeonhole (currently v0.3.1, as this will be provided with an upcoming Debian package) with MySQL dict lookups with the mail setup we're designing. Our (main) goals are: 1. store the filters on the database 2. allow each user to enable/disable any of the filters set we provide (it's a static set of some general filters, available

Hi, somebody from the kolab groupware project recently explained me that the Bus- Factor[1] of around 1 would be one of their primary reasons not to use Dovecot and stick with Cyrus. What do you think about that? Is the bus factor much higher then 1? [1] http://en.wikipedia.org/wiki/Bus_factor Somehow related: Since the free software world[2] slowly converges towards GIT as the "one and

Processing commands for control at bugs.debian.org: > # sorry for the noise > submitter 585188 ! Bug #585188 [convirt] convirt: Python string exceptions no more allowed in Python 2.6 Changed Bug submitter to 'Sandro Tosi <morph at debian.org>' from 'Sandro Tosi <morph at ravel.debian.org>' > submitter 585189 ! Bug #585189 {Done: Julien BLACHE <jblache at

Hello, we found dovecot down on one of our servers, with this error in the log: dovecot: 2009-07-14 04:05:04 Warning: SIGHUP received - reloading configuration dovecot: 2009-07-14 04:05:04 Error: Temporary failure in creating login processes, slowing down for now dovecot: 2009-07-14 04:05:04 Fatal: listen(143) failed: Interrupted system call we can reproduce this error with this tight loop:

Processing commands for control at bugs.debian.org: > submitter 192827 Jos? Luis Gonz?lez <jlgonzal at ya.com> Bug #192827 [xdiskusage] xdiskusage: Printing doesn't manage non-ASCII characters Changed Bug submitter to 'Jos? Luis Gonz?lez <jlgonzal at ya.com>' from 'Jos?? Luis Gonz??lez <jlgonzal at ya.com>' > submitter 208308 R?diger Kuhlmann

Hello, while reading config options for dovecot v1.2.10 I've noticed a very small bug: # ./configure --help | egrep -- 'Dovecot|--with-gnu-ld' `configure' configures Dovecot 1.2.10 to adapt to many kinds of systems. --with-gnu-ld assume the C compiler uses GNU ld [default=no] --with-gnu-ld assume the C compiler uses GNU ld default=no I think the latter

Hello, we are planning to migrate from Courier to Dovecot. We already know courier-dovecot-migrate.pl, that will convert UID list and subscriptions files to dovecot format, and we will run it in batch on all Maildir + enable it at login, once we do the switch But we are also wondering it it might be wise to "force" the creation of dovecot.index{,.cache} files at conversion-time. It

I am attempting to configure a dovecot 2.0 + exim + fetchmail (demon) combination on openSUSE 11.4, initially with the standard dovecot package (2.0.9-3.4-x86_64) and now with the later server:mail build service package (2.0.11-1.1-x86_64). I followed the instructions in http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL but despite the changes in conf.d/10-master.conf the permissions on

3. Januar 2018 00:49, "Stephan Bosch" <stephan at rename-it.nl> schrieb: > Op 1/2/2018 om 10:48 PM schreef Daniel Kenzelmann: > >> Hi, >> >> I'm not entirely sure whether this issue is with exim or with dovecot. >> >> First some background: >> I'm using exim with dovecot-auth which in turn is using LDAP for >>

Op 1/3/2018 om 10:58 AM schreef Stephan Bosch: > Op 1/3/2018 om 8:31 AM schreef Daniel Kenzelmann: >> 3. Januar 2018 00:49, "Stephan Bosch" <stephan at rename-it.nl> schrieb: >> >>> Op 1/2/2018 om 10:48 PM schreef Daniel Kenzelmann: >>> >>>> Hi, >>>> >>>> I'm not entirely sure whether this issue is with exim

On Tue, 8 May 2012 15:22:11 +0200 Frank Elsner wrote: > > Hi to both adressed mailing lists, > > I followed the instructions in http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL Forgot to mention the versions :-( exim 4.77 dovecot 2.1.6 self compiled under Fedora 14. --Frank Elsner

Hi to both adressed mailing lists, I followed the instructions in http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL exim.conf: | plain: | driver = dovecot | public_name = PLAIN | server_socket = /var/run/dovecot/auth-client | server_set_id = $auth1 | | login: | driver = dovecot | public_name = LOGIN | server_socket = /var/run/dovecot/auth-client |

hi! i'm trying to do smtp authentication using dovecot and exim4 by following this guide http://wiki.dovecot.org/HowTo/EximAndDovecotSASL. for the exim4 part, i got an authenticator dovecot: cannot find authenticator driver "dovecot" ?error after i entered the codes in /etc/exim4/exim4.conf.template and reloaded exim4 with the update-exim4.conf command. i'm running debian

Hi, I'm not entirely sure whether this issue is with exim or with dovecot. First some background: I'm using exim with dovecot-auth which in turn is using LDAP for authentication. When using AUTH PLAIN with the optional initial response argument, everything is fine. However when using AUTH PLAIN without the optional response argument, instead of getting an empty challenge ("334

Op 1/3/2018 om 8:31 AM schreef Daniel Kenzelmann: > 3. Januar 2018 00:49, "Stephan Bosch" <stephan at rename-it.nl> schrieb: > >> Op 1/2/2018 om 10:48 PM schreef Daniel Kenzelmann: >> >>> Hi, >>> >>> I'm not entirely sure whether this issue is with exim or with dovecot. >>> >>> First some background: >>>

i'll guess the solution to my problem will be something simple and obvious, because i know i ain't the first person to do this and it ain't all that complicated, but i've been staring at it for days and can't see what's wrong. new installation; os x snow leopard server; postfix 2.5.5; dovecot 1.1.17apple0.5 i'm trying to get SMTP auth working via SASL. using a

tag 469013 patch thanks Hi, Sandro Tosi asked me to forward the attached patch fixing the problem. Kind regards T. -------------- next part -------------- A non-text attachment was scrubbed... Name: xen-unstable.memory.morph_.diff Type: text/x-c Size: 528 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20080307/b7367328/attachment-0001.bin

Hi List, I just updated an old sendmail installation to a modern postfix/dovecot system with mysql backend. Everything works fine but SMTP-AUTH fails with some clients. The problem is, that with PLAIN (old) clients send the base64 coded form: USERNAME\0USERNAME\0PASSWORD which, as i understand dovecot interprets as MASTERUSER\0USERNAME\PASSWORD. New clients send \0USERNAME\0PASSWORD which works