starred/nmail

Fork 0

mirror of https://github.com/d99kris/nmail.git synced 2026-04-26 09:46:01 +03:00

[GH-ISSUE #97] [Bug] Fail to connect to mail account after changing computer's hostname #84

New issue

Closed

opened 2026-03-03 01:19:40 +03:00 by kerem · 6 comments

kerem commented

2026-03-03 01:19:40 +03:00

Owner

Originally created by @krackout on GitHub (Mar 31, 2022).
Original GitHub issue: https://github.com/d99kris/nmail/issues/97

Originally assigned to: @d99kris on GitHub.

I changed my computer's hostname and after that nmail opened, but could not connect. After I restored the hostname (hostname command, no reboot), closed-reopened nmail, it could connect again.

Can't tell if it's looking for runtime initial setup hostname or compile time hostname.

Originally created by @krackout on GitHub (Mar 31, 2022). Original GitHub issue: https://github.com/d99kris/nmail/issues/97 Originally assigned to: @d99kris on GitHub. I changed my computer's hostname and after that nmail opened, but could not connect. After I restored the hostname (`hostname` command, no reboot), closed-reopened nmail, it could connect again. Can't tell if it's looking for runtime initial setup hostname or compile time hostname.

kerem closed this issue

2026-03-03 01:19:40 +03:00

kerem commented

2026-03-03 01:19:40 +03:00

Author

Owner

@d99kris commented on GitHub (Mar 31, 2022):

Could you share which email service you are using? And also which OS/distro?
I'd like to try reproduce the problem.

@d99kris commented on GitHub (Mar 31, 2022): Could you share which email service you are using? And also which OS/distro? I'd like to try reproduce the problem.

kerem commented

2026-03-03 01:19:40 +03:00

Author

Owner

@krackout commented on GitHub (Mar 31, 2022):

gmx.com mail provider, IMAP enabled; free service, you can give it a try.

Debian 11 Bullseye, 64bit, fully updated. Compiled and run on the same machine.

@krackout commented on GitHub (Mar 31, 2022): gmx.com mail provider, IMAP enabled; free service, you can give it a try. Debian 11 Bullseye, 64bit, fully updated. Compiled and run on the same machine.

kerem commented

2026-03-03 01:19:41 +03:00

Author

Owner

@d99kris commented on GitHub (Mar 31, 2022):

Thanks 👍 Will try it out!

@d99kris commented on GitHub (Mar 31, 2022): Thanks 👍 Will try it out!

kerem commented

2026-03-03 01:19:41 +03:00

Author

Owner

@d99kris commented on GitHub (Apr 3, 2022):

I'm not able to reproduce this issue. I tried Debian 11 Bullseye with gmx.com. Both IMAP login (initial connecting) and SMTP login (sending emails) are working fine after renaming hostname - both temporarily using hostname or permanently editing /etc/hostname.

If you encounter this again, perhaps you can capture the log ~/.nmail/log.txt and share it with me - you can send privately to d99kris at gmail dot com. Ideally running nmail with --verbose flag, but a regular log may be useful as well.

Hostname shouldn't really affect anything important in nmail. The hostname is only used as part of Message-Id and in SMTP authentication, but I don't see how different hostname would cause any issues - unless it contains some type of special character perhaps.

@d99kris commented on GitHub (Apr 3, 2022): I'm not able to reproduce this issue. I tried `Debian 11 Bullseye` with `gmx.com`. Both IMAP login (initial connecting) and SMTP login (sending emails) are working fine after renaming hostname - both temporarily using `hostname` or permanently editing `/etc/hostname`. If you encounter this again, perhaps you can capture the log `~/.nmail/log.txt` and share it with me - you can send privately to `d99kris at gmail dot com`. Ideally running nmail with `--verbose` flag, but a regular log may be useful as well. Hostname shouldn't really affect anything important in `nmail`. The hostname is only used as part of `Message-Id` and in SMTP authentication, but I don't see how different hostname would cause any issues - unless it contains some type of special character perhaps.

kerem commented

2026-03-03 01:19:41 +03:00

Author

Owner

@krackout commented on GitHub (Apr 3, 2022):

I tried again just now, no such problem occurred. I really double checked it when it occurred, to be certain that there was such an issue. Sorry for the fuss, feeling a bit embarrassed I'm closing the issue.

@krackout commented on GitHub (Apr 3, 2022): I tried again just now, no such problem occurred. I really double checked it when it occurred, to be certain that there was such an issue. Sorry for the fuss, feeling a bit embarrassed I'm closing the issue.

kerem commented

2026-03-03 01:19:41 +03:00

Author

Owner

@d99kris commented on GitHub (Apr 3, 2022):

No worries, it could very well be an actual bug with some random intermittent behavior. But yeah if not seen now, let's close it for now and re-open if it re-appears.

@d99kris commented on GitHub (Apr 3, 2022): No worries, it could very well be an actual bug with some random intermittent behavior. But yeah if not seen now, let's close it for now and re-open if it re-appears.