SlackBuilds.org Mailing Lists

Known Issues with Slackbuilds mailing lists

Today a SlackBuilds.org list poster with a DMARC "reject" policy inadvertently caused all gmail and Google-hosted domain subscribers to be removed from the Users mailing list. The issue is discussed in full in this list post. We have enabled a workaround in GNU Mailman which will prevent this from recurring. Removed subscribers were notified by email, and they should resubscribe. We are sorry for the inconvenience, and yes, sorry that DMARC made this mess possible.     -- rob0 2018-03-18 22:02 UTC Update: We have reenabled subscriptions now. Anyone who was on the list at the time of the DMARC mess should now be receiving list mail again.     -- rob0 2018-03-22 04:20 UTC

The entire SlackBuilds.org infrastructure now supports (enforces, even) http over ssl (https). If you are unable to access the main site, mailing list archives, or any other part of the infrastucture using a modern web browser, please let us know.     -- rworkman 2016-01-24 05:58 UTC

We recently started checking (and enforcing) DNSSEC signatures for signed domains. This means if your domain was signed, it must have a valid signature, or we cannot resolve the name. Of course in that case we are unable to send mail to that domain, and we are (as always) unwilling to accept mail from domains which do not resolve. If your domain is not signed (and the parent domain has no Delegation Signer, or "DS", record for you), we will still be able to resolve your names. DNSSEC is a good idea, but be sure to do it right. If not you could end up with worse problems. Note: we have not yet signed Slackbuilds.org and the other domains, but that will probably be done soon.     -- rob0 2011-06-03 02:15 UTC

We're changing our spam protection strategies here somewhat, to take advantage of the new postscreen "triage" server. I think this will make us stronger (blocking more spam) and safer (less likely to block non-spam) at the same time. What a deal! No system can be perfect, so please let us know if you have any problems posting to the list. If your own usual mail server is blocked for some reason, you can sign up for any free mail service and send from there: those services should not be blocked, typically. In conjunction with this change, I have signed us up for the DNSWL.org DNS-based whitelisting service (and we're using it here as well.) We were assigned a trust score of "medium", which means, if you (or your email provider) are using that service, our mail is less likely to be blocked.     -- rob0 2011-02-15 02:15 UTC

Sometime before 2010-03-19 03:25 UTC, our hoster seems to have deleted the DNS records which were providing our reverse DNS (IP-address-to-hostname) resolution. As a result, we had several subscribers who lost list mail. If you were one of them, you will be hearing from me directly. The hoster was alerted to this situation in early hours of 2010-03-22, and is looking into it, but the problem has not yet been, ahem, resolved. We're still receiving list and @slackbuilds.org mail, but we're keeping it enqueued until the rDNS is fixed. I will post here when we get it fixed, and subscribers can expect a minor flood at that time. If you have any questions, feel free to ask.     -- rob0 2010-03-23 02:20 UTC Update: List mail is now moving again. Some subscribers are certain to have delivery issues, such as possible classification as spam. I don't think there were any major problems, but as always, hit the above mailto: link if you have any questions. If you're interested (or a postmaster yourself), you will be seeing the list mail now coming from a different host: sorry.nodns4.us[66.226.201.55]. This is temporary, we hope.     -- rob0 2010-03-24 14:15 UTC FINAL update: The issue is now resolved, and list mail will be coming directly from the list server. Big thanks, as always, to Adam Kennedy and the fine crew at Omnicity, Inc.     -- rob0 2010-03-24 19:20 UTC

One or more hosts at mo-p05-ob.rzone.de[81.169.146.18x] (x=0-2) have been implicated in a mail forwarding loop for the slackbuilds-users@slackbuilds.org list posting address. As a result our Postfix MTA discovered the loop and sent bounces to the posters. As a resolution, these hosts have been blocked from sending mail to the posting address. If you are the perpetrator, please fix the problem and advise us when the problem is resolved.     -- rob0 2009-05-19 05:30 UTC

This host changed IP address on 2008-11-15, and the new address was listed in the Spamhaus PBL DNSBL. I just caught the problem today, and delisted the new IP address. Some subscribers at better-protected sites (we use and recommend the Spamhaus Zen list here) might have lost list mail as a result of this problem. We apologize for any inconvenience this might have caused you.     -- rob0 2008-11-16 19:55 UTC

Subscribers from @web.de addresses are no longer receiving list mail. The MX host is rejecting our delivery attempts at initial connection. This is not a valid SMTP rejection, by the way. We have reviewed the Web page they linked, and we see no problems with our host. Apparently we are in a private blocklist there. SlackBuilds.org is not going to attempt to resolve this issue. Our members with @web.de addresses are welcome to discuss it with the WEB.DE FreeMail Anti-Spam Team, and to advise us if the problem is resolved.     -- rob0 2008-04-20 08:35 UTC