16 Aug
2011
16 Aug
'11
8:55 a.m.
Hello,
we are expiriencing issues with latest Apple Mail (OS X Lion) and perdition 1.19-rc4. The
problem (as it seems) lies in Apple Mail way of using AUTHENTICATE PLAIN with perdition.
The log from Apple mail shows:
READ Aug 14 21:00:09.405 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:imap_host --
port:993 -- socket:0x7fb51fc20b60 -- thread:0x7fb51f125e10
* OK [CAPABILITY IMAP4 AUTH=LOGIN LITERAL+ IMAP4REV1] perdition ready on imap_host
0002b2fb
WROTE Aug 14 21:00:09.413 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:imap_host
-- port:993 -- socket:0x7fb51fc20b60 -- thread:0x7fb51fb448e0
1.219 AUTHENTICATE LOGIN
READ Aug 14 21:00:09.437 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:imap_host --
port:993 -- socket:0x7fb51fc20b60 -- thread:0x7fb51fb448e0
1.219 NO AUTHENTICATE mechanism not supported, mate
I know that there are some issues with latest Apple Mail (http://goo.gl/RmCGc), but I am
unable to resolve them.
Does anyone of you have a similar case and knows how to resolve it? I have tried to change
the imap_capability, but it does not resolve the issue.
Thank you in advance,
regards, Jernej
16 Aug
16 Aug
9:59 a.m.
Hello,
On Tue, 16 Aug 2011 10:55:18 +0200 Jernej Porenta wrote:
we are expiriencing issues with latest Apple Mail (OS
X Lion) and
perdition 1.19-rc4. The problem (as it seems) lies in Apple Mail way of
using AUTHENTICATE PLAIN with perdition.
Currently still using an older version of perdition on the production
servers here...
The log from Apple mail shows:
READ Aug 14 21:00:09.405 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:imap_host -- port:993 -- socket:0x7fb51fc20b60 --
thread:0x7fb51f125e10
* OK [CAPABILITY IMAP4 AUTH=LOGIN LITERAL+ IMAP4REV1] perdition ready on
imap_host 0002b2fb
WROTE Aug 14 21:00:09.413 [kCFStreamSocketSecurityLevelNegotiatedSSL]
-- host:imap_host -- port:993 -- socket:0x7fb51fc20b60 --
thread:0x7fb51fb448e0 1.219 AUTHENTICATE LOGIN
READ Aug 14 21:00:09.437 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:imap_host -- port:993 -- socket:0x7fb51fc20b60 --
thread:0x7fb51fb448e0 1.219 NO AUTHENTICATE mechanism not supported, mate
I know that there are some issues with latest Apple Mail
(http://goo.gl/RmCGc), but I am unable to resolve them.
Does anyone of you have a similar case and knows how to resolve it? I
have tried to change the imap_capability, but it does not resolve the
issue.
This is rather strange, because we fixed that problem by removing
AUTH=PLAIN from the capabilities string, which had no place being there in
the first place (cut and paste from the dovecot capabilities).
Note that the apple mail client tries to use this even when SASL itself
was not announced, somebody taking mighty big liberties with the RFC at
apple there.
You will likely want to remove that AUTH=LOGIN capability and reload
perdition.
For what it's worth, this seems to work for us right now with a dovecot
1.2 backend, note the absence of all AUTH bits:
imap_capability IMAP4 IMAP4rev1 LITERAL+ ID ENABLE SORT
SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE
UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN
CONTEXT=SEARCH LIST-STATUS QUOTA STARTTLS
Regards,
Christian
--
Christian Balzer Network/Systems Engineer
chibi(a)gol.com Global OnLine Japan/Fusion Communications
http://www.gol.com/
10:44 a.m.
On Aug 16, 2011, at 11:59 AM, Christian Balzer wrote:
Thank you for the hint. Did you experience any problems with the clients after removing
AUTH values?
Our dovecot installation lists AUTH versions, that is why we are still sticking to it.
* CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY
THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS
LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH
LIST-STATUS QUOTA AUTH=PLAIN AUTH=LOGIN
Thank you in advance,
regards, Jernej
The log from Apple mail shows:
READ Aug 14 21:00:09.405 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:imap_host -- port:993 -- socket:0x7fb51fc20b60 --
thread:0x7fb51f125e10
* OK [CAPABILITY IMAP4 AUTH=LOGIN LITERAL+ IMAP4REV1] perdition ready on
imap_host 0002b2fb
WROTE Aug 14 21:00:09.413 [kCFStreamSocketSecurityLevelNegotiatedSSL]
-- host:imap_host -- port:993 -- socket:0x7fb51fc20b60 --
thread:0x7fb51fb448e0 1.219 AUTHENTICATE LOGIN
READ Aug 14 21:00:09.437 [kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:imap_host -- port:993 -- socket:0x7fb51fc20b60 --
thread:0x7fb51fb448e0 1.219 NO AUTHENTICATE mechanism not supported, mate
I know that there are some issues with latest Apple Mail
(http://goo.gl/RmCGc), but I am unable to resolve them.
Does anyone of you have a similar case and knows how to resolve it? I
have tried to change the imap_capability, but it does not resolve the
issue.
This is rather strange, because we fixed that problem by removing
AUTH=PLAIN from the capabilities string, which had no place being there in
the first place (cut and paste from the dovecot capabilities).
Note that the apple mail client tries to use this even when SASL itself
was not announced, somebody taking mighty big liberties with the RFC at
apple there.
You will likely want to remove that AUTH=LOGIN capability and reload
perdition.
For what it's worth, this seems to work for us right now with a dovecot
1.2 backend, note the absence of all AUTH bits:
11:29 a.m.
On Tue, 16 Aug 2011 12:44:39 +0200 Jernej Porenta
On Aug 16, 2011, at 11:59 AM, Christian Balzer wrote:
Thank you for the hint. Did you experience any problems with the clients
after removing AUTH values?
Our dovecot installation lists AUTH versions, that is why we are still
sticking to it.
* CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT
SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE
CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC
ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA
AUTH=PLAIN AUTH=LOGIN
Thank you in advance,
regards, Jernej
--
Christian Balzer Network/Systems Engineer
chibi(a)gol.com Global OnLine Japan/Fusion Communications
http://www.gol.com/
The log from Apple mail shows:
READ Aug 14 21:00:09.405 [kCFStreamSocketSecurityLevelNegotiatedSSL]
-- host:imap_host -- port:993 -- socket:0x7fb51fc20b60 --
thread:0x7fb51f125e10
* OK [CAPABILITY IMAP4 AUTH=LOGIN LITERAL+ IMAP4REV1] perdition ready
on imap_host 0002b2fb
WROTE Aug 14 21:00:09.413 [kCFStreamSocketSecurityLevelNegotiatedSSL]
-- host:imap_host -- port:993 -- socket:0x7fb51fc20b60 --
thread:0x7fb51fb448e0 1.219 AUTHENTICATE LOGIN
READ Aug 14 21:00:09.437 [kCFStreamSocketSecurityLevelNegotiatedSSL]
-- host:imap_host -- port:993 -- socket:0x7fb51fc20b60 --
thread:0x7fb51fb448e0 1.219 NO AUTHENTICATE mechanism not supported,
mate
I know that there are some issues with latest Apple Mail
(http://goo.gl/RmCGc), but I am unable to resolve them.
Does anyone of you have a similar case and knows how to resolve it? I
have tried to change the imap_capability, but it does not resolve
This is rather strange, because we fixed that problem by removing
AUTH=PLAIN from the capabilities string, which had no place being
there in the first place (cut and paste from the dovecot
capabilities). Note that the apple mail client tries to use this even
when SASL itself was not announced, somebody taking mighty big
liberties with the RFC at apple there.
You will likely want to remove that AUTH=LOGIN capability and reload
perdition.
For what it's worth, this seems to work for us right now with a dovecot
1.2 backend, note the absence of all AUTH bits:
11:31 a.m.
Sorry about the previous mail, this keyboard is in need of serious
spanking or a bath in nitric acid...
On Tue, 16 Aug 2011 12:44:39 +0200 Jernej Porenta wrote:
Nope, all oranges and peaches from that point on.
This is rather strange, because we fixed that problem by removing
AUTH=PLAIN from the capabilities string, which had no place being
there in the first place (cut and paste from the dovecot
capabilities). Note that the apple mail client tries to use this even
when SASL itself was not announced, somebody taking mighty big
liberties with the RFC at apple there.
You will likely want to remove that AUTH=LOGIN capability and reload
perdition.
For what it's worth, this seems to work for us right now with a dovecot
1.2 backend, note the absence of all AUTH bits:
Thank you for the hint. Did you experience any problems with the clients
after removing AUTH values?
Our dovecot installation lists AUTH versions, that is
why we are still
sticking to it.
* CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT
SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE
CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC
ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA
AUTH=PLAIN AUTH=LOGIN
For the time being, get rid of all AUTH and SASL bits, I'd say.
Regards,
Christian
--
Christian Balzer Network/Systems Engineer
chibi(a)gol.com Global OnLine Japan/Fusion Communications
http://www.gol.com/
10:18 a.m.
On Tue, Aug 16, 2011 at 10:55:18AM +0200, Jernej Porenta wrote:
Hello,
we are expiriencing issues with latest Apple Mail (OS X Lion) and perdition 1.19-rc4. The
problem (as it seems) lies in Apple Mail way of using AUTHENTICATE PLAIN with perdition.
Hi,
Unfortunately Perdition (still) does not support AUTHENTICATE PLAIN.
22 Aug
22 Aug
8:18 a.m.
We have changed the imap_capability to the one that backend machines advertise without
AUTH parts and it is working fine. Users are not calling in yet ;)
thanks for your help,
cheers, Jernej
On Aug 16, 2011, at 12:18 PM, Simon Horman wrote:
On Tue, Aug 16, 2011 at 10:55:18AM +0200, Jernej
Porenta wrote:
Hello,
we are expiriencing issues with latest Apple Mail (OS X Lion) and perdition 1.19-rc4. The
problem (as it seems) lies in Apple Mail way of using AUTHENTICATE PLAIN with perdition.
Hi,
Unfortunately Perdition (still) does not support AUTHENTICATE PLAIN.
4635
days inactive
4641
days old
6 comments
3 participants
participants (3)
-
Christian Balzer -
Jernej Porenta -
Simon Horman