similar to: Master credentials for sieve

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

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?

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

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

Without having looked into the code: Does Pigeonhole automatically compile a sieve script if the compiled form is not /strictly/ newer than the text form? I'm running into the problem that during automatic installation of a global sieve-after script, my Makefile has a rule to compile, yet afterwards, the sieve plugin complains about not being able to compile (which is correct, but it

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

Is there some simple textual frontend to the ManageSieve protocol somewhat easier to use than gnutls-cli? I.e. something to use like managesieve -u ef putscript myscript < /tmp/myscript Password: managesieve -u ef setactive myscript Password: simply doing the TLS authentication and length computation for me.

I'm trying to integrate both the new sieve implementation and managesieve into pkgsrc. Managesieve seems to need some dovecot libraries that dovecot doesn't install (lib-storage/libstorage.a, lib-auth/libauth.a, lib-imap/libimap.a, lib-index/libindex.a, lib-mail/libmail.a, lib-charset/libcharset.a, lib-dict/libdict.a and lib-charset/libcharset.a). There seems to be no provision in pkgsrc

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

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

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.

With 1.2, is there a syntax to, for LDAP lookups, use a given fixed replacement for a non-present LDAP attribute? E.g. something that would extend user_attrs = mailFileServer=mail=maildir:/import/mail/%$/%d to use maildir:/import/mail/foo/%d in case the mailFileServer attribute is not present?

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

Hi, I'm currently running version v2.0.x in production (using Maildir storage) and it's been working well. I'm interested in moving to version 2.2.x and am preparing a test server to do so. As I have been merging the conf file changes between the two versions I noticed syntax changes for the 90-sieve.conf file. There are now 'locations' and presumably to keep referring to

Thanks Buddy, I got it working. It was giving error when running make 'undefined reference to `request_init' etc' then I ran it with gmake LDFLAGS+=-lwrap and it worked and everything is working fine. Thanks again for your help Thankyou Tahir Riaz Assistant Director (Systems) COMSATS Internet Services COMSATS Headquarters Building 9, Shahrah-e-Jamhuriat, G-5/2 Islamabad.

Hi, As the "new Sieve implementation" is using a "gratefully stolen copy of deliver.c from dovecot" (i.e. a dirty code in mail-raw.c), would it be possible for the Sieve piece 1 - to be using files from dovecot directly rather than copying&changing it (which is very bad for maintenance) 2 - to be incorporated in the hg/mercurial tree of dovecot ? Thanks a lot

I've just written an NUT driver to manage a Masterguard UPS connected via USB, and some questions arose. Why I wrote a new driver? The servers in question only have two serial ports, so I want to use USB. I first wrote the low-level USB routines expecting to integrate them into the existing masterguard driver. However, that driver was so rudimentary I wrote my own one. It can be

I need to connect to a database in a script called using Sieve extprograms plugin. When delivering mail, Sieve is running as the mail recipient user, which means any files, either the sieve script or the extprograms it invokes, are run under that user's permissions. What would be a way to hide the database credentials in a more restricted file? I can think of... * Store the credentials in

Hello all. In my dovecot install we have a default.sieve script which filters incoming mail based on the subdomain of our main domain. All it does is if the mail comes from A.domain.com move in to folder A in inbox, and if it comes from B.domain.com, move to folder B also in inbox. In my personal sieve script, I'd like to grab a particular email each day that the default.sieve saw coming