Bugzilla temporarily down

[mark]

Hi all, I'm moving Bugzilla and so it'll be down for a few hours. Just FYI.

Denise: your email will be down for ~2 hours too, until DNS propagates. Sorry!

Update: This is done. DNS is rolling through the wild TTLs, everything should be back up and running in the next hour or two. If you see any problems please let me know.

Comments

[fu]

Looks like XMLRPC isn't installed -- got an error with the changelog hook when I tried to commit something.

[mark]

Oops, fixed. Sorry.

[fu]

Thank you!

[ninetydegrees]

My apologies if this is completely unrelated but I used to be able to see patches in diff mode (with the colored lines) and now all the 'diff' links are gone.

[mark]

That's absolutely related! It's fixed now, thanks for the report.

[ninetydegrees]

Wonderful! Thank you!

[pauamma]

Whine emails appear to be broken.

[mark]

Thanks, fixed. Weirdly, I don't know how this worked on the old server? I can't find a cron job to send this anywhere... oh well, it should be fixed now.

[pauamma]

Confirmed working, thanks. Not working today. :-( (Whether the cronjob didn't run or the email was rejected/dropped by @yahoo.com I can't say.)

[mark]

Almost certainly related to the black hole that EC2 lives in. Sadness. I'm signing up for Elastic Email now and I'll route all of the outgoing email through that. That should fix the problem.

Sorry for the trouble. I know email is vital for really using Bugzilla.

[mark]

It should be happier now. I'm routing it through Dyn's SMTP gateway at the moment. Elastic Email turned out not to be a great option for the rest of the mail from this box.

[pauamma]

Got some bugmail today, at 8:32am GMT. No whine email, but that could be on account of when you made that change.

Another thing to consider: Yahoo inserts a ReceivedSPF header complaining of: softfail (transitioning domain of bugs.dwscoalition.org does not designate 204.13.248.66 as permitted sender)

Received: from 127.0.0.1 (EHLO mho-01-ewr.mailhop.org) (204.13.248.66) by mta173.mail.sp2.yahoo.com with SMTP; Wed, 12 Oct 2011 01:32:51 -0700
Received: from ec2-50-16-84-216.compute-1.amazonaws.com ([50.16.84.216] helo=qq.is) by mho-01-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from <bugzilla-daemon@bugs.dwscoalition.org>) id 1RDuF8-0008U4-Hb for fduuvrzv@yahoo.com; Wed, 12 Oct 2011 08:32:50 +0000
Received: from bugs.dwscoalition.org (localhost [127.0.0.1]) by qq.is (Postfix) with ESMTP id C2194227A9 for <fduuvrzv@yahoo.com>; Wed, 12 Oct 2011 08:32:35 +0000 (UTC)

[mark]

The SPF record was still on the domain from when I was testing Elastic Email. It has been removed now, thanks. We should be back to the state we were in... well, it should be working now.

Email sucks.

Bugzilla's IP is in the Spamhaus blacklist

[kaisa]

I was thinking about starting coding again, and went to reset my bugzilla password, but bugzilla's IP is blocked by Spamhaus blacklist... I turned off spamblocking from my e-mail server, so my problem is solved, but I thought I'd let you know about the blacklisting anyway, since other people may not be able to control what kind of spamblocking their e-mail server is doing.

SpamProtection rejected RCPT (Sender: bugzilla-daemon@bugs.dwscoalition.org, IP:50.16.84.216, Reason: Rejected by Spamhaus)
http://www.spamhaus.org/query/bl?ip=50.16.84.216
http://www.spamhaus.org/pbl/query/PBL1205767

Re: Bugzilla's IP is in the Spamhaus blacklist

[mark]

What. The reason it's on the blocklist is because the IP is part of Amazon's EC2 service. Pardon my giggling over here, but that's kind of hilarious.

It also means I am not going to really be able to fix this issue. If SpamHaus wants to block all of EC2, that's their deal.

Re: Bugzilla's IP is in the Spamhaus blacklist

[kaisa]

The way I understood that was that AWS/EC2 has a policy that the servers on this IP range are not supposed to send e-mail directly but through specific SMTP servers, and that Spamhaus knows this policy and blocks because of it. So another option could be to use a SMTP server assigned by AWS/EC2, I guess, and that would make SpamHaus happy, too.

But as I said, it's not a problem for me since I control my e-mail server and can turn off the e-mail server's spam protection temporarily. You could just wait and see if this affects anyone else, and if not, who cares. :P

Re: Bugzilla's IP is in the Spamhaus blacklist

[mark]

I'm not aware of an Amazon EC2 SMTP relay? I'd love some documentation if you have it, because I'm happy doing it how they want. I don't see one though.

I suppose I could pay for service through one of the million providers...

Re: Bugzilla's IP is in the Spamhaus blacklist

[kaisa]

Ahh I think you're right.

I went to look at the AWS forums, and it seems a lot of people have the same problem, and they're solving it in various ways... some use the Amazon SES SMTP servers as relays, which allows 2000 free e-mails per day before you have to start paying, some are using some other external STMP relay, and some have actually managed to get Amazon to get their IP address either off the PBL list or on a whitelist instead.

I looked at their FAQ also, and it seems to imply that it should be possible to use e-mail servers in EC2, too. (http://aws.amazon.com/ses/faqs/#14)

Seems like an annoying problem. :(

[afuna]

Pony Request: can you enable the JSONRPC feature in bugzilla? I've been using it to automate certain steps in the commit workflow.

[ninetydegrees]

I've just noticed this but I don't know when it started happening: Bugzilla has an 'Automatic Username Completion' feature, which used to be working but no longer does. When you edit the Assigned To, there's no autocompletion now. Tried it in FF and Chrome to make sure it wasn't me blocking stuff.