similar to: still strugling

Timo, I nervously ran rc6 plus the patch: http://dovecot.org/tmp/ssl-proxy-openssl.c on my Solaris 9 box, in production, this morning. My dovecot.conf file is attached. Like similar reports for BSD, rc6 fell over after an hour and a half. The final syslog message was: dovecot: [ID 920869 mail.error] Login process died too early - shutting down I rolled back to rc2 for production. BTW,

Hello people!! First, thanks very much to Ejay Hire and to John Peacock for your quickly answer!! Now, I've dovecot installed, I downloaded the source and I compiled them. It's running ok now. But.....as I am new in all these issues I have some problems with the configuration. I have a user called "webmaster" that have a mail into /var/spool/mail, I want to redirect these

I'm trying to set up a pop3 server for a project for class, but it keeps giving me the following error: Error: Login user doesn't exist: dovecot Fatal: Invalid configuration in /usr/local/etc/dovecot.conf And I have no clue what's wrong. I've look and modifying the dovecot.conffile for days and I am not having any luck. ## Dovecot configuration file # If you're in a

Hi, I'm trying to get dovecot set up better. I am using 1.0alpha3. It takes a long long time to move messages for some reason. It seems it may be a timeout thing, because neither the client or server is using any cpu time or disk i/o or network to speak of. (To move maybe 400 messages, it seems to take maybe half an hour, maybe longer.) With alpha 2 I was getting messages from

Trying to figure out how to convert an existing mbox system to maildir Below is my dovecot.conf file. Tried adding this at the bottom of the file and nothing happens. plugin { convert_mail = mbox:/vhome/%d/home/%n:INBOX=/vhome/%d/home/%n/INBOX convert_skip_broken_mailboxes=yes } What am I doing wrong? ## Dovecot 1.0 configuration file # '#' character and everything after it is

I having a hard time working this out, I've looked in the wiki and various other places but am still cueless (stupid me) mercury:/etc/dovecot# imtest -a graeme 203.96.154.204 S: * OK dovecot ready. C: C01 CAPABILITY S: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN S: C01 OK Capability

Hi folks. New to both dovecot and openldap. Trying to set up virtual domains using the wanderingbarque howto: http://www.wanderingbarque.com/mailserver.html Platform is RH enterprise 3. Only difference is I'm trying to use phamm instead of jamm: http://phamm.rhx.it/ dovecot doesn't seem to want to play nice with my openldap; everything else (postfix, etc) seems to work alright.

Timo, I got bit last night during my upgrade to beta1 by uncommenting the following part of dovecot.conf for my site: #passdb passwd-file { # File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} I did a "s/#//" over this block of code, thereby uncommenting the comment too. Then I wondered why beta1 wouldn't start for me,

hi there... i HAVE practically searched in ALL messages from 2004 year, and haven't any luck with this problem, so I'm inserting here "dovecot.conf" content: ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based

Hey, I am setting up Dovecot on Debian with Postfix. I am telling Dovecot to use maildir:~/Maildir but it persists in dumping mail in mbox format in /var/mail/username. Can anyone suggest ideas? My config file is attached. Thanks Kevin -------------- next part -------------- ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment #

I'm running Dovecot dovecot-1.0.r13 on FreeBSD (FreeBSD 6.1-RELEASE- p10). Mail is stored in mbox format (dovecot.conf after the msg). Procmail delivers mail to subfolders under ~/.mail, locking using dotfiles. One folder in particular for one user has an mbox file ~/.mail/Cron. Quite often, I'll see that procmail processes are stacking up because ~/.mail/Cron.lock exists, and

Hi, I am running dovecot 0.99.10.4 on SuSE 9. I installed it using apt-get from the gwdg repository. The dovecot service is configured to start at boottime in run level 3 and 5. However, it dies immediately with this error (/var/log/mail.err): dovecot: Login process died too early - shutting down Starting the service afterwords from a prompt as root with the command: /etc/init.d/dovecot

Hi folks, I've updated my dovecot 0.99.14 with the last package (0.99.14-1sarge0), but it doesn't work. I've found that problem: http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/80872 then I've removed that, and reinstalled first package (from /var/cache/apt/archives), and NOW it doesnt' work too :( When I start the daemon, I see in my logs: dovecot: May 31

I have a really weird problem. To whit: I compiled dovecot 0.99.10 on two different systems: a linux-ppc box running Debian, and a Mac OS X Server v. 10.2.8. It compiled fine on both. The same Maildir's are being served up on both -- the OS X server exports home directories to the clients via NFS. BUT the OS X box orders mailboxes this way: INBOX Deleted Items Sent Items . . . And the

In our environment home directories are auto-mounted via /home/<user> including on the server provided mail. Within the various mail services though we try to isolate and override with local /mail/home/<user> Works well except that dovecot still wants to cd to the real home triggering a useless and potentially hindering automount when it invokes the imap or pop3 process specified by

Hi, Sometimes a script kiddie tries to guess passwords on our mailserver (Ubuntu 10.04.2 LTS, postfix, dovecot 1.2.9, scanners, the standard stuff). That leads to a nagios message about the high number of processes. The number goes above 500. Nagios threshold is set to 250, which is more than enough for normal operation of this server. When are these processes supposed to die again? They seem to

Hi List, last time i did a lot of packaging and installing different versions of dovecot 1.0.x (rc not included ;) )and all was fine. Now a have a little problem. In this case it was an update from 1.0.13 to 1.1.1 Sometime it happens that 1 user out of x (more than 100) got this standardmessage for ~1 or ~2 thousend times in his mailbox (mbox) for example: >From MAILER_DAEMON Mon Sep 18

Dovecot users list, I started having problems with Outlook not syncing with Dovecot a public imap folder upon issuing a send/receive in the client; eventually Outlook timed out, and I received the following error in the Dovecot log. Jan 23 09:20:23 imap(user at mydom.com): Error: FETCH [] for mailbox projects.myfolder UID 120 got too little data: 7744 vs 7759 Jan 23 09:20:23 imap(user at

HI I use dovecot-1.0.r17 on FreeBSD scat.setcom 6.2-RELEASE. Recently authentification stop working. May 10 02:56:02 scat dovecot: auth(default): passwd(test,127.0.0.1): unknown user May 10 02:56:02 scat dovecot: auth(default): client out: OK 1 user=test User= &:/home/test:/tmp/email/bin/nonexistance= May 10 02:56:02 scat dovecot: auth(default): master in: REQUEST 23 43856 1

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