dovecot, kmail & thunderbird

[federico]

Doh! sent it from the wrong address and it bounced.
Here it goes again.

I managed to make a fool of myself three times!
and kmail crashed on me while resending.
Not my day.


On Wednesday 08 March 2006 23:56, Art Alexion wrote: 
Art Alexion escribió:
> Fedirico, you are the best!

:-) (:blush:)

> On Wednesday 08 March 2006 10:10, federico wrote:
> > On Monday 06 March 2006 20:54, Derek Broughton wrote:
> > Derek Broughton escribió:
>

>
> > Do sudo invoke-rc.d dovecot restart
>
> This didn't work so I did
> sudo /etc/init.d/dovecot restart
> That worked.  I assume it does the same thing.
>

I wonder why it did not work but it should be 
the same thing, yes.



> Mar  8 21:42:51 localhost fetchmail[954]: SMTP connect to localhost failed
> Mar  8 21:42:51 localhost fetchmail[954]: SMTP transaction error while
> fetching from pop.mail.yahoo.com
> Mar  8 21:42:51 localhost fetchmail[954]: Query status=10 (SMTP)
> Mar  8 21:42:51 localhost fetchmail[954]: Warning: server certificate
> verification: unable to get local issuer certificate
> Mar  8 21:42:51 localhost fetchmail[954]: SSL connection failed.
> Mar  8 21:42:51 localhost fetchmail[954]: Query status=3 (AUTHFAIL)
> Mar  8 21:42:51 localhost fetchmail[954]: sleeping at Wed 08 Mar 2006
> 09:42:51 PM EST
>

We seem to have two issues here:
1) Connection with localhost, verified as per Derek's suggestion.
2) Connection with pop.mail.yahoo.com

> Note that I configured 3 accounts in fetchmailrc and artalexion at yahoo.com
> is only one of them.

How are them configured in thunderbird/kmail ?
Do they use TLS or SSL ?

If so, I think you need to download the keys and
install them so fetchmail can use them. This is similar
to what one does with apt-keys but a little bit more
involved :-/

For gmail go to:

http://freshmeat.net/articles/view/1673/

and in the "Fetchmail" section it explain what to do
to get and import the key. It is rather easy and
a good read.

It should be similar in other cases but I can 
not tell since I haven't had the chance to do this
for other than gmail.

For my other servers, those that need TLS 
just work as in the snip I posted earlier.

Now let's test postfix:

check /etc/hosts

it should have something along the lines:

127.0.0.1       localhost localhost.localdomain
192.168.1.1     machine-name

The 127.0.0.1 line should be the same.
The other address is your internal ip and your machines name.
This name should be the same as 
/etc/mailname

Then try 

sudo dpkg-reconfigure -plow postfix 

again and this time tell it to be an
"internet site" 
( translated from spanish, pay attention, may vary ;-) )

Tell it :

+ Mail to root: your local username

+ Mail name: same as /etc/mailname 

+ Other destinations: should be:
	 machine-name, localhost.localdomain, localhost
	(machine-name as in /etc/mailname)

+ Force synchronous updates on mail queue?: yes

+ Local networks: 127.0.0.0/8
	
+ procmail: yes ( hehe postfix uses procmail! )

+ mailbox limit: default is ok.

+ the rest as default

Now postfix should be ok. I just did a purge and install
to check this and it worked fine. I also have this setup
in my machine and in one client who is a small 
handcrafts association.

A mail sent internally yields:
---------------------------------------
To: f <f at auda-pza>
Subject: test
From: f <f at auda-pza>

ss
---------------------------------------
( auda-pza being machine-name )

Next I would advise you to test one account at a time
in the fetchmailrc file.

Monitor this two files:
tail -f /var/log/mail.log  <-- postfix logs here.
tail -f /var/log/syslog

and then restart fetchmail.

In the MUA the server type is IMAP and
use your machine name as server name.
You can also try localhost or your ip.

Wow, aren't computers fun? (:ironic-grin:)

I hope that does it. 
You could be able to use only procmail, but I 
can not help there. In fact, if someone can
point to a good resource, I would be grateful.
( the reading never ends! )

Ok, have fun. Me gotta code a bit more.

f

-- 
Enter any 11-digit prime number to continue...

-- 
Enter any 11-digit prime number to continue...