Configuration of fetchmail, fetchyahoo, gotmail, procmail, or whatever is needed to get email from common accounts into an IMAP server. Reproducible: Always Steps to Reproduce:
These topics are covered in http://www.gentoo.org/doc/en/guide-to-mutt.xml. Further the desktop guide already descibes postfix and mutt usage in brief. There's a veritable ton of information on the other tools in the forums as well if the user so desires.
the bug report was only faguely about postfix and almost unrelated to mutt. Downloading remote POP and Yahoo mailboxes into local mail accounts is what lacks documentation.
Is http://dev.gentoo.org/~spider/local-mail-0.2.1/local-email.html a sufficient guide for this?
It's good, but it lacks info on how to setup fetchyahoo and gotmail...
D.M.D: do you think you can add information about fetchyahoo and gotmail? And if you do, can I then steal your xml and put it online as official documentation? :)
I haven't ever used either of theese tools, and my accounts with both have expired because I did not accept their updated privacy policy ant terms of use. Could somone who has used them fill me in with the relevant details (configurations and testing how it works) and I'll fix that? I also have to fix smtp outbound relaying, but its a simple change.
It may be worth adding the SquirrelMail docs (from the Desktop Guide) in here also...
http://dev.gentoo.org/~spider/local-mail-0.3.0/local-email.html Just updated it with outgoing SMTP changes and a securityfix for procmail configurations :-/
It seems the people on the desktop project will help in creating such documentation; see http://www.gentoo.org/proj/en/desktop/research/meeting_reports.xml
Bouncing back to the documentation team
Okay, apparently we don't have a good e-mail specific guide yet that covers "everything". What we need is a guide that bundles the following aspects (most of which we already have in other guides): 0. Inform that the document is about getting the mails yourself, not just configuring your graphical MUA to receive the e-mails from the external e-mail server (that's too easy to document I suppose). 1. Setting up an MTA (PostFix?) 2. Downloading your e-mails - fetchmail - getmail - gotmail (for HotMail) - fetchyahoo or yosucker (for Yahoo!) 3. Processing your e-mails - procmail (check mail-filter) 4. Sending and Receiving e-mails - Quickly list some common pitfalls for MUAs or link to individual MUA-centric guides No? Yes?
Some dev has such a guide in their dev.g.o area, but it lacks stuff to fetch from Yahoo/Hotmail... I think that's all I was referring to, but it's been so long...
that'd be me. As I personally don't have either HoTMaiL or Yahoo email, I cannot do that authoring myself, hwoever, otherwise it should be fairly simple. (note that my guide was aimed at using procmail for all sorting /Delivering to aid filtering..)
And there's hotwayd as well, to get emails from hotmail as well as various lycos accounts.... I don't know how relevant lycos will be since it's been sold off though. Could help with the hotwayd/yosucker parts.
I have this half done guide laying around: http://home.coming.dk/homemail.html
Hey All, Between my wife and I we have a couple Hotmail and Yahoo! acounts. I actually harass her allot about the Hotmail one. Anyways, I wouldn't mind playing with some of the packages to download those and use them with Mozilla at home and then write some docs for them. I'm not an expert with procmail or some of the others, but I'm not a Linux newbie either so I'm sure I can figure it out. Let me know what I need to do and I'll start looking at the packages and getting some notes together to write some stuff up.
You might want to start off with Spider and/or Sune's documents and extend it with the stuff that's still missing. I would even appreciate simple and small excerpts of documentation for specific items (such as hotmail fetching).
I can help with the fetchyahoo. I've been using it for a couple of weeks now, downloading into a maildir (in case I want to fire up courier-imap and IMAP it back down somewhere else). I didn't bother setting up courier on my local box, but I could emerge it tonight and make sure that IMAP works and that the mail formats are the same. That way I could IMAP in and out of the same storage for testing, as well as show how to store the mail so you don't have to mess with IMAP at all to just store the Yahoo mail locally. I'm reading it with Ximian, which supports Maildir format, so Ximian just "sees" the mail once fetchyahoo picks it up, IMAP not required. I download each Yahoo folder seperately by using different config files.
curtis119 and cokehabit are attempting to finish this guide. We will use all the docs that have been posted here as well as any new information that we discover. We intend on actully installing and testing this from scratch to ensure our work is accurate. We are going to focus on postfix as the server. yahoo, hotmail and gmail will be the 3 big free email providers that we will focus on for now. Once the basic guide is finished we will add any others that are requested. A FAQ on the mbox USE flag will be included as part of the initial doc. We will base this doc on the excellent work already done by spider here: http://dev.gentoo.org/~spider/local-mail-0.3.0/local-email.html Any comments or suggestions?
the latest version is 0.3.2 overhere ... http://dev.gentoo.org/~spider/local-email.html
Just a note: maildir is generally superior to mbox Is there a way to notify the clients of new mail via IMAP (w/o their checking request every 10 min or so)? If so, info on how to do that would do well in the guide.
I'm going to timeout this bug; it's still listed on our roadmap (request for new document). Marking as LATER.
Why do we want a doc that covers every kind of email setup possible? 99% of users will probably want to use something like Kmail. Something like "how to set up your own Gentoo webmail server" would encompass a lot of the stuff mentioned so far, and it would tie it all together nicely. Most users might think it's really cool to have webmail at home! Any ideas? If you guys think that's a good idea, I will gather ideas and write the doc.
Using a graphical mail client without additional software isn't hard - there is no need to document that (everybody should know how to configure KMail to retrieve mails from a POP/IMAP server and send mails through your ISP's relay server). However, what some people do want is to retrieve the emails, filter them (anti-spam, anti-virus, hierarchical storage, ...) before they read them. That means Comment #11. A Gentoo webmail server is not the purpose of this proposed doc, although you can very well write such one (but use a different bug :) However, a part of what you are proposing is already documented in the Virtual Mailhosting Guide <http://www.gentoo.org/doc/en/virt-mail-howto.xml>. This covers the setup of PostFix and Squirrelmail, and a few other applications. The document has a specific purpose.
i'm on it. gimme a few days
draft from comment #15 is back if any inspiration is needed.
thank you! do you have the xml for that lying around anywhere?
xml source from comment #15: http://home.coming.dk/homemail.xml Good luck with the guide!
thank you! i have the intro, qmail, and fetchmail sections finished. i coppied a good deal of your section on mbox vs maildir. i hope thats ok. consequently, you are listed as a contributer in the author section... its chugging along, though
Of course it is ok! I just want to see better docs:-)
just as a random note: i will be keeping this document on which i am working on my personal webspace if anyone wants to follow/comment/help take a look: http://neverland.ncssm.edu/~smithj/home-email-guide.html xml source (will _not_ display properly in a browser): http://neverland.ncssm.edu/~smithj/home-email-guide.xml
Created attachment 60565 [details] yosucker.xml (In reply to comment #11) > Okay, apparently we don't have a good e-mail specific guide yet that covers "everything". > > What we need is a guide that bundles the following aspects (most of which we already have in other guides): > . . . > 2. Downloading your e-mails . . . > - fetchyahoo or yosucker (for Yahoo!) Attached is yosucker.xml This is a guide to YoSucker, a Yahoo Mail fetching application. I researched this and fetchyahoo. fetchyahoo has not had any activity on it's project page since November 2004. YoSucker has had continuous commits and updates from the developer. Feel free to cut this document up and insert it into this larger guide or any other way it may be useful to this mini-project. Good Luck smithj!
Created attachment 60566 [details] yosucker-r1.xml Oops. I forgot to add the keyword instructions.
(In reply to comment #32) > [snip] > Feel free to cut this document up and insert it into this larger guide or any > other way it may be useful to this mini-project. > > Good Luck smithj! i am indeed integrating it into my doc. sorry for the delay, but other things (gentoo related and rl) have come up. in any case, curtis119, i have a few comments which might aid you in your doc-writing career: listing dependencies in a document is, in almost every case (and certainly in this one) useless when doing <pre caption="blah"> tags, be sure to make blah verbose. don't simply say "emerge" don't reinvent the wheel. most of the config file in your doc is already installed in /usr/share/doc/yosucker-71/config/sample1.conf. adding all of this to the doc simply takes up space and makes the doc harder to maintain please note: the above is not meant to criticize; simply for you to learn thanks for the help also, when writing code inside <pre>, surround it with <i>, as so (when issuing a command for a non-root user, replace the # with $): <pre caption="Installing YoSucker"> # <i>emerge yosucker</i> </pre> "<path>~/</path>" is a little silly. just say "home directory". if people don't know what that is, they shouldn't be reading this document touching something and then editing it right afterwords is a little redundant and silly if you are making comments about a command being typed, make those comments on the line _above_, not the line after commands like "nano -w blah" are useless. just tell the editor what file to edit and let him/her decide editor on their own
swift, can we get this reopened? i don't have the proper bugzilla rights
Reopening on smithj's request...
I don't think we want to document all the perl scripts used to download mail that are out there. Their authors should provide docs on how to use their programs, not us. Besides, fetchmail and procmail are already documented in the guide-to-mutt.xml, so this guide has really no reason to be written.
