Mutt - Interrupted system call / SMTP STARTTLS
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I am using arch linux with neomutt and sending email was possible. All of a sudden I get
could not connect to <server> (Interrupted system call).
here is my account settings
set imap_user = "user"
set imap_pass = "password"
set folder = "imap://user@server:143"
set spoolfile = "+INBOX"
mailboxes = +INBOX
set ssl_starttls=yes
set header_cache = ~/.mutt/<path>
set message_cachedir = ~/.mutt/<path>
set certificate_file = ~/.mutt/<path>
unset imap_passive
set imap_keepalive = 300
set mail_check = 120
set smtp_url = "smtp://user@server:587/"
set smtp_pass = "password"
set from="user@mail.com"
set use_from=yes
set realname = "myname"
set postponed = "+[folder]/Drafts"
set sort = reverse-date-received
color index red default ~P
set editor=vim
Did something change since the last update or are my settings wrong?
email mutt
asked Oct 22 '17 at 7:58
A.Dumas
536
add a comment |Â
up vote
0
down vote
favorite
I am using arch linux with neomutt and sending email was possible. All of a sudden I get
could not connect to <server> (Interrupted system call).
here is my account settings
set imap_user = "user"
set imap_pass = "password"
set folder = "imap://user@server:143"
set spoolfile = "+INBOX"
mailboxes = +INBOX
set ssl_starttls=yes
set header_cache = ~/.mutt/<path>
set message_cachedir = ~/.mutt/<path>
set certificate_file = ~/.mutt/<path>
unset imap_passive
set imap_keepalive = 300
set mail_check = 120
set smtp_url = "smtp://user@server:587/"
set smtp_pass = "password"
set from="user@mail.com"
set use_from=yes
set realname = "myname"
set postponed = "+[folder]/Drafts"
set sort = reverse-date-received
color index red default ~P
set editor=vim
Did something change since the last update or are my settings wrong?
email mutt
asked Oct 22 '17 at 7:58
A.Dumas
536
The rename of the binary to /usr/bin/neomutt was the only big change in the latest update that I’m aware of. Have you tried the git package as well?
– Philipp
Oct 22 '17 at 12:42
I might need to do this. This might be a solution. However after usingtelnet <mailserver> 587and receiving atimeoutI was wondering if the server might be down could this be the simple explanation?
– A.Dumas
Oct 22 '17 at 13:00
This looks like a bug, incorrect signal handling. Report it toneomutt's authors.
– SatÅ Katsura
Oct 22 '17 at 15:21
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am using arch linux with neomutt and sending email was possible. All of a sudden I get
could not connect to <server> (Interrupted system call).
here is my account settings
set imap_user = "user"
set imap_pass = "password"
set folder = "imap://user@server:143"
set spoolfile = "+INBOX"
mailboxes = +INBOX
set ssl_starttls=yes
set header_cache = ~/.mutt/<path>
set message_cachedir = ~/.mutt/<path>
set certificate_file = ~/.mutt/<path>
unset imap_passive
set imap_keepalive = 300
set mail_check = 120
set smtp_url = "smtp://user@server:587/"
set smtp_pass = "password"
set from="user@mail.com"
set use_from=yes
set realname = "myname"
set postponed = "+[folder]/Drafts"
set sort = reverse-date-received
color index red default ~P
set editor=vim
Did something change since the last update or are my settings wrong?
email mutt
asked Oct 22 '17 at 7:58
A.Dumas
536
I am using arch linux with neomutt and sending email was possible. All of a sudden I get
could not connect to <server> (Interrupted system call).
here is my account settings
set imap_user = "user"
set imap_pass = "password"
set folder = "imap://user@server:143"
set spoolfile = "+INBOX"
mailboxes = +INBOX
set ssl_starttls=yes
set header_cache = ~/.mutt/<path>
set message_cachedir = ~/.mutt/<path>
set certificate_file = ~/.mutt/<path>
unset imap_passive
set imap_keepalive = 300
set mail_check = 120
set smtp_url = "smtp://user@server:587/"
set smtp_pass = "password"
set from="user@mail.com"
set use_from=yes
set realname = "myname"
set postponed = "+[folder]/Drafts"
set sort = reverse-date-received
color index red default ~P
set editor=vim
Did something change since the last update or are my settings wrong?
email mutt
asked Oct 22 '17 at 7:58
A.Dumas
536
asked Oct 22 '17 at 7:58
A.Dumas
536
asked Oct 22 '17 at 7:58
A.Dumas
536
asked Oct 22 '17 at 7:58
A.Dumas
536
536
The rename of the binary to /usr/bin/neomutt was the only big change in the latest update that I’m aware of. Have you tried the git package as well?
– Philipp
Oct 22 '17 at 12:42
I might need to do this. This might be a solution. However after usingtelnet <mailserver> 587and receiving atimeoutI was wondering if the server might be down could this be the simple explanation?
– A.Dumas
Oct 22 '17 at 13:00
This looks like a bug, incorrect signal handling. Report it toneomutt's authors.
– SatÅ Katsura
Oct 22 '17 at 15:21
add a comment |Â
The rename of the binary to /usr/bin/neomutt was the only big change in the latest update that I’m aware of. Have you tried the git package as well?
– Philipp
Oct 22 '17 at 12:42
I might need to do this. This might be a solution. However after usingtelnet <mailserver> 587and receiving atimeoutI was wondering if the server might be down could this be the simple explanation?
– A.Dumas
Oct 22 '17 at 13:00
This looks like a bug, incorrect signal handling. Report it toneomutt's authors.
– SatÅ Katsura
Oct 22 '17 at 15:21
The rename of the binary to /usr/bin/neomutt was the only big change in the latest update that I’m aware of. Have you tried the git package as well?
– Philipp
Oct 22 '17 at 12:42
The rename of the binary to /usr/bin/neomutt was the only big change in the latest update that I’m aware of. Have you tried the git package as well?
– Philipp
Oct 22 '17 at 12:42
I might need to do this. This might be a solution. However after using
telnet <mailserver> 587 and receiving a timeout I was wondering if the server might be down could this be the simple explanation?– A.Dumas
Oct 22 '17 at 13:00
I might need to do this. This might be a solution. However after using
telnet <mailserver> 587 and receiving a timeout I was wondering if the server might be down could this be the simple explanation?– A.Dumas
Oct 22 '17 at 13:00
This looks like a bug, incorrect signal handling. Report it to
neomutt's authors.– SatÅ Katsura
Oct 22 '17 at 15:21
This looks like a bug, incorrect signal handling. Report it to
neomutt's authors.– SatÅ Katsura
Oct 22 '17 at 15:21
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399664%2fmutt-interrupted-system-call-smtp-starttls%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
The rename of the binary to /usr/bin/neomutt was the only big change in the latest update that I’m aware of. Have you tried the git package as well?
– Philipp
Oct 22 '17 at 12:42
I might need to do this. This might be a solution. However after using
telnet <mailserver> 587and receiving atimeoutI was wondering if the server might be down could this be the simple explanation?– A.Dumas
Oct 22 '17 at 13:00
This looks like a bug, incorrect signal handling. Report it to
neomutt's authors.– SatÅ Katsura
Oct 22 '17 at 15:21