search for: axelluttgen

While investigating Dovecot's deliver with Postfix, I encountered some behaviors making me wonder whether I really understand the purpose of that binary. So, if you allow... This is from Postfix' main.cf: mailbox_command = /usr/local/dovecot/libexec/dovecot/deliver -e -n This is my quick setup for Dovecot: # 1.2.rc4: /usr/local/etc/dovecot.conf # OS: Darwin 9.7.0

Hello, At http://wiki2.dovecot.org/MailboxFormat/mbox: The UID for a new message is calculated from "last used UID" in X-IMAP header + 1 Shouldn't it read "in X-UID header + 1" instead? Axel

Hi, Is there a configuration element that would allow me to change the dot-lock name for the user's /var/mail inbox when it is locked? dovecot (correctly) acquires <username>.lock, but I'm having a problem with procmail where some obscure code path is preventing procmail's acquisition of a lock when it's that default name in /var/mail. The issue is not permissions

Hello, 1. Considering a user_query similar to this one: SELECT ... FROM ... WHERE CASE '%s' WHEN 'lmtp' THEN ... and issuing following command: doveadm user -x service=lmtp someuser at example.com the log shows: SELECT ... FROM ... WHERE CASE 'doveadm' WHEN 'lmtp' THEN ... and the query of course fails. The same config with Dovecot 2.1.16 yields expected

Hello, Is there any way to easily check a master user's password, for itself, without having to refer to another user or to weak the security by allowing master users to log in for themselves? For example, this works: # doveadm auth test 'someuser*masteruser' Password: <enter master user's password here> passdb: someuser*masteruser auth succeeded but depends on the

...#39;m looking forward to is to eliminate the need for returning these two fixed items, as long as all the virtual_users will be using the same uid and gid. Does anybody know how can I do it?? Regards, and thank you! Felix > Date: Thu, 1 Aug 2013 17:50:33 +0200 > From: Axel Luttgens <AxelLuttgens at swing.be> > To: Dovecot Mailing List <dovecot at dovecot.org> > Subject: Re: [Dovecot] misconception in uid and gid > Message-ID: <89AC3212-EFE6-41E5-A22D-97DC8E771218 at swing.be> > Content-Type: text/plain; charset=iso-8859-1 > > Le 1 ao?t 2013 ? 15:43, Felix...

Hello, Let's say dovecot.conf contains: mail_uid = dovemailer mail_gid = dovemailer mail_home = /some/path/%n mail_location = mbox:~/mboxes:INBOX=~/mboxes/inbox and that the password database query is of the form: password_query = \ SELECT \ passwd AS password, \ nickname AS user, \ mail_home AS userdb_home, \ mail_location AS userdb_mail, \ WHERE \ ... The database

Bernhard Schmidt <berni at birkenwald.de> wrote: Hi, > Axel Luttgens <AxelLuttgens at swing.be> wrote: > > Hi Axel, > >> Le 11 f?vr. 2014 ? 08:34, Bernhard Schmidt a ?crit : >> >>> [...] >>> so Dovecot should reject in RCPT TO phase, but according to the logs of the >>> upstream Postfix it does so after END-OF-DATA >>>...

Hello, I'm currently experimenting with this quota-status service configuration: service quota-status { client_limit = 1 executable = quota-status -p postfix # Let's make the default explicit. user = root unix_listener /var/spool/postfix/private/quota-policyd { user = postfix } } The idea is to run the service as root during the preliminary tests (at worst, since

Le 17 mars 2010 ? 21:25:38, Timo Sirainen a ?crit : > On Wed, 2010-03-17 at 21:21 +0100, Renaud Allard wrote: >>>> dovecot_delivery transport output: lda: Fatal: User lookup failed: >>>> net_connect_unix(/opt/dovecot/etc/dovecot/dovecot.conf) failed: No such >>>> file or directory >>> >>> Yeah, I broke this yesterday. Fixed it today.

Let's say one has a SQL table with following fields for John Doe: login: u0007 password: {SHA1}... mailhome: /path/to/joeshome email: john.doe at example.com To log in, for internal policy reasons, John MUST make use of his userid "u0007". So, in the password_query, one would need something like: ... WHERE login = '%u' ... On the other hand, for receiving mail thru

Hello, "doveadm auth user password" may be scripted without a glitch. But this comes with the usual problem of a "ps" command showing the password, which may be especially annoying in case of a single-letter typo: the almost correct password is then visible for about two seconds... Clearing the password argument (zeroing it) in doveadm-auth.c, in the hope to reduce the window

Suspecting a problem with the "virtual" uids/gids, I've tried with a real user for the mail user: # 2.1.14: /_ETC/dovecot/dovecot.conf # OS: Darwin 12.2.1 x86_64 auth_verbose = yes disable_plaintext_auth = no mail_debug = yes mail_gid = dovemailer mail_location = mbox:~/mboxes:INBOX=~/mboxes/inbox mail_uid = dovemailer passdb { args = /_ETC/dovecot/db.conf driver =

Hello, As to be expected with low system limits, a warning may be written to the logs: master: Warning: fd limit (ulimit -n) is lower than required under max. load (256 < 1000), because of default_client_count Shouldn't it read "default_client_limit" instead of "default_client_count"? It seems that the warning is written only when reloading Dovecot, not upon

Hello, Variable %u may be used in dovecot.conf whenever the "full username" is needed. But the expansion of %u returns the username before a possible change performed thru a password or user database lookup (e.g., in the case of a SQL database, thru as "AS user" clause). Is there a variable that would expand to the changed name when used in the configuration file? TIA, Axel

Hello, While experimenting with the sqlite backend, I noticed a big vacuum wrt its use for a quota dict. This is thus an opportunity to share a solution I managed to devise after some trials and errors and a (very quick and unscientific) look at the code. And also the opportunity to ask the community to check for possible flaws. Yes, nothing comes for free... ;-) TIA, Axel This is the SQL

Hello, With this one in Postfix' main.cf: virtual_transport = lmtp:unix:/_ROOT/var/run/dovecot/lmtp and Dovecot settings reproduced at the end of this message, there is no problem for having mail delivered into a user's INBOX. But as soon as I try the security improvement suggested in the docs: service lmtp { user = dovemailer } this is what I get in the logs:

Hello, I'm currently experimenting with the 2.1.x series and am facing a behavior I can't explain; I must be doing something wrong and probably miss the obvious... ;-) This is a very basic build on Mac OS X 10.8.2: ./configure --prefix=/_COD/dovecot-2.1.14 --sysconfdir=/_ETC --localstatedir=/_VAR --with-sqlite --with-ldap=yes (Yes, I know, a strange layout, yet very convenient for

Hello, With the same basic configs as in my previous messages, I tried with the maildir format instead of the mbox format. That is, in both cases ("virtual" uids/gids vs a single "real" uid/gid), doveconf -n shows: mail_location = maildir:~/maildir instead of: mail_location = mbox:~/mboxes:INBOX=~/mboxes/inbox Here too, with "virtual" uids/gids, connections thru

I was going to test 1.1.16 so as to see how it handles global ACLs (in the hope to have a possible comparison with 1.2.0's odd behavior), when I encountered the problem described hereafter. Note that just disabling ACLs is sufficient to get back a fully functional imap binary. So, should there be some plans for a 1.1.17 version, perhaps could the info provided here prove somewhat