I found it and fixed it :-)
Seems like mozilla doesn't like a final space before the closing ) in a
status response.
I've also cleaned up imapcommands to use the ci_write wrapper for
writing output to clients which helped with making dbmail's tcp
behaviour more compliant.
Mozilla/thunderbird will now behave as expected when checking all imap
folders.
Paul J Stevens wrote:
> More on this;
>
> I've fixed imapcommands to strictly use ci_write. The packet trace now
> looks real clean in terms of tcp. Still no luck though. I'll have to use
> another imap server as comparison. Mozilla apparently doesn't like
> something about dbmail's responses and just disconnects, period.
>
> Paul J Stevens wrote:
>
>> Following up on myself,
>>
>>
>> Looks like imapcommands.c writes after the client sends FIN packets. I
>> guess the ci_write patch should be expanded to include imapcommands as
>> well.
>>
>> Mozilla closes the connection by sending FIN after receiving response
>> to a command. If the server then wants to send OK tags after that the
>> client barfs and sends RST.
>>
>> I've attached a ethereal capture.
>>
>> Paul J Stevens wrote:
>>
>>>
>>> When I specify mentioned option in mozilla or thunderbird, the client
>>> will happily check all imap mailfolders on uw-imapd. However, this
>>> does not work for dbmail.
>>>
>>> This very annoying problem was identified today as being a dbmail
>>> issue, instead of a client issue.
>>>
>>> Looks like IMAPClientHandler bails out when it shouldn't. I'll see
>>> what I can find.
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Dbmail-dev mailing list
>> Dbmail-dev@dbmail.org
>> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>
>
--
________________________________________________________________
Paul Stevens mailto:paul@nfg.nl
NET FACILITIES GROUP PGP: finger paul@nfg.nl
The Netherlands________________________________http://www.nfg.nl
Seems like mozilla doesn't like a final space before the closing ) in a
status response.
I've also cleaned up imapcommands to use the ci_write wrapper for
writing output to clients which helped with making dbmail's tcp
behaviour more compliant.
Mozilla/thunderbird will now behave as expected when checking all imap
folders.
Paul J Stevens wrote:
>
> I've fixed imapcommands to strictly use ci_write. The packet trace now
> looks real clean in terms of tcp. Still no luck though. I'll have to use
> another imap server as comparison. Mozilla apparently doesn't like
> something about dbmail's responses and just disconnects, period.
>
> Paul J Stevens wrote:
>
>> Following up on myself,
>>
>>
>> Looks like imapcommands.c writes after the client sends FIN packets. I
>> guess the ci_write patch should be expanded to include imapcommands as
>> well.
>>
>> Mozilla closes the connection by sending FIN after receiving response
>> to a command. If the server then wants to send OK tags after that the
>> client barfs and sends RST.
>>
>> I've attached a ethereal capture.
>>
>> Paul J Stevens wrote:
>>
>>>
>>> When I specify mentioned option in mozilla or thunderbird, the client
>>> will happily check all imap mailfolders on uw-imapd. However, this
>>> does not work for dbmail.
>>>
>>> This very annoying problem was identified today as being a dbmail
>>> issue, instead of a client issue.
>>>
>>> Looks like IMAPClientHandler bails out when it shouldn't. I'll see
>>> what I can find.
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Dbmail-dev mailing list
>> Dbmail-dev@dbmail.org
>> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>
>
--
________________________________________________________________
Paul Stevens mailto:paul@nfg.nl
NET FACILITIES GROUP PGP: finger paul@nfg.nl
The Netherlands________________________________http://www.nfg.nl