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

Sending mail suddenly times out - Can send with Thunderbird #984

Open
ryspace opened this issue Mar 11, 2024 · 3 comments
Open

Sending mail suddenly times out - Can send with Thunderbird #984

ryspace opened this issue Mar 11, 2024 · 3 comments

Comments

@ryspace
Copy link

ryspace commented Mar 11, 2024

I've had this email configured via mw for quite a while (well over a year), and suddenly over the past couple weeks, I cannot send email via neomutt. Every time I try, I get a timeout.

I can switch over to Thunderbird and send the email just fine.

Any idea what might be happening?

I have noticed in the past that I'll have to accept a new certificate from time to time with Thunderbird (and K-9 on my phone), but that's never been brought up in neomutt. I'm wondering if that somehow has something to do with it?

I should add that this is a mailserver that was set up using your emailwiz script

@ZaTank
Copy link

ZaTank commented Apr 1, 2024

I've also had trouble with suddenly losing the ability to send mail (albeit with an Outlook account), and I wonder if this issue is related. Viewing logs with neomutt -d 2 hasn't given any information, and I can switch to my emailwiz server and send mail just fine.

@tjex
Copy link

tjex commented Apr 18, 2024

whenever this has happened to me, it's been because of a gpg problem. Either I moved the email.gpg file in the password store, or there was an issue with pinentry, or ...

@ryspace
Copy link
Author

ryspace commented Jun 4, 2024

whenever this has happened to me, it's been because of a gpg problem. Either I moved the email.gpg file in the password store, or there was an issue with pinentry, or ...

I had moved my password long ago, but I updated my msmtp config and ~/.mbsyncrc to reflect its new location. Is there somewhere else I need to update this?

(It's been long enough that I don't remember if the timelines correlate, so I'm willing to accept that it may be the issue...just need to know what other configuration change I missed when I did it)

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

No branches or pull requests

3 participants