Categories
Announcements Changes Status

Bug in “Mail Server” Type Outbound Accounts

We recently announced several major new features for our Outbound Mail service. The new mirroring and BCC options necessitated a major rewrite of the account control center interface in addition to the server-side processing. The rewrite was based on the original implementation as described in the online documentation, but a bug was discovered in the old version that allowed the source filter to be removed for “mail server” outbound types after it was added (entering a source filter was always required during the add process).

Connection source filters are only mandatory on mail server type accounts; filters for the other two types (single address and single domain) are optional.

Upon further research we discovered that there were only 24 mail server outbound accounts that are missing the required source filtering. We have notified these account holders individually of the bug, so if you didn’t get a email directly from us, your account is not affected. This post is in the interest of full disclosure rather than sweeping the problem under the rug.

This requirement will be enforced starting May 22, 2010. After this date, mail server type accounts that are missing a source filter will return the error “An IPv4 address or host filter is required for this submission type.” We apologize for any inconvenience this may cause. Please contact technical support if you require assistance.

Categories
Announcements IPv6 Status

Mail Forwarding IPv6 Enabled

As part of our ever expanding quest to fully IPv6 enable our services, the new IPv6 enabled mail forwarding servers are now online. If a forwarding destination is reachable via IPv6, we’ll try it.

We’re getting close to tackling the big one: IPv6 enabled incoming mail. Stay tuned!

Categories
Changes IPv6 Status

Forwarded Mail Source Change

We are changing the source of forwarded mail as handled by the “Mail Forwarding” option in the account control center. Messages forwarded to external email addresses were previously sent from 208.79.240.32/28. Starting today, we will begin migrating forwarding to a new group of servers out of 208.79.241.112/28. This change is permanent and is being made as part of our recent announcement on enforced content filtering for forwarded mail.

This will also allow us, in the future, to insert forwarding delivery results into the online mail logs. More immediately, these new servers will be also be IPv6 enabled.

[May 8] The IPv6 enabled servers are now online. If a forwarding destination is reachable via IPv6, we’ll try it.

Categories
Changes Status

Anti-Virus Filter Changes Today!

As we mentioned here last week, today is the day we will be activating the additional databases for the anti-virus content filter. Third party databases are marked as “UNOFFICIAL” in the signature name should one of them trigger. The default behavior for the filter will be to use all signatures available. If you do not wish to use these databases, you may opt out at any time by updating your anti-virus settings in the account control center. If you decide to disable them, the signature matches will still be logged in the mail logs.

Our development lab tests have indicated that the process of adding the new databases will not be service impacting. If you have any questions, please let us know.

[12:51] Now active on messages processed through MX record mail2.rollernet.us

[13:06] Now active on messages processed through MX record mail.rollernet.us

Categories
Status

Broken Roundcube Address Book

The Roundcube webmail client address book is currently broken. The logs are reporting “DB Error: MDB2 Error: unknown error”. Only the address book function is affected. We are investigating this issue, but we do not have an estimated resolution time.

[RESOLVED] Roundcube had an extra bind variable in SQL queries related to the address book. The SQL statement that contained the bind was dynamically defined, but the variable itself was always passed, leading to an extra bind variable when the SQL statement didn’t contain the bind. We have removed the offending lines from our Roundcube source. (For the programmers in the audience, here’s our diff: rcube_contacts.patch)