Should there have been an email announcing theme voting?

Cosmologicon on 2013/08/26 18:17

I didn't get one this time, and I usually do. I think it's a pretty good reminder to have.

(log in to comment)

Comments

richard on 2013/08/26 21:53:

You aren't listed in the email out - I only email people who have registered a team, not everyone registered with the site.

reidrac on 2013/08/27 05:55:

richard: I recall getting the mail two PyWeeks ago and I've never been in a team. When I didn't get the mail in PyWeek 16 I thought it was because you were away and all that stuff.

Not that getting that mail is a big deal for, but I think it is useful for newbies.

richard on 2013/08/27 06:44:

I've been meaning to send out email to everyone registered but that requires I implement an unsubscribe mechanism which I've not had a chance to do.

richard on 2013/08/27 06:46:

OK that wasn't clear.

@reidrac: I should have said "entry", not "team". Sorry about that.

All people who have an entry in the current pyweek will receive emails about it from the pyweek bot.

And when I said "registered" in my comment above I mean all users of the site, not just those who have an entry.

reidrac on 2013/08/27 12:06:

So I should have received the mail and I didn't.

OK, I investigated a little bit and I found a log of a mail from richard at pyweek.org that was rejected because the server identified itself as pylet.org (helo=pyglet.org, with IP ending in 48.21) and the SPF record of pyglet.org doesn't authorize that IP. The same would have happened if the server identified itself as pyweek.org (same SPF record).

So the mail is not being delivered correctly because configuration issues :(

If the mail always comes from richard at pyweek.org I think I can whitelist that address but I suspect other users will have the same problem.

Let me know if you need help with this!

richard on 2013/08/27 23:39:

Ouch. Um, I'm kinda not a system administrator, and indeed the host is "pyglet.org" but also has the name "pyweek.org" because that's also hosted there. No idea what an SPF is (beyond cryptic stuffs in teh Googles) or how to make it Right. If someone could clue me in to making that correctly configured, I'd appreciate it :)

reidrac on 2013/08/28 05:54:

The domain name has a TXT record that includes the SPF:

$ dig pyglet.org TXT | grep -A1 ";; ANSWER"
;; ANSWER SECTION:
pyglet.org. 3595    IN    TXT    "v=spf1 ip4:66.96.128.0/18 ?all"

The SPF record specifies who's allowed to send mail from that domain. The address range specified in that record doesn't include current IP of pygler.org machine. You need to change that TXT record, and I think the easiest way would be:

v=spf1 ip4:66.96.128.0/18 ipv4:66.35.48.21 ?all

In that way you include current IP of pyglet.org and the HELO part of the SMTP session will be correct!

You can ask tummy.com about this, looks like the machine changed IP but someone forgot to change the SPF record :(

Send me a mail if you need extra help.

reidrac on 2013/08/28 06:06:

Sorry, I meant:

v=spf1 ip4:66.96.128.0/18 ip4:66.35.48.21 ?all

(I added an extra 'v' in the previous post).

It's too early in the morning and the post was sent before the coffee was in my organism!

richard on 2013/08/28 09:11:

thanks!

(one of these days I'll add comment editing lol)