The following technical requirements apply to the Internet e-mail (e-mail) delivery through BOL network.
- BOL's servers will not accept connections from unsecured systems. These include open relays, open proxies or any other system that has been determined to be applicable for unauthorized use.
- BOL's mail servers will not accept connections from systems that use dynamic or residential assigned IP addresses.
- BOL will not deliver e-mail that contains suspicious messages, which might violate the filtering rules, such as the hex-encoded Universal Resource Locator (URL). (Ex: http://%6d%6e%3f/), text or html-encoded files with base64.
- BOL's mail servers can reject connections from any IP address that does not comply with the RFC 1912 guidelines, including the reverse DNS settings (a PTR authoritative and valid record requirement).
- BOL’s analysis system scans the flow of e-mail messages and can reject connections from servers suspected of sending SPAM.
- BOL may reject connections from servers whose recipient lists consistently generate a higher than 10% bounce failure rate. (e.g. over 10% of a sender's mailing list is destined for users that do not exist on our system)
- BOL may reject connections from senders who are unable to accept at least 90% of the bounce-return messages (mailer-daemon failure/error messages) destined for their systems.
- Complaints submitted by BOL customers will be used as a basis for refusing connections from any mail server.
- BOL can reject messages when the origin of the IP address connection is defined as not valid on your SPF entry, for all domains that have published the SPF record.
- BOL publishes the SPF record and recommends its validation for messages whose sender’s domain is “uol.com.br.”
If you have any questions, please contact us through this form.