Date: prev next · Thread: first prev next last


we're blacklisted at SORBS, a mail blacklist.

I've tried to clarify why, but their responses so far aren't that helpful. The messages headers they sent clearly show it was a legitimate message on the users@ mailing list. As the mailing list requires double opt-in confirmation, contains unsubscription information and a human contact in case of questions, the listing is not legitimate. Sadly, all tickets I opened with these information simply have been ignored.

Well, we are in good neighbourhood, e.g. certain Google Mail servers are listed as well, and other mail servers from providers and mailing lists as well. Anyone may Google about SORBS or look it up at Wikipedia and make up their own mind.

Sadly, there are still some postmasters who solely rely on that blacklist. They are acting unprofessional and irresponsible, but anyways, right now, there are about 70 mails not delivered in the queue because of the listing, plus many more bouncing.

So, if you receive complaints from users that they cannot e-mail us anymore, they should ping their ISPs asking about blacklist usage.


Florian Effenberger <>
Steering Committee and Founding Member of The Document Foundation
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Skype: floeff | Twitter/ @floeff

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.