<<< Date Index >>>     <<< Thread Index >>>

Re: Multiple emailaddresses and mailing-lists



On Fri, Apr 23, 2004 at 03:17:59PM EDT, Mutter wrote:
> On Thu, 22 Apr 2004, David Yitzchak Cohen wrote:
> > On Thu, Apr 22, 2004 at 06:47:31AM EDT, Mutter wrote:

> > > What is the easy way to use *many* email addresses with mutt? How to
> > > switch addresses?
> [Snip]
> 
> > The easiest way I know of to autochoose your email address based on the
> > list you're sending to is to use my makenewlistsrc [1] script to turn a
> > newlists [2] file into a newlistsrc [3] file.  You use the my_addy field
> > to override the default addy (the contents of the my_default_list_addy
> > [4] file with a resource (+blahblahblah) matching the list's listnick)
> > for a list, or you can modify the script slightly to generate addresses
> > in a different way.
> 
> Hmm, I downloaded everything from your muttdir, from your site.

Well, okay, you didn't have to, but it doesn't hurt ;-)

> Reading
> the WHY_USE I like what it has but I do not understand how to use these
> scripts?

Well, in order to use the mailing list configuration, you don't need
much other than the files I explained about above.  You may want to also
get the addlistfrommail script (which requires 822fields, 822addy2name,
and 822addy2addy (all in my bin directory [5])) to make it easy to add
mailing lists on-the-fly from emails you get, though.  (Simply pipe an
email to the script (using a macro, presumably), and it'll extract the
address from the email and add it to your list config.)

[5]
http://www.bigfatdave.com/dave/bin/

If you want to use the other stuff, it's probably wise to read the README.

> Are all these scripts to be used separately or is there some
> install script ...

Nope, there's no install script.  The idea is to allow people to pick out
the stuff they want to use quickly and easily.  Any type of installation
system would just get confused if you only got some of the stuff,
modified stuff, etc.

> are these patches?

I don't patch my Mutt (except to correct some PO stuff - full diff against
CVS available).  If you want to see the actual Mutt build directory I use
(full CVS sources, object files, and i686 executables), it's online [6]
(as is a tarball of it [7] for anybody who'd otherwise want to waste lots
of time downloading the whole thing recursively), as is the diff against
official CVS [8] (which is bigger than it ought to be, since I converted
es.po to UTF in order to be able to edit it, which kinda threw diff(1)
for a bit of a loop).

[6]
http://www.bigfatdave.com/dave/download/from_cvs/mutt/

[7]
http://www.bigfatdave.com/dave/download/from_cvs/mutt.tgz

[8]
http://www.bigfatdave.com/dave/download/from_cvs/diff.mutt

> There's no readme

Well, no, there's no readme.  There's a README, though ;-P

> so I do not
> understand how to use them, can you please explain?

If you've got questions after reading the README, feel free to ask away.
If you can contribute comments afterwords for me to collect in the
official documentation, I'll be even happier :-)

>  May be my question
> would sound silly but hope you don't mind.

I've heard many far sillier questions (as has everybody else in the
list), so don't worry.  Besides, I'm a big fan of the Radio Shack motto:
"You've got questions; we've got answers!"

> And what are all the other files/scripts other than these 4, for?

Well, different files are for different things ;-)

> Is there
> some readme file for them?

Well, the same README works reasonably well for most of the stuff.
Looking at it again, though, I see there's a fair amount to improve on
(like how to use the filter), so if you can put together a list of stuff
that makes no sense to you, I'll have a big enough list to get me up
off my bigfatdaveass to fix the README ;-)

> Thanks for the help!

Any time :-)

Happy Muttin',
 - Dave

BTW - You stole the name for a package I was trying to put together a
couple of years ago for using Jabbin' (the famous uncrashable Jabber
client that never managed to stay up for more than a few minutes at a
time without crashing, and that's probably not going to end up being
rewritten using FUSE (Filesystem in USErspace), since I'm finding
(during my trial - turning the address book into a filesystem, which
will obsolete the makealiasesrc script) the FUSE API to be seriously
lacking in flexibility) as a Mutt folder.  ("Why, you. . .")

Also BTW - I just spotted an interesting problem (read: security hole)
in the Makefile.  You'll almost certainly want to get the new version.
(The new NEWS file gives details of the vulnerability and the fix.)

-- 
Uncle Cosmo, why do they call this a word processor?
It's simple, Skyler.  You've seen what food processors do to food, right?

Please visit this link:
http://rotter.net/israel

Attachment: pgpxfpTUHCeeS.pgp
Description: PGP signature