On 07/27/2014 08:17 AM, Joachim Schrod wrote:
On 07/27/14 13:42, Anton Aylward wrote:
On 07/26/2014 09:35 PM, Damon Register wrote:
In the past, I used qpopper to allow pop3 retrieval of those system mail spool messages? Why? My favorite mail software has been Thunderbird since it was Netscape. I liked the convenience of being able to see my ISP e-mail such as this as well as the local system mail spool messages from the same client. qpopper was my interface between the system mail and Thunderbird.
That seems non sequitor. "Retrieve" from mail spool? - that makes no sense.
It's quite clear what he's doing.
By implication not by explicit statement ..
He knows how to configure Thunderbird to create a mail account, backed by a POP3 server. He does so for his ISP email.
I infer that. I'd like him to say that and say if that is all that Thunderbird is doing. I'd like him to confirm that he is using T'Bird to download from the ISP using POP to store the mail in whatever mailbox and folders T'Bird is set up for. I'd also like to know ho he's set up T'Bird for sending mail.
In previous releases, he accessed his system mail (in /var/spool/mail) by running qpopperd.
That makes no sense to me. On the one hand is the system is set up to deliver mail to /var/spool/mail rather than to ~/Mail then that is one case. If he's running Postfix to handle system mail then that could be configured, as I have done in many instances, to send system mail to a particular user at ~/Mail. This makes more sense in single user system where the single user doubles as the sysadmin & postmaster. See, for example, the Postfix 'aliases' file.
So he could reuse that knowledge and only needed to add another account backed by a POP3 server (his own local server). With the demise of qpopperd his approach has gotten more difficult to realize.
I don't get it. It was irrelevant in the first place. So he was using qpopper to make mail that was available on the system available to be downloaded to another part of the system, delivered by qpopper and downloaded by T'Bird accessing qpopper via POP3. It makes no sense to me. Why not just T'Bird at it in the first place? That's what I did here years ago, before I moved all my email off to a mail server hub and ran T'Bird on my workstation, accessing the mail hub via IMAP.
You shouldn't need anything to do that.
You might be right in this specific case.
its worked in the past here and on many other machines/sites I've installed it. If you are making use of mail hub on your LAN then yes, run an IMAP server on the mail hub for the workstations on the LAN. But if you have a single machine and have downloaded all the mail (or equivalent) the its all accessible as files on your machine. You don't need a server to dish it up, you can just point T'Bird at the files.
I don't know Thunderbird, but probably one can create a mail account backed by "Unix Mailspool" or however Thunderbird calls this.
You can create any number of accounts. You can point their working directories wherever you want. You can point what they use for the inbox, the 'sent', the 'junk', the 'draft' wherever, not just at files but at other counts. So you could set up a dozen different file, IMAP and POP account that all 'point' to the same 'inbox'. T'Bird is very capable, and that's before you start using the plugins.
Nevertheless, there are many other reasons why one might want to have a simple and pure download oriented interface to a mail spool.
Such as using 'fetchmail'.
E.g., I use it for automated mail processing on a different server than the mail server. qpopperd+fetchmail delivered a light-weight ability to realize that service. It's a pity that I must implement the big jack-hammer Dovecot in my infrastructure for that small nail.
My experience has always been that when the solution looks gargantuan then there's another KISS way to do it. Not knowing what you app is trying to _achieve_ I can't suggest an alternative. -- /"\ \ / 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