Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

socat[122] E write(6, 0x5ab150, 21): Broken pipe #32

Open
ronaldt80 opened this issue May 5, 2021 · 4 comments
Open

socat[122] E write(6, 0x5ab150, 21): Broken pipe #32

ronaldt80 opened this issue May 5, 2021 · 4 comments

Comments

@ronaldt80
Copy link

ronaldt80 commented May 5, 2021

Thanks for all the work. I installed the bridge following instructions. Running 1.4.5-build on a Pi3B+ which I want to address from other machines on the network.

When I enter the SMTP server in Unifi the test-email generates an error, at the same time a log error appears in the proton mail bridge (so at least something happens..) - no clue what it means though and where to start:

2021/05/05 19:44:09 socat[122] E write(6, 0x5ab150, 21): Broken pipe

Many thanks for any suggestions!

Addition 22:08 CET - I tested IMAP with Mozilla Thunderbird and added the SMTP account to Nextcloud; both work flawlessly

@shenxn
Copy link
Owner

shenxn commented May 15, 2021

It might be related to the self signed TLS cert the bridge uses. Can you ignore TLS check or disable TLS in Unifi?

@vpresecki
Copy link

Hi, I have the same problem. But running in kubernetes.

I have a service that re-routes contact form from website.

First mail goes to my protonmail inbox.
Second mail goes to sender / client from website.

First try did all good, I received email both on my protonmail inbox and other "sender" email.

Second try I received this:
socat[34650] E write(5, 0x5c0a9ee389f0, 40): Broken pipe
And email came just to my protonmail inbox, sender did not receive anything.

Additional 10 tries did the same as second try.

After ~1 hour
everthing was fine again for first try.
Second try no one received mail and I get 2 messages each time I try:
socat[34650] E write(5, 0x5c0a9ee389f0, 40): Broken pipe

So it seams when this appears emails wont go through anymore.
Did not have time to test it more yet but when I do will post update.

@simonfelding
Copy link
Collaborator

@vpresecki Hey, I'm wondering what the cause of this is too. Did you learn anything?

@vpresecki
Copy link

@vpresecki Hey, I'm wondering what the cause of this is too. Did you learn anything?

No, still happening. Could not resolve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants