DimeFAQ:System Status
From DimeWiki
Our regular housekeeping downtime is every day at 06:25 AM CET/CEST [as applicable, depending on the season], normally lasting ten minutes. The daily reboot of tracker server b2 is at 05:00 AM CET/CEST, also usually lasting ten minutes. Those are to be expected and will not be noted in entries below.
Automated announcements of tracker outages are recorded in the tracker outage log.
If you see no entries here nor on the tracker outage log, then all known problems were cleared up at least twenty-four hours ago.
Timestamps are by CEST (Central European Summer Time, +0200) or CET (Central European Time, +0100) as marked.
Decommissioning of the hostnames b3, b4, b5, b6, and b7
For a long time, our tracker cluster had consisted of three more powerful boxes instead of the original eight, and the eight hostnames b0 through b7 each pointed to one of those three. On June 29, Erwe reconfigured the cluster to use only one name for each server: b0, b1, and b2. For about a week after that, announces to b3 through b7 (if you were using an older dot-torrent file that pointed to one of those names) were getting the "download a new copy" error message to tell you to get a fresh copy of the dot-torrent file.
Now the retired hostnames are fully canceled, and announces to b3 through b7 will get "address not found" or "host not found" errors. If that occurs to you, go back to the torrent's page and get a fresh copy of the dot-torrent file. It will point to a working hostname.
With some clients, you may need to stop and remove the torrent job that was using the old dot-torrent file and re-add it with the new copy. You do not have to redownload torrent content, only the dot-torrent metafiles.
--Nightshifted 18:07, 7 July 2008 (CEST)
Problems with eMail notifications
Netzero, Juno, and Verizon
Email from our bot to addresses in the netzero.com, netzero.net, juno.com, and verizon.net domains will be rejected as spam by their system filters. A filter added at the user level will come in too late and will not help.
Replacement passwords requested for existing accounts with addresses in any of those domains will vanish into the ether, disabling the account (these may, in some cases, be recoverable with administrator intervention). Address updates into those domains for existing acccounts will be impossible, as the address change confirmation link message will never arrive.
If you already have a DIME account with a Verizon, Netzero, or Juno email address on it, update your DIME profile. If you want to sign up for DIME with an address in any of those domains, you can't, and you'll need to use an email address where you can decide for yourself what you consider to be spam.
Yahoo/Ymail and Hotmail/Live/MSN
Both of those providers are treating mail from our bot as spam. If your account's email address is in any of their domains, if you want to change your DIME account's email address to any of their domains, or if you want to sign up for DIME using an email address in any of their domains, first make sure that
- for Yahoo/Ymail, you have a filter rule that directs mail with @dimeadozen.org in the From header to your Inbox or to a special folder that you designate;
- for Hotmail/Live/MSN, you have the @dimeadozen.org domain in your Safe Senders List and your Junk Mail controls are set to put suspected spam into the Junk folder rather than deleting it on receipt.
Outblaze
Outblaze reimposed their block against mail from our bot. We're not going to keep arguing with them. Since it's impossible to keep an up-to-date list of all their domains, new account registrations that use Outblaze domains in their email addresses will be accepted but, of course, will be deleted when their confirmation link messages bounce. Replacement passwords requested for existing accounts with addresses in Outblaze domains will never arrive, thus disabling the account (these may, in some cases, be recoverable with administrator intervention). Address updates into any Outblaze domain for existing acccounts will be impossible, as the address change confirmation link message will never arrive.
There is nothing the user can do to prevent it. A filter rule on your Outblaze-powered webmail account will come into play too far downstream. If you already have a DIME account with an Outblaze email address on it, update your DIME profile. If you want to sign up for DIME with an Outblaze-powered address, you can't, and you'll need to use an email address that is not under Outblaze's control.
Earthlink and Mindspring
As of January 3, 2009, mail from our bot is rejected by Earthlink for addresses in the earthlink.net and mindspring.com domains. A filter added at the user level comes in too late and does not help.
Erwe has followed their instructions for getting the block removed, and we'll see if we get any results.
Unless they lift the block (and they keep it lifted and don't reimpose it the way Verizon and Outblaze did), the situation is the same as Verizon, Netzero, or Juno:
Replacement passwords requested for existing accounts with earthlink.net or mindspring.com addresses will vanish into the ether, disabling the account (these may, in some cases, be recoverable with administrator intervention). Address updates into those domains for existing acccounts will be impossible, as the address change confirmation link message will never arrive.
If you already have a DIME account with an Earthlink or Mindspring email address on it, update your DIME profile. If you want to sign up for DIME with an address in either of those domains, you can't, and you'll need to use an email address where you can decide for yourself what you consider to be spam.
--Nightshifted 06:40, 17 December 2008 (CET)
