email
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
email [2022/06/15 19:49] – [2 Spam/Junk Folders] jim | email [2022/06/15 19:49] – [#5 client firewall blocking] jim | ||
---|---|---|---|
Line 25: | Line 25: | ||
* Advanced: whitelist 50.116.32.101 and 2600: | * Advanced: whitelist 50.116.32.101 and 2600: | ||
- | =====#4 denied by rules for .WAV and .PDF===== | + | =====4. Denied By Rules for .WAV & .PDF===== |
A lot of company/ | A lot of company/ | ||
- | =====#5 client firewall blocking===== | + | =====5. Client Firewall Blocking===== |
The Hello Hub relays mail via: ops4.ring-u.com port 2552. It's encrypted and authenticated by your Hello hub, but in some cases, higher end firewalls block this traffic. They may recognize the opening communications as e-mail, or just not allow the unusual port. Most firewalls aren't that smart, but SonicWall, pfSense, Cisco, etc.. may be configured to block what they think might be outgoing spam. In some cases, they then block all traffic from the Hello Hub, including voice telephone calls when this happens. It's rare, but worth mentioning here. Common residential and small business firewalls do not do this. | The Hello Hub relays mail via: ops4.ring-u.com port 2552. It's encrypted and authenticated by your Hello hub, but in some cases, higher end firewalls block this traffic. They may recognize the opening communications as e-mail, or just not allow the unusual port. Most firewalls aren't that smart, but SonicWall, pfSense, Cisco, etc.. may be configured to block what they think might be outgoing spam. In some cases, they then block all traffic from the Hello Hub, including voice telephone calls when this happens. It's rare, but worth mentioning here. Common residential and small business firewalls do not do this. | ||
email.txt · Last modified: 2022/06/15 19:51 by jim