To make Postfix work with GMail you just need to add these lines to main.cf:

relayhost = [smtp.gmail.com]:587

# TLS
smtp_use_tls = yes
smtp_tls_CAfile=/etc/pki/tls/cert.pem # CentOS path
smtp_tls_loglevel=2
smtp_sasl_tls_security_options = noanonymous
tls_random_source = dev:/dev/urandom


And put just one line in sasl_passwd

[smtp.gmail.com]:587 username@gmail.com:password


After issuing following commands a connection between GMail and Postfix should work fine. You can test it using mail or sendmail program:

$ postmap hash:/etc/postfix/sasl_passwd
$ /etc/init.d/postfix restart
$ mail test@example.com
Subject: Test main
Test message
.
Cc:


You should have something like this in your /var/log/maillog file:

Dec 29 00:49:48 localhost postfix/smtp[5942]: setting up TLS connection to smtp.gmail.com
Dec 29 00:49:48 localhost postfix/smtp[5942]: certificate verification depth=2 subject=/C=US/O=Equifax/OU=Equifax Secure Certificate Authority
Dec 29 00:49:48 localhost postfix/smtp[5942]: verify return: 1
Dec 29 00:49:48 localhost postfix/smtp[5942]: certificate verification depth=1 subject=/C=US/O=Google Inc/CN=Google Internet Authority
Dec 29 00:49:48 localhost postfix/smtp[5942]: verify return: 1
Dec 29 00:49:48 localhost postfix/smtp[5942]: certificate verification depth=0 subject=/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com
Dec 29 00:49:48 localhost postfix/smtp[5942]: verify return: 1
Dec 29 00:49:48 localhost postfix/smtp[5942]: SSL_connect:SSLv3 read server certificate A
Dec 29 00:49:48 localhost postfix/smtp[5942]: SSL_connect:error in SSLv3 read server key exchange A
Dec 29 00:49:48 localhost postfix/smtp[5942]: SSL_connect:error in SSLv3 read server key exchange A
Dec 29 00:49:48 localhost postfix/smtp[5942]: SSL_connect:SSLv3 read server done A
Dec 29 00:49:48 localhost postfix/smtp[5942]: SSL_connect:SSLv3 write client key exchange A
Dec 29 00:49:48 localhost postfix/smtp[5942]: SSL_connect:SSLv3 write change cipher spec A
Dec 29 00:49:48 localhost postfix/smtp[5942]: SSL_connect:SSLv3 write finished A
Dec 29 00:49:48 localhost postfix/smtp[5942]: SSL_connect:SSLv3 flush data
Dec 29 00:49:48 localhost postfix/smtp[5942]: SSL_connect:error in SSLv3 read finished A
Dec 29 00:49:48 localhost last message repeated 3 times
Dec 29 00:49:48 localhost postfix/smtp[5942]: SSL_connect:SSLv3 read finished A
Dec 29 00:49:48 localhost postfix/smtp[5942]: Verified: subject_CN=smtp.gmail.com, issuer=Google Internet Authority
Dec 29 00:49:48 localhost postfix/smtp[5942]: TLS connection established to smtp.gmail.com: TLSv1 with cipher RC4-SHA (128/128 bits)
Dec 29 00:49:50 localhost postfix/smtp[5942]: 955CE3D48A06: to= , relay=smtp.gmail.com[74.125.79.108]:587, delay=2.2, delays=0.12/0.03/0.9/1.2, dsn=2.0.0, status=sent (250 2.0.0 OK 1325116190 t59sm126911139eeh.10)
Dec 29 00:49:50 localhost postfix/qmgr[5923]: 955CE3D48A06: removed


GIT

Today I used git cherry-pick command for the first time, and I am really impressed. In my current project I’ve few branches, just for fixing/delopment. There are also a few common files like documentation, TODO – simple text files. Sometimes I came up with a genius idea and I want to put it in TODO file just not to forget. The problem is that I can’t guarantee that I will be working on 'master' branch at that time. Using cherry-pick I was able to update ‘master’ branch just with this one commit from other branch.
One might say that instead of using cherry-pickI could first switch to ‘master’ and made a change. But this have to be done immediatly, while cherry-picking can be deferred in time:

$ git checkout master
$ git cherry-pick -x aac5f43

where „aac5f43″ is a part of commit SHA1 that should be picked. Commits information can be retrived using git log command.

-- {{{ Tags
-- Define a tag table which hold all screen tags.
tags = {}
for s = 1, screen.count() do
    -- Each screen has its own tag table.
    tags[s] = awful.tag({ "WEB", "MAIL/IM", "TERM", "DEV", "NOTES", "WORK", 7, 8, 9 }, s, layouts[1])

    awful.tag.seticon("/home/pejotr/awesomeicons/INTERNET_16x16-32_b.png", tags[s][1])
    awful.tag.seticon("/home/pejotr/awesomeicons/CHAT_16x16-32_b.png", tags[s][2])
    awful.tag.seticon("/home/pejotr/awesomeicons/SHELL_16x16_b.png", tags[s][3])
    awful.tag.seticon("/home/pejotr/awesomeicons/BUG_16x16_b.png", tags[s][4])
    awful.tag.seticon("/home/pejotr/awesomeicons/ADDRESSBOOK_16x16-32_b.png", tags[s][5])
    awful.tag.seticon("/home/pejotr/awesomeicons/TOOLS_16x16-32_b.png", tags[s][6])
end
-- }}}

And the result is:

1. 1. Copy database tables and Mambo code from remote server to local system. I used WAMP to do all migration. By doing that the site was still online, while I was doing some research. If for some reason you don’t have access to phpMyAdmin or any other database client, use SIDU 3.2 DB Web GUI
2. 2. Convert SQL file to UTF8 encoding.You can do this using i.e. Notepad++ – use Convert to UTF8 (without BOM).
   Also change tables encoding to UTF8. This operation will cause problems with ‘ocp_core_acl_aro’ table "#1071, Specified key was too long; max key length is 1000 bytes". Rewrite it as below

   CREATE TABLE `ocp_core_acl_aro` (
   `aro_id` int(11) NOT NULL auto_increment,
   `section_value` varchar(240) NOT NULL default '0',
   `value` varchar(240) NOT NULL default '',
   `order_value` int(11) NOT NULL default '0',
   `name` varchar(255) NOT NULL default '',
   `hidden` int(11) NOT NULL default '0',
   PRIMARY KEY  (`aro_id`),
   UNIQUE KEY `ocp_gacl_section_value_value_aro` (`section_value`(100),`value`(75)),
   UNIQUE KEY `section_value_value_aro` (`section_value`(100),`value`(75)),
   KEY `hidden_aro` (`hidden`),
   KEY `ocp_gacl_hidden_aro` (`hidden`)
   ) ENGINE=MyISAM AUTO_INCREMENT=13 DEFAULT CHARSET=utf8
   

3. 3. Migrate to Mambo 4.5.2 Create local database for Mambo 4.5.2 and use utf8_general_ci for connection and comparison. Download and extract Mambo 4.5.2 to webserver directory. Change db settings in configuration.php and apply sql script upgrade451to452.sql from installation\sql direcotry
4. 4. Install Joomla 1.5 but do not load sample data
5. 5. Install mtwmigrator for Joomla 1.5 You can download it here mtwmigrator-v0-2-1. Run component and go to Preference. Set db name, location, login and password. Select data you want to migrate and launch migration process. After this step you should have all data from Joomla 1.0 availbale in new installation on Joomla 1.5
6. 6. Migrate to Joomla 1.6 using jUpgrade. You can download it here jUpgrade. All you have to do is to install it within Joomla 1.5 and start. If some problem occurs try enabling Debuging in jUpgrade

Now, you should have new installation of Joomla 1.6 created for you and available in jUpgrade dir in Joomla 1.5 directory. New tables were created in same database as Joomla 1.5, so depending on needs, final step might be to dump those tables and move to new, dedicated location.

Program('main.cpp')

Na Windows domyślnie zostanie wykorzystany (o ile dostępny) kompilator Microsoftu. Jeśli jednak chcemy użyć g++, wystarczy dopisać jeszcze jedną linię:

env = Environment(tools = ['mingw'], CC = 'gcc', CCFLAGS = '-O2')
env.Program('main.cpp')

Piewsze lody przełamane, kolejne próby będą sprawdzały łatwość dołączania zewnętrzych bibliotek jak boost czy qt.

Postanowiłem skupić się tylko i wyłącznie na Java’ie ( j2se, j2ee, raczej nie j2me ), C++, na Windowsie 2008 bo nadarzyła się okazja poadministrowania takim systemem oraz na moich skromnych osiągnięciach w zakresie elektroniki – ogólnie rzecz ujmując wszystkim czym będę się zajmował. Różnice w stosunku do poprzedniego bloga? Wpisy bardziej do rzeczy, więcej szczegółów, więcej sensu, więcej treści, i multimediów.

Kolorowanie kodu powinno działać:

class PolskiAlfabetMorsea extends JFrame {
  public static void main(String[] args) {
    System.out.println("Witaj świecie");
  }
}

#include <iostream>
#include <fstream>

class XmlTokenizer
{
public:
  void tokenize(const std::ifstream&amp;amp;amp;amp;amp; strumien);
};

Kilka najsensowniejszych wpisów z poprzedniego bloga zapewne odpowiednio obrobię aby spełniały moje nowe kryteria i tu umieszczę. Dla zainteresowanych, stara wersja jest cały czas dostępna pod adresem:  www.piotr.doniec.eu/blog/

Test eg-attachments: