similar to: APOP

Hi Folks, I'm fairly new to linux so this message may reflect that. dovecot info (running on CentOS 5.0): protocols: pop3s listen: ssl_cert_file: /etc/pki/dovecot/certs/dovecot.pem ssl_key_file: /etc/pki/dovecot/private/dovecot.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_executable:

Hello all, this patch add APOP authentication mechanism to dovecot 1.0-test23. Please take a look. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke at donpac.ru | PGP key: wwwkeys.pgp.net -------------- next part -------------- diff -udrpN -X /usr/share/dontdiff -x Makefile dovecot-1.0-test23.vanilla/src/auth/Makefile.am dovecot-1.0-test23/src/auth/Makefile.am ---

Hi, all! I configured Dovecot to use many protocols. To do this, I wrote: mechanisms = plain digest-md5 cram-md5 apop ntlm Very strange, if I ask the capability, I get: CAPA TOP UIDL RESP-CODES PIPELINING STLS USER SASL PLAIN DIGEST-MD5 CRAM-MD5 NTLM . I can't understand why APOP is not written (but I can use it!) and why I can see SASL, that I didn't configure... How can I change

Hi, We're running dovecot 1.2.15 and use SQL authentication. We'd like to be able to support APOP, but can't see how this would fit in with SQL auth. Currently we have: password_query = SELECT email as user, password FROM virtual_users WHERE email='%u' or (email LIKE '%n@%%' AND unhashed='%w') It seems that in order to auth APOP logins, we'd need to

Timo, It looks like Dovecot 2.0 appends an APOP challenge to the POP3 greeting even if APOP is not an enabled auth mechanism. Is there any way to disable this? We don't support APOP, and the challenge includes the private hostname of the server, which we'd rather not have in the banner. It looks like get_apop_challenge in 1.2 returns NULL if APOP isn't supported, which causes

Dear all, Hi. This is imacat from Taiwan. I'm new to this list. I was migrating from Qpopper to Dovecot. (Qpopper copies the mailbox when POP3 logged in, which causes quota problem.) Generally Dovecot is nice. However, I have a few questions: 1. I have a few virtual users, and I'm not using IMAP. Do I still have to give them a writable home directory? I mean, they

How does one go about generating a local password database for apop authentication? Or can it simply run against /etc/passwd, using a PAM entry? (I forgot to append this to my last message... sorry...). Thanks much. -=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner & Head Hardware Heavy, Blue Feather Technologies -- http://www.bluefeathertech.com kyrrin (at) bluefeathertech do/t c=o=m "If

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm very happy with Dovecot and wish the best for its continued development. It's a true testament to brilliant componentised design and Unix philosophy. Configuration made easy because of the way the file is parsed and a single point of startup make it ridiculously straightforward (and lovely) to administer. But of course, we all

Hello, i know its a little bit Offtopic, but i know many Mailadmins are reading here ;) Does anybody know howto autoconfigure Mac Mail als ISP Provider. We have troubles with the default Settings of Mac Mail (POP3s with APOP) and want to change them via autodiscover. Is there something simular to Thunderbirds Config Site: https://developer.mozilla.org/en/Thunderbird/Autoconfiguration google

Fellow Dovecot'ers, I've -almost- got Dovecot completely functional, and I will add that it works just fine for non-authenticated POP3. The problem begins when I try to use authentication for same against the system's /etc/passwd section. This is the error message that comes up in /var/log/maillog Jul 9 21:14:10 featherweb dovecot: auth(default): pam(kyrrin at

I am using Dovecot to provide IMAP and IMAP+SSL service for my users, but am still using QPopper for POP3 service, wrapped with stunnel for POP3+SSL. I am hesitant to get rid of QPopper because it supports APOP, which encrypts authentication data (both where it is stored, and when it is transmitted), and because APOP passwords can be managed by the users themselves, via the popauth tool that they

I have been running Dovecot 1.2.5 since Sept 14. Beginning at about 03:28 on Sept 21 for no apparent (to me) reason and continuing through the present, I am seeing log messages like the following and am experiencing delays logging in. Sep 22 19:07:15 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal:

Fellow Dovecot'ers. I tried something tonight that I should have done a while back: Turned on verbose logging in the authentication section. I'm still unable to get the mail client I'm experimenting with (Pegasus) to complete a pop3s connection, in that I still get an indication of a failed password. However, at least I'm a little closer to understanding the failure itself.

Sigh, In the interest of moving forward on this project I've given up trying to get Dovecot to support mailboxes, rather I've tweaked around in qmail and had it deliver into a mail directory on a disk, that isn't NFS mounted. That got me past the various locking complaints and "operation not supported" on home directories that were mounted from the NetApp filer. Going as

On 2018-06-12 15:18, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 12 Jun 2018, Walter Ulmke wrote: > >> Date: Tue, 12 Jun 2018 14:23:30 +0200 >> From: Walter Ulmke <ulw at ulmke.com> >> To: dovecot at dovecot.org >> Subject: Re: cant login to Dovecot >> >> On 2018-06-12 13:14, Steffen Kaiser wrote:

Hi, I just upgraded to from dovecot v1.1.15 to v1.2.9 so I can use dovecot- sieve. Most everything seems to work but my webmail (roundcube) clients are not seeing their subscribed folders. Reading over the upgrade docs at http://wiki.dovecot.org/Upgrading/1.2 I'm wondering if I have the two settings below configured correctly. dovecot.conf: mail_location =

On 2018-06-12 13:14, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 12 Jun 2018, Walter Ulmke wrote: > >> un 12 12:30:06 ulmke2 dovecot[5814]: auth: Fatal: APOP mechanism can't >> be supported with given passdbs > > Config error. > > "Fatal" sounds fatal ;-) > >> stats: open(old-stats-user)

Fellow dovecot'ers, I'm just getting started with Dovecot, and I'm not a programmer, so please be gentle. ;-) THE PLATFORM: NetBSD 3.0/SPARC, Postfix 2.3-RC8, current Dovecot RC (I forgot the number). Maildir-type directories. THE GOAL: To accommodate authenticated (remote) POP3 users with APOP or SSL/TLS, and allow users on the internal network (192.168.x.x) to just use basic

Hi all, I can't login. This is a dovecot server for a small inhouse network, and I doon't use any encryption, and just want to login using the standard Linux login dovecot status gives me the following error messages: un 12 12:30:06 ulmke2 dovecot[5814]: auth: Fatal: APOP mechanism can't be supported with given passdbs Jun 12 12:30:06 ulmke2 dovecot[5811]: master: Error:

Hi, I'm looking for a solution to access pop mails (sendmail in linux) securely. Most of the access would be from window clients (outlook express etc). Is there a way to encrypt the password (like ssh2) when authenticating with sendmail? Any info is greatly appereceiated. Thx. Regards, Wong.