similar to: Listen on multiple ports possible using same protocol?

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:

Hi! I've got dovecot 1.0.rc15. I want dovecot to listen only on localhost for imap, and on any interfaces for imaps. So I put the following into my config: protocol imap { listen = 127.0.0.1:143 ssl_listen = *:10993 .. } dovecot -n correctly reports: listen: 127.0.0.1:143 ssl_listen: *:10993 But I can still do a 'telnet MY_HOST 143' from the outside, and 'netstat -pltn |

The docs say: > > *protocol*s = imap *imaps* > *Protocol*s we want to be serving: imap *imaps* pop3 pop3s If you > only want to use dovecot-auth, you can set this to "none". > and..... > > If you want to specify ports for each service, you will need to > configure these settings inside the *protocol* imap/pop3 { ... } > section, so you can specify

Hi, I want to change ports that Dovecot uses to listen for connections. I have listen = [::] in global section and listen = 0.0.0.0:10143 and listen = 0.0.0.0:10110 in protocol imap and protocol pop3 sections. The problem is that it doesn't seem to work for SSL ports of the two protocols and I get following error when I try to start the service: Fatal: listen(993) failed: Address already in

Hi chaps We're using the mbox_snarf plugin to snarf mail from /var/mail/%U to ~%U/Mail/inbox and using dotlocking on all accesses. This is on Solaris with NFS mounted home directories. We're getting a few (very few) of these for just a couple of users: Error: nfs_flush_file_handle_cache_dir: rmdir(/var/mail) failed: Device busy Which, having searched, I see some discussion of in the

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

I'm running Dovecot version 1.2.11 and getting this assertion error on a user's mail: Panic: file /home/durket/dovecot-1.2.11/src/lib-index/mail-transaction-log-view.c: line 290 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq || max_file_seq != view->head->hdr.file_seq || max_file_offset != (uoff_t)-1 || min_file_offset <=

not possible make operation with dovecot version 2.x as was possible in version 1.x: requisites description: connect to dovecot service on IP1 - dovecot must serve users that related to domain1 located in database1 connect to dovecot service on IP2 - dovecot must serve users that related to domain2 located in database2 login must be with username that form not as "user at domain" but

I've been testing my user community's IMAP clients when I try to login and then transfer a big message from the inbox into a folder in an overquota folder directory. I am using native filesystem quotaing in AIXV5.3 with UWIMAP and comparing my results with what I see with Dovecot 1.0.0. (My Dovecot built without any plugins or quota extensions) Everything matches/works except for Mac

Using 1.2.11 I am getting some people repeating that they are getting repeated POP3 e-mails. My configuration is # 1.2.11: /usr/dovecot/etc/dovecot.conf # OS: BSD/OS 4.3 i386 base_dir: /var/run/dovecot/ protocols: pop3 pop3s imap imaps ssl_listen: 204.209.81.1 ssl_cipher_list: ALL:!LOW:!SSLv2 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default):

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, I have dovecot set up with expire-tool to nuke Junk messages greater than 30 days old. On a server with many user accounts, it seems to work on most of them. However, on my user account, expire-tool skips my Junk folder entirely, despite it containing messages from January of this year. Here is the expire-tool --test output: Info: alex at scienceforums.net/Junk: timestamp 1284027481 (Thu

Hello, I'm try to use the convert plugin, but I cannot seem to get it working properly. Is there any setting that I'm missing. -------- dovecot -n # 1.0.10: dovecot.conf log_path: /var/log/dovecot protocols: imap imaps pop3 pop3s listen(default): 127.0.0.1:143 listen(imap): 127.0.0.1:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995

Hello list, I try to get dovecot listen only at localhost. I try listen localhost:993 and it did not work. The installation I made from http://holl.co.at/howto-email/ How it is possible that dovecot with imaps only work on localhost? Thanks for the help. Best regards Dirk

We are running Postfix 2.3.3 and Dovecot 1.0-RC27 on a Solaris 10 server. We use the Dovecot LDA for local delivery. Problems arise with looping mail whenever a user's .forward contains a reference to themselves. This most frequently occurs when a user sets up a vacation since it then puts this in their .forward file: \username, "|/usr/bin/vacation username" The vacation program

I'm seeing this periodically in my logs for a specific user (followed by a backtrace which I've deleted from this post): Panic: file dovecot-1.2.11/src/lib-index/mail-transaction-log-view.c: line 290 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq || max_file_seq != view->head->hdr.file_seq || max_file_offset != (uoff_t)-1 || min_file_offset <=

Hello , Went to /etc/dovecot/dovecot.conf, hunted down "ssl_listen =" which I had set it up to "ssl_listen = required" and commented it out. Tried "service dovecot start" and it started. The USD2,000,000 question being : what does this do (I know , I know, I cannot remember, I documented all this for v1.2.14) and will I need it in the future ? THank you people,

I'm having a problem with Dovecot and forwarding of aliases. Any help would be greatly appreciated. I'm using Postfix, Mysql, dovecot, amavis. mysql> SELECT * FROM alias; | address | goto | domain | created | modified | active | It seems from the logs that incoming mail is being delivered to the mailbox via dovecot. Mail gets to the correct mailbox (address field), however, if I

Hi everyone: when I try to run dovecot after modifying the dovecot.conf file I have the following error messages: Mar 23 09:56:52 mailer dovecot: [ID 583609 mail.info] Dovecot v1.2.10 starting up Mar 23 09:56:52 mailer dovecot: [ID 583609 mail.info] Generating Diffie-Hellman parameters for the first time. This may take a while.. Mar 23 09:56:52 mailer dovecot: [ID 583609 mail.error]

This issue is peripherally related to the following thread Re: [Dovecot] client certs with godaddy ssl cert This is running on CentOS 5.2 with latest Atrpms for Dovecot as of this weekend. # rpm -qa | grep dovecot dovecot-sieve-1.1.5-8.el5 dovecot-1.1.4-0_81.el5 With assistance from Rainer Frey (Inxmail GmbH), I am able to successfully use client ssl certs for imap access on both my Nokia