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 Ollie
Web technologist with the know-how to Release the Power of Information by creating collaborative environments for staff to share effectively the knowledge within their organisations. Recipients of consultancy on rich internet applications, from inception to lifecycle support, have benefited from remodelled and renewed revenue streams.
An expert in delivering business and enterprise grade applications from recruitment software to customer relationship management to data collection and warehousing platforms. Practical programming skills are particularly strong in user interface and experience application development with the latest Web2.0 technologies..
Specialities
Management skills: Project Management, Web Systems Architect, Consultancy on Rich Internet Applications, Server Administration, System Deployment and Developer Collaboration/Management.
Expert technical skills: Linux (Redhat & CentOS), Zend (PHP, Zend Platform, PEAR, PECL), Application Layer Programming (MVC, ORM, RAD, OOP, SVN), MySQL (SQL, PDO, Replication), UI Development (JavaScript, Prototype, Mootools, ExtJS, jQuery, Flex, WebObjects, XML, JSON, AJAX, CSS, XHTML)
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
Vision of the web
- 100% ACID score on all browsers
- Cloud web hosting please!
- I'd love to see Push Technology application frameworks for the masses
- Enterprise web application frameworks with common data protocols
- Cheap bandwidth for everyone
0845 625 2825