9 Feb
2012
9 Feb
'12
7:39 p.m.
Hello,
We have deployed Perdition 1.19rc4 to proxy user requests during a migration with popmap
via LDAP. While POP works fine, we are seeing authentication failures through Perdition
to the Courier IMAP, as shown below. I see there was a similar issue reported in build
1.18, in early 2011, but it was thought to be fixed since then. That post is at:
http://lists.vergenet.net/pipermail/perdition-users/2011-January/002468.html
Am I missing an IMAP configuration setting or is this still a bug? Any help you can offer
is much appreciated.
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: CLIENT: ". login
hemigtest5@unix.local<mailto:hemigtest5@unix.local> password\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: username_add_domain:
username_add_domain 0 1
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: do_getserver: dbserver_get returned
empty string
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: username_add_domain:
username_add_domain 0 4
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "* OK [CAPABILITY
IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA
ACL ACL2=UNION XIMAPPROXY] Courier-IMAP ready. Copyright 1998-2010 Double Precision, Inc.
See COPYING for distribution information.\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: SELF: "flim0a
CAPABILITY\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "* CAPABILITY
IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA
ACL ACL2=UNION XIMAPPROXY\r\nflim0a OK Completed\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: SELF: "flim0b LOGIN
{21}\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "+ go ahead\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: SELF:
"hemigtest5@unix.local<mailto:hemigtest5@unix.local> {8}\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "flim0b NO LOGIN
failed\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: imap4_out_response: invalid tag
from server 1
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: imap4_out_authenticate:
imap4_out_response name
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: SELF: "password\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "password BAD Null
command\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: imap4_out_response: invalid tag
from server 1
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: imap4_out_authenticate:
imap4_out_response passwd
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: main: protocol->out_authenticate
-1
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: Fatal error authenticating user.
Exiting child.
Thanks,
Todd
13 Feb
13 Feb
9:08 a.m.
On Thu, Feb 09, 2012 at 07:39:42PM +0000, Todd Taylor wrote:
Hello,
We have deployed Perdition 1.19rc4 to proxy user requests during a migration with popmap
via LDAP. While POP works fine, we are seeing authentication failures through Perdition
to the Courier IMAP, as shown below. I see there was a similar issue reported in build
1.18, in early 2011, but it was thought to be fixed since then. That post is at:
http://lists.vergenet.net/pipermail/perdition-users/2011-January/002468.html
Am I missing an IMAP configuration setting or is this still a bug? Any help you can
offer is much appreciated.
Hi Todd,
what you are seeing does look a lot like the bug at the URL above.
Unfortunately I don't remember the details of how I (claimed to have)
fixed it before not does the patch jump out of the changelog.
I will take a closer look into this.
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]:
CLIENT: ". login hemigtest5@unix.local<mailto:hemigtest5@unix.local>
password\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: username_add_domain:
username_add_domain 0 1
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: do_getserver: dbserver_get
returned empty string
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: username_add_domain:
username_add_domain 0 4
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "* OK [CAPABILITY
IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA
ACL ACL2=UNION XIMAPPROXY] Courier-IMAP ready. Copyright 1998-2010 Double Precision, Inc.
See COPYING for distribution information.\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: SELF: "flim0a
CAPABILITY\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "* CAPABILITY
IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA
ACL ACL2=UNION XIMAPPROXY\r\nflim0a OK Completed\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: SELF: "flim0b LOGIN
{21}\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "+ go
ahead\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: SELF:
"hemigtest5@unix.local<mailto:hemigtest5@unix.local> {8}\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "flim0b NO LOGIN
failed\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: imap4_out_response: invalid tag
from server 1
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: imap4_out_authenticate:
imap4_out_response name
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: SELF: "password\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "password BAD Null
command\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: imap4_out_response: invalid tag
from server 1
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: imap4_out_authenticate:
imap4_out_response passwd
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: main:
protocol->out_authenticate -1
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: Fatal error authenticating user.
Exiting child.
Thanks,
Todd
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
16 Feb
16 Feb
8:32 a.m.
On Mon, Feb 13, 2012 at 06:08:24PM +0900, Simon Horman wrote:
On Thu, Feb 09, 2012 at 07:39:42PM +0000, Todd Taylor
wrote:
Hi Todd,
I have taken a closer look into this but unfortunately I have drawn a blank,
the sequence below seems to work for me. Could you let me know
which version of Courier IMAP you are using. My test environment was:
Debian Testing (amd64)
* From the courier 0.66.3-2 source package
+ courier-base 0.66.3-2
+ courier-imap 4.9.3-2
* From the courier-authlib 0.63.0-4 source package
+ courier-authdaemon 0.63.0-4
+ courier-authlib 0.63.0-4
+ courier-authlib-userdb 0.63.0-4
Hello,
We have deployed Perdition 1.19rc4 to proxy user requests during a migration with popmap
via LDAP. While POP works fine, we are seeing authentication failures through Perdition
to the Courier IMAP, as shown below. I see there was a similar issue reported in build
1.18, in early 2011, but it was thought to be fixed since then. That post is at:
http://lists.vergenet.net/pipermail/perdition-users/2011-January/002468.html
Am I missing an IMAP configuration setting or is this still a bug? Any help you can
offer is much appreciated.
Hi Todd,
what you are seeing does look a lot like the bug at the URL above.
Unfortunately I don't remember the details of how I (claimed to have)
fixed it before not does the patch jump out of the changelog.
I will take a closer look into this. Feb 9
14:53:44 dp-perdition-01 perdition.imap4[5904]: CLIENT: ". login
hemigtest5@unix.local<mailto:hemigtest5@unix.local> password\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: username_add_domain:
username_add_domain 0 1
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: do_getserver: dbserver_get
returned empty string
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: username_add_domain:
username_add_domain 0 4
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "* OK [CAPABILITY
IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA
ACL ACL2=UNION XIMAPPROXY] Courier-IMAP ready. Copyright 1998-2010 Double Precision, Inc.
See COPYING for distribution information.\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: SELF: "flim0a
CAPABILITY\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "* CAPABILITY
IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA
ACL ACL2=UNION XIMAPPROXY\r\nflim0a OK Completed\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: SELF: "flim0b LOGIN
{21}\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "+ go
ahead\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: SELF:
"hemigtest5@unix.local<mailto:hemigtest5@unix.local> {8}\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "flim0b NO LOGIN
failed\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: imap4_out_response: invalid tag
from server 1
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: imap4_out_authenticate:
imap4_out_response name
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: SELF: "password\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: REAL: "password BAD Null
command\r\n"
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: imap4_out_response: invalid tag
from server 1
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: imap4_out_authenticate:
imap4_out_response passwd
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: main:
protocol->out_authenticate -1
Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: Fatal error authenticating user.
Exiting child.
Thanks,
Todd
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
4458
days inactive
4465
days old
2 comments
2 participants
participants (2)
-
Simon Horman -
Todd Taylor