GNOME Bugzilla – Bug 714053
Improved SMTP error reporting
Last modified: 2019-03-31 07:13:10 UTC
---- Reported by eric@yorba.org 2013-01-09 17:15:00 -0800 ---- Original Redmine bug id: 6200 Original URL: http://redmine.yorba.org/issues/6200 Searchable id: yorba-bug-6200 Original author: Eric Gregory Original description: 1. Compose a new message 2. Attach a big file. For Gmail, "big" is anything larger than 25 MB 3. Hit send Notice how the message sits in your outbox forever. Eventually you'll get something like this in the log: > [deb] 17:09:47 [smtp.gmail.com/default:465] SMTP Response: 552-5.2.3 Your message exceeded Google's message size limits. Please visit 552-5.2.3 http://support.google.com/mail/bin/answer.py?answer=8770 to review 552 5.2.3 our size guidelines. px5sm3700310igc.0 > > [deb] 17:09:47 smtp-outbox-folder.vala:499: SMTP send mail error: Unable to send message: 552-5.2.3 Your message exceeded Google's message size limits. Please visit [deb] 17:09:47 [smtp.gmail.com/default:465] SMTP Request: quit [deb] 17:09:48 [smtp.gmail.com/default:465] SMTP Response: 221 2.0.0 closing connection px5sm3700310igc.0 > > [deb] 17:09:48 smtp-outbox-folder.vala:123: Outbox postman send error, retrying: Unable to send message: 552-5.2.3 Your message exceeded Google's message size limits. Please visit [deb] 17:09:48 smtp-outbox-folder.vala:119: Outbox postman: Sending "Sample of large file" (ID:1)... There's two things we can do better here: * Detect the SMTP error and report it to the user. The outbox should be smart enough to not send the same message again. * When we log on to the SMTP server, we should remember the SIZE parameter (if present) and make sure our outgoing messages don't exceed the provided size. Related issues: related to geary - Feature #5281: Better error reporting (Open) related to geary - 7481: report SMTP send errors to the user (Fixed) related to geary - 7432: Memory leak when repeatedly unable to send email (Open) related to geary - 6797: Cannot remove mail from outbox (Fixed) duplicated by geary - 6788: Large upload network usage (Duplicate) ---- Additional Comments From geary-maint@gnome.bugs 2013-09-17 15:54:00 -0700 ---- ### History #### #1 Updated by Jim Nelson 11 months ago * **Priority** changed from _Normal_ to _High_ * **Target version** set to _0.3.0_ We should do both. #### #2 Updated by Jim Nelson 10 months ago * **Category** changed from _engine_ to _server-support_ #### #3 Updated by Jim Nelson 9 months ago * **Keywords** set to _string-change_ #### #4 Updated by Jim Nelson 9 months ago * **Target version** changed from _0.3.0_ to _0.4.0_ #### #5 Updated by Charles Lindsay 8 months ago * **Subject** changed from _Messages with large attachments sit in the outbox forever_ to _Messages with certain attachments sit in the outbox forever_ This also apparently happens for messages with executable file attachments. #### #6 Updated by Jim Nelson 3 months ago * **Category** changed from _server-support_ to _outbox_ #### #7 Updated by Jim Nelson 2 months ago * **Target version** changed from _0.4.0_ to _0.5.0_ We need better SMTP error handling and reporting, but #7481 and #4629 will suffice for 0.4. Let's pick this up again when we start 0.5. --- Bug imported by chaz@yorba.org 2013-11-21 20:24 UTC --- This bug was previously known as _bug_ 6200 at http://redmine.yorba.org/show_bug.cgi?id=6200 Unknown milestone "unknown in product geary. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution
Created attachment 286929 [details] Geary error message via notify daemon
Created attachment 286931 [details] frame running across top of window
This bug looks to be the same as reported above; although the attachment size is *much* smaller in my case, approx 3MB's. Running Geary 0.8 on Linux 3.16+; x86_64 ; GTK+ 3.12.2. I just installed 0.8 and tested it by sending an email with an attachment of approx 3 MB's and the problem occurred immediately--so it seems easy to reproduce (bug is carried over from version 0.7+). When I send an email with an attachment of approx. 2 or 3 MB's, the email is (or seems to be) sent but not written to "Sent/FCC" folder and stays in Outbox; The error message is: "Geary encountered an error saving a Sent message to Sent Mail. The message will stay in your Outbox folder until you delete it." It is difficult to know IF message actually got sent; but checking with my recipients seems to confirm message was indeed sent. (Needless to say, this issue is really a problem for anyone who has to send documents or presentations on a regular basis.) I took screenshots and am attaching those to the ticket.
stef_204: your error seems a different one, that I've already seen in the past: the message is sent, but could not be saved to the sent folder. This may be fixed now. Original report from Eric says, IIUC, that the message was not even sent because of the file size limit. I'm now trying to reproduce it on a Gmail account. I launch Geary this way: geary -d --log-network I attach a 30MB flac file, hit send button and after a while I get an error report. (since a month or so we have in master branch a nice error reporting) As you can see below, the report tells me about the message size limit. The message stays in the Outbox folder, without attachment (correct). TODO: It would be nice if Geary was able to check and remember these limits, in order to warn the user before sending the message. Geary version: master~gb627fd4f GTK version: 3.22.26 Desktop: GNOME Problem type: GEARY_PROBLEM_TYPE_SERVER_ERROR Account type: GMAIL Service type: GEARY_SERVICE_SMTP Endpoint: smtp.gmail.com/default:465 Error type: GearySmtpError 6 Message: Unable to send message: 552-5.2.3 Your message exceeded Google's message size limits. Please visit Back trace: - geary_account_problem_report_construct - geary_service_problem_report_construct - geary_smtp_outbox_folder_notify_report_problem - geary_smtp_outbox_folder_start_postman_async_co - g_simple_proxy_resolver_set_uri_proxy - g_task_attach_source - geary_smtp_outbox_folder_postman_send_co - g_simple_proxy_resolver_set_uri_proxy - g_task_attach_source - geary_smtp_outbox_folder_send_email_async_co - g_simple_proxy_resolver_set_uri_proxy - g_task_attach_source - geary_smtp_client_session_logout_async_co - g_simple_proxy_resolver_set_uri_proxy - g_task_attach_source - geary_smtp_client_connection_disconnect_async_co - g_simple_proxy_resolver_set_uri_proxy - g_task_attach_source - g_io_stream_clear_pending - g_simple_proxy_resolver_set_uri_proxy - g_simple_proxy_resolver_set_uri_proxy - g_list_sort_with_data - g_main_context_dispatch - g_main_context_dispatch - g_main_context_iteration - g_application_run - _vala_main - __libc_start_main - _start
This seems to be a special case of Bug 713006 - we are now at least reporting an error has occurred and let the user address it (retry sending, delete the message), but we should also be looking at the SMTP error code an presenting a more specific, localised error message to the user. We might want to do that on a per-message basis as well, by recording the SMTP error code in the outbox database.
*** Bug 714471 has been marked as a duplicate of this bug. ***
See also gitlab issue #12: https://gitlab.gnome.org/GNOME/geary/issues/12
*** Bug 726289 has been marked as a duplicate of this bug. ***
*** Bug 713744 has been marked as a duplicate of this bug. ***
Closing this in favour of https://gitlab.gnome.org/GNOME/geary/issues/353