I have spent the whole day to work on the qmail server and finally got it done!
Now, my mutt works fine on my freebsd machine, which receives email from the imap server and deliver email through my local qmail server.
The qmail server relays every email to the smtp server in the cs department, which requires smtp auth over SSL/TLS.
The SMTP AUTH over SSL/TLS really causes a big trouble to me, because I was struggling to grab and save the certificate from the server. However, I failed. But, without the local storage of the certificate, the qmail-remote (the program relays email to other smtp server) still works!
All my effort haven't been wasted. I've got a better understanding of SMTP and MUA/MTA/mail relay now. I also spend a lot of time trying to figure out the TLS/SSL certificate related to the smtp protocol. Oh, man. It's so complicated.
I've fixed a bug in the qmail-send-auth-tls patch. (A simple sig. fault)
Played with the muttrc file, I've changed the "From" field in the email header from "freebsd.lrh516.net" to "cs.sfu.ca". Thus, everything works fine now. Bravo!
Friday, July 15, 2005
Use FreeBSD
This week, I started using freebsd intensively on my old desktop.
After hundreds of test-and-try, I am now a bit familar with the freebsd system now.
The following is my short review of the freebsd 5.4-release
1) Installation. With the help of documentation, the installation is not too difficult. I may point out that it involves a lot of network configuration, which might be too hard for newbies. As I had already got used to the text-based installation of Debian, the text-based freebsd installation doesn't give me much trouble.
2) Software installation. You may use both binary package or source based ports system to install softwares. It's flexible. The dependency problem seems no trouble. However, because my desktop is so slow (Celeon 550M), that I can do a "world" source based upgrade.
3) The other part is quite similar to other Linux/Unix system.
Anyway, I have figured out the sawfish configuration a little bit. That's a good thing.
FreeBSD tips
1) LS color: to enable colors in 'ls' command, you have to use 'ls -G' command option. Also, you must set the value of the LSCOLORS variable for propers. It is not as flexible as Linux LS_COLORS variable.
After hundreds of test-and-try, I am now a bit familar with the freebsd system now.
The following is my short review of the freebsd 5.4-release
1) Installation. With the help of documentation, the installation is not too difficult. I may point out that it involves a lot of network configuration, which might be too hard for newbies. As I had already got used to the text-based installation of Debian, the text-based freebsd installation doesn't give me much trouble.
2) Software installation. You may use both binary package or source based ports system to install softwares. It's flexible. The dependency problem seems no trouble. However, because my desktop is so slow (Celeon 550M), that I can do a "world" source based upgrade.
3) The other part is quite similar to other Linux/Unix system.
Anyway, I have figured out the sawfish configuration a little bit. That's a good thing.
FreeBSD tips
1) LS color: to enable colors in 'ls' command, you have to use 'ls -G' command option. Also, you must set the value of the LSCOLORS variable for propers. It is not as flexible as Linux LS_COLORS variable.
Subscribe to:
Posts (Atom)