Differences

This shows you the differences between two versions of the page.

--- email [2022/06/15 19:49] – [#4 denied by rules for .WAV and .PDF] jim
+++ email [2022/06/15 19:51] (current) – [Disclaimer] jim
@@ Line 28: / Line 28: @@
 A lot of company/business mail servers strip file attachments or block email with .PDF (document) and .WAV (audio) file attachments. Solutions: whitelist (as above) or use a different email address.
-=====#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.
-=====#6 the crazy stuff=====
+=====6. The Crazy Stuff=====
 Taken a look at all these, done what you can do and you are still not getting your voicemails and faxes? Open a support ticket including the affected email addresses and we can trace that email via logs in the Hello Hub and our email relay server. Most of the time, we can see where the blockage is and why.
 =====Disclaimer=====
-Ring-u makes a best effort of maintaining our good standing in the email server community using proper DNS, proper SPF (Sender Policy Framework), proper TLS Encryption Certificates, and proper bounce and rejection handling with 1 caveat. That caveat: we do not examine bounced/rejected messages beyond the header or log entry. We do not want to see or hear your private business communications, we take your business very seriously. Even with that best effort, ring-u can not be responsible for anything past handing that email to your mail system provider. After that, it is the responsibility of the receiving email system and the client to handle, deliver and read these messages.
+Ring-u makes a best effort of maintaining our good standing in the email server community using proper DNS, proper SPF (Sender Policy Framework), proper TLS Encryption Certificates, and proper bounce and rejection handling with 1 caveat.\\
+That caveat: we do not examine bounced/rejected messages beyond the header or log entry. We do not want to see or hear your private business communications, we take your business very seriously. Even with that best effort, ring-u can not be responsible for anything past handing that email to your mail system provider. After that, it is the responsibility of the receiving email system and the client to handle, deliver and read these messages.