similar to: "logins with UID ... are not permitted"

hi, For some of our customers we provide a pop3 access, and after an upgrade to alpha3, it is not working anymore. All of our data is ldap based and everything is working as before for our IMAP customers, but our POP3 users fail. Obviously the pop3 login process does not read the data correctly that comes from ldap. after enabling mail_debug, I saw the following error in our log:

hi, I am trying to set up dovecot with digest-md5 as authentication mechanism and openldap as passdb. My problem is ... that I just can't get it working. PLAIN authentication works as expected, but no luck with digest-md5. An excerpt from the two configuration files: dovecot.conf: --------CUT-------- auth = default auth_mechanisms = plain digest-md5 auth_userdb = ldap

Hello, I am developing a Java application that requires me to read from and write to a samba share. When developing in a windows environment this was not a problem. I mounted the share as "M:/", built a path to a file, checked if the file exists using the Java function file.exists(), and went on my merry way. Now I am developing in a Linux environment(SuSE 10). I mount the samba

Hi, is there a chance to alter the list behaviour to not use the sender address of a posting in the reply-to field but dovecot at dovecot.org instead? That way one has to either use "reply to all" in the MUA or manually enter dovecot at dovecot.org in any replies. And a "reply to all" duplicates postings because the posting once goes to the list and once to the original

Hi, does anyone know where Timo is around lately? I haven't seen a post from him for some weeks now and "normally" Timo is quite active when it comes to supporting his 'dovecot' warp drive :-) Udo Rader -- bestsolution.at EDV Systemhaus GmbH http://www.bestsolution.at -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type:

Hi, we have recently been hit by a couple of brute force password attacks against dovecot. So what I want to do now is to add dovecot to fail2ban in order to block further attacks. However, I don't seem to be able to find out password verifification failures for our LDAP based user data. The only thing I see are loads of lines like these in the logfiles: -------CUT------- dovecot: Nov

hi, I'm trying to get this app running under wine http://appdb.winehq.org/appview.php?appId=2002 It is a free Austrian accounting software. So far I have managed to install it and even use it to some degree but I have some strange optical "sideeffects": #1: the menu bar on the right side duplicates, see screenshot here: http://www.bestsolution.at/documents/eufibu_wine01.jpg #2:

hi, I am just playing a bit with the dovecot SASL plugin for postfix and so far my tests have been very successfull, can't wait to get the cyrus-sasl beast replaced. However, I found a potential problem when doing some "illegal" stuff on the postfix side: -------CUT------- cerberus:/var/log# telnet smtptest 25 Trying 192.168.99.99... Connected to smtptest.bestsolution.at. Escape

<pre>I have a machine with the follow specs.<br /><br />Linux hermes.business.com 2.6.11-1.1369_FC4 #1 Thu Jun 2 22:55:56 EDT 2005<br />i686 i686 i386 GNU/Linux<br /><br />pam-0.79-8<br />dovecot-0.99.14-4.fc4<br /><br />No one is able to receive e-mails due to authentication failures and yesterday afternoon<br />they were able to.<br

Hi, we are facing some weird performance issues after we upgraded on of our mail servers to a new Opteron 64bit machine. The problem we are facing is that mail retrieval from external clients is incredibly slow. Fetching a mail with say a size of 3MB takes 7 minutes vs. sending exactly the same mail back to our postmaster account is only a question of seconds. I've verified this with

Once again I have updated Timo's auth patch for Postfix 2.2.1 to work with a 2.3 snapshot. It applied cleanly and compiled and is running for me, but is not really tested. This is Timo's code, not mine. All I did was manually edit in the rejects from the old patch. Find it here if you're interested: http://www.nodns4.us/postfix-2.3-20051121-dovecot-auth.patch.gz md5sum:

Hi, we've been using dovecot for the past 2 years or so for our 3K+ mail accounts and have never regretted our step. Yet from time to time there appear to be, how shall I say, "major" problems in the daemon that of course are no reason to whine and complain about because dovecot is OSS and everybody can do something about it. And that's where I would like to make a suggestion.

Hi, we are just testing postfix 2.3 in combination with its new dovecot SASL plugin. Now what we would like to have was dovecot SASL without acutally running dovecot ... The reason for this is because we have the "real" dovecot running on a different server than the postfix instance and it would be nice if it would not be necessary running an "full" dovecot on that server for

Hi, after setting up a KVM based virtual guest on one of our virtualization servers, we see dovecot die on that virtual guest regularly because of an alleged time shift. The virtual guest is Centos 5.4 based with dovecot 1.2.8 (at first we also tried with the original 1.0.7 (?) dovecot shipped with Centos). I wrote "alleged time shift" because there is no timeshift whatsoever, or

Hi, I've reported this some month ago before (without response), but still I have no clue what is going wrong. Our installation is LDAP based (for virtual hosting) and up to I think alpha2 or 3 everything was working as expected. The trouble I have is that dovecot does not correctly use the information it gets about mailLocation. This is what is stored in the MailMessageStore attribute

I thought I had just about got the old server to the point of being switched off. I have been reading from the dovecot server for a couple of days, and this evening I switched the 'sending' to the new server as well - but I couldn't get anything out. I got: Error while uploading message Could not upload the message dated Wed Feb 1 21:2:56 2006 from Anne Wilson <cannewilson

Hi, I was heaving some grave problems with dovecot's ldap client that left me with the following settings for virtual users: -------CUT------- mbox: data=/virtual/oeush.at/home/f.someone/mail/:INBOX=/var/mail/f.someone.oeush.at -------CUT------- data in that case was correct, yet the INBOX location was wrong, this should have been /virtual/oeush.at/var/mail/f.someone.oeush.at instead. My

I'd previously had dovecot running on a Debian server but recently migrated to Suse. The nice, simple setup for dovecot on debian is not as easy using the dovecot sources. My lack of experience I'm afraid! I'd like to continue to use dovecot, especially as my current maildir directories are all set up ready to be use again. On suse (sles9) I have users authenticating by LDAP. In

Hi! I'm wondering how close Dovecot can be said to be to 1.0 "Final". How stable can the alpha branch be said to be? I was browsing around the Dovecot homepage, but I couldn't find any answer to this question. I hope it hasn't been asked (too many times) before. Fredrik Tolf

Hello, Is it possible to use dovecot version 1.0.rc6 to authenticate users against Active Directory on a Windows 2000, without PAM, Kerberos or SAMBA. Thanks,