Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

barbie (2653)

barbie
  reversethis-{ku. ... m} {ta} {eibrab}
http://barbie.missbarbell.co.uk/

Leader of Birmingham.pm [pm.org] and a CPAN author [cpan.org]. Co-organised YAPC::Europe in 2006 and the 2009 QA Hackathon, responsible for the YAPC Conference Surveys [yapc-surveys.org] and the QA Hackathon [qa-hackathon.org] websites. Also the current caretaker for the CPAN Testers websites and data stores.

If you really want to find out more, buy me a Guinness ;)

Links:
Memoirs of a Roadie [missbarbell.co.uk]
[pm.org]
CPAN Testers Reports [cpantesters.org]
YAPC Conference Surveys [yapc-surveys.org]
QA Hackathon [qa-hackathon.org]

Journal of barbie (2653)

Monday November 14, 2005
12:07 PM

It's In The Post

[ #27571 ]

My mail trials seem to be dragging on. After figuring out the various configs from FAQs, HowTos, man pages and various websites, I've got further with my mail. Not all the way, but further.

fetchmail

I now have fetchmail working. This was the easy part, but then the config is 4 lines long, so I'd be hard pushed to screw that up ;)

procmail

I have created a set of recipes and apart from an initial hiccup, with a bad regex on my part, it appears to be able to pick up mail and put the filtered ones into the correct files. It's saving in mbox format, and checking the files by hand, they all seem to be correct. However, I still seem to have a problem. A couple of the recipes were incomplete, and as such a number of mails got left in my system mailbox. Having changed the recipes, the mails don't seem to get reparsed and moved on. How do I tell procmail to reparse the whole mailbox?

mutt

Well mutt is better than mail, but I have hit a problem. Getting procmail to filter all the mails into various mbox files is great, but only if you can navigate through them easily. mutt doesn't even see them initially, it just loads up all the mails in my system mailbox. I set the .muttrc file to include 'set folder=~/Mail' but that didn't seem to work. I then discovered the command ESC-c and '?' for the directory list. Although I can now choose a file, to go back to the system mailbox or another file, I have to quit mutt and start again. It keeps asking me to move messages to a local mailbox as well, which is getting to be annoying. I filter the damn things to be in separate files, why would I want them back in one great big file again? I guess I must have missed something, because so many people think its so great.

Thunderbrd

After the half-working mutt, I did expect Thunderbird to be a breeze. It has a shiny GUI after all. Alas it was non-starter. I can't get it to look at any folders that I want it to, even though it claims to support mbox format. I can't even get it to import files and redo my recipes in procmail. I think I actually need to sit down with someone so they can point out quite clearly the fundamental flaws in my research and reading.

It really can't be this awkward to set up a mail client, can it?


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

It's In The Post 7 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • The command "c" is used in mutt to change folders. If you start the folder name with "=" mutt will look in the ~/Mail directory (or whatever you have the home mail folder set to). If you use a folname of "!" you can switch back to mailbox (/var/mail/$USER or the equivalent on your system). In a .muttrc file, you can select what is done for many circumstances; usually the choices are yes/no/ask-yes/ask-no to choose whether the action is taken, not taken, or interactive with a default.
    • Excellent, thanks for the info. I'll try out those commands when i get back home tonight. I did notice something about the yes/no/ask-yes/ask-no stuff in one of the websites I found, but it didn't include examples, so I wasn't clear what I was supposed to do with them. Will dig a little deeper now :)

  • Having changed the recipes, the mails don’t seem to get reparsed and moved on. How do I tell procmail to reparse the whole mailbox?

    procmail doesn’t parse your mailbox, it only directs mail that is fed to it to the right place according to its rules. So you have to feed the mails from your inbox to it. This is achieved using formail -s procmail < /your/mailspool. With -s, formail will parse its input and invoke the given program for each mail, feeding the mail to the program’s stdin.

    • Oh! And don’t forget to save the mails from your inbox/spoolfile to another place before you re-filter them, else they’ll show up in your inbox in duplicate. I usually do this simply by mving my spool out of the way before piping it into formail (it gets recreated automatically by procmail).

    • formail, great. I knew there must be something already to refeed without me having to write a script to do it :)

      Thanks for the .muttrc hints too. I'll add those in a bit and see how I get on. Thanks.

  • You're probably seeking some combination of:

    set quit=yes
    set copy
    set delete=yes
    set fast_reply
    set askcc=no
    unset metoo
    set abort_unmodified=no
    set recall=no
    set reply_to=yes
    set record=+sent
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.