My mother can receive mail through Geary, but it does not send. It used to work fine, then out of the blue suddenly not. Anyone here who uses Geary to send Gmails?
Does it support OAUTH2? Because of security, Gmail doesnât allow connections only using password in general.
But do you have a log? Otherwise itâs impossible to know whatâs going on.
I have Geary v40.0 with Gmail & yes it works. yes it uses OAUTH2.
Currently, I use Mailspring as my main mail client, but I have had Geary set-up with Gmail for about a year & yes itâs still working fine right now.
Thanks for confirming, so weâll need the log of the program.
Did it ever work?
Can you confirm that you are able to send messages as well? Are you using v.40.0-6?
Yes, I can send. I specifically tested both send & receive in Geary.
My version as shown in the app âaboutâ window is (40.0 (tags/gnome-40.0-0-ge561775c1-dirty)
Thanks for confirming that.
She has since upgraded Geary to 40.0-7, but the problem still persists.
You have to enable imap in your settings in the web based interface
Yes, it did work. Hereâs the story: I install Manjaro Gnome and set up her email to work with Geary. She then goes back to Sweden and Geary works fine for a few days, but then suddenly doesnât allow to send messages.
I have posted about this before and the best guess at the time was that Google had changed some protocols, but @Riquez proves differently.
Hereâs the Geary log again:
Account identifier: account_01
Account provider: GEARY_SERVICE_PROVIDER_GMAIL
Service type: GEARY_PROTOCOL_SMTP
Service host: smtp.gmail.com
Error type: GearySmtpError 6
Message: ârcpt to:â failed: 553-5.1.3 The recipient address is not a valid RFC-5321 address. Learn
Back trace:
- geary_problem_report_construct
- geary_account_problem_report_construct
- geary_service_problem_report_construct
- application_main_window_update_account_status
- application_controller_expunge_accounts
- g_closure_invoke
- g_signal_handlers_destroy
- g_signal_emit_valist
- g_signal_emit
- g_flags_to_string
- g_object_notify_by_pspec
- g_closure_invoke
- g_signal_handlers_destroy
- g_signal_emit_valist
- g_signal_emit
- g_flags_to_string
- g_object_notify_by_pspec
- geary_client_service_notify_unrecoverable_error
- geary_smtp_capabilities_add_ehlo_response
- g_subprocess_new
- g_tls_database_lookup_certificates_issued_by_finish
- geary_smtp_capabilities_add_ehlo_response
- g_subprocess_new
- g_tls_database_lookup_certificates_issued_by_finish
- geary_smtp_capabilities_add_ehlo_response
- g_subprocess_new
- g_tls_database_lookup_certificates_issued_by_finish
- geary_smtp_capabilities_add_ehlo_response
- g_subprocess_new
- g_tls_database_lookup_certificates_issued_by_finish
- geary_smtp_capabilities_add_ehlo_response
- g_subprocess_new
- g_tls_database_lookup_certificates_issued_by_finish
- g_input_stream_close_async
- g_subprocess_new
- g_subprocess_new
- g_main_context_dispatch
- g_io_channel_new_file
- g_main_context_iteration
- g_application_run
- main
- __libc_start_main
- _start
It indicates that she is typing the recip email address wrong, but she has checked that and is confident she isnât.
This comes from Googleâs server, so it has nothing to do with protocols or the connection.
Can she send emails if she types the mail in the most basic format: test@example.com
This seems probably like a copy&paste error (additional spaces in before or after, weird quotation marks, etc.)
No, typing an email address âfrom scratchâ as opposed to pull it from Contacts still returns the error. The lady is confident sheâs not typing spaces or stuff like that into the address line.
@jrichard326 has posted some links that I still need to walk through.
Solved. The problem is down to a bug or a mayor annoyance in Geary.
If you type an invalid email address, such as a single character or a single word, the email will get stuck in the outbox. Any subsequent emails (even with correct addresses), refuse to send until the offending email first in the queue has been dealt with. The solution is to delete the offending email and do a reboot or $ pkill geary
.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.