Masand, Manish proclaimed on mutt-users that:
> how can i set the reply-to in .muttrc as different from my sender address
Use my_hdr to do this.
see my muttrc at http://www.hserus.net/muttrc.html or other muttrcs at
http://www.mutt.org
ps: please trim your signature
--
Suresh Ramasu
On Thu, May 10, 2001 at 09:06:04PM -0700, Carl Constantine wrote:
> On 5/10/01 9:28, adam morley at [EMAIL PROTECTED] wrote:
>
> > i actually have mutt runing on solaris 8. the colors in the config file never
> > seem to mactch up with the colors diplayed. i just play around with it until
> > i
Hi,
I've set my sent-mail folder to ~/Mail/sent-mail. Mutt creates the
folder, but the mail is not saved.
I suppose this should be done, if the $record variable is set.
Thanks,
Jens
At 23:04 -0400 10 May 2001, adam morley <[EMAIL PROTECTED]> wrote:
> On Fri, May 11, 2001 at 12:43:28AM +0530, Suresh Ramasubramanian wrote:
> > format=flowed requires a lot more implementation than just adding a
> > content-type header, iirc.
I wouldn't really say "a lot more" (at least when not
On Fri, May 11, 2001 at 10:49:50AM +0200, Masand, Manish wrote:
> actually i am getting a syntax error when i do a . .muttrc
>
> /export/home/tks01 > . .muttrc
> ksh: syntax error: `(' unexpected
Why are you sourcing your mutt configuration file into your shell?
> ``set'' sig_dashes=yes
Why
On Fri, May 11, 2001 at 11:16:25AM +0200, Jens Chr. Lisner wrote:
> Hi,
>
> I've set my sent-mail folder to ~/Mail/sent-mail. Mutt creates the
> folder, but the mail is not saved.
>
> I suppose this should be done, if the $record variable is set.
This was all that was required for me.
# S
Jens Chr. Lisner wrote:
> I've set my sent-mail folder to ~/Mail/sent-mail. Mutt creates the
> folder, but the mail is not saved.
>
> I suppose this should be done, if the $record variable is set.
You will need to set $copy as well as $record, e.g.
set folder="~/Mail"
set copy=y
Hi there,
after changing from elmME+ to mutt (mainly because of threads and
colors) I'm unable to find one feature I really got used to:
after attaching a file of name "something.extension" I want it to have
a filename of "something.else" when viewed by the recipient. s far as
I know, this means
Clemens Vonrhein ([EMAIL PROTECTED]) said something to this effect on
05/11/2001:
> after changing from elmME+ to mutt (mainly because of threads and
> colors) I'm unable to find one feature I really got used to:
After attaching the file, in the compose menu, use the arrow keys
to select the att
Jens Chr. Lisner wrote:
> I've set my sent-mail folder to ~/Mail/sent-mail. Mutt creates the
> folder, but the mail is not saved.
>
> I suppose this should be done, if the $record variable is set.
Mr. Wade advised:
> You will need to set $copy as well as $record, e.g.
>
> set folder="~/Mail"
> se
Hi,
I am searching for a way defining a default TO: address depending on the
actual folder. Let's say I am in the mutt's Mailinglist folder. If I
press "m" I want a default address [EMAIL PROTECTED] there.
I think it is an folder-hook thing, but I have no idea how to implement
this. Any suggesti
Kai Weber wrote:
> I am searching for a way defining a default TO: address depending on the
> actual folder. Let's say I am in the mutt's Mailinglist folder. If I
> press "m" I want a default address [EMAIL PROTECTED] there.
>
> I think it is an folder-hook thing, but I have no idea how to implem
On Fri, May 11, 2001 at 04:34:03AM -0500, Aaron Schrab wrote:
> At 23:04 -0400 10 May 2001, adam morley <[EMAIL PROTECTED]> wrote:
> > On Fri, May 11, 2001 at 12:43:28AM +0530, Suresh Ramasubramanian wrote:
> > > format=flowed requires a lot more implementation than just adding a
> > > content-typ
On Fri, May 11, 2001 at 04:34:03AM -0500, Aaron Schrab wrote:
> At 23:04 -0400 10 May 2001, adam morley <[EMAIL PROTECTED]> wrote:
> > On Fri, May 11, 2001 at 12:43:28AM +0530, Suresh Ramasubramanian wrote:
> > > format=flowed requires a lot more implementation than just adding a
> > > content-typ
Quoting adam morley <[EMAIL PROTECTED]>, who wrote:
> On Fri, May 11, 2001 at 04:34:03AM -0500, Aaron Schrab wrote:
> > At 23:04 -0400 10 May 2001, adam morley <[EMAIL PROTECTED]> wrote:
> > > On Fri, May 11, 2001 at 12:43:28AM +0530, Suresh Ramasubramanian wrote:
> > > see in one second, then it
On Fri, May 11, 2001 at 05:12:34PM +0200, Kai Weber wrote:
> I am searching for a way defining a default TO: address depending on the
> actual folder. Let's say I am in the mutt's Mailinglist folder. If I
> press "m" I want a default address [EMAIL PROTECTED] there.
>
> I think it is an folder-h
* On [010511 18:02] adam morley <[EMAIL PROTECTED]> wrote:
>> Your nested quoting was also done incorrectly. According to section 4.5
>> of RFC 2646 there should be no space between the '>' marks at the start
>> of quoted lines.
>
> that, my friend was mutts doing, not mine. so if someone could
On Fri, May 11, 2001 at 12:04:50PM -0400, Sam Roberts wrote:
> Quoting adam morley <[EMAIL PROTECTED]>, who wrote:
> > On Fri, May 11, 2001 at 04:34:03AM -0500, Aaron Schrab wrote:
> > > At 23:04 -0400 10 May 2001, adam morley <[EMAIL PROTECTED]> wrote:
> > > > On Fri, May 11, 2001 at 12:43:28AM +
On Fri, May 11, 2001 at 06:49:19PM +0200, Lawrence Mitchell wrote:
> * On [010511 18:02] adam morley <[EMAIL PROTECTED]> wrote:
> >> Your nested quoting was also done incorrectly. According to section 4.5
> >> of RFC 2646 there should be no space between the '>' marks at the start
> >> of quoted
On 2001-05-10 23:04:34 -0400, adam morley wrote:
>well, if i write my messages so they are wrapped like this as you
>will see in one second, then it can be classified as a flowed
>message. a zero paragraph flowed message. hence my need to know
>how to do such a thing. would require reformat
On 2001-05-10 13:29:17 -0400, adam morley wrote:
>so currently, the mime type of my message is text/plain. i want
>to change this to text/plain; format=flowed for each outgoing mail
>message. i didn't see this in the muttrc file or manual. thanks.
You could update to the latest CVS version.
On 2001-05-11 13:21:40 -0400, adam morley wrote:
>ah, if mutts not putting in the > right, then MUTT is what is
>non-compliant, correct? i shouldn't have to make a vim macro to
>fix mutt's non-compliance?
It's configurable, and the mutt version you are using doesn't even
claim that it's prod
Kai Weber wrote:
> I am searching for a way defining a default TO: address depending on the
> actual folder. Let's say I am in the mutt's Mailinglist folder. If I
> press "m" I want a default address [EMAIL PROTECTED] there.
>
> I think it is an folder-hook thing, but I have no idea how to implem
Hello Kai!
On Fri, 11 May 2001, Kai Weber wrote:
> I am searching for a way defining a default TO: address depending on
> the actual folder. Let's say I am in the mutt's Mailinglist folder. If
> I press "m" I want a default address [EMAIL PROTECTED] there.
>
> I think it is an folder-hook thing
On Fri, May 11, 2001 at 07:45:46PM +0200, Thomas Roessler wrote:
> On 2001-05-11 13:21:40 -0400, adam morley wrote:
>
> >ah, if mutts not putting in the > right, then MUTT is what is
> >non-compliant, correct? i shouldn't have to make a vim macro to
> >fix mutt's non-compliance?
>
> It's conf
On Fri, May 11, 2001 at 01:37:16PM -0500, Paul Cox wrote:
> On Friday, May 11, 2001, adam morley wrote:
>
> > ah, if mutts not putting in the > right, then MUTT is what is non-compliant,
>correct? i shouldn't have to make a vim macro to fix mutt's non-compliance?
>
> indent_string
>
> Type: s
On Fri, May 11, 2001 at 06:58:08PM +0200, Thomas Roessler wrote:
> On 2001-05-10 23:04:34 -0400, adam morley wrote:
>
> >well, if i write my messages so they are wrapped like this as you
> >will see in one second, then it can be classified as a flowed
> >message. a zero paragraph flowed messag
On Fri, May 11, 2001 at 06:55:47PM +0200, Thomas Roessler wrote:
> On 2001-05-10 13:29:17 -0400, adam morley wrote:
>
> >so currently, the mime type of my message is text/plain. i want
> >to change this to text/plain; format=flowed for each outgoing mail
> >message. i didn't see this in the m
On 2001-05-11 15:56:33 -0400, adam morley wrote:
>I've just been told that > > is non-standard though. which means
>we are distributing a software package that is non-standard. is
>that bad?
Is not _what_ standard? If we don't say "this is format=flowed", we
also don't have to emit "format=
On 2001-05-11 15:59:30 -0400, adam morley wrote:
>ah, no line *should* be longer than 78 chras, correct? its a
>should, not a must if i remember.
Which means that you shouldn't violate this unless you have a very
good reason (such as a long word) to violate it.
--
Thomas Roessler
On 2001-05-11 16:02:11 -0400, adam morley wrote:
>that is not required by rfc 2646, it is a should statment. and it
>is there for non-flow aware mail readers. we avoid this when not
>wrapping and using fixed, as it aint flowed text.
You don't expect this to look nice in any usual mailer, do
On Fri, May 11, 2001 at 10:43:58PM +0200, Thomas Roessler wrote:
> On 2001-05-11 16:02:11 -0400, adam morley wrote:
>
> >that is not required by rfc 2646, it is a should statment. and it
> >is there for non-flow aware mail readers. we avoid this when not
> >wrapping and using fixed, as it ain
On Fri, May 11, 2001 at 10:42:43PM +0200, Thomas Roessler wrote:
> On 2001-05-11 15:59:30 -0400, adam morley wrote:
>
> >ah, no line *should* be longer than 78 chras, correct? its a
> >should, not a must if i remember.
>
> Which means that you shouldn't violate this unless you have a very
> g
On Fri, May 11, 2001 at 05:29:44PM -0400, adam morley wrote:
>
> my point is the reason for not violating said should clause is
> archaic. my reason is that if your mail reader can't handle it, step
> into the 21st century and get a reader that knows how to wrap text.
Mail systems unpredictably
I had this symptom, I needed the file to have a .html suffix:
text/html; lynx -localhost -dump %s ; copiousoutput ; nametemplate=%s.html
Your problem sounds slightly different, but maybe give it a whirl.
Sam
Quoting "Dr. Christian Seberino" <[EMAIL PROTECTED]>, who wrote:
> Stephan,
>
> Here
On Fri, May 11, 2001 at 02:48:27PM -0700, [EMAIL PROTECTED] wrote:
> On Fri, May 11, 2001 at 05:29:44PM -0400, adam morley wrote:
> >
> > my point is the reason for not violating said should clause is
> > archaic. my reason is that if your mail reader can't handle it, step
> > into the 21st cent
On Fri, May 11, 2001 at 02:59:25PM -0700, Dr. Christian Seberino wrote:
> You never had any strange variation of html and/or
> xml that w3m could not handle? I'm using lynx.
> Is w3m better than lynx at this?
I have never received a message that w3m couldn't handle. I really like
w3m because i
Chris,
After getting the view of the attachments with "v", select the
file labelled "text/html" and enter. If you mailcap file is
right, you'll see the Lynx version of html in the window.
jc
On Fri, May 11, 2001 at 02:58:34PM -0700, Dr. Christian Seberino wrote:
> Suresh,
On Fri, May 11, 2001 at 04:45:31PM -0700, Gary Johnson wrote:
> On Fri, May 11, 2001 at 02:59:25PM -0700, Dr. Christian Seberino wrote:
>
> > You never had any strange variation of html and/or
> > xml that w3m could not handle? I'm using lynx.
> > Is w3m better than lynx at this?
>
> I have nev
If a MIME entity (either a sub-part of a multipart message or in this
case the entire body of the message) is not of a type that Mutt can
handle internally, but it's been told to autoview it then Mutt saves
the entity to a temporary file, runs the appropriate command on this
file and shows you the
Using a large mallet, Mr. Wade whacked out:
> > folder-hook .'unmy_hdr To:'
> > folder-hook =IN-L-mutt-users 'my_hdr To: [EMAIL PROTECTED]'
> > A problem with this, though, is that list-replies tend to have
> > the list address twice in the To: field. I haven't spent any
> > ti
41 matches
Mail list logo
