So today I finally got round to transferring my main domain email over to Google Apps. It's something I've been looking into for a while now (ever since Jem and work started using it, haha) but have either not had the time, or had some reason or other why I couldn't do it. Lately though, SpamAssassin - which I'd been using on my hosting account - had been eating a lot of genuine mail while letting some obvious spam through. No amount of twiddling the settings or turning on/off seemed to fix it and I was getting really bored of having to whitelist every single person who emailed me.

So far, so good. Gmail has caught lots of spam and genuine messages have got through. I'm a bit worried that all my forwarders won't work since I used multiple domains and Gmail doesn't seem to want to differentiate between domains... blah@domain1 is the same as blah@domain2, it seems. Oh, and the IMAP interface takes some getting used to, but I've been using it at work with no problems and Thunderbird seemed to be coping well so here's hoping it continues for my own account.

I did have a minor problem though... I had all my PHP-generated emails (e.g. new comment notifications, etc) go through my old SMTP gateway. Of course, that no longer works now since I'm all Gmailed, and Gmail seem to want an SSL connection when sending email and I can't work out how to do that in PHP right now (any ideas? Let me know! I know we had all sorts of issues at work doing it and Google weren't too happy at the end anyway so not sure if it's worth it...). Hope my ISP doesn't mind me using their SMTP for now, heh. :D

Right then, two weeks off :D I hope I can finally get round to finishing PAI/Askably/whatever-it's-called-these-days v3.1 as it's kind of been in the works for 2 years... Small matter of Christmas getting in the way but maybe I'll find some time here and there. Get any feature requests in now if you have any, the main point of this release is to tidy up coding and such really, database queries are stupidly ... stupid ... in v3.0 and need optimising, as well as the actual coding structure being awkward and full of stuff I thought I knew but really didn't. Busy busy!

I like cats. Have I mentioned that? Ever since I moved into my new house, I have wanted to own one, however time and money constraints have meant that hasn't happened :( Jem has 2 cats, Melissa has 2 cats, Sarah is getting one next month... I feel left out when I look at their pictures of cutesy kitties :P

So, in the near future, we have decided: kitty will be coming. I used to have 3 when I was younger but I never knew them as kittens so don't know what to expect. Should I keep them inside? Mix of both outside and inside? Litter-train or make them go outside?

In other non-cat news, new names for PHPAskIt and NL-Wotsit have been tentatively decided: Askably and Mailably. I will be rebranding them as such soon, unless I (or anyone else) can think of a better name. :)

It came to my attention recently that using "PHP" in a script name goes against the PHP licence. Don't know why I've never noticed this before - I've read the PHP licence several times and it's been in there ever since version 3.0 - but there you go. This means that PHPAskIt and NL-PHPMail need to be renamed.

So, this leaves me with a dilemma. What do I call them instead? I could just drop the "PHP" but NL-Mail sounds a bit ... eh ... and AskIt has already been taken by another script so I can't use that. NL wasn't my script to begin with so the name wasn't my choice, so now is a good time to really make it mine... But with what name? Hmmm.

Any ideas?

Edit: I know that technically the term in the licence only applies to software derived from the PHP sources, but when I asked the PHP people what their official stance on it was, they said they really would prefer I renamed the scripts. So, whether or not their licence terms apply to my scripts or not, I am going to comply with their wishes and rename. K? K.