similar to: Dovecot pop3s problem : can't see email

I've installed dovecot 1:1.1.11-0ubuntu4.1 on my jaunty system. Access from the same host works well, but when I access remotely (from various MUAs and networks) I get *very* frequent disconnects. Authentication is fine, and I can usually open a mail folder, but larger operations such as copying 20 messages into an imap folder always get disconnected. I can reconnect, but I often get

Hi, I'm trying to setup a new mail server where postfix 2.3-20060405 would use Dovecot's SASL and users located in LDAP. It's with dovecot-1.0-beta5. On the postfix side, I followed the SASL_README and have the following in main.cf: smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes On the dovecot side I have the following related to auth:

Now most things seem to work (rc12 on Mandriva 2007.0), I've been looking more thoroughly at the syslog file. I see a 'syscall failed' at the end of a normal timed poll from the client. I wonder what it means. Sorry for the layout, it is messed up by the cut and paste. I have created the selfsigned cert and key in the /etc/ssl/dovecot/[certs,private] directories. Egbert Jan Nov 8

I can consistently reproduce a crash in dovecot: Select 20 or more messages and copy them to a test folder. Go into that test folder and SHIFT-DEL the messages rapidly (holding down SHIFT-DEL works best) Just rapidly DELing them (even holding down DEL) doesn't do it (unless it's the Trash folder) I'm using the following namespace (in case that's relevant) namespace private {

I've run this test on every permutation of poll and notify: can NOT reproduce the crash: --with-ioloop=select --with-notify=none --with-ioloop=select --with-notify=dnotify --with-ioloop=select --with-notify=inotify --with-ioloop=poll --with-notify=none --with-ioloop=poll --with-notify=dnotify --with-ioloop=poll --with-notify=inotify CAN reproduce the crash: --with-ioloop=epoll

Hello, having difficulty setting up a 'secure-only' service on a non-standard port. Objective is to open a secure Dovecot service on an internet-visible port, while also using an insecure service for hosts on an internal network (so that one particular client which is not SSL/TLS-capable can continue to use the service). Checking wiki1 and wiki2, I think that port 143 can be used for a

Hi list Im currently run debian sarge / testing. I upgraded my dovecot this morning on my mail server this morning, and my dovecot stopped working for my mail users email clients. I told debconf to replace the dovecot.conf (Baring in mind I saved my conf file). The output I was getting was as so: ====================================================================== Aug 11 10:09:56 mail dovecot:

Hi guys Im viewing how to repair a problem using a postfix platform with openldap and dovecot. This is the problem: -When I create a new user inside openldap with mail account appears correctly inside ldap but when I access first time appears inside /var/spool/dovecot/ the folder of account bad. Not appears the name of uid, appears the name of user mail, for ex: drwx------ 5 exemple

Hi, first of all, it is very nice that dovecot has quotas now! Thank you very much. Now, I want to use quotas with LDAP requests, but I am having the following issues. First, contrary to what is written in the Wiki about quota and LDAP ("# quotaStorage must be in the format mentioned above, # For example: dirsize:storage=10240"), it is possible to have an LDAP field with just a

Hi List, I'm setting up a new Dovecot server and am having some issues getting Dovecot to see the mailbox correctly. I already have several mailboxes (From another Dovecot server) but my new install does not see them. I'm running Ubuntu 6.06 w/ Dovecot 1.0.beta3. When I try to login, I get the following in the log. Sep 23 15:11:55 nibiru dovecot: auth(default): client out: CONT^I1^I Sep

Vielen Dank f?r Ihre Email! Ich bin heute leider nicht im B?ro, erhalte Ihre Email aber trotzdem. In dringenden F?llen k?nnen Sie mich auch per Handy erreichen: 0177-7372923. Mit freundlichen Gr??en aus Sarstedt Hauke Hagedorn -- Hagedorn Internet- & Veranstaltungsdienstleistungen Wenderter Str. 37d 31157 Sarstedt Ust-Id DE 256037115 Tel: +49 5066 917 339 1 Fax: +49 5066 917 339 9

I see the following history in my log during message delivery: Mar 1 13:35:09 mailserver postfix/pickup[21464]: 5FAFC2A002: uid=0 from=<root> Mar 1 13:35:09 mailserver postfix/cleanup[21526]: 5FAFC2A002: message-id=<20090301213509.5FAFC2A002 at mailserver.amfeslan.local> Mar 1 13:35:09 mailserver postfix/qmgr[21429]: 5FAFC2A002: from=<root at mailserver.amfeslan.local>,

a "masteruser" login fails: Oct 8 15:12:54 postamt dovecot: auth: Debug: auth(masteruser,141.42.206.38,master): Master user lookup for login: nonworkinguser Oct 8 15:12:54 postamt dovecot: auth: passdb(masteruser,141.42.206.38,master): Master user logging in as nonworkinguser Oct 8 15:12:54 postamt dovecot: auth: Debug: cache(nonworkinguser,141.42.206.38): expired Oct 8 15:12:54

Hi list, I have 7 virtual users in a sql database. I don't want any systemusers or local delivery using postfix. On the postfix side everything works fine as long as I use the 'local' delivery agent. But since I want to use dovecot's sieve functionality I set local_transport to dovecot. From now on Postfix seems to ignore local_* settings like local_recipient_maps. Here is my

Hello... I have dovecot 1.0.10 running with users in an LDAP database. Things are working as they should with IMAP. However, I can't seem to make deliver w. postfix work they way I want. My problems are: Mail to users who do not exist in LDAP or locally are accepted and mailfolders are created. I want mail to users that do not exist in LDAP or locally to be rejected. Mail is delivered

Hello, it seems that there is some bug in authentication cache code in dovecot version 1.1.alpha4 - after login attempt with wrong password the correct password also will fail. I can reproduce it very easy: $telnet 10.10.10.30 110 +OK Server. <861.2.46e6c679.jZ8QYpFmU8ZN6XIq7zPhkw==@server2> user testuser +OK pass pass +OK Logged in. quit +OK Logging out. Connection closed by foreign host.

Our setup is ok with Postfix / Dovecot. I just need to add dovecot LDA. I use the 1.0beta9 LDA Configuration: protocol lda { postmaster_address = postmaster@clm.net4all.ch #hostname = #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/imap #sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot/auth-master } auth default-socket { mechanisms = plain login passdb

Dear all: There seems to be a problem with scoping, for irf() in vars, when called within a function. Try the following: ----------------------- testfun <- function(lags){ data(Canada) var.2c <- VAR(Canada, p = lags, type = "const") print(var.2c) } testfun(lags=3) ## Everything OK. Now this: testfun2 <- function(lags){ data(Canada) var.2c <- VAR(Canada, p = lags, type =

Hey, I'm using SAMBA 2.0.9 and only on very large file transfers (500 MB or more) to or from the SAMBA share after I logout and log back in I'll get this error message,"Microsoft Windows Network: The local device name is already in use." If I wait just a couple of minutes the connection will be made and everything is fine including access to the share once again. SAMBA 2.0.9

Hi, I keep having errors when I try to authenticate to my imap acount, and I can't get my email like this. Here are the logs when i try to authenticate using PLAIN or CRAM-MD5 : PLAIN Dec 24 22:06:25 domain dovecot: auth(default2): client in: AUTH^I1^IPLAIN^Iservice=IMAP^Isecured^Ilip=1.2.3.4^Irip=1.2.3.4^Iresp=<hidden> Dec 24 22:06:27 domain dovecot: auth(default2): pam(email at