takizo, not takezo

If you email having problem with rejected EHLO or HELO, caused by syntactically invalid argument(s).

• Possible the hostname contains underscore(_).
• This is not standard practice, having _ for your domain
• for example takizo_mail.takizo.com
• Most of the mail server rejected hostname with underscore.
• Possibility is a Windows Admin

Error message shows in exim’s log;

2007-01-31 09:13:21 rejected EHLO from [123.123.123.123]: syntactically invalid argument(s): stupid_proxy.windowsadmin.com.my
2007-01-31 09:13:21 rejected HELO from [123.123.123.123]: syntactically invalid argument(s): stupid_proxy.windowsadmin.com.my

Solutions: Add this line in exim configuration main section;

helo_allow_chars = _

Now your exim should be working and receive email from the l33t! hostname. _hell_.lamer.com

In our mailserver, we backup every incoming email and keep it for a week. Sometime, it’s PITA when you want to purge the old email. For example;

[takizo@rooney backup]# rm -rf S0118*
-bash: /bin/rm: Argument list too long

when come to rm large amount of files, or editing, or rename, xargs is … very useful, no more PITA.

[takizo@rooney backup]# find . -name ‘S0118*’ | xargs rm

that’s it, so my friend, don’t do rm S011800*, S011802*, S011803*, S011804*, S011823 …. It’s wasting your time

update 20080721 : for file name with spaces with it use “find . -iname S0118* -print0 | xargs -0 rm”.

mincus has written useful Firefox extension called Adsense Notifier. It displays your Adsense latest earning at Firefox toolbar. If you are always concern what is your adsense earning, it’s a great tool for you.

Website: http://code.mincus.com/3/adsense-notifier/