<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
-------- Original Message --------<br>
Subject: Re: 'PLAIN encryption needed to use mechanism' error<br>
From: Dan White <a class="moz-txt-link-rfc2396E" href="mailto:dwhite@olp.net"><dwhite@olp.net></a><br>
To: Blake Hudson <a class="moz-txt-link-rfc2396E" href="mailto:blake@ispn.net"><blake@ispn.net></a><br>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:info-cyrus@lists.andrew.cmu.edu">info-cyrus@lists.andrew.cmu.edu</a><br>
Date: Wednesday, July 29, 2009 2:49:51 AM<br>
<blockquote cite="mid:4A6FFF1F.2080307@olp.net" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
Blake,<br>
<br>
What sasl lines do you have in /etc/imapd.conf. Do you have any proxies
installed?<br>
</blockquote>
my mech list was posted... see below I also have "sasl_pwcheck_method:
auxprop", everything else sasl has to do with my sql config. no proxies
are present.<br>
<blockquote cite="mid:4A6FFF1F.2080307@olp.net" type="cite"><br>
"pop3PRTC" in your syslog looks suspicious...:<br>
</blockquote>
that's just the name I gave it...<br>
<blockquote cite="mid:4A6FFF1F.2080307@olp.net" type="cite"><br>
Usually, pop3 and imap will offer the same mechanisms based on this
config item:<br>
<br>
sasl_mech_list: x x x<br>
</blockquote>
as posted initially I have the following mech list line in imapd.conf:<br>
<pre wrap="">sasl_mech_list: PLAIN LOGIN CRAM-MD5 DIGEST-MD5</pre>
imap advertises the full list as specified (see original message)<br>
<blockquote cite="mid:4A6FFF1F.2080307@olp.net" type="cite"><br>
if this line is commented out, then sasl should attempt to initialize
all available mechs.<br>
<br>
Be on the lookout for customization like this (which overrides the
sasl_mech_list config item):<br>
<br>
pop3_mech_list: x x x<br>
imap_mech_list: x x x<br>
<br>
</blockquote>
good idea, though I don't have these specified. <br>
<br>
<br>
I see your cyrus server is outputting the full mech list via 110...
wonder why mine isn't?<br>
<br>
------------YOURS-----<br>
+OK <1114961040.1248853981@neo> neo Cyrus POP3 Murder
v2.3.12-Debian-2.3.12-1-5<br>
server ready<br>
auth<br>
+OK List of supported mechanisms follows<br>
CRAM-MD5<br>
PLAIN<br>
GSSAPI<br>
OTP<br>
DIGEST-MD5<br>
LOGIN<br>
.<br>
------------MINE-----<br>
+OK twinP Cyrus POP3 v2.3.7-Invoca-RPM-2.3.7-2.el5 server ready
<163906105530322<br>
97444.1248854211@twinP><br>
auth<br>
+OK List of supported mechanisms follows<br>
DIGEST-MD5<br>
CRAM-MD5<br>
.<br>
<br>
<br>
<blockquote cite="mid:4A6FFF1F.2080307@olp.net" type="cite">- Dan<br>
<br>
Blake Hudson wrote:
<blockquote cite="mid:4A6FEE8B.2000805@ispn.net" type="cite">
<pre wrap="">Thanks for the reply Scott. I can auth as you described using the
User/Pass method (allowplaintext: is already set to 1 and I've also
tried sasl_minimum_layer: 0 at the same time).
My concern is that over port 110 the server is only advertising CRAM-MD5
and DIGEST-MD5. POP3s appears to be advertising PLAIN. Why isn't PLAIN
advertised over both?
--Blake
-------- Original Message --------
Subject: Re: 'PLAIN encryption needed to use mechanism' error
From: Scott M. Likens <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto:damm@yazzy.org"><damm@yazzy.org></a>
To: Blake Hudson <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:blake@ispn.net"><blake@ispn.net></a>
Cc: <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:info-cyrus@lists.andrew.cmu.edu">info-cyrus@lists.andrew.cmu.edu</a>
Date: Wednesday, July 29, 2009 1:30:46 AM
</pre>
<blockquote type="cite">
<pre wrap="">Hi Blake,
Actually pop3 by default should be using plain, like
damm@desolation> telnet localhost
pop3
~
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
+OK desolation Cyrus POP3 v2.3.14 server ready
<8505169291665378509.1248848742@desolation>
user root
+OK Name is a valid mailbox
pass toor
+OK Mailbox locked and ready
However, if you man imapd.conf you will notice there is such an option
as,
allowplaintext: 0
You may need to change that to 1, in order for plaintext ala pop3 to
work.
Scott
On Jul 28, 2009, at 10:44 PM, Blake Hudson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">-------- Original Message --------
Subject: 'PLAIN encryption needed to use mechanism' error
From: Blake Hudson <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto:blake@ispn.net"><blake@ispn.net></a>
To: <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:info-cyrus@lists.andrew.cmu.edu">info-cyrus@lists.andrew.cmu.edu</a>
Date: Wednesday, July 29, 2009 12:13:52 AM
</pre>
<blockquote type="cite">
<pre wrap="">I recently setup a new server and everything tested well. However, once
in production I am seeing errors like the following:
pop3PRTC[20896]: badlogin: [204.x.x.x] PLAIN encryption needed to use
mechanism
I wasn't aware that POP utilized other mechanisms? I can login just
fine
with telnet and tbird, and cannot replicate this error myself. Any
ideas?
--Blake
</pre>
</blockquote>
<pre wrap="">Looks like the POP side is not advertising LOGIN/PLAIN auth types while
the imap side is. Is this the intended behavior?
In my imapd.conf i have the following mech list defined:
sasl_mech_list: PLAIN LOGIN CRAM-MD5 DIGEST-MD5
---------------------- POP3----------------------
+OK twinP Cyrus POP3 v2.3.7-Invoca-RPM-2.3.7-2.el5 server ready
<173180331313918
17429.1248845988@twinP>
auth
+OK List of supported mechanisms follows
DIGEST-MD5
CRAM-MD5
..
--------------------------------------------
----------------------IMAP----------------------
* OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID STARTTLS AUTH=DIGEST-MD5
AUTH=LOGIN
AUTH=PLAIN AUTH=CRAM-MD5 SASL-IR] twinP Cyrus IMAP4
v2.3.7-Invoca-RPM-2.3.7-2.el5 server ready
--------------------------------------------
I suppose this is likely a bad client that is not refreshing its mech
list after the server switch, but I'd still like to know how to resolve
the issue server side (if possible).
-Blake
----
Cyrus Home Page: <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://cyrusimap.web.cmu.edu/">http://cyrusimap.web.cmu.edu/</a>
Cyrus Wiki/FAQ: <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://cyrusimap.web.cmu.edu/twiki">http://cyrusimap.web.cmu.edu/twiki</a>
List Archives/Info: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://asg.web.cmu.edu/cyrus/mailing-list.html">http://asg.web.cmu.edu/cyrus/mailing-list.html</a>
!DSPAM:4a6fe485262521931426455!
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!----></pre>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>