Re: [Dovecot] Problem with dovecot on home LAN
On Tuesday 07 December 2004 15:28, David Sheryn wrote:
With fetchmail I get the error message:
[tim@william ~]$ fetchmail alfred fetchmail: Server CommonName mismatch: localhost.localdomain != alfred fetchmail: Server CommonName mismatch: localhost.localdomain != alfred
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This would appear to be you problem. You have an identity crisis somewhere. Either your laptop or you dektop (or both) are confused as to their (LAN, i.e. IP) network identity (note that this has nothing to do with UUCP -- unless, of course, you are attempting to run UUCP over IP which would be ill-advised.)
It's not at all obvious where the misconfig lies, but I'd start with host files / interface configs.
I'm sure you are right that this is where the problem lies. Unfortunately I don't know what the solution is. There is no "identity crisis" normally, as I ssh from one machine to the other with no problem, and eg keep a yum repository on the desktop which I use to update Fedora-3 on the small number of machines on my two little LANs (Ethernet and WiFi).
I googled for this error "Server CommonName mismatch" and found dozens fo hits, but none of them seemed to suggest a concrete solution.
What slightly puzzles me is that dozens of people must be using dovecot for more or less the purpose I envisage - otherwise what are they using it for - so my little problem must have arisen many times before.
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
--On 07 December 2004 20:58 +0000 Timothy Murphy tim@birdsnest.maths.tcd.ie wrote: | | What slightly puzzles me is that dozens of people must be using dovecot | for more or less the purpose I envisage - | otherwise what are they using it for - | so my little problem must have arisen many times before.
I use Dovecot on a small home LAN with no problems. However, the server runs the SME-Server distro (www.contribs.org), which comes with Dovecot pre-configured, so I've never had to set it up from scratch.
Also, I've never tried using fetchmail on a client (although the server uses it in the way you use uucp), I use conventional IMAP clients - generally Mulberry and sometimes OE. This all runs like clockwork.
Your fetchmail errors look to me like a fetchmail config issue (e.g. why would fetchmail want an SMTP connection to localhost?), though not being a fetchmail expert I'm not sure what it's indicating.
Have you tried any other IMAP clients? Again, I don't know KMail, but getting an IMAP client to make its first connection to a server is sometimes a black art, as it has to discover what mailboxes the server offers, etc. You could try Mulberry, you can download a free trial from www.mulberrymail.com - there are builds for RH5 & RH6, and people report success on Fedora.
-- HTH Rick Jones
On Tue, 07 Dec 2004 22:30:14 +0000 Rick Jones rick@activeservice.co.uk wrote:
--On 07 December 2004 20:58 +0000 Timothy Murphy tim@birdsnest.maths.tcd.ie wrote: | | What slightly puzzles me is that dozens of people must be using | dovecot for more or less the purpose I envisage - | otherwise what are they using it for - | so my little problem must have arisen many times before. Your fetchmail errors look to me like a fetchmail config issue (e.g. why would fetchmail want an SMTP connection to localhost?), though not being a fetchmail expert I'm not sure what it's indicating.
It looked to me as though there is no smtp daemon running on localhost. As this is the way that fetchmail normally delivers, it's gonna die (you can change how it delivers locally, but fetchmail's default is grab mail from server, hand it to localhost smtp for local delivery). Consequently, I don't think it's the tool I would use to test IMAP, but p'raps it's just me.
Have you tried any other IMAP clients? Again, I don't know KMail, but getting an IMAP client to make its first connection to a server is sometimes a black art, as it has to discover what mailboxes the server
offers, etc. You could try Mulberry, you can download a free trial from www.mulberrymail.com - there are builds for RH5 & RH6, and people report success on Fedora.
Err. telnet? As long as you can turn on plaintext auth, it's not particularly painful, and it's good for figuring out whether things are actually working or not.
Alternately, turn on tcpdump/ethereal/some other packet analyzer to capture port 143 traffic (in and out) on the server, and see what's actually happening at the protocol level. If KMail can't log in, oops. Figure out why; reconfigure/fix. If it logs in and then can't find a mailbox, you should see that as well. Some of this information *may* show up in logs, but watching the interaction is usually more comprehensible (you see what the client expects, and what the server actually presents).
Amy!
Amelia A. Lewis amyzing {at} talsever.com Life is a glorious cycle of song / a medley of extemporanea; and love is a thing that can never go wrong; and I am Marie of Roumania. -- Dorothy Parker
participants (3)
-
Amelia A Lewis
-
Rick Jones
-
Timothy Murphy