Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Cannot connect to gmail account in thunderbird 78 on MX Linux

  • 22 replies
  • 2 have this problem
  • 10 views
  • Last reply by christ1

more options

My thunderbird client cannot connect to the IMAP server of gmail. After I have set up my gmail account in thunderbird, it is unable to fetch the messages from the mail server. Besides, I have enabled IMAP in my google account and also checked to allow cookies from third party. I have followed[link]. However, this does not work for me. I also tried resetting my iptables but that did not work out too. Can anyone help me out with this? Thanks in advance.

My thunderbird client cannot connect to the IMAP server of gmail. After I have set up my gmail account in thunderbird, it is unable to fetch the messages from the mail server. Besides, I have enabled IMAP in my google account and also checked to allow cookies from third party. I have followed[[https://support.mozilla.org/en-US/questions/1234176#answer-1155359|this link]]. However, this does not work for me. I also tried resetting my iptables but that did not work out too. Can anyone help me out with this? Thanks in advance.

All Replies (2)

more options

This is my iptables configuration. You may want to have a look at it. I don't know if anything is wrong about it.

-P INPUT DROP -P FORWARD DROP -P OUTPUT DROP -N DOCKER -N DOCKER-ISOLATION-STAGE-1 -N DOCKER-ISOLATION-STAGE-2 -N DOCKER-USER -N ufw-after-forward -N ufw-after-input -N ufw-after-logging-forward -N ufw-after-logging-input -N ufw-after-logging-output -N ufw-after-output -N ufw-before-forward -N ufw-before-input -N ufw-before-logging-forward -N ufw-before-logging-input -N ufw-before-logging-output -N ufw-before-output -N ufw-logging-allow -N ufw-logging-deny -N ufw-not-local -N ufw-reject-forward -N ufw-reject-input -N ufw-reject-output -N ufw-skip-to-policy-forward -N ufw-skip-to-policy-input -N ufw-skip-to-policy-output -N ufw-track-forward -N ufw-track-input -N ufw-track-output -N ufw-user-forward -N ufw-user-input -N ufw-user-limit -N ufw-user-limit-accept -N ufw-user-logging-forward -N ufw-user-logging-input -N ufw-user-logging-output -N ufw-user-output -A INPUT -i eth0 -p udp -m udp --dport 1194 -j ACCEPT -A INPUT -i tun0 -j ACCEPT -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -s 0.0.0.0/7 -j DROP -A INPUT -s 2.0.0.0/8 -j DROP -A INPUT -s 5.0.0.0/8 -j DROP -A INPUT -s 7.0.0.0/8 -j DROP -A INPUT -s 10.0.0.0/8 -j DROP -A INPUT -s 23.0.0.0/8 -j DROP -A INPUT -s 27.0.0.0/8 -j DROP -A INPUT -s 31.0.0.0/8 -j DROP -A INPUT -s 36.0.0.0/7 -j DROP -A INPUT -s 39.0.0.0/8 -j DROP -A INPUT -s 42.0.0.0/8 -j DROP -A INPUT -s 49.0.0.0/8 -j DROP -A INPUT -s 50.0.0.0/8 -j DROP -A INPUT -s 77.0.0.0/8 -j DROP -A INPUT -s 78.0.0.0/7 -j DROP -A INPUT -s 92.0.0.0/6 -j DROP -A INPUT -s 96.0.0.0/4 -j DROP -A INPUT -s 112.0.0.0/5 -j DROP -A INPUT -s 120.0.0.0/8 -j DROP -A INPUT -s 169.254.0.0/16 -j DROP -A INPUT -s 172.16.0.0/12 -j DROP -A INPUT -s 173.0.0.0/8 -j DROP -A INPUT -s 174.0.0.0/7 -j DROP -A INPUT -s 176.0.0.0/5 -j DROP -A INPUT -s 184.0.0.0/6 -j DROP -A INPUT -s 192.0.2.0/24 -j DROP -A INPUT -s 197.0.0.0/8 -j DROP -A INPUT -s 198.18.0.0/15 -j DROP -A INPUT -s 223.0.0.0/8 -j DROP -A INPUT -s 224.0.0.0/3 -j DROP -A INPUT -i br-44c25 -p udp -m udp --dport 16514 -j ACCEPT -A INPUT -i br-44c25 -p tcp -m tcp --dport 16514 -j ACCEPT -A INPUT -i docker0 -p udp -m udp --dport 16514 -j ACCEPT -A INPUT -i docker0 -p tcp -m tcp --dport 16514 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --dport 16514 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 16514 -j ACCEPT -A INPUT -i wlan0 -p udp -m udp --dport 16514 -j ACCEPT -A INPUT -i wlan0 -p tcp -m tcp --dport 16514 -j ACCEPT -A FORWARD -j DOCKER-USER -A FORWARD -j DOCKER-ISOLATION-STAGE-1 -A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A FORWARD -o docker0 -j DOCKER -A FORWARD -i docker0 ! -o docker0 -j ACCEPT -A FORWARD -i docker0 -o docker0 -j ACCEPT -A FORWARD -o br-44c25d8fa256 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A FORWARD -o br-44c25d8fa256 -j DOCKER -A FORWARD -i br-44c25d8fa256 ! -o br-44c25d8fa256 -j ACCEPT -A FORWARD -i br-44c25d8fa256 -o br-44c25d8fa256 -j ACCEPT -A FORWARD -i tun0 -o eth0 -j ACCEPT -A FORWARD -i eth0 -o tun0 -j ACCEPT -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A OUTPUT -o lo -j ACCEPT -A OUTPUT -o br-44c25 -p udp -m udp --sport 67:68 --dport 67:68 -j ACCEPT -A OUTPUT -o br-44c25 -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -o br-44c25 -p tcp -m tcp --dport 80 -m state --state NEW -j ACCEPT -A OUTPUT -o br-44c25 -p tcp -m tcp --dport 443 -m state --state NEW -j ACCEPT -A OUTPUT -o br-44c25 -p udp -m udp --sport 123 --dport 123 -j ACCEPT -A OUTPUT -o br-44c25 -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o br-44c25 -p tcp -m tcp --dport 25 -m state --state NEW -j ACCEPT -A OUTPUT -o br-44c25 -p tcp -m tcp --dport 22 -m state --state NEW -j ACCEPT -A OUTPUT -o docker0 -p udp -m udp --sport 67:68 --dport 67:68 -j ACCEPT -A OUTPUT -o docker0 -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -o docker0 -p tcp -m tcp --dport 80 -m state --state NEW -j ACCEPT -A OUTPUT -o docker0 -p tcp -m tcp --dport 443 -m state --state NEW -j ACCEPT -A OUTPUT -o docker0 -p udp -m udp --sport 123 --dport 123 -j ACCEPT -A OUTPUT -o docker0 -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o docker0 -p tcp -m tcp --dport 25 -m state --state NEW -j ACCEPT -A OUTPUT -o docker0 -p tcp -m tcp --dport 22 -m state --state NEW -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --sport 67:68 --dport 67:68 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 80 -m state --state NEW -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 443 -m state --state NEW -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --sport 123 --dport 123 -j ACCEPT -A OUTPUT -o eth0 -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 25 -m state --state NEW -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 22 -m state --state NEW -j ACCEPT -A OUTPUT -o wlan0 -p udp -m udp --sport 67:68 --dport 67:68 -j ACCEPT -A OUTPUT -o wlan0 -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -o wlan0 -p tcp -m tcp --dport 80 -m state --state NEW -j ACCEPT -A OUTPUT -o wlan0 -p tcp -m tcp --dport 443 -m state --state NEW -j ACCEPT -A OUTPUT -o wlan0 -p udp -m udp --sport 123 --dport 123 -j ACCEPT -A OUTPUT -o wlan0 -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o wlan0 -p tcp -m tcp --dport 25 -m state --state NEW -j ACCEPT -A OUTPUT -o wlan0 -p tcp -m tcp --dport 22 -m state --state NEW -j ACCEPT -A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2 -A DOCKER-ISOLATION-STAGE-1 -i br-44c25d8fa256 ! -o br-44c25d8fa256 -j DOCKER-ISOLATION-STAGE-2 -A DOCKER-ISOLATION-STAGE-1 -j RETURN -A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP -A DOCKER-ISOLATION-STAGE-2 -o br-44c25d8fa256 -j DROP -A DOCKER-ISOLATION-STAGE-2 -j RETURN -A DOCKER-USER -j RETURN

more options

Did you manually create those rules? I'd expect Linux distributions come up with reasonable defaults, so that receiving and sending email works out of the box. All email protocols (POP, IMAP, SMTP) run over TCP. You can look up the port numbers used on the servers in your Thunderbird account settings, and create firewall rules accordingly if needed.

  1. 1
  2. 2