similar to: IMAP over SSL

On 15/04/2019 13:43, Larry Rosenman via dovecot wrote: > Again, this doesn't help with doveadm?running as the local user, and > also doesn't help with > the PAM authentication. > > passdb { > ? driver = pam > ? #[session=yes] [setcred=yes] [failure_show_msg=yes] [max_requests=20] > ? #[cache_key=<key>] [<service name>] > ? args = failure_show_msg=yes

I'm having an issue I can't seem to work around after upgrading from Dovecot 1.0.7 to 1.2.17. After getting Dovecot 1.07 working on CentOS 5.9, I decided that it might be wise to upgrade to a later version, so I stuck with 1.x and went with 1.2.17, which I had to compile from source. CentOS was originally using /etc as the starting path for Dovecot files but the source distribution puts

I have normal system users, some and some virtual domains (2 different flavors). I have this job that runs from cron on my own userid to archive mail I want Dovecot to use my system password for mail authentication. I, therefore, use PAM to authenticate system users Everything works great, modulo getting the auto-index to be visible using RoundCube (which if I log into roundcube using

Again, this doesn't help with doveadm running as the local user, and also doesn't help with the PAM authentication. passdb { driver = pam #[session=yes] [setcred=yes] [failure_show_msg=yes] [max_requests=20] #[cache_key=<key>] [<service name>] args = failure_show_msg=yes session=yes max_requests=20 skip = authenticated } How can I default the domain for PAM

Dear All, Is it possible to make any authorization (eg. checking of group membership) in case of GSSAPI authentication? Our dovecot authenticates the users against PAM and GSSAPI. In the PAM file I'm able to check if a user is a member of a selected (e.g mailreader) group. If the user is member, he can login otherwise not (see below). If the user has a valid Kerberos ticket and he

>> how to disable throttling (or better - put other limits) for 127.0.0.1? > > https://wiki2.dovecot.org/Upgrading/2.3 - look for "Localhost Auth Penalty" > that's certainly this. but i am not an expert in this passdb system my current config is passdb { driver=passwd-file args= username_format=%Lu /usr/local/etc/dovecot/aliasy } passdb { driver = pam #

Dear All, We are having a very similar issue with dovecot 2.2.34 as ?kos. We want our users to authenticate via GSSAPI over Kerberos using their TGT. Our setup is two distinct locations with their own dovecot's with access to these being handled via LDAP auth mechanism with filters to check for their group memberships, i.e. users from location A are in group A and users from location B

Hi Aki, I also tried with changing the original ldap source to svr2. Although everywhere svr2 is configured, still mails keep being delivered locally on svr1. Do I need to configure more than 20-lmtp.conf? [@svr1 conf.d]# cat 20-lmtp.conf | grep -v '^#' lmtp_proxy = yes protocol lmtp { # Space separated list of plugins to load (default is global mail_plugins). mail_plugins

Thanks very much; please see in-line for clarification questions. At 8:22 AM +0100 11/28/14, Steffen Kaiser wrote: > On Thu, 27 Nov 2014, Randall Gellens wrote: > >> I'm still having trouble getting users accepted by postfix + dovecot. > > I suppose in your system + virtual user mix, you should use LMTP: > http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP > So

Some preamble information? OS X 10.4.10 (all updates) Power Mac Dual G5, 2.0 Postfix with Dovecot SASL, Dovecot LDA, Dovecot imaps (openssl) Mail clients Apple Mail v 2.1 SquirrelMail v 1.4.10a Thunderbird v 2.0.0.6 Mulberry v 4.06 For various versions of Dovecot, from 0.9m up through 1.0.3 things went well, no memorable big problems, with one exception: Mulberry v 4.0.8 would/will not

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,

Good evening! Dear list I have problem with quota-fs (rquota) support with dovecot. I use dovecot version: dovecot --version 2.3.7.1 (0152c8b10) build options: dovecot --build-options Build options: ioloop=epoll notify=inotify openssl io_block_size=8192 SQL driver plugins: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap(plugin)

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 am staring constantly at the same logs, this is what I get from dovecot[1]. Sendmail[2] is sending with test at svr1 maybe this overrides lmtp proxying? This is a test with a special-userdb passwd-file also having host=svr2 [1] Dec 16 16:30:16 svr1 dovecot: lmtp(16466): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= Dec 16 16:30:16 svr1 dovecot: lmtp(16466): Connect from

Hi, I'm trying to config dovecot to enable IMAP protocol only for certain IPs and users. The logical steps I've followed are: 1. If a user is trying to login from an IP that I've authorized ( listed in a file) the request is authorized. 2. If not, if the user is listed in a second file the request is authorized. 3. If also this check fails the request is rejected. I'm using PAM

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 All, I am struggling for 2 weeks solving authentication problem in dovecot. logs from /etc/mail/maillog Oct 15 18:00:35 localhost dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Oct 15 18:00:35 localhost dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so Oct 15 18:00:35 localhost dovecot: auth: Debug: Module loaded:

Hi Aki, If I adapt this configuration on svr1 like this[0], should the mail not be delivered at svr2 passdb { driver = pam # [session=yes] [setcred=yes] [failure_show_msg=yes] [max_requests=<n>] # [cache_key=<key>] [<service name>] #args = dovecot default_fields = proxy=y host=svr2 } passdb { driver = passwd skip = authenticated default_fields = proxy=y

Hello, I use dovecot 1.2.15 as an IMAP backend for Horde webmail. When I enable PLAIN and GSSAPI as authentication mecanisms, it makes Horde very slow. If I enable only PLAIN it is a lot more fast. Do you have a clue to solve this issue ? Here is my dovecot.conf : protocols = imap imaps pop3s managesieve mail_location = maildir:/ext/spool/imap/%1Mu/%u first_valid_uid=97 last_valid_uid=97

Hi, Just writing here my note about auth_default_realm, pam_krb5 and gssapi. It seems that 'pam' passdb and 'gssapi' auth_mechanism doesn't honor 'auth_default_realm' setting, at least in several setups I deal with. Here is a part of the config: passdb { args = max_requests=100 cache_key=%u%r dovecot driver = pam } auth_default_realm = REALM.COM