similar to: Domain blacklisting

hi everybody having I believe sort of plain-vanilla config with section in 10-tcpwrapper.conf as per docs login_access_sockets = tcpwrap service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user mode = 0600 user = $default_login_user } } /etc/hosts.deny contains: ALL: given_host and yet dovecot logins IMAP client in whereas other tcpwrapper aware

Hello, I'm running dovecot-1.1.8/Maildir/ACL plugin. I sucessfully set up a Maildir shared between users of the unix group 'doveshared' via a public namespace, unix permissions and ACL files. The location of my public namespace is /path/to/public. I tried 2 sub-setups : First setup ---------- drwxrws--- 4 root doveshared 4096 Jan 30 13:39 public -rw-r----- 1 root doveshared

Hello, I'm trying to set up, as explained in the wiki, shared mailboxes with symlink. I'm running dovecot-1.1.8 with LDAP pass/userdb. The Maildir layout goes like this : /courriel/boites/foobar : Maildir of user foobar (nfs) /courriel/meta/foobar : control files of user foobar (nfs) /var/dovecot/indexes : indexes (locally stored) I created : /courriel/boites/doveshared/.box/ :

Hi, I had successfully set up dovecot-1.0-test62 + ldap pass/user db, but now I'm encoutering a SIGSEV problem with a similar set up of a brand new dovecot-1.0-test65 installation. The auth process is killed by a SIGSEV as reported in the error log file : dovecot: Mar 30 17:06:59 Error: child 28291 (auth) killed with signal 11 To be precise, the problem occurs in the

Can anyone share the proper config to get wrappers working in dovecot on FreeBSD? The dovecot examples do not seem to work, and I thought perhaps FBSD needs slightly different configs. I've compiled with: -DHAVE_LIBWRAP which I presume is the first step. The example for dovecot.conf in uncommenting: login_access_sockets = tcpwrap merely causes a log error of "imap-login: Error:

Hello, I'm trying to figure out what exactly (and why) are the consequences of a lost or removal of the dovecot-uidlist file on an IMAP client (Thunderbird for instance). I took for granted that it was that the client would download all messages again since it might be confused by some UID changes. But I don't really see why (on the IMAP protocol level) and I don't know how to

Hi all, I'm still using beta8 (on FreeBSD 5.4-RELEASE). Recently I put a co-worker who's using Thunderbird (1.5.0.4) on it and he seemed to have lost some messages (which were delivered on the spool since seen on procmail logfile). I switched him on another server to play safe and tried to test it myself but failed to reproduce the issue. I myself use mutt on a daily basis with no

Hello Timo, your patch introducing pass_attr_names and user_attr_names fixed the problem of the 'shared' attr_names member of [passdb|userdb]_ldap_conn as I answered in the relative thread. Now I think there is a problem while comparing user-provided and ldap-provided passwords causing a false 'password mismatch' situation, while using PLAIN mechanism with LDAP authentication.

Hello Timo, I just switched from dovecot-1.0.14 to dovecot-1.1.2 and noticed a significant drop in the server load average (which has become lower and above all doesn't seem to have unexplained peaks). Indexes are still locally stored and nfs attribute caching is still off). I searched the list archives for an explanation of what changed in the code that could explain such an improvement but

Hello, let me re-state, hopefully in clearer terms, what I tried to described in a previous thread : With dovecot-1.1.8/Maildir/LDAP pass/userdb (prefetch), I'm trying to set up a Maildir ".box" shared in rw between 2 users in a "Public" namespace. I can't get it to work unless I chmod 777 everything, which obiously is not what I want. 1) am I correct thinking that

Hello Timo, I switched this morning from dovecot-1.2.12 to 2.0.8 with a basic setup (high performance login mode, Maildir, everyhing on NFS, one shared but unused namespace). No problem so far except that some Thunderbird users who wouldn't succeed in moving messages from some one folder to another. They'd get a message about some illegal character in the mailboxname (already existing

Hello Timo, How exactly would translate the "passdb" userdb example which is in the Wiki for SQL auth with LDAP auth, both in dovecot.conf and dovecot-ldap.conf ? -- Thomas Hummel | Institut Pasteur <hummel@pasteur.fr> | P?le informatique - syst?mes et r?seau

Hello Timo, is there a way, either in 1.2.x or in 2.x to activate disable_plaintext_auth=yes only for some address or network ? The idea would be to enable clients from the internal networks to keep making clear text connections while forbidding it to the rest of the world. Thanks. -- Thomas Hummel | Institut Pasteur <hummel at pasteur.fr> | P?le informatique - syst?mes et

Hello, I'm wondering if the following situation is valid (though I think it isn't since I still cannot authenticate with ldap pass/userdb on test67 running on FreeBSD-5.3). Is it normal that the passdb_ldap_conn->attr_names second element (for instance) "turns to" "homeDirectory" as the following step by step gdb run sample shows ? : -- Breakpoint 1,

It works ! It was THAT easy ! Can you suggest how to replace the hair I pulled out ? :-) On 2016-12-29 5:27 PM, Larry Rosenman wrote: > login_access_sockets = tcpwrap > > service tcpwrap { > unix_listener login/tcpwrap { > group = $default_login_user > mode = 0600 > user = $default_login_user > } > } > > > > On Thu, Dec 29, 2016 at

Hello Timo, With dovecot-2.0.8/Maildir, in a simple shared mailboxes setting I noticed the following : - user "doveimap" has 2 mailboxes : "Common" and "Private" - he shares only the "Common" mailbox to user "dovepop" doing : x setacl "Common" dovepop lrwstipekxacd x OK Setacl complete. - he subscribed to both x lsub

Hello, I was asking what was the motivation for not having the envelope From in the Maildir format, as defined in the qmail spec : "The message is delivered without an extra UUCP- style From_ line, without any >From quoting, and without an extra blank line at the end." which may sound silly since we lose an important piece of information. Same question about the motivation in

Hello Timo, I'm running dovecot-1.2.11/Maildir and plan to migrate to single UID mailboxes some day, but for now, I've got "system" users and I'm testing permissions handling in order to set up shared mailboxes. The private namespace mailboxes location is location = maildir:/courriel/boites/%u:CONTROL=/courriel/meta/%u:INDEX=/var/dovecot-test/indexes/%1u/%u I've

I have compiled dovecot2 for FreeBSD with the tcpwrap option. A tcpwrap binary gets built and resides in the FreeBSD directory /usr/local/libexec/dovecot an examination of the compiled options (using the FreeBSD pkg install dovecot2) confirms: LIBWRAP : on yet, when I adjust dovecot.conf with: login_access_sockets = tcpwrap I get the following logged error message: 20161229 17:02:49

Hello Timo, I'm trying to get a clear understanding of dovecot's (1.2.x) flags and keywords sharing possibilities or impossibilities in a shared-mailboxes setup. By definition, a shared mailbox is a mailbox from a personal namespace which has been made available to someone else who sees it in a shared namespace. There can be some combinatorics according to the fact that INDEX and