subject:"imapd dies when connecting with Mozilla\-1.6beta Mail IMAP account"

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-05 Thread Hajo Beckefeld

Hi,

PLAIN works,... well, because it works with saslauthd. You should try 
and setup CRAM-MD5 or better yet DIGEST-MD5, since they encrypt the 
password. I'm not sure what your saslauthd is using as a reference 
mechanism (where it gets USER/PASS from), most likely your UNIX accounts 
- which is BAD.

Yes, plain works fine now! But important - maybe for others - is that it 
works with mech PLAIN with my configuration and cyrus-sasl-2.1.17.
First Mozilla-1.6 tries to login with CRAM-MD5 - after that fails 
Mozilla makes a PLAIN login.

After writing "sasl_mech_list: PLAIN LOGIN" in the /etc/imapd.conf 
Mozilla just tries a PLAIN login.

OK, it works, I'll grant you that. But you could give a thought or two 
to security issues. One quick fix is to setup SSL connections and use them.

MD5 mechanisms requre user/pass to be stored in /etc/sasldb2 database, 
which is maintained manually by the admin. This also might not be what 
you want. If you have a Kerberos service (unlikely), you could try to 
set it up for your IMAP. But it is a long way and requires patience and 
endurance. :-)

You're right! I think I'll try to set up my mail server with DIGEST-MD5 
next days!
Here is only one mail user! It's no problem to put me into sasldb2;-)
I drive this machine here just for fun an learning about UNIX/Linux!

c-You
Hajo

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-05 Thread Hajo Beckefeld

Hi Sebastian,

I've no idea what I have to do to get the CRAM-MD5 stuff running!


if you want to use CRAM-MD5, you have to add all your users to sasldb 
using saslpasswd2. Then you need to change /etc/imapd.conf so that it 
uses sasldb and offers CRAM-MD5:

sasl_pwcheck_method: auxprop
sasl_mech_list: DIGEST-MD5 CRAM-MD5 PLAIN LOGIN
Mozilla should be able to use it after that. saslauthd doesn't support 
CRAM-MD5.

´Great, I think I got it! The next days I'll try it!

Thanks
Hajo

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-05 Thread Sebastian Hagedorn

Hi,

--On Sonntag, 4. Januar 2004 23:47 Uhr +0100 Hajo Beckefeld 
<[EMAIL PROTECTED]> wrote:

jinn:[hajo]# sasldblistusers2
[EMAIL PROTECTED]: cmusaslsecretOTP
[EMAIL PROTECTED]: userPassword
I've no idea what I have to do to get the CRAM-MD5 stuff running!
if you want to use CRAM-MD5, you have to add all your users to sasldb using 
saslpasswd2. Then you need to change /etc/imapd.conf so that it uses sasldb 
and offers CRAM-MD5:

sasl_pwcheck_method: auxprop
sasl_mech_list: DIGEST-MD5 CRAM-MD5 PLAIN LOGIN
Mozilla should be able to use it after that. saslauthd doesn't support 
CRAM-MD5.

Cheers, Sebastian Hagedorn
--
Sebastian Hagedorn M.A. - RZKR-R1 (Gebäude 52), Zimmer 18
Zentrum für angewandte Informatik - Universitätsweiter Service RRZK
Universität zu Köln / Cologne University - Tel. +49-221-478-5587

pgp0.pgp
Description: PGP signature

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-04 Thread Hajo Beckefeld

Hi Nix,

Maybe that is refering to something else, like Kerberos5 (GSS-API) login,
which is getting more and more popular with the advance of Microsoft's
Active Directory.
Yes it seems so!

Now my configuration is working fine! I upgraded to cyrus-sasl-2.1.17! 
After that the imap connect with Mozilla-1.6beta works again.

/var/log/messages:
 Jan  4 23:15:53 jinn imapd[25584]: login: 
luke.beckefeld-online.de[192.168.1.20] hajo plaintext
Jan  4 23:19:04 jinn imapd[25587]: no secret in database
Jan  4 23:19:04 jinn imapd[25587]: badlogin: 
oola.beckefeld-online.de[192.168.1.42] CRAM-MD5 [SASL(-13): user not 
found: no secret in database]
Jan  4 23:19:07 jinn imapd[25587]: login: 
oola.beckefeld-online.de[192.168.1.42] hajo plaintext

Then I wrote in /etc/imapd.conf: "sasl_mech_list: PLAIN LOGIN" then I've 
only:

/var/log/messages:
Jan  4 23:05:42 jinn imapd[25410]: login: 
luke.beckefeld-online.de[192.168.1.20] hajo plaintext



This usually means that the server is failing to perform that
authentication. My guess is that PLAIN is using "saslauthd" (SASL
Authentication Daemon for PLAIN authentication) and that your /etc/sasldb2
(SASL DataBase module) is empty or unreadable by Cyrus user.
My /etc/sasldb2 looks fine, I think:
jinn:[hajo]# ls -l /etc/sasldb2
-rw-r-1 cyrusmail12288 Jan  4 22:51 /etc/sasldb2
jinn:[hajo]# sasldblistusers2
[EMAIL PROTECTED]: cmusaslsecretOTP
[EMAIL PROTECTED]: userPassword
I can create the same entry for mail user "hajo" but noting changes at all!!

In any case, server shouldn't crash. Ever. Try setting up /etc/sasldb2 and
see what happens (run "saslpasswd2 -c cyrus").
It doesn't crashes anymore - more than that: I get an error message!


Jan  4 18:53:04 jinn perl: No worthy mechs found
This is Perl side, which has nothing to do with IMAP server.

Yepp, it doesn't matter what kind of perl modules I have:-)

No. Perl modules are solely for "cyradm" client. "cyradm" is just a Perl
application using IMAP protocol to administer mailboxes. All it does you,
can do yourself from telnet to IMAP port - providing you know IMAP protocol
by heart :-)
Yes, Yes it's very nice to study RFCs;-) I speek a little bit pop3;-)

Nix.


At last cyrus-imap works fine again, but I do not understand the 
/etc/sasldb2 thing working with CRAM-MD5! Would't it be right that an 
IMAP client can authenticate with CRAM-MD5???

Here my cyradm:

When I try:
jinn:[hajo]# cyradm --user cyrus --auth CRAM-MD5 localhost
cyradm: cannot authenticate to server with CRAM-MD5 as cyrus
/var/log/messages:
Jan  4 23:25:16 jinn imapd[25591]: badlogin: 
jinn.beckefeld-online.de[127.0.0.1] CRAM-MD5 [SASL(-13): user not found: 
no secret in database]

With auth PLAIN everything works fine!

Thanks for your help!
c-You
Hajo

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-04 Thread Hajo Beckefeld

Hi Ken,

I'm running a cyrus IMAP server 2.1.16 on an Linux 2.2.25 machine.
When I try connect from an Mozilla 1.6/1.7 IMAP client, I can't 
establish the connection. The log just says:

Jan  4 13:52:43 jinn master[12215]: about to exec /usr/cyrus/bin/imapd
Jan  4 13:52:43 jinn imap[12215]: executed
Jan  4 13:52:43 jinn imapd[12215]: accepted connection
Jan  4 13:52:50 jinn master[2293]: process 12215 exited, signaled to 
death by 11


Can you provide a backtrace of a core dump and/or a telemetry log of the 
traffic?  Since it looks like its crashing before/during authentication, 
you'll need to use something like ssldump (or the like) to capture the 
IMAP traffic.

I posted a lot of informations.
Now my configuration is working! I update cyrus-sasl to v2.1.17! Then I 
get the following log:

Jan  4 23:19:04 jinn imapd[25587]: badlogin: 
oola.beckefeld-online.de[192.168.1.42] CRAM-MD5 [SASL(-13): user not 
found: no secret in database]
Jan  4 23:19:07 jinn imapd[25587]: login: 
oola.beckefeld-online.de[192.168.1.42] hajo plaintext
Jan  4 23:19:07 jinn imapd[25587]: seen_db: user hajo opened 
/var/imap/user/h/hajo.seen
Jan  4 23:19:07 jinn imapd[25587]: open: user hajo opened INBOX

... and can access my mail account via imap.

When I put a line "sasl_mech_list: PLAIN LOGIN" in my /etc/imapd.conf 
the "badlogin message don't occur! That means for me, that the 
authentication with CRAM-MD5 wasn't attempted by the Mozilla Mail Client?!?

When I try:
jinn:[hajo]# cyradm --user cyrus --auth CRAM-MD5 localhost
cyradm: cannot authenticate to server with CRAM-MD5 as cyrus
log:
Jan  4 23:25:16 jinn imapd[25591]: badlogin: 
jinn.beckefeld-online.de[127.0.0.1] CRAM-MD5 [SASL(-13): user not found: 
no secret in database]

With auth PLAIN everything works fine!

My sasldb2 looks like this:

jinn:[hajo]# ls -l /etc/sasldb2
-rw-r-1 cyrusmail12288 Jan  4 22:51 /etc/sasldb2
jinn:[hajo]# sasldblistusers2
[EMAIL PROTECTED]: cmusaslsecretOTP
[EMAIL PROTECTED]: userPassword
I've no idea what I have to do to get the CRAM-MD5 stuff running!

Thanks for your help
Hajo

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-04 Thread Hajo Beckefeld

Hi Sebastian,



Thanks, I think the problem is, that the Mozilla Mail Client didn't send
the username/passwd in plain test! I posted an ethereal trace in this
thread!


Your IMAP server offers CRAM-MD5 and so Mozilla (finally!) does what it 
should: it uses it.

I guess you're using saslauthd and not sasldb, right? You need to change 
your /etc/imapd.conf file so that it doesn't offer CRAM-MD5:

sasl_mech_list: PLAIN LOGIN

Thanks a lot! I ugraded to cyrus-sasl-2.1.17 and wrote that line into my 
/etc/imapd.conf - now it works fine:-)

c-You
Hajo

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-04 Thread Sebastian Hagedorn

-- Hajo Beckefeld <[EMAIL PROTECTED]> is rumored to have mumbled on 
Sonntag, 4. Januar 2004 18:03 Uhr +0100 regarding Re: imapd dies when 
connecting with Mozilla-1.6beta Mail IMAP account:

Thanks, I think the problem is, that the Mozilla Mail Client didn't send
the username/passwd in plain test! I posted an ethereal trace in this
thread!
Your IMAP server offers CRAM-MD5 and so Mozilla (finally!) does what it 
should: it uses it.

I guess you're using saslauthd and not sasldb, right? You need to change 
your /etc/imapd.conf file so that it doesn't offer CRAM-MD5:

sasl_mech_list: PLAIN LOGIN

Greetings, Sebastian
--
Sebastian Hagedorn M.A. - RZKR-R1 (Flachbau), Zi. 18, Robert-Koch-Str. 10
Zentrum für angewandte Informatik - Universitätsweiter Service RRZK
Universität zu Köln / Cologne University - Tel. +49-221-478-5587

pgp0.pgp
Description: PGP signature

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-04 Thread Hajo Beckefeld

Hi Sebastian,

you can log using Mozilla:



Thanks, I think the problem is, that the Mozilla Mail Client didn't send 
the username/passwd in plain test! I posted an ethereal trace in this 
thread!

c-You
Hajo
That's what I got from Mozilla1.6beta:

[EMAIL PROTECTED]: hajo]50$ tail -f /tmp/ttt.log
98310[8dcabf8]: ImapThreadMainLoop entering [this=8dc21b8]
16384[80a53d8]: 8dc21b8:mail.beckefeld-onine.de:NA:SetupWithUrl: 
clearing IMAP_CONNECTION_IS_OPEN
98310[8dcabf8]: 8dc21b8:mail.beckefeld-onine.de:NA:ProcessCurrentURL: 
entering
98310[8dcabf8]: 
8dc21b8:mail.beckefeld-onine.de:NA:ProcessCurrentURL:imap://[EMAIL PROTECTED]:143/select%3E.INBOX: 
 = currentUrl
98310[8dcabf8]: ReadNextLine [stream=8dcb180 nb=64 needmore=0]
98310[8dcabf8]: 
8dc21b8:mail.beckefeld-onine.de:NA:CreateNewLineFromSocket: * OK 
mail.beckefeld-online.de Cyrus IMAP4 v2.1.16 server ready
98310[8dcabf8]: 8dc21b8:mail.beckefeld-onine.de:NA:SendData: 1 capability
98310[8dcabf8]: ReadNextLine [stream=8dcb180 nb=282 needmore=0]
98310[8dcabf8]: 
8dc21b8:mail.beckefeld-onine.de:NA:CreateNewLineFromSocket: * CAPABILITY 
IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS 
ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND SORT 
THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE STARTTLS AUTH=GSSAPI 
AUTH=OTP AUTH=DIGEST-MD5 AUTH=CRAM-MD5 LISTEXT LIST-SUBSCRIBED ANNOTATEMORE
98310[8dcabf8]: ReadNextLine [stream=8dcb180 nb=16 needmore=0]
98310[8dcabf8]: 
8dc21b8:mail.beckefeld-onine.de:NA:CreateNewLineFromSocket: 1 OK Completed
98310[8dcabf8]: 8dc21b8:mail.beckefeld-onine.de:NA:SendData: 2 
authenticate CRAM-MD5
98310[8dcabf8]: ReadNextLine [stream=8dcb180 nb=68 needmore=0]
98310[8dcabf8]: 
8dc21b8:mail.beckefeld-onine.de:NA:CreateNewLineFromSocket: + 
PDQxNjQ1MjM0MTEuMTYyNzA4ODRAbWFpbC5iZWNrZWZlbGQtb25saW5lLmRlPg==
98310[8dcabf8]: 8dc21b8:mail.beckefeld-onine.de:NA:SendData: 
aGFqbyA0MDA2YWFkYTA1NWMyODc2ZjllMmUxYzZlNmZhNGQzZA==
98310[8dcabf8]: ReadNextLine [stream=8dcb180 nb=0 needmore=1]
98310[8dcabf8]: ReadNextLine [stream=8dcb180 nb=0 needmore=0]
98310[8dcabf8]: 
8dc21b8:mail.beckefeld-onine.de:NA:CreateNewLineFromSocket: clearing 
IMAP_CONNECTION_IS_OPEN - rv = 80470002
98310[8dcabf8]: 8dc21b8:mail.beckefeld-onine.de:NA:TellThreadToDie: 
close socket connection
98310[8dcabf8]: 
8dc21b8:mail.beckefeld-onine.de:NA:CreateNewLineFromSocket: (null)
98310[8dcabf8]: 8dc21b8:mail.beckefeld-onine.de:NA:SendData: clearing 
IMAP_CONNECTION_IS_OPEN
98310[8dcabf8]: 8dc21b8:mail.beckefeld-onine.de:NA:TellThreadToDie: 
close socket connection
98310[8dcabf8]: 8dc21b8:mail.beckefeld-onine.de:NA:SendData: clearing 
IMAP_CONNECTION_IS_OPEN
98310[8dcabf8]: 8dc21b8:mail.beckefeld-onine.de:NA:TellThreadToDie: 
close socket connection
98310[8dcabf8]: 8dc21b8:mail.beckefeld-onine.de:NA:SendData: clearing 
IMAP_CONNECTION_IS_OPEN
98310[8dcabf8]: 8dc21b8:mail.beckefeld-onine.de:NA:TellThreadToDie: 
close socket connection
98310[8dcabf8]: 8dc21b8:mail.beckefeld-onine.de:NA:ProcessCurrentURL: 
aborting queued urls
98310[8dcabf8]: ImapThreadMainLoop leaving [this=8dc21b8]
16384[80a53d8]: 8d72160:mail.beckefeld-onine.de:NA:SetupWithUrl: 
clearing IMAP_CONNECTION_IS_OPEN
114694[8c28c78]: ImapThreadMainLoop entering [this=8d72160]
114694[8c28c78]: 8d72160:mail.beckefeld-onine.de:NA:ProcessCurrentURL: 
entering
114694[8c28c78]: 
8d72160:mail.beckefeld-onine.de:NA:ProcessCurrentURL:imap://[EMAIL PROTECTED]:143/select%3E.INBOX: 
 = currentUrl
114694[8c28c78]: ReadNextLine [stream=8e71b88 nb=64 needmore=0]
114694[8c28c78]: 
8d72160:mail.beckefeld-onine.de:NA:CreateNewLineFromSocket: * OK 
mail.beckefeld-online.de Cyrus IMAP4 v2.1.16 server ready
114694[8c28c78]: 8d72160:mail.beckefeld-onine.de:NA:SendData: 1 
authenticate CRAM-MD5
114694[8c28c78]: ReadNextLine [stream=8e71b88 nb=68 needmore=0]
114694[8c28c78]: 
8d72160:mail.beckefeld-onine.de:NA:CreateNewLineFromSocket: + 
PDQxNjM4ODA2NTQuMTYyNzA5MDhAbWFpbC5iZWNrZWZlbGQtb25saW5lLmRlPg==
114694[8c28c78]: 8d72160:mail.beckefeld-onine.de:NA:SendData: 
aGFqbyA5M2QxNmVhYjc3Nzc4Zjc4N2FhYWJlMjg2YTA0YTdjMQ==
114694[8c28c78]: ReadNextLine [stream=8e71b88 nb=0 needmore=1]
114694[8c28c78]: ReadNextLine [stream=8e71b88 nb=0 needmore=0]
114694[8c28c78]: 
8d72160:mail.beckefeld-onine.de:NA:CreateNewLineFromSocket: clearing 
IMAP_CONNECTION_IS_OPEN - rv = 80470002
114694[8c28c78]: 8d72160:mail.beckefeld-onine.de:NA:TellThreadToDie: 
close socket connection
114694[8c28c78]: 
8d72160:mail.beckefeld-onine.de:NA:CreateNewLineFromSocket: (null)
114694[8c28c78]: 8d72160:mail.beckefeld-onine.de:NA:SendData: clearing 
IMAP_CONNECTION_IS_OPEN
114694[8c28c78]: 8d72160:mail.beckefeld-onine.de:NA:TellThreadToDie: 
close socket connection
114694[8c28c78]: 8d72160:mail.beckefeld-onine.de:NA:SendData: clearing 
IMAP_CONNECTION_IS_OPEN
114694[8c28c78]: 8d72160:mail.beckefeld-onine.de:NA:TellThreadToDie: 
close socket connection
114694[8c28c78]: 8d72160:mail.beckefeld-onine.de

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-04 Thread Hajo Beckefeld

Ok, I traced it with tethereal it's more readable, I think;-)
The IMAP traffic should at least tell us what the client is trying to do.

I hope this might help!
For me it looks like Mozilla-1.6 sends username/passwd not in clear text 
put something encoded and cyrus-imapd can't handle that!?!

c-You
Hajo
This is the login and the first "Get Msgs":

Mozilla-1.6beta - not working

jinn:[/root]# tethereal -i eth0 -n 'dst port imap or src port imap'
Capturing on eth0
  0.00 192.168.1.42 -> 192.168.1.30 TCP 32822 > 143 [SYN] 
Seq=3905136509 Ack=0 Win=5840 Len=0
  0.57 192.168.1.30 -> 192.168.1.42 TCP 143 > 32822 [SYN, ACK] 
Seq=1044389215 Ack=3905136510 Win=32120 Len=0
  0.000155 192.168.1.42 -> 192.168.1.30 TCP 32822 > 143 [ACK] 
Seq=3905136510 Ack=1044389216 Win=5840 Len=0
  0.029703 192.168.1.30 -> 192.168.1.42 IMAP Response: * OK 
mail.beckefeld-online.de Cyrus IMAP4 v2.1.16 server ready
  0.029853 192.168.1.42 -> 192.168.1.30 TCP 32822 > 143 [ACK] 
Seq=3905136510 Ack=1044389280 Win=5840 Len=0
  0.092080 192.168.1.42 -> 192.168.1.30 IMAP Request: 1 capability
  0.092110 192.168.1.30 -> 192.168.1.42 TCP 143 > 32822 [ACK] 
Seq=1044389280 Ack=3905136524 Win=32120 Len=0
  0.092902 192.168.1.30 -> 192.168.1.42 IMAP Response: * CAPABILITY 
IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS 
ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND SORT 
THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE STARTTLS AUTH=GSSAPI 
AUTH=OTP AUTH=DIGEST-MD5 AUTH=CRAM-MD5 LISTEXT LIST-SUBSCRIBED ANNOTATEMORE
  0.093044 192.168.1.42 -> 192.168.1.30 TCP 32822 > 143 [ACK] 
Seq=3905136524 Ack=1044389578 Win=6432 Len=0
 18.940461 192.168.1.42 -> 192.168.1.30 IMAP Request: 2 authenticate 
CRAM-MD5
 18.942770 192.168.1.30 -> 192.168.1.42 IMAP Response: + 
PDEwMDI0MDA0NTkuMTYyNjk3OThAbWFpbC5iZWNrZWZlbGQtb25saW5lLmRlPg==
 18.942906 192.168.1.42 -> 192.168.1.30 TCP 32822 > 143 [ACK] 
Seq=3905136549 Ack=1044389646 Win=6432 Len=0
 18.945945 192.168.1.42 -> 192.168.1.30 IMAP Request: 
aGFqbyBlZTNmYWZmZTNhYTY3YmNhYjJkOWMyNzI1ZWY3ZmE1NQ==
 18.947351 192.168.1.30 -> 192.168.1.42 TCP 143 > 32822 [FIN, ACK] 
Seq=1044389646 Ack=3905136603 Win=32120 Len=0
 18.947844 192.168.1.42 -> 192.168.1.30 TCP 32822 > 143 [FIN, ACK] 
Seq=3905136603 Ack=1044389647 Win=6432 Len=0
 18.947910 192.168.1.30 -> 192.168.1.42 TCP 143 > 32822 [ACK] 
Seq=1044389647 Ack=3905136604 Win=32120 Len=0
 39.309910 192.168.1.42 -> 192.168.1.30 TCP 32823 > 143 [SYN] 
Seq=3941702989 Ack=0 Win=5840 Len=0
 39.309989 192.168.1.30 -> 192.168.1.42 TCP 143 > 32823 [SYN, ACK] 
Seq=1075223227 Ack=3941702990 Win=32120 Len=0
 39.310095 192.168.1.42 -> 192.168.1.30 TCP 32823 > 143 [ACK] 
Seq=3941702990 Ack=1075223228 Win=5840 Len=0
 39.338670 192.168.1.30 -> 192.168.1.42 IMAP Response: * OK 
mail.beckefeld-online.de Cyrus IMAP4 v2.1.16 server ready
 39.338816 192.168.1.42 -> 192.168.1.30 TCP 32823 > 143 [ACK] 
Seq=3941702990 Ack=1075223292 Win=5840 Len=0
 39.340664 192.168.1.42 -> 192.168.1.30 IMAP Request: 1 authenticate 
CRAM-MD5
 39.340693 192.168.1.30 -> 192.168.1.42 TCP 143 > 32823 [ACK] 
Seq=1075223292 Ack=3941703015 Win=32120 Len=0
 39.341607 192.168.1.30 -> 192.168.1.42 IMAP Response: + 
PDE1MzU0OTExOTguMTYyNjk4MTlAbWFpbC5iZWNrZWZlbGQtb25saW5lLmRlPg==
 39.342251 192.168.1.42 -> 192.168.1.30 IMAP Request: 
aGFqbyAxNjMyOWMxYmNkZTU2NjcyNDYyM2E4MWZjZDRjNDE4Yw==
 39.343623 192.168.1.30 -> 192.168.1.42 TCP 143 > 32823 [FIN, ACK] 
Seq=1075223360 Ack=3941703069 Win=32120 Len=0
 39.343959 192.168.1.42 -> 192.168.1.30 TCP 32823 > 143 [FIN, ACK] 
Seq=3941703069 Ack=1075223361 Win=5840 Len=0
 39.344020 192.168.1.30 -> 192.168.1.42 TCP 143 > 32823 [ACK] 
Seq=1075223361 Ack=3941703070 Win=32120 Len=0

Mozilla-1.5 - working fine
71.562022 192.168.1.20 -> 192.168.1.30 TCP 35151 > 143 [SYN] Seq=6745490 
Ack=0 Win=5840 Len=0
 71.562078 192.168.1.30 -> 192.168.1.20 TCP 143 > 35151 [SYN, ACK] 
Seq=1119348975 Ack=6745491 Win=32120 Len=0
 71.562163 192.168.1.20 -> 192.168.1.30 TCP 35151 > 143 [ACK] 
Seq=6745491 Ack=1119348976 Win=5840 Len=0
 71.590771 192.168.1.30 -> 192.168.1.20 IMAP Response: * OK 
mail.beckefeld-online.de Cyrus IMAP4 v2.1.16 server ready
 71.590930 192.168.1.20 -> 192.168.1.30 TCP 35151 > 143 [ACK] 
Seq=6745491 Ack=1119349040 Win=5840 Len=0
 71.776691 192.168.1.20 -> 192.168.1.30 IMAP Request: 1 capability
 71.776728 192.168.1.30 -> 192.168.1.20 TCP 143 > 35151 [ACK] 
Seq=1119349040 Ack=6745505 Win=32120 Len=0
71.777610 192.168.1.30 -> 192.168.1.20 IMAP Response: * CAPABILITY IMAP4 
IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS ID 
NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND SORT 
THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE STARTTLS AUTH=GSSAPI 
AUTH=OTP AUTH=DIGEST-MD5 AUTH=CRAM-MD5 LISTEXT LIST-SUBSCRIBED ANNOTATEMORE
 71.10 192.168.1.20 -> 192.168.1.30 TCP 35151 > 143 [ACK] 
Seq=6745505 Ack=1119349338 Win=6432 Len=0
 77.325221 192.168.1.20 -> 192.168.1.30 IMAP Request: 3 login "hajo" 
""
 77.329306 192.168.1.30 -> 192.168.1.20 I

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-04 Thread Sebastian Hagedorn

-- Ken Murchison <[EMAIL PROTECTED]> is rumored to have mumbled on Sonntag, 4. 
Januar 2004 11:06 Uhr -0500 regarding Re: imapd dies when connecting with 
Mozilla-1.6beta Mail IMAP account:

Yes you're right! The Mozilla mail client is waiting for the
authentication!
I allready looked for a switch in cyrus-imap to enable further logging,
is there anything?
Not for pre-authentication traffic.  Are you getting any further info in
your auth.log?
Hajo,

you can log using Mozilla:

<http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap>

Cheers, Sebastian
--
Sebastian Hagedorn M.A. - RZKR-R1 (Flachbau), Zi. 18, Robert-Koch-Str. 10
Zentrum für angewandte Informatik - Universitätsweiter Service RRZK
Universität zu Köln / Cologne University - Tel. +49-221-478-5587

pgp0.pgp
Description: PGP signature

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-04 Thread Hajo Beckefeld

Hi,

I'm running a cyrus IMAP server 2.1.16 on an Linux 2.2.25 machine.
When I try connect from an Mozilla 1.6/1.7 IMAP client, I can't 
establish the connection. The log just says:

Jan  4 13:52:43 jinn master[12215]: about to exec /usr/cyrus/bin/imapd
Jan  4 13:52:43 jinn imap[12215]: executed
Jan  4 13:52:43 jinn imapd[12215]: accepted connection
Jan  4 13:52:50 jinn master[2293]: process 12215 exited, signaled to 
death by 11


Can you provide a backtrace of a core dump and/or a telemetry log of the 
traffic?  Since it looks like its crashing before/during authentication, 
you'll need to use something like ssldump (or the like) to capture the 
IMAP traffic.

Here's a tcpdump of my IMAP traffic:

Mozilla-1.6beta - no connection:

jinn:[/root]# tcpdump -n  -i eth0 'dst port imap or src port imap'
tcpdump: listening on eth0
16:55:34.009979 192.168.1.42.32808 > 192.168.1.30.imap2: S 
1228258981:1228258981(0) win 5840  (DF)
16:55:34.010038 192.168.1.30.imap2 > 192.168.1.42.32808: S 
2589395966:2589395966(0) ack 1228258982 win 32120  (DF)
16:55:34.010136 192.168.1.42.32808 > 192.168.1.30.imap2: . ack 1 win 
5840  (DF)
16:55:34.038366 192.168.1.30.imap2 > 192.168.1.42.32808: P 1:65(64) ack 
1 win 32120  (DF)
16:55:34.038506 192.168.1.42.32808 > 192.168.1.30.imap2: . ack 65 win 
5840  (DF)
16:55:34.040309 192.168.1.42.32808 > 192.168.1.30.imap2: P 1:26(25) ack 
65 win 5840  (DF)
16:55:34.040355 192.168.1.30.imap2 > 192.168.1.42.32808: . ack 26 win 
32120  (DF)
16:55:34.041641 192.168.1.30.imap2 > 192.168.1.42.32808: P 65:129(64) 
ack 26 win 32120  (DF)
16:55:34.042300 192.168.1.42.32808 > 192.168.1.30.imap2: P 26:80(54) ack 
129 win 5840  (DF)
16:55:34.043366 192.168.1.30.imap2 > 192.168.1.42.32808: F 129:129(0) 
ack 80 win 32120  (DF)
16:55:34.043701 192.168.1.42.32808 > 192.168.1.30.imap2: F 80:80(0) ack 
130 win 5840  (DF)
16:55:34.043766 192.168.1.30.imap2 > 192.168.1.42.32808: . ack 81 win 
32120  (DF)



Mozilla-1.5 - working fine:

jinn:[/root]# tcpdump -n  -i eth0 'dst port imap or src port imap'
tcpdump: listening on eth0
16:56:28.537966 192.168.1.20.33423 > 192.168.1.30.imap2: P 
594722016:594722026(10) ack 1462713209 win 44888  (DF)
16:56:28.538229 192.168.1.30.imap2 > 192.168.1.20.33423: P 1:19(18) ack 
10 win 32120  (DF)
16:56:28.538328 192.168.1.20.33423 > 192.168.1.30.imap2: . ack 19 win 
44888  (DF)
16:56:28.598500 192.168.1.20.33423 > 192.168.1.30.imap2: P 10:36(26) ack 
19 win 44888  (DF)
16:56:28.598793 192.168.1.30.imap2 > 192.168.1.20.33423: P 19:56(37) ack 
36 win 32120  (DF)
16:56:28.598891 192.168.1.20.33423 > 192.168.1.30.imap2: . ack 56 win 
44888  (DF)
16:56:28.658224 192.168.1.20.33423 > 192.168.1.30.imap2: P 36:66(30) ack 
56 win 44888  (DF)
16:56:28.658352 192.168.1.30.imap2 > 192.168.1.20.33423: P 56:123(67) 
ack 66 win 32120  (DF)
16:56:28.658443 192.168.1.20.33423 > 192.168.1.30.imap2: . ack 123 win 
44888  (DF)

It's the same, if I run Mozilla-1.6beta on the "working machine"!

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-04 Thread Ken Murchison

Hajo Beckefeld wrote:

Thanks for the very fast reply!


Hi List!

I'm running a cyrus IMAP server 2.1.16 on an Linux 2.2.25 machine.
When I try connect from an Mozilla 1.6/1.7 IMAP client, I can't 
establish the connection. The log just says:

Jan  4 13:52:43 jinn master[12215]: about to exec /usr/cyrus/bin/imapd
Jan  4 13:52:43 jinn imap[12215]: executed
Jan  4 13:52:43 jinn imapd[12215]: accepted connection
Jan  4 13:52:50 jinn master[2293]: process 12215 exited, signaled to 
death by 11


Can you provide a backtrace of a core dump and/or a telemetry log of 
the traffic?  Since it looks like its crashing before/during 
authentication, you'll need to use something like ssldump (or the 
like) to capture the IMAP traffic.

Yes you're right! The Mozilla mail client is waiting for the 
authentication!
I allready looked for a switch in cyrus-imap to enable further logging, 
is there anything?
Not for pre-authentication traffic.  Are you getting any further info in 
your auth.log?

I don't know how to get a core dump. I'm not very confirm with that, sorry!
I just try to post the tcp traffic!
The IMAP traffic should at least tell us what the client is trying to do.

--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26  Orchard Park, NY 14127
--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-04 Thread Hajo Beckefeld

Thanks for the very fast reply!

Hi List!

I'm running a cyrus IMAP server 2.1.16 on an Linux 2.2.25 machine.
When I try connect from an Mozilla 1.6/1.7 IMAP client, I can't 
establish the connection. The log just says:

Jan  4 13:52:43 jinn master[12215]: about to exec /usr/cyrus/bin/imapd
Jan  4 13:52:43 jinn imap[12215]: executed
Jan  4 13:52:43 jinn imapd[12215]: accepted connection
Jan  4 13:52:50 jinn master[2293]: process 12215 exited, signaled to 
death by 11


Can you provide a backtrace of a core dump and/or a telemetry log of the 
traffic?  Since it looks like its crashing before/during authentication, 
you'll need to use something like ssldump (or the like) to capture the 
IMAP traffic.

Yes you're right! The Mozilla mail client is waiting for the authentication!
I allready looked for a switch in cyrus-imap to enable further logging, 
is there anything?
I don't know how to get a core dump. I'm not very confirm with that, sorry!
I just try to post the tcp traffic!

c-You
Hajo

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-04 Thread Ken Murchison

Hajo Beckefeld wrote:

Hi List!

I'm running a cyrus IMAP server 2.1.16 on an Linux 2.2.25 machine.
When I try connect from an Mozilla 1.6/1.7 IMAP client, I can't 
establish the connection. The log just says:

Jan  4 13:52:43 jinn master[12215]: about to exec /usr/cyrus/bin/imapd
Jan  4 13:52:43 jinn imap[12215]: executed
Jan  4 13:52:43 jinn imapd[12215]: accepted connection
Jan  4 13:52:50 jinn master[2293]: process 12215 exited, signaled to 
death by 11
Can you provide a backtrace of a core dump and/or a telemetry log of the 
traffic?  Since it looks like its crashing before/during authentication, 
you'll need to use something like ssldump (or the like) to capture the 
IMAP traffic.

--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26  Orchard Park, NY 14127
--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp

imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

2004-01-04 Thread Hajo Beckefeld

Hi List!

I'm running a cyrus IMAP server 2.1.16 on an Linux 2.2.25 machine.
When I try connect from an Mozilla 1.6/1.7 IMAP client, I can't 
establish the connection. The log just says:

Jan  4 13:52:43 jinn master[12215]: about to exec /usr/cyrus/bin/imapd
Jan  4 13:52:43 jinn imap[12215]: executed
Jan  4 13:52:43 jinn imapd[12215]: accepted connection
Jan  4 13:52:50 jinn master[2293]: process 12215 exited, signaled to 
death by 11

With Mozilla-1.5 Mail everything works fine!?!

Jan  4 14:21:58 jinn master[12230]: about to exec /usr/cyrus/bin/imapd
Jan  4 14:21:58 jinn imap[12230]: executed
Jan  4 14:21:58 jinn imapd[12230]: accepted connection
Jan  4 14:22:03 jinn imapd[12230]: login: 
luke.beckefeld-online.de[192.168.1.20] hajo plaintext
Jan  4 14:22:04 jinn imapd[12230]: seen_db: user hajo opened 
/var/imap/user/h/hajo.seen
Jan  4 14:22:04 jinn imapd[12230]: open: user hajo opened INBOX

Here is my configure command for cyrus imapd:

./configure  --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --infodir=/usr/share/info --mandir=/usr/share/man 
--with-auth=unix --with-sasl=/usr/lib --disable-krb 
--with-cyrus-user=cyrus --with-cyrus-group=mail --enable-listext 
--enable-annotatemore --enable-murder

and my imapd.conf

configdirectory: /var/imap
partition-default: /var/spool/imap
servername: mail.beckefeld-online.de
admins: cyrus
allowanonymouslogin: no
# certificate key files
tls_cert_file: /var/imap/server.pem
tls_key_file: /var/imap/server.pem
# The  mechanism used by the server to verify plaintext
# passwords.  Possible values  also  include  "sasldb",
# "kerberos_v4", "passwd", and "shadow".
#sasl_pwcheck_method: saslauthd
sasl_pwcheck_method: saslauthd
Thanks a lot for any kind of hint!
Hajo
Btw: Happy new Year!

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

Re: imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

imapd dies when connecting with Mozilla-1.6beta Mail IMAP account

15 matches

Site Navigation

Mail list logo

Footer information