similar to: Getting more out of the %w variable.

This is probably a misconfiguration of my MUA; however, I thought I would ask here first. I am using IMAP with Dovecot. Claws-mail is my MUA. Now, when fetching mail via port 143, everything works fine: Mar 29 10:33:00 imap-login: Info: Login: user=<user at domain.net>, method=CRAM-MD5, rip=127.0.0.1, lip=127.0.0.1, TLS However, when I attempt to fetch mail via port 993, I get this

Hi, Seem i switch my dovecot authentification to cram-md5 mecanism, i'am unable to authenticate to managesieve login. log: Dec 16 23:50:16 managesieve-login: Info: Disconnected (disconnected while authenticating): method=CRAM-MD5, rip=192.168.0.100, lip=192.168.0.50 dovecot -n : # 1.2.8: /etc/mailapp/dovecot/dovecot.conf # OS: Linux 2.6.22.8 x86_64 log_path: /var/log/dovecot.log

Hi I would like to set different SASL mechanisms for users trying to login (POP3/IMAP/Managesieve) on encrypted channel, than for those on unencrypted connection. Specificaly: For users on unencrypted channel, i need to allow login with CRAM-MD5 (to improve security - I have users who require unencrypted connection but i cant let tem use PLAIN login, of course). But for users on

I have enabled SSL support for my dovecot installation but if I enable secure authentication in my MUA, I get an error from dovecot telling me that this is not supported.. Is this because dovecot does not support this or am I missing some config? Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bj?rn T Johansen btj at havleik.no

Hi Friends! An opinion. I would like to facilitate the configuration of one's mail client (desktop or mobile) to my users server. Some time ago I asked the same question and you suggested me to use "Automx". So I started of good will and I looked for the Automx documentation. And here the problems started as I found several inconsistencies, even parameters (in official

Timo, we want to implement SPECIAL-USE in Thunderbird (TB), but we've run into problems. I believe you could help change that. Here's the problem: By default TB only lists subscribed (LSUB) folders when it accesses an IMAP server. However when I do a LSUB on recent Dovecot 2.1 code from mercurial I don't get to see the SPECIAL-USE flags. Therefore TB fails to identify which folders

Hello, I'm using version 2.3.4.1 and I have a fairly simple setup based on a submission server where I run dovecot and a relay server with postfix. The relevant part of dovecot's config is as follows (sanitized): hostname = submission.domain.local submission_client_workarounds = whitespace-before-path submission_relay_host = 192.168.1.1 <- postfix submission_relay_port = 25

I'm wondering what I'd need to do to get the "important" flag set on an incoming message according to a pre-specified header. I know the problem of this not being a "joined-up" feature in standard email, but in practice many MUAs set headers like X-priority etc, and IMAP has an "important" flag that is the obvious mapping. I'm not really sure where

On Mon, Nov 02, 2020 at 09:33:08PM +0100, R. Diez wrote: > OK, so I gather that the Submission Server cannot do that (yet). And probably would never do. It isn't its job description. Actually, it is just a convenience/workaround feature, which comes handy only if your own MTA cannot handle dovecot's SASL authentication (must be something real strange) or there are some

HI folks, I've an up-to-date CentOS 5.x box on a small intranet (<20 users). We did a reboot over the weekend and all appears well except that clients on the LAN can no longer send email. Just hangs/times out. No clear identifiers in the /var/log/maillog or /var/log/messages. We're not setup for ESMTP as it's a closed network and I'm really hoping for a kickstart as to

I know how to ENABLE CRAM-MD5, but getting it to actually work? <http://wiki2.dovecot.org/HowTo/CRAM-MD5> It looks like I have to 1) manually create a CRAM-MD5 data file and, I suppose, 2) manually manage the file? Given I do not know user's passwords, this might be tricky. Currently I have users authenticate against MySQL (virtual users) or pam (local users). Or do i just ignore it

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have a configuration problem, that I ignored till now. Many MUAs tag SPAM themselves and move SPAM to a junk folder (Thunderbird uses "Junk"). It is said to not automatically train these mails, but let have an human revise them. Currently, I have configured those folders as "trash" folders for antispam, which means

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I'm migrating from ?old skool? solution with one mail client (MUA) on one computer, which retrieves mail via POP3, sorts it and manages it locally to installation when there are several MUAs on different devices, accessing mail via IMAP4, and all sorting and management should be server-side. Sorting is ?easy?: sieve. Here are some nuisance

I'm getting imap-login: Internal login failure: bob whenever I try to check mail. I'm new to mail server setup, new to IMAP, and I don't know a heck of a lot about authentication schemes. I've set up Dovecot as an IMAP server on FreeBSD 4.8. I've got OpenLDAP running on the same system. Users will access mail via Eudora on Windows and Macs, so that's how I'm

Hello all. Sorry for a lot of question - im making a new mail system now. Im wondering how to auth different MUA. For example Thunderbird & The Bat 4.x - CRAM-MD5 MS Outlook 2007 - DIGEST-MD5 Im create a 3 users and store passwords in LDAP using MD5-CRYPT(1), CRYPT(2) and MD5(3) - for tests. If im not use "secure connection" in thunderbird - im auth fine(plain text over SSL)

When I used backup copy of the dovecot.conf file I have this same error. So I think that maybe something was written to database? I really would point out that I only added passdb { driver = passwd-file args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd } and comment out from above block default lines #args = /etc/dovecot/dovecot-sql.conf #driver = sql And in auth_mechanisms add line

Am 2015-03-18 20:46, schrieb Reindl Harald: > Am 18.03.2015 um 20:40 schrieb Conrad Kostecki: >> Hi! >> Currently, the passwords are stored in plaintext for my dovecot, as I >> am >> still using cram-md5 AND digest-md5. >> I have still to offer that, as I have some deprecated clients, >> therefore, I am unable to hash at least those passwords for that

It still use: passdb { driver = passwd-file args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd } When I delete above and delete "cram-md5" in auth_mechanisms it still not working. 2017-02-01 8:45 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>: > You are probably wanting to do > passdb { > driver = passwd-file > args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd

I can check each logs, I have root privileges. 2017-02-01 9:04 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>: > Can you check your logs? > > Aki > > > On 01.02.2017 10:02, Poliman - Serwis wrote: > > When I used backup copy of the dovecot.conf file I have this same error. > So > > I think that maybe something was written to database? I really would >

Hi, Trying to solve the problem of supporting multiple auth mechanisms + proxy and really don't want to store user passwords in plain test and fine to do master user to backend. I had the crazy thought I could do something like the following: For each user Store supported password schemes as LDAP attributes: userPasswordCRAM-MD5: {CRAM-MD5}xxx userPasswordDIGEST-MD5: {DIGEST-MD5}xxxx