deltachat / deltachat-desktop

Email-based instant messaging for Desktop.
GNU General Public License v3.0
941 stars 166 forks source link

To many open Connections for Exchange Server #1527

Closed cracker0dks closed 3 years ago

cracker0dks commented 4 years ago

Our external Exchange Expert wrote to me:

"Ich nehme an dass hier die Anwendung ihre Sessions nicht sauber trennt bevor sie neue aufbaut oder tatsächlich viele gleichzeitig betreiben will. Um beim Test sicher zu gehen parallel keine anderen IMAP clients betreiben. Bitte kontaktieren Sie den Hersteller und bitten um support."

English something like:

"I think your application does not close the session correctly before establishing a new one. [...] Please ask the software producer for help."

I closed Thunderbird and any other mail client and still got this error.

In the DeltaChat client / and any other mail client I want to connect then, I can't login for a short amount of time (Message: User/Password wrong) If I close the DC Desktop Client, then wait a few seconds, I can login from any other client again.

Greetings

r10s commented 4 years ago

not sure about desktop in special, but the core typically uses 3 imap-connections. if interaction with non-delta-clients and/or multi device is not needed, the "Watch DeltaChat folder" and "Watch Sent folder" can be disabled at "Settings" and you go down to only 1 imap-connection this way.

this is the theory, of course, there can be bugs :)

cracker0dks commented 4 years ago

Yeah I already removed watch inbox and moved deltaChat msgs into the DeltaChat folder with a server rule. (Also removed watched folders by thunderbird and Android dc client just in case). But still get the error even when only dc desktop is running.

hpk42 commented 4 years ago

@cracker0dks do you have and switch between multiple desktop accounts? If you do, can you see to get a recording of the log before/during/after the switch? @jikstra @Simon-Laux @nicodh maybe switching desktop accounts does not terminates the just-left account correctly?

my 2c

cracker0dks commented 4 years ago

This even happens without switch. Fresh start and only using this one account. I will delete the second account, maybe this helps finding the bug.

gerryfrancis commented 4 years ago

@cracker0dks I wonder if the log file you provided really is from Delta Chat Desktop version 1.2.0:

"deltachat_core_version":"v1.26.0"

cracker0dks commented 4 years ago

I wrote: "This log is from some days ago, but still get the same error from time to time" should I post a new log as well ?

gerryfrancis commented 4 years ago

@cracker0dks I guess this log in here is not very helpful, anyway. Please provide another one, the time period should be some hours to see what is going on. Thanks in advance.

gerryfrancis commented 4 years ago

@cracker0dks Any news on this?

cracker0dks commented 4 years ago

Oh sorry, didn't saw your post. I reinstalled 3 Days ago, same problem. Here is the log since then (About 3 Days, ~5MB) https://cloud13.de/index.php/s/XRYqmn7WJ8xBnEe thanks

gerryfrancis commented 4 years ago

@cracker0dks Thank you for the log, though I cannot locate where the problem lies. My best guess is that multiple clients are logged in with your account. (One client may use more than one connection.) Remember, the screenshot in your first post of the issue says "16 objects of type Session", so the maximum of 16 connections per user does include those from/to Outlook and any other client, too.

cracker0dks commented 4 years ago

I closed every other client and still got this problem. Also should work even with all of my 3 clients running because all in all there should not be more than 6 Subed folders (6 Connections). Changed the max connection limits in thunderbird / subed folders and removed DC from watching any other folder than DC (added server rule to move dc mails to dc folder).

hpk42 commented 4 years ago

i couldn't read that log -- what's ".tsv"?

On Thu, Apr 09, 2020 at 12:25 -0700, Cracker wrote:

Oh sorry, didn't saw your post. I reinstalled 3 Days ago, same problem. Here is the log since then (About 3 Days, ~5MB) https://cloud13.de/index.php/s/XRYqmn7WJ8xBnEe thanks

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/deltachat/deltachat-desktop/issues/1527#issuecomment-611710588

cracker0dks commented 4 years ago

logfile from DC Dekstop, just a text file I think.

gerryfrancis commented 4 years ago

logfile from DC Dekstop, just a text file I think.

Correct, all log files from Delta Chat Desktop have this extension.

hpk42 commented 4 years ago

ah k -- for some reason my libreoffice decided to suggest opening it with utf16 resulting in chinese signs mostly ... forcing latin1/ascii helped.

anyway, the log file contains tons of failed-to-login messages as warnings. And it seems it does not show INFO messages showing even a single successful login.

I think we first need to get better logs (by default) with desktop as this is not really helpful. cc @jikstra @simon-laux @nicodh At least INFO level messages from core should be shown by default.

On Sat, Apr 11, 2020 at 11:30 -0700, Cracker wrote:

logfile from DC Dekstop, just a text file I think.

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/deltachat/deltachat-desktop/issues/1527#issuecomment-612484530

Simon-Laux commented 4 years ago

Sure we can change the debug level of core info messages, but this will apply only in the next release after changing it. See the logging options for how to log everything now: https://github.com/deltachat/deltachat-desktop/blob/master/README.md#logging-options

TSV is the same as CSV, only difference is that it uses tabs instead of commas, best opened with ms excel or libreoffice calc. Also the format should be utf-8... strange that you get Chinese signs.

On Apr 12, 2020, at 8:01 PM, holger krekel notifications@github.com wrote:

ah k -- for some reason my libreoffice decided to suggest opening it with utf16 resulting in chinese signs mostly ... forcing latin1/ascii helped.

anyway, the log file contains tons of failed-to-login messages as warnings. And it seems it does not show INFO messages showing even a single successful login.

I think we first need to get better logs (by default) with desktop as this is not really helpful. cc @jikstra @simon-laux @nicodh At least INFO level messages from core should be shown by default.

On Sat, Apr 11, 2020 at 11:30 -0700, Cracker wrote:

logfile from DC Dekstop, just a text file I think.

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/deltachat/deltachat-desktop/issues/1527#issuecomment-612484530 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

hpk42 commented 4 years ago

On Mon, Apr 13, 2020 at 04:58 -0700, Simon Laux wrote:

Sure we can change the debug level of core info messages, but this will apply only in the next release after changing it. See the logging options for how to log everything now: https://github.com/deltachat/deltachat-desktop/blob/master/README.md#logging-options

thanks -- let's also change the default as i don't want to teach users who already submitted a log that they should redo and try to use some command line options ....

TSV is the same as CSV, only difference is that it uses tabs instead of commas, best opened with ms excel or libreoffice calc. Also the format should be utf-8... strange that you get Chinese signs.

maybe libreoffice had some "default" cached from other documents -- whatever. not to worry about.

gerryfrancis commented 4 years ago

Maybe related to https://github.com/deltachat/deltachat-core-rust/issues/1402 .

cracker0dks commented 4 years ago

yes maybe, I only have one account but could be still the problem somehow

Simon-Laux commented 4 years ago

Does this still occur?

cracker0dks commented 4 years ago

I'm not using this server anymore but was present the last time I checked. You can close the issue if you want to. grafik