On 07/26/2014 06:20 PM, Damon Register wrote:
I have just installed SuSE 13.1 and I wanted to install qpopper since that is what I was using to make local sendmail available to Thunderbird (pop3). I found that qpopper was missing from the repository and with a little google work, I found one post that asked about qpopper for 13.1. One person suggested using dovecot so I thought I would give it a try.
Like all amazingly capable software, dovecot is amazingly configurable to achieve that capability. In fact its a "learning experience" in its won right. PLEASE: do not get confused when you visit the wiki between the stuff about V1 and the stuff about V2. And please do not try upgrading from V1 to V2. Their config are quite different.
Installing was easy and I thought running might be too. I started the service through yast, services manager.
Ah, not what I did not what what I would advise. I don't think dovecot is yast-friendly. It *is* very CLI friendly and very VIM friendly. Oh, and its not AppArmour friendly out of the box. You can see that in the logs. There's a tool you can run that parses the logs and updates apparmor. You'll need to run it and dovecot a couple or three times to get it all sorted out. My mail arrangement with the local mail repository, spamassassin processing, procmail processing, sanitisation and more ends up with quite a complex mail store and needs a heavily customized Dovecot config.
It seemed that dovecot didn't stay running so as suggested in dovecot manual, I looked at /var/log/mail. I saw that it failed on detection of the mail folder for my username. The manual had some info about that and suggested editing the dovecot.conf file. I did and now dovecot seems to be working and I can even connect from Thunderbird.
Good.
It appears however that I might not understand very well how to get my goal for dovecot. I see that dovecot works and Thunderbird connects but I see that dovecot has created its own set of mail files and folders in the mail dir that seem to be parallel to the sendmail files but not connected with the sendmail files.
Correct. Don't worry about them. Unless you go to great lengths to get dovecot to do otherwise it 'manages" the repository for you. Those 'great lengths" might, for example, involve having dovecot use a SQL or LDAP database to keep this auxiliary information in. (On re-reading this before sending I realise you may be talking about something different from what I am interpreting. Can you detail this please: what files? What do you mean by 'sendmail' files?) If this was all on a remote IMAP server you really wouldn't care, would you? Dovecot is doing its won indexing and 'bookmarking'. Some of this only comes alive when you tell Thunderbird to use the removte index, which is great when you are accessing the indexes on a off site server. Dovecot has the hooks for the plucine full text indexing. That is great, much better than having T'Bird down load each message and scan it when you are searching "Body". Dovecot indexes each message as it arrives so the overhead of the full text search doesn't hit you when you do it, as with T'Bird alone.
Can anyone tell me how to get dovecot to do what I used to do with qpopper? I want dovecot to repackage sendmail messages for use by Thunderbird (or any other pop3 client).
What do you mean by 'repackage'? You may gather from the above that Dovecot works best in IMPA mode. Perhaps what you need to do is tell us what your configuration is. Mine is, among others, to use fetchmail to read in the mail from various ISPs via POP# and pipe it though procmail, spamassassin and procmail again into various repositories that Dovecot knows about. My T'Bird then access my local repositories via IMAP talking to Dovecot. I am aware that some people make use of Postfix in that chain and other variations. What are YOU doing to get the mail to where your Dovecot is accessing it? -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org