From: Mark Alexander <marka@pobox.com>
To: Jonas H. <jonas@lophus.org>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Help me getting started.
Date: Mon, 20 Dec 2010 08:41:36 -0500 [thread overview]
Message-ID: <1292851798-sup-1112@bloovis.org> (raw)
In-Reply-To: <4D0E8DDD.20505@lophus.org>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
Excerpts from Jonas H.'s message of Sun Dec 19 17:57:33 -0500 2010:
> 4. For incoming mails, I used to use POP3, and I want keep storing my
> mail locally (only). Which MDA solution is the best as far as
> performance is concerned? My netbook has very poor CPU and HDD
> performance (loooong HDD wakeup times), so that's what matters most in
> this regard.
Fetchmail would be a good choice, and you can use it with procmail or
maildrop to deliver the mail to your local maildir(s). The
configuration language for maildrop is somewhat easier to learn than
procmail's.
I once tried using offlineimap, but had to stop because our Exchange
mail server at work would occasionally cause mails to be deleted and
that would mess up sup. (I think was a "feature" of Exchange or Outlook
that allowed people to recall messages after they'd been sent. I am
not sure, though; I don't use Windows.)
In case this would be useful, I've attached sanitized examples of my
fetchmail and maildrop config files. I've got them set up to use two
different incoming mail accounts, one for personal mail (gmail) and
one for work mail (a bogus company, widgets.com), with separate
maildirs for each.
[-- Attachment #2: .fetchmailrc --]
[-- Type: application/octet-stream, Size: 386 bytes --]
#File : .fetchmailrc
set postmaster "myusername"
poll pop.gmail.com with proto POP3 and options no dns
user 'gmailuser@gmail.com' there with password 'gmailpasswd' is 'myusername' here options ssl keep
mda "/usr/bin/maildrop"
poll imap.widgets.com protocol imap user widgetuser@widgets.com pass widgetpasswd fetchall
mda "/usr/bin/maildrop /home/myusername/.mailfilter.widgets"
[-- Attachment #3: .mailfilter --]
[-- Type: application/octet-stream, Size: 235 bytes --]
DEFAULT="$HOME/Maildir/inbox"
FRIEND="$HOME/Maildir/friend"
WOTD="$HOME/Maildir/wotd"
logfile "$HOME/Maildir/maildrop.log"
if (/^From:.*friend@example\.com/)
{
to $FRIEND
}
if (/^From:.*word@m-w\.com/)
{
to $WOTD
}
to $DEFAULT
[-- Attachment #4: .mailfilter.widgets --]
[-- Type: application/octet-stream, Size: 91 bytes --]
DEFAULT="$HOME/widgets/Maildir"
logfile "$HOME/widgets/Maildir/maildrop.log"
to $DEFAULT
[-- Attachment #5: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-12-20 13:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 22:57 Jonas H.
2010-12-19 23:34 ` Ben Walton
2010-12-20 7:57 ` Tero Tilus
2010-12-20 13:39 ` Jonas H.
2010-12-20 18:24 ` Marc Hartstein
[not found] ` <4D0F5C5E.7030809@lophus.org>
2010-12-20 13:57 ` Tero Tilus
2010-12-23 10:17 ` Jonas H.
2010-12-30 13:14 ` Jonas H.
2010-12-30 15:31 ` Tero Tilus
2010-12-30 21:33 ` Tero Tilus
2010-12-30 23:09 ` Tero Tilus
2010-12-30 23:03 ` Tero Tilus
2010-12-30 23:37 ` Jonas H.
2010-12-31 0:45 ` Tero Tilus
2010-12-31 10:14 ` Jonas H.
2011-03-22 18:01 ` Jonas H.
2010-12-20 13:41 ` Mark Alexander [this message]
2010-12-20 14:10 ` Shadowfirebird
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1292851798-sup-1112@bloovis.org \
--to=marka@pobox.com \
--cc=jonas@lophus.org \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox