Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Size limit ends in endless upload #102

Closed
JobbeDeluxe opened this issue Jun 11, 2017 · 16 comments
Closed

Size limit ends in endless upload #102

JobbeDeluxe opened this issue Jun 11, 2017 · 16 comments
Labels
Milestone

Comments

@JobbeDeluxe
Copy link

If the email size limit is aktiv and you try to send something (just a file) bigger than this limit, the send will fail and delta chat will try to resend it. This will be repeated for a unlimited time. And every time will be send the max data limit. So it will consume the mobile data as well.
After 3 or more tries, delta should say something or abort the sending?

@r10s r10s added the bug label Jun 12, 2017
@r10s
Copy link
Member

r10s commented Jun 12, 2017

Thank you very much, for this, I will check this. Do you know anything about the typical size limits and/or error codes one gets?

@JobbeDeluxe
Copy link
Author

On my one, Linux with postfix and dovecot the default size limit is 10 MB.
I now removed the limit.
I will try to get an log file from the error today.

@JobbeDeluxe
Copy link
Author

JobbeDeluxe commented Jun 12, 2017

mail.log.txt

I have test this some time.
It seams so be that the connection will be disconnected after size limit is reached. And DeltChat is try to resend ever minute or on every reconnect like mobile data changed.
I can force the re upload by switching Wlan off an on again.
The log ist just i try to upload and wait 5 minutes:
Jun 12 20:12:32 TestServer dovecot: imap-login: Disconnected (no auth attempts in 17 secs): user=<>, rip=0my.0ip.add.000, lip=0my.local.addr.serv, TLS, session=<fCRFQ8dRWd1ZD+4i> Jun 12 20:12:33 TestServer dovecot: imap-login: Login: user=<User>, method=PLAIN, rip=0my.0ip.add.000, lip=0my.local.addr.serv, mpid=16574, TLS, session=<uyY6Q8dR58JZD+4i> Jun 12 20:12:33 TestServer dovecot: imap-login: Disconnected (no auth attempts in 18 secs): user=<>, rip=0my.0ip.add.000, lip=0my.local.addr.serv, TLS, session=<alZRQ8dRvoRZD+4i> Jun 12 20:12:33 TestServer dovecot: imap-login: Login: user=<User>, method=PLAIN, rip=0my.0ip.add.000, lip=0my.local.addr.serv, mpid=16575, TLS, session=<0iRIQ8dRce9ZD+4i> Jun 12 20:13:12 TestServer dovecot: imap(User): Connection closed (IDLE running for 0.001 + waiting input for 332.938 secs, 2 B in + 10+0 B out, state=wait-input) in=28 out=703 Jun 12 20:13:12 TestServer dovecot: imap(User): Connection closed (IDLE running for 0.001 + waiting input for 332.902 secs, 2 B in + 10+0 B out, state=wait-input) in=27 out=705 Jun 12 20:13:15 TestServer dovecot: imap(User): Connection closed (IDLE running for 0.001 + waiting input for 42.634 secs, 2 B in + 10+0 B out, state=wait-input) in=28 out=652 Jun 12 20:13:15 TestServer dovecot: imap(User): Connection closed (IDLE running for 0.001 + waiting input for 42.411 secs, 2 B in + 10+0 B out, state=wait-input) in=27 out=654 Jun 12 20:13:16 TestServer dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=0my.0ip.add.000, lip=0my.local.addr.serv, TLS, session=<HE7jRcdRpOJZ9XNf> Jun 12 20:13:16 TestServer dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=0my.0ip.add.000, lip=0my.local.addr.serv, TLS, session=<lXTjRcdRpuJZ9XNf> Jun 12 20:13:16 TestServer dovecot: imap-login: Login: user=<User>, method=PLAIN, rip=0my.0ip.add.000, lip=0my.local.addr.serv, mpid=16598, TLS, session=<bkzjRcdRo+JZ9XNf> Jun 12 20:13:16 TestServer dovecot: imap-login: Login: user=<User>, method=PLAIN, rip=0my.0ip.add.000, lip=0my.local.addr.serv, mpid=16599, TLS, session=<+OrkRcdRpeJZ9XNf> Jun 12 20:13:27 TestServer dovecot: imap(User): Disconnected for inactivity in=1018 out=35615 Jun 12 20:13:27 TestServer dovecot: imap(User): Disconnected for inactivity in=1210 out=6071 Jun 12 20:13:42 TestServer dovecot: imap-login: Login: user=<User>, method=PLAIN, rip=0my.0ip.add.000, lip=0my.local.addr.serv, mpid=16614, TLS, session=</klxR8dRq+JZ9XNf> Jun 12 20:13:56 TestServer postfix/smtpd[16403]: timeout after AUTH from My.IPS.Provider[0my.0ip.add.000] Jun 12 20:13:59 TestServer postfix/smtpd[16403]: disconnect from My.IPS.Provider[0my.0ip.add.000] ehlo=1 auth=1 commands=2 Jun 12 20:14:00 TestServer postfix/smtpd[16403]: connect from My.IPS.Provider[0my.0ip.add.000] Jun 12 20:14:02 TestServer postfix/smtpd[16403]: 727C5C6080D: client=My.IPS.Provider[0my.0ip.add.000], sasl_method=PLAIN, sasl_username=User Jun 12 20:14:02 TestServer postfix/cleanup[16617]: 727C5C6080D: message-id=<Mr.WT7ZwHAhsnr.User@my_mail_adress.org> Jun 12 20:14:05 TestServer postfix/smtpd[16403]: warning: 727C5C6080D: queue file size limit exceeded Jun 12 20:14:15 TestServer postfix/smtpd[16403]: disconnect from My.IPS.Provider[0my.0ip.add.000] ehlo=1 auth=1 mail=1 rcpt=1 data=0/1 quit=1 commands=5/6 Jun 12 20:15:25 TestServer dovecot: imap(User): Connection closed (IDLE running for 0.001 + waiting input for 128.689 secs, 2 B in + 10+0 B out, state=wait-input) in=28 out=669 Jun 12 20:15:25 TestServer dovecot: imap(User): Connection closed (IDLE running for 0.001 + waiting input for 128.843 secs, 2 B in + 10+0 B out, state=wait-input) in=27 out=671 Jun 12 20:15:41 TestServer dovecot: imap-login: Login: user=<User>, method=PLAIN, rip=0my.0ip.add.000, lip=0my.local.addr.serv, mpid=16656, TLS, session=<1u9xTsdRx+JZ9XNf> Jun 12 20:15:41 TestServer dovecot: imap-login: Login: user=<User>, method=PLAIN, rip=0my.0ip.add.000, lip=0my.local.addr.serv, mpid=16657, TLS, session=<reWDTsdRxuJZ9XNf> Jun 12 20:15:55 TestServer dovecot: imap-login: Login: user=<User>, method=PLAIN, rip=0my.0ip.add.000, lip=0my.local.addr.serv, mpid=16659, TLS, session=<+ptkT8dRyeJZ9XNf> Jun 12 20:16:16 TestServer postfix/smtpd[16670]: connect from My.IPS.Provider[0my.0ip.add.000] Jun 12 20:16:18 TestServer postfix/smtpd[16670]: D7157C6080D: client=My.IPS.Provider[0my.0ip.add.000], sasl_method=PLAIN, sasl_username=User Jun 12 20:16:18 TestServer postfix/cleanup[16671]: D7157C6080D: message-id=<Mr.WT7ZwHAhsnr.User@my_mail_adress.org> Jun 12 20:16:21 TestServer postfix/smtpd[16670]: warning: D7157C6080D: queue file size limit exceeded Jun 12 20:16:26 TestServer postfix/smtpd[16670]: disconnect from My.IPS.Provider[0my.0ip.add.000] ehlo=1 auth=1 mail=1 rcpt=1 data=0/1 quit=1 commands=5/6 Jun 12 20:16:34 TestServer postfix/smtpd[16196]: disconnect from 0my.mobil.addr.000[0my.mobil.addr.000] ehlo=1 auth=1 mail=1 rcpt=1 data=0/1 commands=4/5 Jun 12 20:17:16 TestServer dovecot: imap(User): Connection closed (IDLE running for 0.001 + waiting input for 1457.214 secs, 2 B in + 10+0 B out, state=wait-input) in=1206 out=3348 Jun 12 20:17:26 TestServer postfix/smtpd[16670]: connect from My.IPS.Provider[0my.0ip.add.000] Jun 12 20:17:41 TestServer postfix/smtpd[16670]: 2A478C6080A: client=My.IPS.Provider[0my.0ip.add.000], sasl_method=PLAIN, sasl_username=User Jun 12 20:17:41 TestServer postfix/cleanup[16671]: 2A478C6080A: message-id=<Mr.WT7ZwHAhsnr.User@my_mail_adress.org> Jun 12 20:17:51 TestServer postfix/smtpd[16670]: warning: 2A478C6080A: queue file size limit exceeded Jun 12 20:18:01 TestServer postfix/smtpd[16670]: disconnect from My.IPS.Provider[0my.0ip.add.000] ehlo=1 auth=1 mail=1 rcpt=1 data=0/1 quit=1 commands=5/6 Jun 12 20:18:01 TestServer postfix/smtpd[16196]: connect from My.IPS.Provider[0my.0ip.add.000] Jun 12 20:18:08 TestServer postfix/smtpd[16196]: 1F4A9C6080A: client=My.IPS.Provider[0my.0ip.add.000], sasl_method=PLAIN, sasl_username=User Jun 12 20:18:08 TestServer postfix/cleanup[16203]: 1F4A9C6080A: message-id=<Mr.WT7ZwHAhsnr.User@my_mail_adress.org> Jun 12 20:18:10 TestServer postfix/smtpd[16196]: warning: 1F4A9C6080A: queue file size limit exceeded Jun 12 20:18:20 TestServer postfix/smtpd[16196]: disconnect from My.IPS.Provider[0my.0ip.add.000] ehlo=1 auth=1 mail=1 rcpt=1 data=0/1 quit=1 commands=5/6 Jun 12 20:20:12 TestServer postfix/anvil[16200]: statistics: max connection rate 2/60s for (smtps:0my.0ip.add.000) at Jun 12 20:18:02 Jun 12 20:20:12 TestServer postfix/anvil[16200]: statistics: max connection count 1 for (smtps:0my.0ip.add.000) at Jun 12 20:14:00 Jun 12 20:20:12 TestServer postfix/anvil[16200]: statistics: max cache size 1 at Jun 12 20:16:16 Jun 12 20:20:51 TestServer dovecot: imap(User): Connection closed (IDLE running for 0.001 + waiting input for 1029.489 secs, 2 B in + 10+0 B out, state=wait-input) in=24 out=831

@mukhametshin
Copy link

mukhametshin commented Sep 16, 2017

I confirm the bug (however I currently have no screenshots or logs to prove it). DC has eaten all my cellular traffic for the month in couple of minutes as I was trying to send a large file to a friend of mine over DC. The friend didn't receive the file and now I kill DC if I'm connected over cellular data, and start it if I'm online over wifi.

In disregard of this bug it would be nice to have an option "connect over wifi only" or "send attachments (files) over wifi only" to be introduced.

@r10s
Copy link
Member

r10s commented Sep 16, 2017

+1

@r10s
Copy link
Member

r10s commented Sep 16, 2017

I think, in general, Delta Chat should stop trying after a number of attemps (not counting the cases where there is no connection at the moment of failure)

@lobit0 lobit0 mentioned this issue Nov 17, 2017
@r10s r10s added this to the Release 1.0 milestone Mar 10, 2018
@testbird
Copy link

testbird commented Apr 10, 2018

Is there something else then reinstalling to stop looping?
It's a grave battery and data usage bug, possibly I also overlooked this reason when things got frozen in the past.

@JobbeDeluxe
Copy link
Author

I was able to remove the file that is too large. Than it was done.

@testbird
Copy link

Ah, ok removing from storage, good idea, thanks!

@testbird
Copy link

MUA log from sending a too large message:

ESMTP 235 Authentication succeeded
ESMTP MAIL FROM:<...>
SMTP 552-Requested mail action aborted: exceeded storage allocation 
SMTP 552 Mail size limit exceeded.

@r10s
Copy link
Member

r10s commented May 24, 2018

in general, we should not try to send messages that are "too big"

@testbird
Copy link

testbird commented May 25, 2018

The problem is also prominent with accounts with rather low limits like 10MB. Thus, the need to determine the limit or catch the 552 error from above.

@kecksk0enig
Copy link

kecksk0enig commented Jul 5, 2018

This one hit me too, tried to upload 50MB video...
screenshot_20180705-105442
screenshot_20180705-105336

I also looked at the logs on android, seems the line in:
deltachat-core is faulty and leads to endless retries...
https://github.com/deltachat/deltachat-core/blob/a3e9cc7e649744be5607731d7a5dba89f1476d6c/src/dc_job.c#L615

@r10s
Copy link
Member

r10s commented Jul 10, 2018

@kecksk0enig thanks for the report, i think we will target this issue with the next release, 0.20.0 then

@r10s
Copy link
Member

r10s commented Jul 11, 2018

should be fixed by deltachat/deltachat-core#209:

  • if a message cannot be sent for any reasons, and there is network available after the failure, Delta tries over after 2 seconds and after 60 seconds (we do two tries to catch server-overloads and such things)
  • if the message still cannot be sent, the job is removed and the message is marked as being failed to send.
  • in the message info, the reason for failure is shown.

this approach should catch the issue above - as well as many other issues as bad recipients, quota and so on.

@r10s r10s closed this as completed Jul 11, 2018
@r10s
Copy link
Member

r10s commented Jul 12, 2018

i've refined the cases for low storage and too large mails in deltachat/deltachat-core@c6b158a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants