Implementing and fixing some problems with the statistics in the server. Setting the cron and some extra scripting with the GeoIP related which needed to be compiled, as long as ubuntu set the files in its proper way.
Some code modification, compiling the source and...Wuala!! running whithout a complaint!!

Little poem and that is all for today.
Tomorrow back home running from work, that will be at 14:00.
Needed to setup the tools for testing and some other things in the queue which needs to be done asap.!

Nite.

Gonza.

it took me awhile...but finally done!!
I was getting problems with smtp auhorization, in fact I forgot to include in /etc/postfix/main.cf the following line to open the smtp authorization login:

smtpd_sasl_auth_enable = yes

Also I included:
smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache
for the cache.
Using pam for the login in the sasl/smtpd.conf
I went into cyrus and the configuration was changed into:
pwcheck_method:auxprop

For creating the Berkeley db /etc/sasldb2 needed the following comands:
saslpasswd2 -c -u domain.com -a smtpauth rusername (-c crate -d delete -u domain -a authorization )
sasldblistusers2 to list the users.
Look at the user/group owner. Nice way postfix:root

Debian/ubuntu issue. the file has to be change into its proper place ... /var/spool/postfix/etc/sasldb2
but also can be modfies the /etc/init.d/postfix to point it to : etc/sasld2 ( FILES="etc/localtime etc/services etc/resolv.conf etc/hosts etc/nsswitch.conf etc/sasldb2")

Do not forget also to make an extensive change into the /etc/default/saslauthd as follows:

# This needs to be uncommented before saslauthd will be run automatically
START=yes

PWDIR="/var/spool/postfix/var/run/saslauthd"
#PARAMS="-m ${PWDIR}"
PIDFILE="${PWDIR}/saslauthd.pid"

# You must specify the authentication mechanisms you wish to use.
# This defaults to "pam" for PAM support, but may also include
# "shadow" or "sasldb", like this:
# MECHANISMS="pam shadow"

MECHANISMS="pam sasldb"
PARAMS="-m /var/spool/postfix/var/run/saslauthd
************************

in terms of supporting the standard PAM and the Berkely sasldb

restart /etc/init.d/saslauthd
restart /etc/init.d/postfix
and setup the mail client smtp as : secure wirh username: username@domain.com
password as provided before into the Berkeley db.
And..Wala! Up and Runing !!! relay access granted and routing mail to the internet, supporting both intranet and internet services.
All along with TSL certificates to validate the mail with digital signature and also supporting some virtual domains run by courier pop3/pop3-ssl/imap/imap-ssl.

Tomorrow finishing the whole explanation for the process.

Thanks.

Gonza.