Re: Why bother
> My question is... why bother writing
> this? fetchmail works just as well, and
> has more features.
Well.. I'm working on a Machine wehre fetchmail doesn't compile!!! So, I'm really happy that getmail exist!!!
Simple, easy to use
I must say this was a very easy program to install - it does exactly what I want it to do (ie suck email via POP and store it on my server) and that's it. Highly recommended!
> Fetchmail is bloatware, and not all
> people want to run a SMTP daemon.
You don't have to run a SMTP daemon with
fetchmail. You can configure it
to pass the mails to a specified program.
Ease of Use
I must admit that the ease of use of getmail over fetchmail keeps me using getmail. Initial setup takes a few minutes.
Thanks for sharing your code with the rest of us.
re: Bloatware, and why bother?
Disclaimer: I'm the author of 'getmail'.
A lot of people don't like 'fetchmail' -- that's why I wrote getmail. It's all of 30k of Python code, works well, doesn't do SMTP re-injection or any header re-writing (which a lot of people prefer, because of the way sendmail can obliterate useful information while re-writing headers), etc. In addition, I think getmail is easier to configure and use than fetchmail.
Bottom line: you're entitled to your opinion. If you prefer 'fetchmail', then by all means use it. I wrote getmail for my own reasons, and you're free to use it or not. If you'd like something added to getmail or changed, feel free to suggest it to me in email at firstname.lastname@example.org.
Fetchmail is bloatware, and not all people want to run a SMTP daemon.
My question is... why bother writing this? fetchmail works just as well, and has more features.
An open, cross-platform journaling program.
A scientific plotting package.