Re: Bounced mails
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 Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: Mutt issues with Solaris 8
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 get it to work. ill go back and read your original post and see if i can
> > figure it out.
>
> Really? What did you do and how did you do it? Can you send me your configs
> as well?
sure, my .muttrc is below. the global muttrc file is just the standard one i think.
>
> Did you also use ncurses?
not that i remember. i dont think i have gnu curses, but i do have svr4 curses
>
begin muttrc--
# adam's muttrc. thanks to super tim
#
#
# My mail folder is
set folder=~/mail
# I am not prompted to ask whether I will move message out of the spool
# the answer is no
set move=no
# Messages are automatically purged when marked for deletion
#set delete=yes
#beeping...on new.
set beep_new=yes
set beep=no
set autoedit=yes
set menu_scroll=yes
# Specifies mailboxes with incoming mail
mailboxes deleted because i dont want you to know. :)
#mailing list config
set honor_followup_to=yes
set followup_to=yes
lists
subscribe
# Saves all messages I sent to a folder
set copy=yes
set record=~/mail/sent
# My Aliase file info
set alias_file=~/.mail_aliases
source ~/.mail_aliases
# Defines my header
my_hdr From: adam morley <[EMAIL PROTECTED]>
# Defines my editor
set editor=/usr/bin/vi
# Sets the place to put postponed messages
set postponed=~/mail/postponed
# Does not prompt when saving messages to an existing folder
set confirmappend=no
# Sets it so that when you get to the bottom of the message it stops rather than
going to the next message
set pager_stop=yes
# Makes the index view use threads - a cool feature
set sort=threads
#index formatting
set index_format="%4C %Z %{%d %b} %-15.15F (%4l) %s"
#above changed to handle mailing liststhe F
# header display, j,k are mapped to vi-fu, x for pine like feel, - and space for pine
compatibility. the arrow keys work like pine, cept for left right which scroll like -
and space
bind pager H display-toggle-weed
bind pager h noop
bind pager j next-line
bind pager k previous-line
bind index x sync-mailbox
bind pager previous-line
bind pager next-line
bind pager previous-entry
bind pager next-entry
bind index - previous-page
bind index next-page
#makes it feel like pine, to a certain extent.
# list of header fields to ignore when displaying messages
ignore "from " received content- mime-version status x-status message-id
ignore sender references return-path lines
ignore Envelope-to X- In-Reply-To NNTP-Postings Xref
#
# Stuff taken from the default global file
#
# don't add the hostname to the From header
unset use_domain
# don't generate a From header
unset use_from
# Exim does not removes Bcc headers
unset write_bcc
# imitate the old search-body function
macro index \eb '/~b ' 'search in message bodies'
# simulate the old url menu
macro index \cb |urlview\n 'call urlview to extract URLs out of a message'
macro pager \cb |urlview\n 'call urlview to extract URLs out of a message'
# colors
color hdrdefault brightcyan black #default
color quoted brightblue yellow
color signature cyan black
color attachment brightyellow blue
#color indicator black cyan
color indicator brightblack cyan # nicer in reverse-color xterms
color status brightblue white
color tree blue white
color markers brightblue red
color tildebrightblue red
color header blue white ^From:
color header brightgreen black ^To:
color header brightgreen black ^Cc:
color header brightgreen black ^Reply-To:
color header brightblue yellow ^Subject:
color body brightblue yellow [\-\.+_a-zA-Z0-9]+@[\-\.a-zA-Z0-9]+
color body brightblue yellow (http|ftp)://[\-\.\,/%~_:?\#a-zA-Z0-9]+
#the above stuff with brightblue/yellow is because other color combos don't seem to
work too well.
# aliases for broken MUAs
charset-hook US-ASCII ISO-8859-1
charset-hook x-unknownISO-8859-1
charset-hook windows-1250 CP1250
charset-hook windows-1251 CP1251
charset-hook windows-1252 CP1252
charset-hook windows-1253 CP1253
charset-hook windows-1254 CP1254
charset-hook windows-1255 CP1255
charset-hook windows-1256 CP1256
charset-hook windows-1257 CP1257
charset-hook windows-1258 CP1258
# GnuPG configuration
set pgp_sign_micalg=pgp-sha1 # default for DSS keys
set pgp_decode_command="gpg %?p?--passphrase-fd 0? --no-verbose --batch --output - %f"
set pgp_verify_command="gpg --no-verbose --batch --output - --verify %s %f"
set pgp_decrypt_command="gpg --passphrase-fd 0 --no-verbose --batch --output - %f"
set pgp_sign_command="gpg --no-verbose --batch --output - --passphrase-fd 0 --armor
--detach-sign --textmode %?a?-u %a? %f"
set pgp_clearsign_command="gpg --no-verbose --batch --ou
sent messages
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
Re: Changing the Mime type of the outgoing message by default?
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 dealing with quoted text), but definitely more. > well, if i write my messages so they are wrapped like this as you will You mean not wrapped. > see in one second, then it can be classified as a flowed message. a I suppose it *could* be classified as such, but I don't see much point in doing so. The whole point of format=flowed is so that paragraphs will wrap in programs that support it, but still be readable with programs that don't do wrapping. It also doesn't follow part of RFC 2646: ] When generating Format=Flowed text, lines SHOULD be shorter than 80 ] characters. As suggested values, any paragraph longer than 79 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. -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ ... very sad life. Probably have very sad death but at least there is symmetry. -- Zathras
Re: Bounced mails
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 the quotes around set?
--
Dave Pearson: | mutt.octet.filter - autoview octet-streams
http://www.davep.org/ | mutt.vcard.filter - autoview simple vcards
Mutt: | muttrc2html - muttrc -> HTML utility
http://www.davep.org/mutt/ | muttrc.sl - Jed muttrc mode
Re: sent messages
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. # Set the default folder. set folder="$HOME/Mail" # Always save a copy of outgoing messages. set copy=yes # Default location to save outgoing mail. set record=+outbox That did it for me. Mike -- Michael P. Soulier <[EMAIL PROTECTED]> "With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead." -- RFC 1925 PGP signature
Re: sent messages
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=yes set record="+sent-mail" Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
changing/edit Content-Disposition: ... filename= part
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 changing the "filenam=" part of the Content-Disposition. Doing this was really easy in elmME+ (in the attachement menu). The only feature that looks like it should be doing it is the "R" command in the attachment menu, i.e. the 'rename-file' command. However, changing "something.extension" to "something.else" in there has no effect when trying to save this attachement as recipient. Can I edit the whole message (and change the relevant part in Content-Disposition by hand)? Am I missing some obvious configuration parameter? I tried it both with version 1.2.5i and 1.3.18i ... Cheers Clemens -- *** * Clemens Vonrhein, Ph.D. [EMAIL PROTECTED] * * Global Phasing Ltd. * Sheraton House, Castle Park Tel: +44-(0)1223-353033 * Cambridge CB3 0AX, UK Fax: +44-(0)1223-366889 *-- * BUSTER Development Group (http://babinet.globalphasing.com) ***
Re: changing/edit Content-Disposition: ... filename= part
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 attachment, and hit 'd', to edit the attachment's name. (darren) -- Jesus is coming, everyone look busy.
Re: sent messages
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" > set copy=yes > set record="+sent-mail" Jens Chr. Lisner replied: > I've uncommented the $copy line in the .muttrc. It is explicitly set to > "yes" now. But the mail is not written to the sent-mail file. Hmm... be sure that $save_name and $force_name are unset. Also, check to see if you have any fcc-hooks and fcc-save-hooks interfering with what you want. What about the perms on the ~/Mail/sent-mail file? If it's not writable for you, that could cause a problem. This might be wise: $ chmod u+w ~/Mail/sent-mail (I am assuming mbox mailbox format.) If $copy is set to yes, $save_name and $force_name are unset, there are no interfering fcc-hooks, $record is set to the correct path, and you have write permission to that file, it _should_ work, as far as I can tell! =) I hope this helps. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Folder specific TO-Address
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 suggestions & tips? Kai. -- k a i w e b e r | mailto:[EMAIL PROTECTED] w w w | http://www.glorybox.de/
Re: Folder specific TO-Address
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 implement > this. Any suggestions & tips? This might help or give you a starting place, anyway: folder-hook .'unmy_hdr To:' folder-hook =IN-L-mutt-users 'my_hdr To: [EMAIL PROTECTED]' Obviously, I use "=IN-L-mutt-users" as the mailing list folder; you should sdjust that accordingly for your situation. 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 time determining a method to correct that. Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Changing the Mime type of the outgoing message by default?
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-type header, iirc. > > I wouldn't really say "a lot more" (at least when not dealing with > quoted text), but definitely more. > > > well, if i write my messages so they are wrapped like this as you will > > You mean not wrapped. sorry, ive been talking about this too long with others, it starts to run together in my head. > > > see in one second, then it can be classified as a flowed message. a > > I suppose it *could* be classified as such, but I don't see much point > in doing so. The whole point of format=flowed is so that paragraphs > will wrap in programs that support it, but still be readable with > programs that don't do wrapping. well, the whole point is that ppl dont like unwrapped text. so one solution has been format=flowed. any others? > > It also doesn't follow part of RFC 2646: thats a should clause. not a must > > ] When generating Format=Flowed text, lines SHOULD be shorter than 80 > ] characters. As suggested values, any paragraph longer than 79 > > 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 explain why/how to change that, then thanks! > > -- > Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ > ... very sad life. Probably have very sad death but at least there > is symmetry. -- Zathras -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
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-type header, iirc. > > I wouldn't really say "a lot more" (at least when not dealing with > quoted text), but definitely more. > > > well, if i write my messages so they are wrapped like this as you will > > You mean not wrapped. > > > see in one second, then it can be classified as a flowed message. a > > I suppose it *could* be classified as such, but I don't see much point > in doing so. The whole point of format=flowed is so that paragraphs > will wrap in programs that support it, but still be readable with > programs that don't do wrapping. one gnus user (under emacs) pointed out that unwrapped text is treated as "fixed" text so this line which just wrapped doesn't wrap word boundaries, but letter boundaries. is that wrong/right? > > It also doesn't follow part of RFC 2646: > > ] When generating Format=Flowed text, lines SHOULD be shorter than 80 > ] characters. As suggested values, any paragraph longer than 79 > > 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. > > -- > Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ > ... very sad life. Probably have very sad death but at least there > is symmetry. -- Zathras -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
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 can be classified as a flowed message. a > > > > I suppose it *could* be classified as such, but I don't see much point > > in doing so. The whole point of format=flowed is so that paragraphs > > will wrap in programs that support it, but still be readable with > > programs that don't do wrapping. > > well, the whole point is that ppl dont like unwrapped text. so one solution has >been format=flowed. > > any others? Don't send unwrapped text? Sam -- Sam Roberts <[EMAIL PROTECTED]>
Re: Folder specific TO-Address
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-hook thing, but I have no idea how to implement > this. Any suggestions & tips? I use a set of folder-hooks like this, one for each mailing list folder. folder-hook +Incoming/mutt-users\ 'macro index M ":push m^[EMAIL PROTECTED]^M^M" "mail to list"' Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications PGU http://www.spocom.com/users/gjohnson/mutt/ | Spokane, Washington, USA
Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
* 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 explain > why/how to change that, then thanks! Using vim as an editor, I came up with this: "change double-quoted text to RFC 2646 format autocmd BufNewFile,BufRead .followup,.letter,mutt*,nn.*,snd.* :%s/^>\(.*>\)/>\1/ The command on one line of course, hope that helps lawrence -- Lawrence Mitchell | http://members.tripod.co.uk/EVSvienna/ [EMAIL PROTECTED] | "He says gods like to see an atheist around. Gives them something to aim at." -- (Terry Pratchett, Small Gods)
Re: Changing the Mime type of the outgoing message by default?
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 +0530, Suresh Ramasubramanian wrote: > > > > see in one second, then it can be classified as a flowed message. a > > > > > > I suppose it *could* be classified as such, but I don't see much point > > > in doing so. The whole point of format=flowed is so that paragraphs > > > will wrap in programs that support it, but still be readable with > > > programs that don't do wrapping. > > > > well, the whole point is that ppl dont like unwrapped text. so one solution has >been format=flowed. > > > > any others? > > Don't send unwrapped text? why? (and if you open up this can of worms, i can go on for at least 20 messages, so if others dont want to hear it, we might want to take it off the list) > > Sam > > -- > Sam Roberts <[EMAIL PROTECTED]> -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
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 lines. > > > > that, my friend was mutts doing, not mine. so if someone could explain > > why/how to change that, then thanks! > Using vim as an editor, I came up with this: > "change double-quoted text to RFC 2646 format > autocmd BufNewFile,BufRead .followup,.letter,mutt*,nn.*,snd.* > :%s/^>\(.*>\)/>\1/ > The command on one line of course, hope that helps 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? > > lawrence > -- > Lawrence Mitchell | http://members.tripod.co.uk/EVSvienna/ > [EMAIL PROTECTED] | "He says gods like to see an atheist around. > Gives them something to aim at." > -- (Terry Pratchett, Small Gods) -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
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 reformatting other messages >tho. text/plain; format=flowed actually forbids overly long lines. Indeed, in a properly formatted text/plain; format=flowed message, no line will be longer than 78 characters when the message is viewed with a viewer which does _not_ support format=flowed. The fact that a lines may be flowed is indicated by a space character in the end of a line. (Look closely at this message for an example.) -- Thomas Roessler http://log.does-not-exist.org/
Re: Changing the Mime type of the outgoing message by default?
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. It has some support for text/plain; format=flowed built into it. (Mutt now even makes use of the features for this format when, e.g., replying to messages.) However, you'll also need an editor which supports editing messages in that format - that is, adds spaces whereever necessary, be it in the end of a line when it wraps, or in the beginning of lines where you have a ">" character or the word "From ". I have created a mode for jed which does all this (probably it still has a couple of bugs); you can try this, too. -- Thomas Roessler http://log.does-not-exist.org/
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
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 producing text/plain; format=flowed. -- Thomas Roessler http://log.does-not-exist.org/
Re: Folder specific TO-Address
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 implement > this. Any suggestions & tips? Mr. Wade wrote: > This might help or give you a starting place, anyway: > > folder-hook .'unmy_hdr To:' > folder-hook =IN-L-mutt-users 'my_hdr To: [EMAIL PROTECTED]' > > Obviously, I use "=IN-L-mutt-users" as the mailing list folder; > you should sdjust that accordingly for your situation. > > 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 > time determining a method to correct that. Regarding the "problem" I described: testing indicates that Mutt will include duplicated addresses in the command-line arguments used to call $sendmail, but it seems my MTA, Sendmail 8.11.3, filters out those duplicate addresses anyway, sending a message only once to each recipient, regardless of multiple mentions of the same recipient addresses on the command-line, so it's a non-issue for me, (but it's good to know! I had been very careful in the past to delete multiple mentions of the same recipient in the recipient fields. I guess that's unnecessary.) -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Folder specific TO-Address
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, but I have no idea how to implement > this. Any suggestions & tips? Look at the Mutt-Manual at point 2.3.4. Miscellaneous Functions list-reply (default: L) Reply to the current or tagged message(s) by extracting any addresses which match the addresses given by the ``lists or subscribe'' commands, but also honor any Mail-Followup-To header(s) if the ``$honor_followup_to'' configuration variable is set. Using this when replying to messages posted to mailing lists helps avoid duplicate copies being sent to the author of the message you are replying to. bye - Wilhelm -- ._. Wilhelm Wienemann <[EMAIL PROTECTED]> / _,\ | (_./ Debian GNU/Linux Version 2.2 Potato \, To learn more visit => http://www.debian.org/
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
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 configurable, and the mutt version you are using doesn't even > claim that it's producing text/plain; format=flowed. so how do i make mutt set the quote thing correctly? and im not setting format=flowed right now. mainly because nobody's told me how to automate it save editing the source. > > -- > Thomas Roessler http://log.does-not-exist.org/ -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
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: string > Default: "> " > > Specifies the string to prepend to each line of text quoted in a message > to which you are replying. You are strongly encouraged not to change > this value, as it tends to agitate the more fanatical netizens. 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? > > -- > [EMAIL PROTECTED], ICQ#: 25370820, OpenPGP key at www.keyserver.net > 1024D/39F0BBF4 2024 B7CB 10BF 6BE7 2ECE E0FD 1360 0181 39F0 BBF4 > > Current Linux uptime: 5 days 22 hours 55 minutes. -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
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 message. hence my need to know > >how to do such a thing. would require reformatting other messages > >tho. > > text/plain; format=flowed actually forbids overly long lines. > Indeed, in a properly formatted text/plain; format=flowed message, > no line will be longer than 78 characters when the message is viewed > with a viewer which does _not_ support format=flowed. ah, no line *should* be longer than 78 chras, correct? its a should, not a must if i remember. > > The fact that a lines may be flowed is indicated by a space > character in the end of a line. yes, and if i place the entire line as one big long unwrapped line, then i have zero paragraphs with each paragraph having at least one space-crlf sequence. which is compliant with the rfc in saying that format flowed is in effect. the only reason i bring this up is that people have been arguing that with the gnus mailer (emacs mailer) an unwrapped line of text is wrapped at the char (as it is format=fixed) whereas a flowed message (with the proper options set) is wrapped on word boundaries. > > (Look closely at this message for an example.) > > -- > Thomas Roessler http://log.does-not-exist.org/ -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
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 muttrc file or manual. thanks. > > You could update to the latest CVS version. It has some support for > text/plain; format=flowed built into it. (Mutt now even makes use > of the features for this format when, e.g., replying to messages.) really? thats cool. > > However, you'll also need an editor which supports editing messages > in that format - that is, adds spaces whereever necessary, be it in not if you never space crlf. > the end of a line when it wraps, or in the beginning of lines where 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 have a ">" character or the word "From ". this is an issue > > I have created a mode for jed which does all this (probably it still > has a couple of bugs); you can try this, too. never used jed. too many editors already. > > -- > Thomas Roessler http://log.does-not-exist.org/ -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
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=flowed". (Also, as I said, the CVS has an option to do nice and correct format=flowed when used together with the right kind of editor.) -- Thomas Roessler http://log.does-not-exist.org/
Re: Changing the Mime type of the outgoing message by default?
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 http://log.does-not-exist.org/
Re: Changing the Mime type of the outgoing message by default?
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 you? -- Thomas Roessler http://log.does-not-exist.org/
Re: Changing the Mime type of the outgoing message by default?
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 aint flowed text. > > You don't expect this to look nice in any usual mailer, do you? dont expect what again? i have a short term memory and yeah. thanks. > > -- > Thomas Roessler http://log.does-not-exist.org/ -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
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 > good reason (such as a long word) to violate it. 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. > > -- > Thomas Roessler http://log.does-not-exist.org/ -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
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 truncate lines longer than (IIRC) 1023 characters. So you're likely to have truncated paragraphs and sure to tick off just about everyone with your arrogant attitude. If you want to break RFCs get a job with M$, where doing so seems to be a good career move. -rex
Re: HTML email that is NOT an attachment problem! :(
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 is beginning of an email that is dumping > html source even though it looks like lynx is > activated... > > ... > >"Deborah Warren" <[EMAIL PROTECTED]>, >"Jacob A. Langford" <[EMAIL PROTECTED]>, >"Ralph Nebiker" <[EMAIL PROTECTED]> > Subject: FIE2JIF SITREP 5/11 > Date: Fri, 11 May 2001 17:08:17 -0400 > > [-- Autoview using lynx -dump '/tmp/muttoZiSst' --] > > > > > > > Federation Integration- class=997221315-23022001>2 JIF SITREP class=997221315-23022001>5/1 class=118235920-11052001>1 size=2>: > > Today's highlights: > > etc. > > > Here is my .mailcap and .muttrc... > > (seberino /home/seberino) % more .mailcap > text/html; lynx -dump %s ; copiousoutput > application/msword; /home/seberino/soffice/soffice %s ; > edit=/home/seberino/soffice/soffice %s; > compose="/home/seberino/soffice/soffice %s"; description="Microsoft Word document" > (seberino /home/seberino) % > (seberino /home/seberino) % > (seberino /home/seberino) % more .muttrc > set from = [EMAIL PROTECTED] > fcc-hook . +sent-mail > save-hook . +saved-mail > set hostname = spawar.navy.mil > set fast_reply = yes > set include = yes > auto_view text/html > set autoedit = yes > set reverse_alias = yes > set confirmappend = no > set confirmcreate = no > set move = no > set delete = yes > set sendmail = "/usr/sbin/sendmail -oem -oi" > > I don't think it is part text and part html. > Any other ideas from fragment above? > > Chris > > > > On Wed, May 09, 2001 at 06:35:07PM +0200, Stefan Frank wrote: > > At Tue, May 08 2001 [21:10 -0700], Dr. Christian Seberino aroused my curiosity >with: > > > I got lynx to read HTML attachments but > > > looks like MS Outlook something is sending > > > HTML emails that are NOT attachments and > > > my autofilter is not correcting it so I just > > > see HTML source code. I believe I was not > > > even able to save and view this file the hard > > > way. Anybody having similar problems? > > > > > > Chris > > > > Hello Chris, > > > > perhaps it's a multipart message that also contains a text part > > without HTML. > > > > See section 5.5 of the mutt manual. > > > > I have the following in my .muttrc: > > (text messages are preferred) > > > > alternative_order text/enriched text/plain text/html > > > > When I was new to mutt, I had the problem that mutt couldn't find my > > mailcap file. > > > > You can set the path with the "mailcap_path" variable in your .muttrc: > > > > set mailcap_path=~/.mailcap > > > > And don't forget to include "auto_view text/html" in your .muttrc. > > > > This is in my .mailcap: > > text/html; w3m -dump -T text/html %s; copiousoutput > > > > Tschoe, > > Steff > > -- > === > Dr. Christian Seberino > === > SPAWARSYSCEN D02P || (619) 553-2564 > 49330 ELECTRON DR || > SAN DIEGO CA 92152-5451|| [EMAIL PROTECTED] > === -- Sam Roberts <[EMAIL PROTECTED]>
Re: Changing the Mime type of the outgoing message by default?
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 century and get a reader that knows how to wrap text. > > Mail systems unpredictably truncate lines longer than (IIRC) 1023 > characters. So you're likely to have truncated paragraphs and sure to > tick off just about everyone with your arrogant attitude. actually its 1000--998 + crlf. according to the rfc > > If you want to break RFCs get a job with M$, where doing so seems to > be a good career move. uh. okay > > -rex -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: HTML email that is NOT an attachment problem! :(
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 it handles tables so well, and because of a few other neat features. I don't think I have ever received any XML, however, and I have not used lynx very often since I started using w3m, so I can't really comment on the usability, rendering quality or robustness of the latest versions of lynx. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications PGU http://www.spocom.com/users/gjohnson/mutt/ | Spokane, Washington, USA
Re: HTML email that is NOT an attachment problem! :(
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, > > Thanks for reply. I pressed v but then how do I pipe > it to lynx -dump? > > Chris > >
Re: HTML email that is NOT an attachment problem! :(
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 never received a message that w3m couldn't handle. I really like > w3m because it handles tables so well, and because of a few other neat > features. I don't think I have ever received any XML, however, and I > have not used lynx very often since I started using w3m, so I can't > really comment on the usability, rendering quality or robustness of the > latest versions of lynx. lynx works fine with email - it's webpages that I find w3m chokes on occasionally, as well as links - I run them to compare when I'm curious if they can do something plausible with nested tables that look a little ragged in lynx. -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
Re: HTML email that is NOT an attachment problem! :(
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 output. This temporary file is what lynx is showing you in source form. To get lynx to correctly interpret the file as HTML either add "nametemplate=%s.html" to your .mailcap entry (as suggested below) or add the "-force_html" option to lynx. HTH, Mark. On Fri, May 11, 2001 at 07:21:40PM -0700, Dr. Christian Seberino wrote: > > But there is not "file"! The html code is not part of an > attached file but rather the body of the message. > How could a file suffix enter here? > > Chris > > On Fri, May 11, 2001 at 06:21:19PM -0400, Sam Roberts wrote: > > 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 is beginning of an email that is dumping > > > html source even though it looks like lynx is > > > activated... > > > > > > ... > > > > > >"Deborah Warren" <[EMAIL PROTECTED]>, > > >"Jacob A. Langford" <[EMAIL PROTECTED]>, > > >"Ralph Nebiker" <[EMAIL PROTECTED]> > > > Subject: FIE2JIF SITREP 5/11 > > > Date: Fri, 11 May 2001 17:08:17 -0400 > > > > > > [-- Autoview using lynx -dump '/tmp/muttoZiSst' --] > > > > > > > > > > > > > > >
Re: Folder specific TO-Address
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 > > time determining a method to correct that. Heh, no. Doesnt need to be that way. Trust to mail-followup-to / reply-to set by the list (that takes care of the to) and just set your from header. See my muttrc at http://www.hserus.net/muttrc.html for a "list oriented" muttrc -- Suresh Ramasubramanian + Lumber Cartel India - mallet @ cluestick.org + Wallopus Malletus Indigenensis EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
