headers
Jing Xue | 1 Jan 02:20

Re: Can't reply to the right address

On Sun, Dec 31, 2006 at 01:45:14PM -0600, Travis H. wrote:
> I think there is a setting in muttrc that changes email
> addresses from user <at> foo to "Real Name" based on the addressbook.
> I wonder if that is the problem here.

Hi Travis,
Thanks for the reply. I do have 'reverse_realname' set, if that is
what you are referring to, but it doesn't look like that's causing
it (just tried unsetting it and got the same behavior).

I'm suspecting it's because the sender's Outlook somehow decided to
quote my real name for twice, first with single quote then with double
quote. What puzzles me is how this would cause mutt to figure out the
wrong address to reply to.

--
Jing Xue
Permalink | Reply | 0 comments |
headers
Jing Xue | 1 Jan 04:50

Re: Can't reply to the right address

On Sat, Dec 30, 2006 at 08:04:35PM -0500, Jing Xue wrote:
> 
> This isn't a big deal, of course. But I'm new to mutt, and am very
> interested in learning what exactly is causing the problem - and any
> possible solution.

I finally figured out it was because one of the alternates I set had an
overly broad regex that actually(!) happened to match the sender's
address in this case, which caused mutt to think the email was sent by
myself.

Sure not the first time I shot myself in the foot with one of these
powerful tools. 8-)

--
Jing Xue
Permalink | Reply | 0 comments |
headers
Louis-David Mitterrand | 2 Jan 15:47

saving attachement fails on sshfs filesystem

Hello,

Using debian unstable's 1.5.13-1.1 I can no longer save attachements on 
a sshfs (fuse) partition without any cue from mutt: pressing <enter> at 
the save-file prompt makes mutt wait a few seconds after which the same 
prompt and default filename returns with no error message. Instead of 
saving the file mutt creates a .muttxxx directory for each attempt:

drwx------ 1 ldm ldm    6 2007-01-02 15:31 .mutt7mnbhX/
drwx------ 1 ldm ldm    6 2007-01-02 15:25 .muttKXRT83/

Might this be related to this recent change (debian bug #396104)?

	CVE-2006-5297:
	Race condition in the safe_open function in the Mutt mail client
	1.5.12 and earlier, when creating temporary files in an NFS
	filesystem, allows local users to overwrite arbitrary files due to
	limitations of the use of the O_EXCL flag on NFS filesystems.

	CVE-2006-5298:
	The mutt_adv_mktemp function in the Mutt mail client 1.5.12 and
	earlier does not properly verify that temporary files have been
	created with restricted permissions, which might allow local users to
	create files with weak permissions via a race condition between the
	mktemp and safe_fopen function calls.

	See
	http://marc.theaimsgroup.com/?l=mutt-dev&m=115999486426292&w=2
	for details.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rado S | 2 Jan 16:01
Picon
Favicon

Re: how about the notion of filters for replying, etc.

=- Sweth Chandramouli wrote on Thu 28.Dec'06 at 20:17:53 -0500 -=

> On Thursday, 28 December 2006 at 17:35:26 EST,
>    Kyle Wheeler (<kyle-mutt <at> memoryhole.net>) wrote:
> > ...? You mean like this:
> > 
> >     set editor="myfilter.pl | $EDITOR"
> 
> Nope. What's passed to $editor is the message that you are
> composing. What the hypothetical $reply_filter would be passed
> would be the message to which you are responding. That way, you
> can access and act on info in the headers of the message being
> replied to that would otherwise never even make it into the temp
> file passed to $editor. (Examples below.)

set header=yes
set edit_headers=yes
set weed=no
<reply>

Then see what happens. Use your filter to parse quoted lines as
you desire to adjust your unquoted stuff. If you don't want to
"see" all headers while typing your msg in your real editor, then
make your filter cut them off before sending to the real editor,
and reattach the necessary stuff before returning to mutt,
potentially dropping unwanted quoted lines which have been only
used to digest the msg.

--

-- 
© Rado S. -- You must provide YOUR effort for your goal!
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Champion | 2 Jan 17:57
Favicon

Re: header field "References:" ?

* On 2006.12.28, in <20061228123732.GF15663 <at> lennartsson.se>,
*	"Anders Lennartsson" <anders <at> lennartsson.se> wrote:
> 
> It seems the need for this is sparse, so I wonder "How do you guys do
> it? Are you always subscribed?"

Basically, yes.  I'm subscribed to dozens of lists that I don't read
very often, just for the purpose of building up useful archives.  I use
procmail to match each mailing list I'm subscribed to.  It (a) sets
X-Label: according to the list name, (b) copies incoming messages to
archive mboxes, and (c) copiesd to inbox those lists that I track daily
or semi-daily.  All others are deleted after archival, so I don't wade
through all the noise, but I have the noise available to me if I want to
listen.

If a web search turns up messages on a list I'm subscribed to, I have
only to open that list's archive to respond.

Also: in some MLMs, mbox-format archives are available to subscribers.
You could subscribe to the list but disable delivery, just to have
access to full archives.

--

-- 
 -D.    dgc <at> uchicago.edu        NSIT    University of Chicago
Permalink | Reply | 0 comments |
headers
Sweth Chandramouli | 2 Jan 20:47

Re: how about the notion of filters for replying, etc.

On Friday, 29 December 2006 at 04:43:31 EST,
   Cameron Simpson (<cs <at> zip.com.au>) wrote:
> Or (3) map 'r' to <pipe-message>replier-script.sh<enter>.
[snip]
>   - fire up:
>       mutt -H the-new-reply-message-file

Heh.  It never occurred to me that there's no requirement that the
original mutt process has to do the sending; using another mutt process
should work fine.  Now for me to add "write replier-script" to the todo
list, and maybe come up with another muttrc for the sending mutt process
to use that won't take so long to start up...

Thanks,

Sweth.

--

-- 
Sweth Chandramouli
sweth <at> ethicalhomes.com - http://EthicalHomes.com/
Thinking of buying a home in DC or NoVA?  Local Housing Assistance
Programs can provide first-time buyers up to $70k towards their down
payment, plus below-market loans.  Househould income limits for some
programs are as high as $135k/year; ask me for info on how to apply.
Permalink | Reply | 0 comments |
headers
Travis H. | 3 Jan 02:01
Favicon

list admin: can we have List-Id?

While Majordomo is nice and standard (in that it uses the Sender: header
for list name and has never changed it's mind --- unlike Mailman, which
seems to change headers every year or two), could we get a List-ID header,
as defined by RFC 2919?

http://www.ietf.org/rfc/rfc2919.txt
--

-- 
A: No.
Q: Should I include quotations after my reply?
<URL:http://www.subspacefield.org/~travis/> -><-
Permalink | Reply | 0 comments |
headers
mess-mate | 3 Jan 19:55
Picon

imap user & pass

I've different folders i can access with imap-user and imap-pass set.

When i unset them, to login with the user-name and his password,
i've to do it at EVERY folder !

Is there a way to get a login only when launching mutt ?

best regards
Permalink | Reply | 0 comments |
headers
Albert Shih | 4 Jan 17:29
Picon
Picon
Favicon

save messages

Hi all

I'm question about the name of the folder use by mutt when I want to save a
message. 

Normaly I'm using the name of the sender. It's perfect. But now my imap
server is a courier-imap and in this server the «.» (the dot) is use by the
system for making subfolder. In this condition when the sender is something
like FirstName.LastName if I just use standard config (save) the message is
save in the subsubfolder LastName of subfolder Firstname

How can I make something like

	if the name_of_sender is string1.string2 <at> string3then the name of the folder
	is string1_string2

?

Regards

--
Albert SHIH
Observatoire de Paris Meudon
Heure local/Local time:
Jeu 4 jan 2007 17:25:04 CET
Permalink | Reply | 3 comments |
headers
William Yardley | 5 Jan 02:49
Favicon

re-encrypt encrypted emails

I have a folder with a bunch of gpg encrypted emails (all clearsigned
except for one large PGP/MIME encrypted email). I have a colleage who
lost his old key and didn't have it backed up, so I want to send him a
new copy of all the emails somehow, only re-encrypted for his new key.

Is there any way to do this, either within mutt or outside of mutt? I
have direct access to the mbox folder if it matters.

I was thinking of decrypting the whole thing to a file and then
re-encrypting somehow, but if I run gpg --decrypt on the whole folder, I
get one message decrypted and then:

gpg: [don't know]: invalid packet (ctb=2f)
gpg: WARNING: encrypted message has been manipulated!
gpg: [don't know]: invalid packet (ctb=32)

plus, then the messages wouldn't be broken up correctly anymore.

w
Permalink | Reply | 2 comments |

Gmane