Return Boolean True

The easiest way to backup Google Mail accounts is to enable IMAP on the account and download the messages using getmail. Once getmail is installed you need to create a file called getmailrc. If you plan to download multiple gmail accounts then you might want to create a directory for each account and point the getmail script to that directory. Here is an example of a getmailrc file for Google Mail: [retriever] type = SimpleIMAPSSLRetriever server = imap.gmail.com username = [email protected] password = examplepassword mailboxes = ("[Gmail]/All Mail",) port = 993 [destination] type = Maildir path = ~/[email protected]/ [options] received = false delivered_to = false read_all = false verbose = 1 After this file is saved you can procede to run getmail. I needed getmail to run all night and in the background. I outputted all the stdout to a logfile so I used the following command: getmail --getmaildir . > output.txt 2>&1 & Don't forget to create the directories cur, new, tmp as these are the directories that are needed for IMAP. Now that you have your mail in a Maildir format what do you do with it? In my case I wanted to delete the account off Google Apps but still be able to search the mail if I needed it at a later date. The strategy I came up with to bring up a copy of courier and serve the Maildir using a webmail script (in this case Roundcube). I installed PHP through Nginx first. The easiest way to get a PHP environment up and running on Nginx is to use the Ubuntu packages: php5-cgi php5-common For additional functionality such as PostgreSQL support you can install the package: php5-pgsql I then configured nginx with the following script: server { listen 80; server_name webmail.example.com; access_log /var/log/nginx/access.log; log_subrequest off; location / { root /www/webmail.example.com; index index.php; location ~ \.php$ { include fastcgi_params; fastcgi_pass localhost:9000; fastcgi_param SCRIPT_FILENAME /www/webmail.example.com/$fastcgi_script_name; } } } I then created the script: /etc/init.d/php-fcgi BIND=127.0.0.1:9000 USER=www-data PHP_FCGI_CHILDREN=15 PHP_FCGI_MAX_REQUESTS=1000 PHP_CGI=/usr/bin/php-cgi PHP_CGI_NAME=`basename $PHP_CGI` PHP_CGI_ARGS="- USER=$USER PATH=/usr/bin PHP_FCGI_CHILDREN=$PHP_FCGI_CHILDREN PHP_FCGI_MAX_REQUESTS=$PHP_FCGI_MAX_REQUESTS $PHP_CGI -b $BIND" RETVAL=0 start() { echo -n "Starting PHP FastCGI: " start-stop-daemon --quiet --start --background --chuid "$USER" --exec /usr/bin/env -- $PHP_CGI_ARGS RETVAL=$? echo "$PHP_CGI_NAME." } stop() { echo -n "Stopping PHP FastCGI: " killall -q -w -u $USER $PHP_CGI RETVAL=$? echo "$PHP_CGI_NAME." } case "$1" in start) start ;; stop) stop ;; restart) stop start ;; *) echo "Usage: php-fastcgi {start|stop|restart}" exit 1 ;; esac exit $RETVAL After php was up and running I installed courier: apt-get install courier-imap courier-imap-ssl I then downloaded roundcube and configured roundcube as necessary.

Split delivery for e-mail is when you have a single piece of mail but want a copy of it sent to multiple destinations. There are a couple of reasons you would want to do this: - You are getting ready to migrate to Google Apps but don't want to go all in yet with your current e-mail server. This is understandable since you want to test out Google Apps first to see if it will work. - You like Google Apps but don't want to pay the yearly fee. You rather just stay under the limit of the free accounts but still want to have e-mail accounts on your domain (i.e. @example.com). - You have other special circumstances where you want a copy of all the mail that comes in and have it delivered to some other server. This post is actually more toward the 2nd point. 90% of my e-mails are on Google Apps but there is a remaining 10% that I rather not have a Google Apps account. However I still want them to have e-mail via some webmail client. To get this working I am using Ubuntu with Postfix running the primary mail server for example.com. I set the MX records for example.com to this: 10 mail.example.com 20 ALT1.ASPMX.L.GOOGLE.COM Pretty straight forward so far. The trick is that you need to get Postfix to forward a copy of all Google Apps mail to their mail servers. To do this I use Postfix's Before-Queue Content Filter: http://www.postfix.org/SMTPD_PROXY_README.html. This allows me to create a SMTP server that Postfix will delivery a copy of the mail to Google Apps. In the file /etc/postfix/master.cf I put the following at the end: # ============================================================= # service type private unpriv chroot wakeup maxproc command # (yes) (yes) (yes) (never) (100) # ============================================================= # # Before-filter SMTP server. Receive mail from the network and # pass it to the content filter on localhost port 10025. # smtp inet n - n - 20 smtpd -o smtpd_proxy_filter=127.0.0.1:10025 -o smtpd_client_connection_count_limit=10 This makes Postfix delivery a copy of the incoming mail to the SMTP server at 127.0.0.1:10025. Okay but now you are asking where do I get an SMTP server to do the processing? It so happens Python comes with a smtp server library. I wrote a script that basicallyhttp://www.blogger.com/img/blank.gif inherits the SMTPServer (called CustomSMTPServer). It also implements the one command that is expected by Postfix (EHLO) because Postfix actually speaks ESMTP. I did this by subclassing the smtpd.SMTPChannel class. One caveat is that I had to use the _SMTPChannel__variablename syntax because some variables like fqdn and greeting were made private by the SMTPChannel class. So with Python you use the special syntax of prepending the class name to access it. This is generally bad practice but in this case it was all I had. You can download the script here: http://dl.dropbox.com/u/2177278/pymailforwarder.py Simply run the script to start a basic SMTP server listening on port 10025 and localhost. The script simply accepts a piece of mail and forwards it to Google App's mail server. So what does this let you do? In my case this lets me run Roundcube, Horde, or SquirrelMail for users that don't need a Google Apps e-mail account. For those that do I simply create that user on Google Apps. Things to watch out for with this type of deployment: - You have to edit /etc/postfix/main.cf and add the value local_recipient_maps = (Yes that is a blank or equals nothing). This makes Postfix accept the mail even though the recipient is not in the list. This can be bad. Postfix says this in the documentation: With this setting, the Postfix SMTP server will not reject mail with "User unknown in local recipient table". Don't do this on systems that receive mail directly from the Internet. With today's worms and viruses, Postfix will become a backscatter source: it accepts mail for non-existent recipients and then tries to return that mail as "undeliverable" to the often forged sender address. To get around this you should really have an alias map file. For temporary testing though this setting will work wonders. - The Python SMTP relay should not be exposed to the internet. It listens on localhost but ideally it would be nice to modify the script to accept authentication of some sort.

The list of locales that you have installed on a system are in the directory: /usr/lib/locale To generate a locale you can run: locale-gen en_US.UTF-8 This is very useful when you need to generate a UTF-8 locale.

When using Microsoft Office Communicator with a server that has TLS enabled you might get an error message "Problem verifying certificate from the server.". This message means that the computer you are on does not trust the certificate that is being presented to it. The first way to troubleshoot this is to figure out what certificate it is receiving. The easiest way I've found to do this is to use openssl's s_client: openssl s_client -connect lcs.example.com:5061 By doing this you will see the entire certificate chain. You now need to go into the windows certificate management tools and make sure that chain is valid. Generally this will involve running mmc.exe, then adding the snap in "Certificate Management" for the computer itself. Another option is to cut and paste the BEGIN and END certificate lines into a text file. Name the text file with a .der extension and install the certificate. Then browse to the certificate in MMC and see if anything is wrong. Things that might go wrong include the validity date or being unable to trust the certificate chain (most likely from missing certificates). If you are missing certificates you need to track them down and install them. After this is done you should be able to connect to communicator server.

I was recently trying to upload a video to YouTube but kept getting the Rejected (duplicate upload) message. I found the easiest way to get around this is to change the metadata on the video you are trying to upload. In my case it was an mp4 video. To change the metadata I used a program called AtomicParley: http://atomicparsley.sourceforge.net/ After downloading it simply run AtomicParsley.exe "example.mp4" --artist "Me" Or whatever artist you want. The new file will be written out with new metadata. This should then pass any YouTube duplicate content check.

One of my friends recently had a desire to rewrite some URLs with a Wordpress installation. The theme they were using was called Solid-WP and it supported a concept called "Projects". When you create a new project it actually gives it the URL http://www.example.com/project/ However there was a requirement that the URL should be renamed to http://www.example.com/apps/. To do this I broke out mod_rewrite. Wordpress has some default rewrites stored inside .htaccess. Here is what it looks like: # BEGIN WordPress RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] # END WordPress Rewrite can be hard to understand so I wanted to breakdown exactly what Wordpress was doing. First line turns on the Rewrite engine and 2nd line is used to define a base URL for rewrites. RewriteRule ^index\.php$ - [L] If there is a request for /index.php then don't do any rewriting and just end processing right here (the L flag). RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d These rewrite conditions are to test for real files and directories. Basically we don't want to rewrite a URL if the URL points to a directory or file. We just want to serve the file up. !-f tests whether or not the file exists and !-d tests whether or not the directory exists. RewriteRule . /index.php [L] This last line as I understand it rewrites all requests to index.php. What I ended up adding was this: RewriteEngine On RewriteRule project/(.+) /apps/$1 [L,R] RewriteRule apps/(.+) /example-wp/index.php/project/$1/ [L] RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] The first time a user might hit /project/example. They would hit the first rule and get redirected. Processing would stop. The second time a user hit the URL it would say /apps/example which would trigger the 2nd rule. It would get rewritten to the long form of WordPress's controller action.

I am not going to claim eons of experience in designing good APIs. I am going to approach it from the background of a developer who has to use and integrate with them. What makes a good API? Here are some of my tenets: 1. Make your API calls as RESTful-like as possible Because this term has evolved quite a bit I am going to stick with the primarily principles. Make API calls nouns describing "what" and not "do something". 2. API calls should have defaults. Don't give me 100 required parameters just to see some action. Try as hard as you can to give me a basic call so I know I am doing something right. Along with this is to keep a minimum of API calls. The more calls you have documented the more I have to figure out which one it is I am suppose to be calling to get the right information. This is an area where I actually do want to be spoon-fed. 3. Use HTTP basic over SSL for authentication. If you have the time and energy also support OAuth. The reason I hesitate with going straight to OAuth is because if you are just building an API your resources are probably limited. You are going to make mistakes. Getting it up and running with the lowest (and secure) common denominator is key. Also use dedicated API keys that consist of an ID and a shared secret. Make sure these can be rolled. 4. Make your return format JSON. For the love of god please don't use XML. 5. Version your API call in the end point: /api/1.0/user/3 /api/2.0/user/3 6. Make the calls easily testable. To me this means I can plug it into a web browser, type in some credentials, and get a response back. As a developer this makes me feel good early on. 7. Document your API calls with examples. Especially the ones where I can click on a link and it does an API call for me. This is also great for testing your call. A number of these guidelines are geared heavily to web development. If you are designing an API for a message passing system with latency and size requirements a good deal of this would change.

I recently had to do some shopping for a SSL certificate for my startup Stratismo (I linked to it incase anyone wants to see the actual certificate). Obviously I wanted one that was widely supported and didn't really want to pay a ridiculous amount for it. So shopping around I landed on RapidSSL's site. RapidSSL has a program where you can switch to them if you have a competitor's certificate. On top of that they also give you a free year. All of this for free. The program details are here: http://www.rapidssl.com/switch-ssl/index.html I just happened to have a Comodo certificate so I gave this a test run. The Comodo certificate had some issues because of the number of intermediate certificates I had to include. While this shouldn't cause problems in theory in reality it is just one more thing to deal with. So what I did was apply for RapidSSL. They ended up giving me one of their SSL certificates for free after verifying I had a Comodo SSL certificate. They also extended the validation by a year so basically I got two years for $10. RapidSSL certificates are also signed by Equifax which is installed on almost every browser. Overall a great deal.

Security Assertion Markup Language (SAML) can be a bit confusing to understand. At its core SAML is just a protocol with defined messages written in XML. The main purpose of SAML is to enable you to log in at one place such as a website and then jump over to another website without having to log in again. This setup is commonly called "federation". It is similiar to OAuth. I see SAML continuing to make headroom in the enterprise space while OAuth stays strong in the consumer space. However in the future I hope these two technologies will end up playing well together. In either case I am releasing a small Python library for generating SAML assertions. The main purpose of this is to learn SAML by doing (actually having to create an assertion gives me a good idea of the complexity of the protocol). The library depends on M2Crypto so download and install it: http://chandlerproject.org/bin/view/Projects/MeTooCrypto M2Crypto depends on SWIG so you might need that as well. Once that is installed you can download my distribution of PySAML here: Python 2.6 - Win32: http://darkeneddesire.com/PySAML/PySAML-1.0.win32.exe Unix (source): http://darkeneddesire.com/PySAML/PySAML.tar.gz For windows you just run the executable. For unix you should run the following commands: # cd PySAML # python setup.py build # python setup.by install There are examples in the "examples" folder if you download the full source. The whole project is available on github as well: http://github.com/tachang/PySAML/tree/master

There is a product being sold called "Magic SIM". http://www.magicsim.com/en/dual_sim_show.asp?id=49&cp_id=&sort2name=14 Basically it is a SIM card that has two slots and a small memory chip. After physically cutting up your two SIM cards and putting them into the slots you insert the whole thing into your phone. If your phone supports the GSM STK (SIM Tool Kit) standard then you can switch back and forth between the two SIM cards. However for your phone to actually support the standard the manufacturer had to have built it into the operating system as well as provide a tool to "talk" using the STK. I currently see that the Android development tree has some Stk development going on. I downloaded a precompiled Stk.apk and installed it on my phone with the card. However it does not seem to work. While I do see the SIM Toolkit menu icon and it does seem to read from the custom card I am unable to obtain a carrier signal from either of my SIM cards. When I scroll to any of the menu options such as "SIM 1" or "SIM 2" and press the trackball the phone simply gives me a rotating circle on the upper right saying it is busy. And at that point it hangs. Here is a quick and dirty image of my phone as well as what the SIM menu looks like:

Running the command (making sure we run Git\bin's ssh.exe and not some other one in the PATH): C:\Program Files\Git\bin>ssh.exe -F "C:\Documents and Settings\\.ssh\config-windows" github.com Hi tachang! You've successfully authenticated, but GitHub does not provide shell access. Connection to github.com closed General Git Cloning - Make sure you are using the right Git URL: Suppose your Public Clone URL is: git://github.com/tachang/EyeFiServer.git You should use the following URL that utilizes the SSH transport: git clone ssh://[email protected]:22/tachang/EyeFiServer.git git clone ssh://[email protected]:443/tachang/EyeFiServer.git

One of the central pieces of Django is urls.py: http://docs.djangoproject.com/en/dev/topics/http/urls/ This file is well documented and serves as a central place to match what pages get served by what URLs. Seems simple enough since they accept regular expressions. One thing I did run into though was getting a TypeError exception. It looked something like this: TypeError at /applicationname/ index() takes exactly 1 argument (2 given) To me I was puzzled why this was happening. The reason is that when Django parses the regular expression it not only does a match but saves each of the tuples in the regular expression. In the documentation it is this line: "The view gets passed an HttpRequest as its first argument and any values captured in the regex as remaining arguments." So what happens is that when you start to get fancy with your regular expressions the function signature in your views.py needs to change as well to accommodate the extra parameters.

Save the file as "Generic4xAgent". Now run the command: smobjimport -iGeneric4xAgent -dsiteminder -wpassword -c -i is the filename -d is the SiteMinder admin username -w is the SiteMinder admin password -c indicates that the file has cleartext passwords This creates a 4.x agent named "siteminder" with a shared secret of "password". At this point you should be able to login to the traditional admin UI.

On FreeBSD when you want to install a program you have to make a choice. Your two choices are to install a package or compile from ports. Installing a package means you download a binary package and copy all the files to the right places. Everything is already compiled. This is how Windows works. When you install a piece of software it has already been compiled. Your second option is to compile from ports. What this means is that the source files are downloaded and then compiled on your system. You need to have all the prerequisites for the compile to be successful. Why choose one over the other? Well with packages sometimes the binary doesn't work. Either you happen to have a newer or older file than what the creator compiled it with or you changed something with your system and it doesn't match anymore with the author's compiled environment. However packages are fast to install. No need to break out gcc and compile source code. Ports on the other hand will almost always work. They are targetted for your system because you are compiling them. It takes a bit longer but you also get to customize any of the build options. To install a program from package you use this command: pkg_add -r Examples: pkg_add -r xorg pkg_add -r nano pkg_add -r curl I like pkg_add -r because it fetches the package for me and installs it. It does that by looking at your system's uname (I think) and forms a URL to FreeBSD's software repository. The problem is that after a while repositories are taken offline. So if you are using some older version of FreeBSD and trying to do a pkg_add -r it will return that it can't find the package. The thing is, the package is probably still around but in a newer form. The newer package is compatible with your version if you can find it. FreeBSD makes a statement that says packages in the same stable branch will always be compatible. To force pkg_add -r to bend to your will you edit the PACKAGESITE environment variable. If you want to force pkg_add -to download FreeBSD 7-STABLE packages, set PACKAGESITE to ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/. Be very careful though that you point to the right URL. I actually pointed to the wrong URL and downloaded 32-bit packages instead of the amd64 packages which I needed: http://ftp2.at.freebsd.org/pub/FreeBSD/ports/amd64/packages-7-stable/Latest/

Sometimes you just want to get a file off your phone. One of the easiest ways to do this is bluetooth. The problem is that some carriers (such as Verizon) lock their phones down so you can't transfer files from your phone to your PC over bluetooth. The real technicality is that while the phone can't initiate the sending of the file, you can still browse the phone for files and pull them. So far the most useful tool I found to get files off my phone (which is an LG Chocolate) is obexftp. To get started install the package using Synaptic then open up a console and type: $ obexftp -b When you find a device you want you connect to it like so: $ obexftp -b 00:1E:75:ED:62:2C -l Browsing 00:1E:75:ED:62:2C ... Channel: 7 Connecting...done Receiving "(null)"... done Disconnecting...done The way obexftp works is that you basically have to run the command over and over with different options to get what you want. So after running it with this "list" option I say I want to browse the folder "MyPictures". $ obexftp -b 00:1E:75:ED:62:2C -c MyPictures -l Browsing 00:1E:75:ED:62:2C ... Channel: 7 Connecting...done Sending "MyPictures"... done Receiving "(null)"... done Disconnecting...done Now that I know the location of the file I can procede to actually get the file. $ obexftp -b 00:1E:75:ED:62:2C -c MyPictures -g 0512091207.jpg Browsing 00:1E:75:ED:62:2C ... Channel: 7 Connecting...done Sending "MyPictures"... done Receiving "0512091207.jpg"...|done Disconnecting...done Easy enough. Probably not the most intuitive way to do things but it gets the job done.

Ever get that popup when you visited a supposedly "secure" website that says the certificate is not trusted? Reason you get that popup is because the person who signed/issued the certificate is not trusted by default on your computer. The business of selling certificates is a lucrative one. Large certificate authorities such as Thawte and VeriSign make a killing issuing digital certifcates. They can arbitrarily adjust the parameters on the certificate and charge for it on a case by case basis. The reason they are able to do so is because almost every computer by default trusts these companies. You can check this in Windows by going to start, run, mmc.exe and adding the Certificate snap in. Look under Trusted Root Certification Authorities. In general you have to pay quite a bit of money to get a certificate signed by one of these authorities. However there is one way to get a virtually "free" one. Thawte offers a program called their Web of Trust: https://www.thawte.com/cgi/personal/wot/contents.exe Basically after going through the steps Thawte will give you a free certificate signed by an authority called "Thawte Personal Freemail CA". Because this CA is installed by default on all Windows installations it is trusted everywhere. Getting this certificate involves a combination of sending in documents to Thawte or finding people who have already gone through the process to vouch for you. Once you have it though you keep it forever (as far as I can see) and can generate certificates with your e-mail address in it.

Getting the python xmlsec library to work on windows is a bit of work though it really shouldn't be. Provided here are windows installers for xmlsec. The installer itself is produced by python distutils. In order to get it to work you will also need libxml2. I am providing a copy of it here as well. pyxmlsec-0.3.0.win32-py2.6.exe libxml2-python-2.7.3.win32-py2.6.exe I used MinGW for compilation. The entire environment I used to compile pyxmlsec is available here. Look inside the pyxmlsec directory for build.bat. PythonWindowsCompileEnvironment.zip