similar to: Default for non-present LDAP attributes?

I'm somewhat confused regarding Home Directories needed by sieve and setting them for an LDAP userdb. We have system users, passdb ldap, userdb ldap, but home directories are not mounted on the mail server. Now apparently, sieve needs the home directory for .dovecot.lda-dupes. Is there an easier way to give lda/sieve a home directory than setting something along the lines of

I'm getting this Panic with some users on dovecot-1.2.7: Panic: file maildir-uidlist.c: line 1242 (maildir_uidlist_records_drop_expunges): assertion failed: (recs[i]- >uid < rec-> uid) There's another dovecot-1.2.3 running on identical hardware accessing the same NFS mail storage without problems.

I would like deliver to reject certain users. Since supposedly deliver only uses userdb, not passwd, I can't use deny=yes for that. Or does userdb support deny=yes? Yes, I should rather reject them right in the MTA, but that currently takes too long to implement. Or how to reject gast* in postfix using nss authentication?

We are using Postfix as an MTA delivering via Dovecot's LDA (with sieve). We also use Dovecot as a POP/IMAP server. Mail storage is Maildir on NFS, indexes are stored locally. Quotas are FS quotas enforced by the NFS server. The Dovecot version is 1.2.11. Recently, for one user being over quota, some attempts to deliver mail bounced as expected while some others resulted in zero-sized Maildir

Hello there, I have been trying to make the patch work for libwrap(TCP Wrappers) posted on http://dovecot.org/patches <http://dovecot.org/patches%20Patch%20of%201.1> Patch of 1.1 but could not get it work. Any help will be highly appreciated. After compiling and running it I get error "Error: login_tcp_wrappers can't be used because Dovecot wasn't built with

We have two dovecot 1.2 instances sharing Maildirs on NFS. Indexes are local to the individual servers. Occasionally (no idea how to trigger this), the Seen flag gets lost on some messages. I've verified that actually the ``S'' is missing from the filename. I suspect something like server A caching the flags, server B setting Seen, and then server A flushing its cache for another

We have users existing in LDAP but not supposed to receive mail. We used to handle that (somewhat ungracefully) by simply not creating the top mail directory for those accounts. Since switching to Dovecots LDA, these non-existing dirs are considered temporary failures and so the junk mails pile up in postfix' queue Would it be possible for deliver to optionally treat this as a permanent

I'd like to see tcp-wrappers.patch getting integrated into dovecot. I ported the original 1.0 patch to 1.1, but would prefer not to have to maintain another local patch. As the name suggests, the patch adds libwrap support to dovecot. We use is to limit access from outside our network to secure (imaps/pop3s) protocols only and to exclude certain internal addresses from accessing dovecot in

I'm integrating Sieve (the new one) and ManageSieve into wip/dovecot. Currently, this works as dovecot options because dovecot must be built before sieve can be configured and sieve must be built before managesieve can be configured/built. Now, the question arose what the long-term solution (in pkgsrc) should be. To my understanding, with dovecot 2.0, ManageSieve will no longer need to patch

Is there, among the dovocot community, any preferred LDAP schema and attribute to use for setting the home/mail storage location? Some people seem to use the qmail schema, some a Jamm schema (whatever that is), and Markus Effinger has even created a dovecot schema (https://www.effinger.org/blog/2009/01/11/eigenes-ldap-schema-erstellen/). There may be more. I could even create my own given we have

hi all, I encountered some problem with lowercasing chars like an "?" with user_attrs like this: user_attrs = uid=home=/mail/%Lu, =myvar=%L{ldap:uid} the ? doesnt get lower cased in both cases # doveadm user BL?TULA field value user bl?tula uid vmail gid vmail home /mail/bl?tula mail maildir:~/Maildir:LAYOUT=fs:INBOX=~/Maildir/INBOX myvar bl?tula somebody knows if there a fix for

Dear r-bugs, With AIX 5.3 and OBJECT_MODE=64 CC="xlc -q64" CXX="g++ -maix64" and ./configure --without-iconv --enable-R-shlib the following warning occurs: configure: WARNING: tiffio.h: present but cannot be compiled configure: WARNING: tiffio.h: check for missing prerequisite headers?

Hello, I have an issue with dovecot and Ldap? Any help will be grateful? I have dovecot 1.2.15 and i want to know if in that version can i use two values returned from LDAP in the user_attrs template? Thanking you in anticipation? -- " Notificaci?n Autom?tica: Este mensaje y cualquier archivo que se adjunte contiene informaci?n privilegiada y confidencial. Es para uso exclusivo del

Hola! Dovecot should serve virtual mail users. So I've set user_global_uid and user_global_gid in dovecot_ldap.conf to vmail/vmail. Also I've commented auth the user_attrs field. Still Dovecot tries to switch to the uid that is defined in the LDAP entry. It took me some time to figure out, that the only way to prevent this is to set user_attrs = foo=uid,bar=gid or something like this,

Hi Using Dovecot 1.1.2 with LDAP. If i have this: user_attrs = uid=home=/var/vmail/%$,mailuserquota=quota_rule=*:storage=%$,=mail=maildir:/var/vmail/%n/Maildir OK. But if i have this: user_attrs = uid=home=/var/vmail/%$,mailuserquota=quota_rule=*:storage=%$,uid=mail=maildir:/var/vmail/%$/Maildir I get this error: deliver(usuario1): Jul 25 12:59:08 Error: Per-user script path is unknown. See

I would like deliver not to automatically create subfolders for mails addressed to user+some_strange_name at domain.com, but nevertheless automatically create INBOX for new users. I'm not sure whether a new option like -M or -m -m would be appropriate, i.e., whether anyone needs the current -m behaviour. It looks to me like one would need to change mailbox_open_or_create_synced()

I got the following panic on 1.2.3: Panic: file mail-transaction-log-append.c: line 88 (log_buffer_move_to_memory): assertion failed: (file->buffer_offset + file->buffer->used == file->sync_offset) It's probably related to the file system holding the indexes being full.

Is there a way to limit the amount of disc space dovecot will use for its index cache? Other than putting that on a separate partition, I mean. We host our mail data on the file server, however, the index files are located on local discs on each of the mail servers and seem to grow without bounds. We're above 250M now and soon /var will run out of space. Thanks for any help.

In dovecot-example.conf (dovecot version 1.1.1), a comment to dict_db_config mentions an example file doc/dovecot.db.conf the distribution tar doesn't seem to contain. Has this been lost from 1.1 to 1.1.1?

I'm confident that the question has been asked before, but I can't remember the answer. I have -- dovecot 1.1.2 -- Mail storage (maildir format) on NFS -- Quotas on that file system -- A working rquotad -- mail_plugins = quota imap_quota in the protocol imap section -- quota=fs in the plugin section I get (using Apple Mail as a client) -- Notification that the account supports quotas