similar to: protocol configure confusion

Hi, I'm wondering, whether it's possible, to define an ACL on the mailbox itself. We use Dovecot 1.2.15 (included in Debian 6) and maildir filesystem layout: /home/mail01/user1/Maildir/new \ /home/mail01/user1/Maildir/cur Inbox /home/mail01/user1/Maildir/tmp / /home/mail01/user1/Maildir/.folder1/new \ /home/mail01/user1/Maildir/.folder1/cur folder1

Is it possible to have multiple Listen directives in a dovecot configuration file for the same protocol? I am running dovecot-1.2.11 and I want to be able to use the "standard port" as well as a test port: protocol imap { listen = *:143 listen = *:10143 ssl_listen = *:993 ssl_listen = *:10993 for example. Or is this more preferably done by pointing

Thunderbird (2.0) is all of a sudden checking mail server capabilities and keep posting a popup saying: "Mail Server imap.bard.edu is not an IMAP4 mail server". To the best of my knowledge, neither Tbird nor DC have been updated, though the DC imap host was rebooted today 3 hours ago. Any info on what this is about? DC is currently serving out of a special port and in evaluation

Hello, I'm trying to configure the dovecot-antispam plugin. Now I've run into a problem: whenever I try to move/copy a message in/from the spam mailbox, Thunderbird (and also Sylpheed, haven't tried anything else) says: The current command did not succeed. The mail server responded: Failed to read mail beginning. and in the logs I get: dovecot: Aug 07 10:41:23 Error:

Dear Sirs, I need to know how can I automatically move all emails that are considered as SPAM to a specific directory called SPAM. The server has installed Dovecot + Qmail + Vpopmail + Simscan + Spamassassin + ClamAV. dovecot -n # 1.1.16: /usr/local/etc/dovecot.conf # OS: Linux 2.6.9-67.0.15.plus.c4smp i686 CentOS release 4.6 (Final) log_path: /var/log/dovecot.log listen: *:10143 ssl_listen:

Hello Timo, deliver hangs after reloading the Dovecot configuration. How to reproduce: 1. start dovecot 2. deliver a message via deliver 3. modify dovecot.conf:plugin {quota_rule} 4. kill -HUP $PID_of_dovecot 5. deliver the next message via deliver Dovecot v1.2.beta2 died in this case with a panic: file dict-process.c: line 152 (dict_listener_input): assertion failed:

After V1.2 had been up for a while, I started seeing tons of syslog error messages like this: Nov 5 09:11:52 mercury mail:err|error dovecot: IMAP(sdean): stat(/var/dcindx/sdean/.imap/DadEstate) failed: Permission denied (euid=202(sdean) egid=200(hcrc) missing +x perm: /var/dcindx) Ownernship and Permissions are: The index filesystem 2726 root at mercury:/var/dcindx ## ls -ald drwx--S---

Don't know if anyone else uses Berkeley derived filesystem quota, but IBM's AIX does. A little over a week after migrating from UWIMAP to DC (with mbox format unchanged) everything is clean except for this one problem: When users go over quota, when they login the next time, the folder list is blank. You can imagine the panicked calls to the Helpdesk. If their quotas are raised or

In V1.1.15 that I fell back to. Again: # 1.1.15: /usr/local/etc/dovecot.conf # OS: AIX 3 0001378F4C00 listen: *:143 ssl_listen: *:993 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 774 max_mail_processes: 1024 verbose_proctitle: yes first_valid_uid: 200

@2.0's master.conf, there's, e.g., service config { type= config executable =config unix_listener { path = config mode = 0666 } } can someone please explain function/usage for the 'type', 'executable' & 'path' fields? and, for any file paths, are the presumed to be _relative_ to the dovecot executable? in $PATH? can they accept full/absolute

Read what I could find on possible upgrade issues and saw only one that might be a problem. I don't think it will but figured it was worth checking. Anything jump out at the more experienced users? dovecot -n (edited to protect the guilty. ie. me) attached. # 1.1.11: /etc/dovecot.conf # OS: Linux 2.6.22.19-vs2.3.0.34.1 i686 CentOS release 5.2 (Final) log_path:

Hello, I am using the antispam plugin of Dovecot with SpamAssassin and in some cases when users move back mails from the Spam folder to their INBOX (false positive) they get the following error message: [SERVERBUG] failed to send mail Does anyone have an idea what could be the issue here? It is quite annoying as the mail then stays in the Spam folder and can not been re-learnt has ham. Best

Emailed about this with 1.1rc3 and didn't get a reply. Tried upgrading to 1.1rc4 and got the same crashing: Centos 5 (in openvz container) 2.6.18-53.1.4.el5.028stab053.4 #1 SMP Fri Jan 18 12:29:44 MSK 2008 x86_64 x86_64 x86_64 GNU/Linux /usr/local/dovecot/sbin/dovecot -n # 1.1.rc4: /usr/local/dovecot/etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap imaps pop3 pop3s

Hello all, I'm currently doing some tests with Dovecot 2.0 RC1 and OpenBSD4.7 (socppc or i386 architectures) and I can't compile it : I "./configure" with default options and then "make" : $ make [...] Making all in doc Making all in man make: don't know how to make doveadm.1. Stop in /home/mail/dovecot-2.0.rc1/doc/man. *** Error code 1 Stop in

I'm trying to configure dovecot on a SUSE system, and having trouble with the simplest possible authentication scheme: using the standard Linux users and passwords. My configuration is: dovecot -n # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27.45-0.1-pae i686 openSUSE 11.1 (i586) protocols: imap pop3 ssl_listen: * ssl_disable: yes disable_plaintext_auth: no login_dir:

The apostrophes need to be removed from the LimitCORE example, otherwise the parameter will not be recognized: $ cat /etc/systemd/system/dovecot.service.d/service.conf [Service] #Environment='OPTIONS=-p' #LimitCORE=8192 LimitCORE=infinity -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc:

Hello, is possible in some way use on each ip address different certificate (for imap, for pop3). There are options like (but that is not enough for me): protocol imap { listen = *:10143 ssl_listen = *:10943 .. } protocol pop3 { listen = *:10100 .. } I have server for 4 domains (each has own ip address), so i need bind one ip address to one domain to one certificate(each certificate

My production DC machine owns the mail filesystems and is running DC V1.0.15 and mbox folder format. I am looking to test V1.1.3 on another machine, which NFS mounts the mail filesystems, but has its own local index FS. I have made this test environment my default connection in TBird, and it seems to work just fine. Also, I have made sure that my TBird client isn't connecting to the

Hello all, I`ve tried to run dovecot many times in my system (Conectiva Linux 9) and was unable to do so. For some reason it gives this message and quits - never runs. My system: Linux ba.gazetaweb.com 2.4.21-28872cl #1 Sex Mar 21 22:02:49 BRT 2003 i686 unknown I`m migrating from UW-IMAPD to dovecot. I've compiled it from sources, using default configurations. Any help

I tried to apply the X modifier to the %{gid} variable: 'mail_attachment_dir = /srv/mail/.SiS/%X{gid}'. But the name of the created directory is '0', instead of '11172'. Regards, Pascal -- The trapper recommends today: c01dcofe.1134416 at localdomain.org