Partnering with agencies happen in various ways but benefit from a common goal to stick to core competencies
By applying our experience, libraries and know-how we have come up with some solutions that stand on their own
About Martin
Multi-disciplinary background, with experience in financial, creative, software and communications firms. Releases the power of information through structured information architecture, providing the data models allowing firms to improve their information flow and visibility. Improving marketing efficiency by crafting metrics to display ROI and breaking down user journeys.
An expert in marketing, information architecture and online strategies, clients have benefited from improved organisational data quality, enhanced internal and external communication and improved information lifecycle management..
Specialities
Management skills: Organisational Change, Internal Communications, Change Management, Information Architecture, Online Marketing Strategy, Social Media Strategy.
Expert technical skills: Data Modelling, Data Warehousing, Metric Generation, User Journey Profiling, Object Relationship Modelling, Framework Construction, Web Programming (PHP, PEAR, Zend, PECL), Rich Application Creation and Deployment (MVC, RAD, ORM, OOP), Database Architecture (MySQL, Oracle, PDO, ODBC, Replication)
Recent posts
Zimbra and Spam Assassin Y2k10 bug FH_DATE_PAST_20XX header
25th March 10 - Posted by Ollie Maitland
All the Y2K issues were after all quite a let down yielding almost no exciting failures or blue screens of death.
I did however come across a minor bug in Zimbra and Spam Assassin today which was slightly confusing and an example of some pretty bad programming. Spam Assassin has a number of rules which determine whether an email is valid or not; one such rule is whether an email is dates "grossly in the future".
We noticed that more emails where being detected as spam more than usual. In further investigation this code was found in 72_active.cf :
##{ FH_DATE_PAST_20XX
header FH_DATE_PAST_20XX Date =~ /20[1-9][0-9]/ [if-unset: 2006]^M
describe FH_DATE_PAST_20XX The date is grossly in the future.^M
##} FH_DATE_PAST_20XX
This generates FH_DATE_PAST_20XX on almost all emails. Clearly the programmer could see that when the date goes from 2009 to 2010 this would be illegal.
Anyway, the problem is easily solved:
##{ FH_DATE_PAST_20XX
header FH_DATE_PAST_20XX Date =~ /20[2-9][0-9]/ [if-unset: 2006]^M
describe FH_DATE_PAST_20XX The date is grossly in the future.^M
##} FH_DATE_PAST_20XX
And thankfully happy customers again :)
Note: It also seems like someone else found this too
0845 625 2825