AK's weblog

In less than 3 hours, I'll be on my way to Berlin. Actually, first of all, I have to go to Vienna, where I then go to the airport, where I will take a plane to Berlin. At around 6 pm I should have reached Berlin. Checking out will take some time, so I expect to leave Berlin-Tegel not before 7 pm. Then first I will leave all my stuff at the hotel, and try to get my ticket for tomorrow. Without getting a ticket today, it will be extremely hard to get to the opening event early enough. The opening event is a must, since the official documentation movie about the Chaos Communication Camp will be presented, which I just have to see.

Finally, I found a "good" way to handle not only reading mail from everywhere, but also sending mail. First of all, all my mails are stored on my mail/news/fileserver, where I access them via IMAP. From outside, they're accessible via IMAPS (for the usual security reasons, you know, unencrypted protocols are evil). That's not that weird, because it can all be handled smoothly with some imapd, stunnel (on the server side) and mutt (on the client side). But now the setup for sending mail: first of all, when mutt sends a mail, it runs the sendmail binary provided by nullmailer. When nullmailer-send is being run, it connects to localhost:5000 to send the mail. On this port, stunnel in client mode is listening, which then connects to my machine home. On the machine home, another stunnel in server mode received the connection, and hands over the data to a local SMTP server, where it is then transmitted to my ISP's smarthost. This is really the weirdest mail setup I ever had. But so far, it's the only way to communicate securely (or at least more secure than usual) and using mutt at the same time. I had a similar, but simpler setup with Mail.app from Mac OS X, but this mailer sucks, compared to mutt.