Interviewing at Google

I’m sick and tired of seeing Google’s bullshit “this stuff matters” advertising as part of their latest privacy policy update (which I’ve been doing my best to ignore).

As I was complaining about it I thought I’d try and find some examples of their hypocrisy. I’m fairly sure I’ve seen articles before where people said their job for a Google interview was to process gigabytes of web logs. If you’re data-mining web logs to *spy* on people on the one hand and then telling people you’re protecting their privacy on the other hand then you’re a lying sack of shit really, aren’t you?

Anyway, I didn’t find what I was looking for in a big hurry and I don’t really have time for this, so I’m giving up on my little fact finding mission and just going back to ignoring the whole thing.

However, during my web search I found this article, My Job Interview at Google, which seems like a fairly content rich article. I’m particularly interested in the resources that the guy linked to in his post. So figured I’d swing by my blog and make a note so that when I have some free time (hey, could happen) I can go over that post and read the reference material.

Mailman 3.0 and Postfix Virtual Domains

Read the spec for Mailman 3.0. Looks like it will be pretty good. The feature that I’m interested in, and I’m annoyed I can’t do this with my current version of Mailman, is to be able to put a link to the web archived message in the bottom of the outgoing SMTP message. I.e. so there’s a link back to that message on the web in the message itself. Would be really handy for referencing. At the moment if I want a link I have to go to the web archive for the particular list and find it.

While I was reading the Mailman 3.0 spec I noticed a link to Postfix Virtual Domain Hosting Howto. I think I might have read (at least some of) that before. But… reading that is now definitely on my TODO list.

Postfix Virtual Mailboxes and Procmail Filtering

Am interested in getting procmail to work with my Postfix/Courier setup. Am using virtual domains/aliases/mailboxes stored in a MySQL database and a Maildir file system. Have only just begun my investigations. So far I’ve found:

SpamAssassin whitelist and blacklisting

Today I figured out how to specify whitelist and blacklist email addresses in SpamAssassin.

At the end of /etc/spamassassin/local.cf I added two lines:

include whitelist
include blacklist

Then in the /etc/spamassassin/whitelist file I added some email specifications, e.g.:

jj5@sixsigma:~$ cat /etc/spamassassin/whitelist
# Allow email from system services, e.g. from
# logwatch@hope.progclub.net or root@charity.progclub.org
whitelist_from *@*.progclub.*
# Similarly for blackbrick:
whitelist_from *@*.blackbrick.com

The /etc/spamassassin/blacklist file exists and is ready to go, but I haven’t blacklisted anything yet:

jj5@sixsigma:~$ cat /etc/spamassassin/blacklist
# No email addresses blacklisted yet.
#blacklist_from someone@example.com

Too easy.

There’s some more information on Whitelising a user.

At some point I hope to write a script that processes my users’ maildirs and whitelists everyone they’ve emailed.