1 Topic by tony_ph

  • tony_ph
  • Member
  • Offline
  • Registered: 2018-02-11
  • Posts: 32

Topic: Randomly Connection Timeout via Thunderbird

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.7 MARIADB edition.
- Linux/BSD distribution name and version: Centos 7
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL / MariaDB
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Good day everyone. I have 5 domains on a single VPS, on my mozilla thunderbird i have 1 account each.
Randomly i see thunderbird error msg saying @maildomain3.com timeout
or
sometime when i send email it give connection error, but if i try again after 2 secs it work.

Same the timeout error after a while resolved alone.
I set thinderbird to check all my 5 domains every minute all IMAP/ SMTP

and during a day it show this error maybe 3 or 4 times only.
How can i slove this plz?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by tony_ph

  • tony_ph
  • Member
  • Offline
  • Registered: 2018-02-11
  • Posts: 32

Re: Randomly Connection Timeout via Thunderbird

Any help plz?

3 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,163

Re: Randomly Connection Timeout via Thunderbird

Usually it could be caused by Fail2ban due to the client (you) triggered too many errors (like password failures), and banned for few minutes or hours. But you can reconnect after few seconds, so it's not like Fail2ban.

Please check Dovecot log file instead, try to get related log.

4 Reply by tony_ph

  • tony_ph
  • Member
  • Offline
  • Registered: 2018-02-11
  • Posts: 32

Re: Randomly Connection Timeout via Thunderbird

Tnx i sloved the issue changing IMAP port from 143 to 993.
no more errors.

ZhangHuangbin wrote:

Usually it could be caused by Fail2ban due to the client (you) triggered too many errors (like password failures), and banned for few minutes or hours. But you can reconnect after few seconds, so it's not like Fail2ban.

Please check Dovecot log file instead, try to get related log.