We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Thunderbird Proton Mail eset AV

  • 1 trả lời
  • 0 gặp vấn đề này
  • 26 lượt xem
  • Trả lời mới nhất được viết bởi Matt

more options

Re: Thunderbird - Proton Mail - eset - problem: “Cannot connect to Server 127.0.0.1. The connection was refused”

I found a workaround in eset via Setup - Internet Protection – Email Client Protection – Antispam Protection – Edit – User’s Address List – Add – joegabriele@proton.me – click Exception – Ok

This allows me to receive email on my PC. However, when I try to send an email, I get this error message:

“Sending of the message failed. An error occurred while sending mail: Outgoing server (SMTP) error. The server responded: * OK [CAPABILITY ID IDLE IMAP4rev1 MOVE STARTTLS UIDPLUS UNSELECT] Proton Mail Bridge 03.02.00 - gluon session ID 3.”

Can anyone help?

Re: Thunderbird - Proton Mail - eset - problem: “Cannot connect to Server 127.0.0.1. The connection was refused” I found a workaround in eset via Setup - Internet Protection – Email Client Protection – Antispam Protection – Edit – User’s Address List – Add – joegabriele@proton.me – click Exception – Ok This allows me to receive email on my PC. However, when I try to send an email, I get this error message: “Sending of the message failed. An error occurred while sending mail: Outgoing server (SMTP) error. The server responded: * OK [CAPABILITY ID IDLE IMAP4rev1 MOVE STARTTLS UIDPLUS UNSELECT] Proton Mail Bridge 03.02.00 - gluon session ID 3.” Can anyone help?

Tất cả các câu trả lời (1)

more options

Sounds to me like you are sending on the incoming port, not the outgoing one. That response is IMAP server response to a log in, not an SMTP one.

Personally I think the money folk pay for proton is not a wise choice. The bridge is flaky, just based on the issue that are reported in this forum, and proton has a habit of converting encrypted email where you do not have encryption certificates to web pages and only forwarding a link to it in your email.