Re: mbox opened read only after update to mutt 1.4i

2002-09-26 Thread jochen issing

On Wed, Sep 25, 2002 at 06:47:01PM +0200, Sven Guckes wrote:
> * jochen issing <[EMAIL PROTECTED]> [2002-09-25 16:25]:
> > > after my recent update to 1.4i, I am not able able to remove any mails
> > > out of my spool files. I can open /var/mail/jochen with vim and can
> > > write it, but mutt refuses writing.
> > Ah, I have solved the Problem!!
> > It was the directory access to /var/mail, which was rwxrwxr-x
> > and I have been "other". Hence, I actually was not able to write
> > into the directory. I find it quite interesting that mutt 1.4i
> > has a problem with it and vim and my old mutt (1.3.28?) not.
> 
> check the permissions on the binary of mutt 1.3.28 then.
> is it owned by root:other?

no, its owned by root,root. There are no suid bits set as
for vim and I changed permission of the directory and everything
works fine.

> as for vim - if it allows writing to the mail spool
> then you can have lots of fun with it...

If you think about using vim as a mail client, I don't
think about fun ;-)

jochen
-- 

 jochen issing
 mailto:[EMAIL PROTECTED]
 http://www.mcf-music.de
 GPG:0A121BC




Re: mbox opened read only after update to mutt 1.4i

2002-09-26 Thread Nicolas Rachinsky

* jochen issing <[EMAIL PROTECTED]> [2002-09-26 09:44 +0200]:
> On Wed, Sep 25, 2002 at 06:47:01PM +0200, Sven Guckes wrote:
> > * jochen issing <[EMAIL PROTECTED]> [2002-09-25 16:25]:
> > > > after my recent update to 1.4i, I am not able able to remove any mails
> > > > out of my spool files. I can open /var/mail/jochen with vim and can
> > > > write it, but mutt refuses writing.

Because vim does not create a lockfile.

> > > Ah, I have solved the Problem!!
> > > It was the directory access to /var/mail, which was rwxrwxr-x
> > > and I have been "other". Hence, I actually was not able to write
> > > into the directory. I find it quite interesting that mutt 1.4i
> > > has a problem with it and vim and my old mutt (1.3.28?) not.

Either the old mutt or the old mutt_dotlock binary were setgid mail.

> no, its owned by root,root. There are no suid bits set as
> for vim and I changed permission of the directory and everything
> works fine.

If there are other users on your machine, your created a security hole
by this.

Nicolas



Re: mbox opened read only after update to mutt 1.4i

2002-09-26 Thread jochen issing

On Thu, Sep 26, 2002 at 10:54:48AM +0200, Nicolas Rachinsky wrote:
> * jochen issing <[EMAIL PROTECTED]> [2002-09-26 09:44 +0200]:
> > On Wed, Sep 25, 2002 at 06:47:01PM +0200, Sven Guckes wrote:
> > > * jochen issing <[EMAIL PROTECTED]> [2002-09-25 16:25]:
> > > > > after my recent update to 1.4i, I am not able able to remove any mails
> > > > > out of my spool files. I can open /var/mail/jochen with vim and can
> > > > > write it, but mutt refuses writing.
> 
> Because vim does not create a lockfile.
> 
> > > > Ah, I have solved the Problem!!
> > > > It was the directory access to /var/mail, which was rwxrwxr-x
> > > > and I have been "other". Hence, I actually was not able to write
> > > > into the directory. I find it quite interesting that mutt 1.4i
> > > > has a problem with it and vim and my old mutt (1.3.28?) not.
> 
> Either the old mutt or the old mutt_dotlock binary were setgid mail.
> 
> > no, its owned by root,root. There are no suid bits set as
> > for vim and I changed permission of the directory and everything
> > works fine.
> 
> If there are other users on your machine, your created a security hole
> by this.
> 
> Nicolas
So you suggest me to setgid for mutt and/or mutt_dotlock and reset the
/var/mail directory again?

jochen
-- 

 jochen issing
 mailto:[EMAIL PROTECTED]
 http://www.mcf-music.de
 GPG:0A121BC




Re: looking for a better send-hook

2002-09-26 Thread Aaron Schrab

At 16:55 -0500 25 Sep 2002, Eugene Lee <[EMAIL PROTECTED]> wrote:
> : * Eugene Lee <[EMAIL PROTECTED]> [2002-09-25 12:33]:
> : > 
> : > The command "send-hook '~h address' command"
> : > causes Mutt to generate an error "h: not supported
> : > in this mode" that isn't documented anywhere.

> I'm looking at the header "Received:" and trying to find a match within

send-hooks match against the message which was just started, and thus
they don't have Received: headers.

My parent match patch allows parts of send-hooks to match against the
message to which you are replying, but at this time ~h isn't supported
for send-hooks even when matching against the parent message.  Changing
this would require changes to mutt's internals that I haven't yet had
time to do.  It would also likely require that the patch be updated more
frequently as other parts of mutt change.

  http://www.schrab.com/aaron/mutt/patch-1.3.24.ats.parent_match.1

> I know message-hook supports ~h, but it only activates when I view the
> current message.  And I don't want to remember to view a message to
> activate the hook.  This wouldn't be a such problem with your standard

message-hooks are also applied when you begin a reply, before send-hooks
are applied.

-- 
Aaron Schrab [EMAIL PROTECTED]  http://www.schrab.com/aaron/
 I dunno, I dream in Perl sometimes... --Larry Wall



Re: mbox opened read only after update to mutt 1.4i

2002-09-26 Thread Will Yardley

jochen issing wrote:

> So you suggest me to setgid for mutt and/or mutt_dotlock and reset the
> /var/mail directory again?

chmod 1777 /var/mail should work too. whether you do this or make
mutt_dotlock setgid mail is pretty much up to you.

-- 
Will Yardley
input: william < @ hq . newdream . net . >




Re: $check-new

2002-09-26 Thread Johan Svedberg

On Thu, Sep 26, 2002 at 03:40:07AM +0200, Sven Guckes wrote:
> don't forget about comp.mail.mutt!
> http://www.google.com/search?q=mutt+%22new+mail%22&scoring=d

Ah, TSM must be the problem, thanks.

Johan



mail box name in macro

2002-09-26 Thread Bernard Massot

hi

is there a way to get the current mail box name in a macro ?
for example I'd like to do «macro index m current_box_name»
-- 
Bernard Massot



msg31265/pgp0.pgp
Description: PGP signature


Re: vim+perl=vine

2002-09-26 Thread Sven Guckes

* jochen issing <[EMAIL PROTECTED]> [2002-09-26 07:44]:
> If you think about using vim as a
> mail client, I don't think about fun ;-)

http://www.mossbayeng.com/~ron/vim/vine.html
use vim and perl as a mail client - try it!

Sven



Re: $check-new -> TSM problem?

2002-09-26 Thread Sven Guckes

* Johan Svedberg <[EMAIL PROTECTED]> [2002-09-26 09:58]:
> Sven Guckes wrote:
> > don't forget about comp.mail.mutt!
> > http://www.google.com/search?q=mutt+%22new+mail%22&scoring=d
>
> Ah, TSM must be the problem, thanks.

TSM?

http://www.acronymfinder.com/af-query.asp?String=exact&Acronym=tsm

  TSM IEEE Transactions on Semiconductor Manufacturing
  TSM TAC System Manager
  TSM Tactical Survey Meter
  TSM Tagged-Signal Model
  TSM Tax Systems Modernization
  TSM TCS Security Manager
  TSM Technical Service Manual
  TSM Technical Services Manager
  TSM Terminal Security Matrix
  TSM Terminal Support Module
  TSM Thickness Shear Mode
  TSM Threat Spectrum Model
  TSM Time Shared Monitor
  TSM Timer Standby Monitor
  TSM Tivoli Storage Manager
  TSM Total Suspended Matter
  TSM TRADOC Systems Management
  TSM TRADOC Systems Manager
  TSM Traffic Scheduling Manager
  TSM Training Site Manager
  TSM Training Support Materials
  TSM Transformation Scattering Matrix
  TSM Transportation System Management
  TSM Troop Sergeant-Major (Canadian and British Military)
  TSM True Sharing Miss

i see...  not.

Sven



mutt and exchange

2002-09-26 Thread Gregory Seidman

Happily, I have mutt playing nice with the Exchange server at work over
IMAP. This pleases me. Now I am looking for further interaction with the
Exchange server. In particular, it is my understanding that there is some
way to use the global (and personal?) address book(s) on the server. Maybe
it's LDAP? Perhaps it has something to do with the query functions? Do I
need an external program to help? Is there a HOWTO somewhere (Google did
not find anything useful for "mutt exchange howto")?

--Greg




Re: fast conversion of html mail to text

2002-09-26 Thread Sven Guckes

* Mike Leone <[EMAIL PROTECTED]> [2002-09-26 03:35]:
> > > Actually, I've gotten many non-HTML spams, too.
> > > And I get many valid HTML mail, both
> > > newsletters and private correspondence.
> > has the thought ever struck you that it might be *you*?
>
> Since I know many different people that both send and receive
> HTML mail, none of whome are spammers; and since I get a
> number of HTML-only newletters that are defintely not spam ...
> no, that thought has never struck me.  :-)

well, if you subscribe to a HTML-only newsletter
then you were asking for it - so it's your problem.

> Has the thought ever struck you that perhaps
> you are too restrictive in what you accept?

i have yet to see sn email which was enhanced by html.
and i suppose i do have a problem with DOCuments from
companies which forbid free software to use it, too.

> > > Random Thought:
> > duh.
> Hey, not my fault - my SquirrelMail web interface
> sometimes forgets to read the output of the fortune program.

it's your problem then.  you are responsible for what you send!
please refrain from sending arbitrary noise to lists - thankyou.

Sven  [usually attaching sigs which fit the content of the message]



Tagging mail by date

2002-09-26 Thread Chris Green

I've looked at the documentation and I know it's possible but does
anyone have any examples of tagging mail by date?

I.e. how do I tag all messages more than (say) 365 days old in the
current mailbox?

Or even better does anyone have any sample scripts using mutt as the
'source' for archiving mail?  I've been looking at archmbox but it
doesn't quite fit my requirements and I suspect that using mutt to
actually extract the messages I want to archive may be easier than
bodging archmbox.  I particularly want to preserve the directory
hierarchy, i.e. what I want to do ultimately is extract all messages
older than xxx days from my current mail and append them to mailboxes
in an identical archive hierarchy (which will be on a different
machine with no serious disk quota limits).

-- 
Chris Green ([EMAIL PROTECTED])



Re: Problem with folder-hook - command must be *one* parameter

2002-09-26 Thread Sven Guckes

* D. J. Bolderman <[EMAIL PROTECTED]> [2002-09-26 03:44]:
> >   send-hook   .   "my_hdr From: me "
> >   folder-hook +empty  "my_hdr From: me "
> >   folder-hook +empty  "my_hdr Subject: test"
> 
> > now, when changing to +empty, the folder-hooks do get
> > triggered (i can tell be the X-Test: showing up) - but
> > there is still "From: me ", so the send-hook
> > overrules the From: header as set by the folder-hook.
> 
> You are right, I also tested it with the subject,
> and then the folder-hook works. Now, is there
> any way to work around this problem?

how about using hooks on different folder sets
and using unmy_hdr to throw away already set ones?

  folder-hook  ! +empty  "unmy_hdr *; my_hdr From: me "
  folder-hook+empty  "unmy_hdr *; my_hdr From: me "

this should work.  no time for testing now.

> I would really like to have this
> feature. I'm downloading my hotmail account with gotmail,
> and when I'm in my hotmail IMAP folder, I want to sent
> mails with the from: address of my hotmail account.

i suppose the mail that reaches you at hotmail is
addressed to something like "[EMAIL PROTECTED]"?
in that case - wouldn't "set reverse_name" suffice?

Sven



Re: $check-new -> TSM problem?

2002-09-26 Thread Johan Svedberg

On Thu, Sep 26, 2002 at 02:28:53PM +0200, Sven Guckes wrote:
> * Johan Svedberg <[EMAIL PROTECTED]> [2002-09-26 09:58]:
> > Sven Guckes wrote:
> > > don't forget about comp.mail.mutt!
> > > http://www.google.com/search?q=mutt+%22new+mail%22&scoring=d
> >
> > Ah, TSM must be the problem, thanks.
> 
> TSM?

TSM Tivoli Storage Manager

The backup system we use. Read in the manual that this could be the
problem, but now the admin says that it's not and mutt is compiled the
right way on the system. So I'm confused again. I don't have anything
like biff touching the files (I think)...

Johan



Re: mail box name in macro - nope

2002-09-26 Thread Sven Guckes

* Bernard Massot <[EMAIL PROTECTED]> [2002-09-26 10:54]:
> is there a way to get the current mail box name in a macro ?
> for example I'd like to do «macro index m current_box_name»

you want the name of the current folder as an address to send to?
oh, well, no, it is not possible.  you cannot create
variables in mutt and reference them in commands.

then again, maybe it is possible to stuff the current folder's name
into a file and have it put into a shell variable which then gets
sourced... oh, no, this sounds a really *gross* hack...

Sven



Re: Tagging mail by date

2002-09-26 Thread darren chamberlain

* Chris Green <[EMAIL PROTECTED]> [2002-09-26 09:25]:
> I.e. how do I tag all messages more than (say) 365 days old in the
> current mailbox?

~d >365d

(darren)

-- 
Competence, like truth, beauty, and contact lenses, is in the eye of
the beholder.
-- Dr. Laurence J. Peter



Re: Tagging mail by date -> pattern ~d

2002-09-26 Thread Sven Guckes

* Chris Green <[EMAIL PROTECTED]> [2002-09-26 13:25]:
> I've looked at the documentation and I know it's possible
> but does anyone have any examples of tagging mail by date?
> I.e. how do I tag all messages more than
> (say) 365 days old in the current mailbox?

  ~d<1y"date is less than one year"

rtfm:  "4.2.3.  Searching by Date"

for more examples see also:
http://www.math.fu-berlin.de/~guckes/mutt/setup.php3#moving_mails

> Or even better does anyone have any sample scripts
> using mutt as the 'source' for archiving mail?

procmail exists.  procmail is powerful.  no mutt required.

> .. i.e. what I want to do ultimately is extract all messages
> older than xxx days from my current mail and append them to
> mailboxes in an identical archive hierarchy (which will be
> on a different machine with no serious disk quota limits).

send a copy to that other machine then and never mind
the tedious task of selecting and storing on your
restricted account then.  saves a lot of time...

> User-Agent: Mutt/1.3.16i

upgrade, please!  mutt 1.4 has been out for a while.

> Mail-Followup-To: Chris Green <[EMAIL PROTECTED]>, [EMAIL PROTECTED]

and if you are subscribed to this list
then please tell mutt about it with
"subscribe mutt-users" in your muttrc!
thanks.

Sven

-- 
Sven Guckes   [EMAIL PROTECTED]   http://www.guckes.net/mutt/the MUTT PAGES:
Binaries| Bugs| DOWNLOAD| History| Intro| Installation| Links| MailList| NEWS|
Patches| Philosophy| Pictures| Quotes| SETUP| Sites| Usenet| Users| Utilities|
Windows| Wishlist -- Comparison to Elm|.. Not for everyone!| Pet Peeves| Sigs.



Re: $check-new -> TSM problem?

2002-09-26 Thread Sven Guckes

* Johan Svedberg <[EMAIL PROTECTED]> [2002-09-26 13:41]:
> > > Ah, TSM must be the problem, thanks.
> > TSM?
> TSM Tivoli Storage Manager
> The backup system we use.
> Read in the manual that this could be the problem, but now the admin
> says that it's not and mutt is compiled the right way on the system.
> So I'm confused again. I don't have anything
> like biff touching the files (I think)...

maybe you should just rely on your procmail logfile...

i remember there some nice (perl) script which can
visualize the (new) mails within the folders since
last time you checked.  but this is not in sync with
the current state within the folders, of course...

Sven



Re: reread configuration file

2002-09-26 Thread PeterKorman

On Wed, Sep 25, 2002 at 03:01:06PM -0700, Burton Samograd wrote:
> On Wed, Sep 25, 2002 at 11:36:38PM +0200, Hans Ginzel wrote:
> >
> > Something like:
> > :function reread_cfg_files
> > :   reset all options to compile time
> > :   source startup files as by usual start
> > :endfunction
> > --
> 
> At the top of your .muttrc
> 
> unset *
> unhook *
> 
> should do the trick.
> 
> burton

unset * causes

Error in /home/pkorman/.muttrc, line 1: *: unknown variable
source: errors in /home/pkorman/.muttrc
Press any key to continue...


Mutt manual section 3.23

  The reset command resets all given variables to the compile time
  defaults (hopefully mentioned in this manual). If you use the command
  set and prefix the variable with ``&'' this has the same behavior as
  the reset command.

  With the reset command there exists the special variable ``all'',
  which allows you to reset all variables to their system defaults.



reset all
unhook *

will work. I dont know if it clears folder hooks though.
furthermore, if you rely on settings in /usr/local/etc/Muttrc
you better move everything into your local setting file.

-- 

[]+ Wisdom is vindicated by all her children.  +[]
[]  []
[]+ GnuPG  +[]




msg31277/pgp0.pgp
Description: PGP signature


Re: Tagging mail by date

2002-09-26 Thread Michael Berklmeir

Hi Chris!

On Thu, 26 Sep 2002, Chris Green wrote:

> I've looked at the documentation

Sure?

> and I know it's possible but does anyone have any examples of
> tagging mail by date?

Have a look at:


> I.e. how do I tag all messages more than (say) 365 days old in the
> current mailbox?

T "~d >1y"

or 

T "~d >365d"


Bye
Mike

-- 
Remember, drive defensively!  And of course, the best defense is a good
offense!



Re: looking for a better send-hook

2002-09-26 Thread Eugene Lee

On Wed, Sep 25, 2002 at 05:49:22PM -0500, Aaron Schrab wrote:
: 
: At 16:55 -0500 25 Sep 2002, Eugene Lee <[EMAIL PROTECTED]> wrote:
: > 
: > I know message-hook supports ~h, but it only activates when I view the
: > current message.  And I don't want to remember to view a message to
: > activate the hook.  This wouldn't be a such problem with your standard
: 
: message-hooks are also applied when you begin a reply, before send-hooks
: are applied.

I've tried this.  Several times.  The message-hook isn't applied when I
select a message in index mode.  It's applied only after I view the
currently selected message and then reply to it.


-- 
Eugene Lee
[EMAIL PROTECTED]




redefining mailboxes while running mutt

2002-09-26 Thread Robert Lillack

Hi,

since I have  a lot of mailboxes i wanted  to see only those
containing new mail while in the browser view. Because I use
MH folders all needed is just a really simple shell script:

for i in `flist -all -recurse -noshowzero -fast`
do
echo -n "\"+$i\" "
done

But  I have  trouble using  it. If  I change  my .muttrc  to
contain:

mailboxes `getnewboxes.sh`

everything is great,  but to do that while  Mutt is running.
Something like entering:

:mailboxes `getnewboxes.sh`

doesn't work. Any Ideas?

Thanks,
Rob.
-- 
r o b e r t | l i l l a c k
www.lillaxsitedesign.de/rob
secure mail key: 0xE7FFDF77



Re: reread configuration file

2002-09-26 Thread PeterKorman

On Thu, Sep 26, 2002 at 10:28:56AM -0400, PeterKorman wrote:
> On Wed, Sep 25, 2002 at 03:01:06PM -0700, Burton Samograd wrote:
> > On Wed, Sep 25, 2002 at 11:36:38PM +0200, Hans Ginzel wrote:
> > >
> > > Something like:
> > >   :function reread_cfg_files
> > >   :   reset all options to compile time
> > >   :   source startup files as by usual start
> > >   :endfunction
> > > --
> > 
> > At the top of your .muttrc
> > 
> > unset *
> > unhook *
> > 
> > should do the trick.
> > 
> > burton
> 
> unset * causes
> 
> Error in /home/pkorman/.muttrc, line 1: *: unknown variable
> source: errors in /home/pkorman/.muttrc
> Press any key to continue...
> 
> 
> Mutt manual section 3.23
> 
>   The reset command resets all given variables to the compile time
>   defaults (hopefully mentioned in this manual). If you use the command
>   set and prefix the variable with ``&'' this has the same behavior as
>   the reset command.
> 
>   With the reset command there exists the special variable ``all'',
>   which allows you to reset all variables to their system defaults.
> 
> 
> 
> reset all
> unhook *
> 
> will work. I dont know if it clears folder hooks though.
> furthermore, if you rely on settings in /usr/local/etc/Muttrc
> you better move everything into your local setting file.

I'm pretty sure it clears folder hooks.
if your first lines of .muttrc are:

reset all
unhook *
source /usr/local/etc/Muttrc

Your probably in good shape as long as your Muttrc is on this path.

JPK
-- 

[]+ Wisdom is vindicated by all her children.  +[]
[]  []
[]+ GnuPG  +[]




Re: looking for a better send-hook

2002-09-26 Thread Aaron Schrab

At 10:05 -0500 26 Sep 2002, Eugene Lee <[EMAIL PROTECTED]> wrote:
> I've tried this.  Several times.  The message-hook isn't applied when I
> select a message in index mode.  It's applied only after I view the
> currently selected message and then reply to it.

Of course message-hooks aren't applied when a message is simply selected
in the index, but they are applied when you start a reply to a message
even from the index.  I tried it before sending my previous message, and
it worked for me.  I've now tried it with 1.4, just to make *sure* that
this wasn't something that's been changed in the 1.5 development
version, and it works for me there as well.

Do you have a send-hook that's overriding the setting from the
message-hook?

-- 
Aaron Schrab [EMAIL PROTECTED]  http://www.schrab.com/aaron/
 [It is] best to confuse only one issue at a time.  -- K&R



Re: LC filename of attachement (off topic)

2002-09-26 Thread Michael Elkins

Hans Ginzel wrote:
> Does anybody probably know how to set sender's MUA (MS Outlook Express)
> to do it correctly? How does mutt encode the filenames?

Mutt uses the method described in RFC2231.  It should look something
like this:

Content-Disposition: attachment;
filename*=iso-8859-2'cz'poutn%ED_slavnost_SW.doc



The browser

2002-09-26 Thread Johan Svedberg

Anyone experinced mutt going to the wrong mailbox when you're in the
browsers mailbox view and place the indicator on some mailbox and press
enter?

-- 
Johan Svedberg, [EMAIL PROTECTED], http://www.acc.umu.se/~winkle



Re: S/MIME "encrypt-to" functionality as in GnuPG

2002-09-26 Thread Omen Wild

Quoting Omen Wild <[EMAIL PROTECTED]> on Wed, Sep 25 10:37:
>
> I'll look into this.  If that's the cause, then the problem is between
> my keyboard and chair, not yours.  ;-)

For anyone following this, the problem was indeed on my end.  I have an
updated patch, available from
http://descolada.dartmouth.edu/mutt/patch-1.5.1-ow.smime-encrypt-self.2
for anyone interested.

Omen

-- 
Too much of a good thing is WONDERFUL.



smime.p7s
Description: application/pkcs7-signature


Re: mutt and exchange

2002-09-26 Thread Michael Leone

Gregory Seidman said:
> Happily, I have mutt playing nice with the Exchange server at work over
> IMAP. This pleases me. Now I am looking for further interaction with the
> Exchange server. In particular, it is my understanding that there is
> some way to use the global (and personal?) address book(s) on the
> server. Maybe it's LDAP?

By default, Exchange turns on POP and IMAP, and also LDAP. You can browse
the GAL (Global Address List) via LDAP, but not personal address books.

> Perhaps it has something to do with the query
> functions? Do I need an external program to help? Is there a HOWTO
> somewhere (Google did not find anything useful for "mutt exchange
> howto")?

Good question. Dunno how mutt integrates with LDAP, but I know I have used
Outlook Express to query a GAL via LDAP. If you need to configure a
firewall or anything, LDAP access is port 389, I believe.

-- 
PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF
Member, LEAF Project AIM: MikeLeone
Public Key - 
Registered Linux user# 201348


Random Thought:
--





Re: fast conversion of html mail to text

2002-09-26 Thread Michael Leone

Sven Guckes said:
> * Mike Leone <[EMAIL PROTECTED]> [2002-09-26 03:35]:
>> > > Actually, I've gotten many non-HTML spams, too.
>> > > And I get many valid HTML mail, both
>> > > newsletters and private correspondence.
>> > has the thought ever struck you that it might be *you*?
>>
>> Since I know many different people that both send and receive
>> HTML mail, none of whome are spammers; and since I get a
>> number of HTML-only newletters that are defintely not spam ...
>> no, that thought has never struck me.  :-)
>
> well, if you subscribe to a HTML-only newsletter
> then you were asking for it - so it's your problem.

It's *not* a problem, for me, anyway. I know about the possible security
implications of HTML email, and know how to get around them. (most of
them, anyway).

>> Has the thought ever struck you that perhaps
>> you are too restrictive in what you accept?
>
> i have yet to see sn email which was enhanced by html.
> and i suppose i do have a problem with DOCuments from
> companies which forbid free software to use it, too.

Separate issue, tho.

-- 
PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF
Member, LEAF Project AIM: MikeLeone
Public Key - 
Registered Linux user# 201348


Random Thought:
--
Cigarro: Objeto cilíndrico de papel, recheado com palha. Contém uma faísca
numa ponta e um idiota na outra.





Re: fast conversion of html mail to text

2002-09-26 Thread Laurabelle

On Sep 26 2002, Sven Guckes shared a puddle of experience:



Just my 2p - I use procmail recipes (and a couple of scripts) to strip
HTML formatting from all legitimate email.  The same scripts add a note
to the effect that HTML has been removed; if I want to exchange email
with that person again, I generally ask for text-only email.  People
tend to cooperate, since after all they probably just don't realize it.

>Sven  [usually attaching sigs which fit the content of the message]

I find that my current .sig is often quite relevant when answering
questions but even more so when asking them.  It reminds me that the
answer is only as good as the question.  Besides, it's short.

Laurabelle
-- 
ASCII silly question, get a silly ANSI.



download pgpwrap from where?

2002-09-26 Thread savanna

Where do I download pgpewrap from? It's referred to in the sample
muttrc files, for encrypting mail with gpg, however I can't find it
anywhere on the web (though I've found hundreds of references to using
it in my .muttrc ;-) ).

I've searched debian.org, rpmfind, and the archives of mutt-users.

Here's one of the offending lines from my .muttrc:

set pgp_encrypt_sign_command="pgpewrap gpg --passphrase-fd 0 -v --batch
--output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r
-- %f"

--
Savanna.

 Free as in 'free speech', not 'free beer'.



msg31289/pgp0.pgp
Description: PGP signature