Re: ansi colors without X
On Thu, Jan 20, 2000 at 03:36:36PM -0700, Harold Oga wrote: :On 03:05 PM 1/20/2000 , Eugene Lee wrote: :>I have the latest version of Mutt on my FreeBSD 3.3 system. It works :>fine, except that color support doesn't seem to work. I don't have X :>on the system. But I continue to get these messages: :> :> Error in /usr/home/eugene/.muttrc, line 2: default: no such color [...] :> color quoted green default [...] :This is a guess, since I've never used FreeBSD 3.3, but maybe your :version of ncurses is too old. I'm not too sure what version of ncurses :that the default color stuff first appeared. Try changing the default to :an actual color in the 3 lines in your .muttrc and see if the errors go away. Following everyone's advice, I installed ncurses-4.2, then rebuilt Mutt to use it. It didn't work, and I still got the same error messages. I then tried Harold's suggestion, replaced "default" with a real color, and it worked fine. This surprised me a bit, because a friend of mine is also running Mutt on his RH Linux box. His is linked to S-lang, but the docs say "default" and "brightdefault" only work if COLORFGBG is defined, and it's not defined on his box. Oh well, the things I learn. Thanks for everyone's tips. :) -- Eugene Lee [EMAIL PROTECTED]
problem with bounce
hi, I have linux installed on my local machine. sendmail is configured with DSsmtp:tagore But when I bounce a message, the recepient gets the mail with broken headers. Example: I am bouncing a mail with headers: - SENT HEADERS - >From smtp Wed Jan 12 12:38 IST 2000 remote from tagore >From [EMAIL PROTECTED] Tue Jan 11 22:55:10 PST 2000 Received: from kmglmail.wipsys.soft.net (kmglmail.wipsys.soft.net [164.164.26.11]) by vayu.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id MAA17486 for <[EMAIL PROTECTED]>; Wed, 12 Jan 2000 12:26:28 +0500 (GMT) Received: from wiprok1mx1.wipro.com ([164.164.90.11]) by kmglmail.wipsys.soft.net (Netscape Messaging Server 3.6) with ESMTP id AAA74F9 for <[EMAIL PROTECTED]>; Wed, 12 Jan 2000 12:26:15 +0530 Received: from daffy.ee.lbl.gov (daffy.ee.lbl.gov [131.243.1.31]) by wiprok1mx1.wipro.com (8.9.3/8.9.3) with ESMTP id OAA14706 for <[EMAIL PROTECTED]>; Wed, 12 Jan 2000 14:55:06 +0530 Received: (from vern@localhost) by daffy.ee.lbl.gov (8.9.2/8.9.2) id WAA24595; Tue, 11 Jan 2000 22:55:10 -0800 (PST) Message-Id: <[EMAIL PROTECTED]> To: Raju K V <[EMAIL PROTECTED]> Subject: Re: converting lex to flex In-reply-to: Your message of Wed, 12 Jan 2000 12:20:03 +0530. Date: Tue, 11 Jan 2000 22:55:10 PST From: Vern Paxson <[EMAIL PROTECTED]> Status: RO Content-Length: 6136 Lines: 258 - SENT HEADERS - The recepient gets a mail with headers like this: - RECEIVED HEADERS - >From [EMAIL PROTECTED] Fri Jan 21 14:45:28 2000 Return-Path: <[EMAIL PROTECTED]> Received: from vayu.wipinfo.soft.net (vayu.wipinfo.soft.net [192.168.200.170]) by canine.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id OAA04835 for <[EMAIL PROTECTED]>; Fri, 21 Jan 2000 14:45:28 +0530 Received: from rajukv.wipinfo.soft.net (IDENT:root@[192.168.205.27]) by vayu.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id OAA11411 for ; Fri, 21 Jan 2000 14:47:27 +0500 (GMT) Received: (from rajukv@localhost) by rajukv.wipinfo.soft.net (8.9.3/8.9.3) id OAA06172 for rajukv@canine; Fri, 21 Jan 2000 14:50:40 +0530 Date: Fri, 21 Jan 2000 14:50:40 +0530 From: Raju K V <[EMAIL PROTECTED]> Message-Id: <[EMAIL PROTECTED]> Status: RO Content-Length: 7319 Lines: 282 >From [EMAIL PROTECTED] Tue Jan 11 22:55:10 PST 2000 Received: from kmglmail.wipsys.soft.net (kmglmail.wipsys.soft.net [164.164.26.11]) by vayu.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id MAA17486 for <[EMAIL PROTECTED]>; Wed, 12 Jan 2000 12:26:28 +0500 (GMT) Received: from wiprok1mx1.wipro.com ([164.164.90.11]) by kmglmail.wipsys.soft.net (Netscape Messaging Server 3.6) with ESMTP id AAA74F9 for <[EMAIL PROTECTED]>; Wed, 12 Jan 2000 12:26:15 +0530 Received: from daffy.ee.lbl.gov (daffy.ee.lbl.gov [131.243.1.31]) by wiprok1mx1.wipro.com (8.9.3/8.9.3) with ESMTP id OAA14706 for <[EMAIL PROTECTED]>; Wed, 12 Jan 2000 14:55:06 +0530 Received: (from vern@localhost) by daffy.ee.lbl.gov (8.9.2/8.9.2) id WAA24595; Tue, 11 Jan 2000 22:55:10 -0800 (PST) Message-Id: <[EMAIL PROTECTED]> To: Raju K V <[EMAIL PROTECTED]> Subject: Re: converting lex to flex In-reply-to: Your message of Wed, 12 Jan 2000 12:20:03 +0530. Date: Tue, 11 Jan 2000 22:55:10 PST From: Vern Paxson <[EMAIL PROTECTED]> Resent-From: [EMAIL PROTECTED] Resent-Date: Fri, 21 Jan 2000 14:50:40 +0530 Resent-To: rajukv@canine - RECEIVED HEADERS - Please notice that the 'From:' has been changed. There is also a space added between the actual headers & the newly added headers. Is there a way to overcome this problem? I can also send the actual messages(sent & received) as attachments if you want. I am using sendmail-8.9.3-15. I am using mutt-1.1.2i Thanks in advance, Raju
Charset in mutt 1.0i
Hi! I have a problem with "charset" variable in mutt. Mutt seems to ignore this variable (I've set it to iso-8859-2), if $LANG environment variable isn't set to "pl_PL", and I'd like to keep it set to "C". Do you have any suggestions ? TIA Siaco. -- Ryszard Łach Internet Designers s.c. http://www.id.pl
Re: Charset in mutt 1.0i
Ryszard Lach <[EMAIL PROTECTED]>: > I have a problem with "charset" variable in mutt. Mutt seems to ignore this > variable (I've set it to iso-8859-2), if $LANG environment variable isn't set to > "pl_PL", and I'd like to keep it set to "C". Do you have any suggestions ? Can you solve this by setting LC_CTYPE? I'm not sure whether LC_CTYPE is supposed to override LANG; man 7 locale and man 3 setlocale seem to contradict each other on this machine ... Edmund
Re: Colour loss when running via an exec command...
On Thu, Jan 20, 2000 at 02:11:40PM -0600, Jamie Novak wrote: [...] > Eterm --trans --shade "40%" -T Mutt -n "Electronic Mail" -e mutt [...] > What happens, though, is that mutt defaults to a monochrome colour > scheme when I open it via an exec like that. (It does the same for rxvt > terms, etc., as well.) > > Does anyone know how to get around this? It's rather annoying. > Any suggestions would be greatly appreciated. Edit your Eterm theme and in the section misc add or modify term_name to say `xterm-color'. (BTW I use (slightly modified) mutt theme that came with Eterm instead of specifying all arguments every time in every menu) Marius Gedminas -- "If it ain't broke, don't fix it." - Bert Lantz
$write_inc had no effect on MH/Maildir mailbox
I found a small problem about $write_inc.
If $write_inc variable is set,
the number of mails be written is printed
when writing the mbox or MMDF mailbox.
But its function does not work on the MH and Maildir mailbox.
It seems that mutt-unstable-2121, the current version of mutt,
has same problem.
The following patch may make it worked.
This patch is for mutt-1.0pre3, but can be apllied to any version.
*** mh.c.orig Fri Jan 21 18:27:56 2000
--- mh.cFri Jan 21 19:56:37 2000
***
*** 736,741
--- 736,744
for (i = 0; i < ctx->msgcount; i++)
{
+ if (!ctx->quiet && WriteInc && ((i % WriteInc) == 0 || i == 1))
+ mutt_message (_("Writing messages... %d"), i);
+
if (ctx->hdrs[i]->deleted)
{
snprintf (path, sizeof (path), "%s/%s", ctx->path, ctx->hdrs[i]->path);
--
NAKATA, Junya
School of Information Science
Japan Advanced Institute of Science and Technology
Email: [EMAIL PROTECTED]
Re: saving mails -> savename + fcc-hook
* Jason Helfman <[EMAIL PROTECTED]> [000120 17:16]: > .. everytime I send a msg, Mutt wants to create a mailbox for it. I suppose you have "savename" set, ie mails to "user@domain" are saved in folder "=user". You might want to unset this or define a fcc-hook to set the folder used for saving the copies: fcc-hook . "=OUT" The single dot always matches so folder "OUT" should be used to save all outgoing mails. Sven -- Sven [EMAIL PROTECTED] using mutt-1.1.2i [000108] and ,, MUTT http://www.mutt.org/ news:comp.mail.mutt (__/'. MUTT http://www.math.fu-berlin.de/~guckes/mutt/ /| |\ MUTT MUTT - *the* mailer for UNIX with color, threading, IMAP+MIME+PGP+POP
Re: Charset in mutt 1.0i
On Fri, 21 Jan 2000, Ryszard Lach wrote: > Hi! > > I have a problem with "charset" variable in mutt. Mutt seems to ignore this > variable (I've set it to iso-8859-2), if $LANG environment variable isn't set to The charset variable only affects the Content-Type header of _sent_ mails. (AFAIK) > "pl_PL", and I'd like to keep it set to "C". Do you have any suggestions ? I use LANG=en_us.ISO-8859-1 as workaround to display the german "o "u "a. Maybe you can use en_US-ISO-8859-2. CU Dirk -- Linux is like a wigwam - no windows, no gates and apache inside!
mailing list
i have no idea why my mail is being fcc'd to the mailing list folder I
am mailing to.? all mail should be going to +sent.
I have specified this in my .muttrc file
-
Jason Helfman Linux Advocate & User
http://www.digitalklown.net/pages/linux.html Playwright/Poet/Lost
"At any given moment, you may find the ticket to the circus that has always been
in your possession."
---
##
## File:$HOME/.muttrc
## Purpose: Setup file for the Mail program "Mutt"
## I am using mutt-1.1.1i now
## which lists 195 configuration variables.
## Last update: Wed Nov 24 12:00:00 MET 1999
## Author: Sven Guckes [EMAIL PROTECTED]
## Availability: This file is available as
## http://www.math.fu-berlin.de/~guckes/mutt/muttrc>
##
## If you read this then please let me know how you like it!
## Send me an email at [EMAIL PROTECTED] - thanks! :-)
##
## Additional Info:
## Sven's pages: http://www.math.fu-berlin.de/~guckes/mutt/
## Current manual: http://www.math.fu-berlin.de/~guckes/mutt/doc/manual.txt
## News/Usenet:comp.mail.mutt (since 980401)
##
## This is new - and you should know about it:
set ignore_list_reply_to # ignore the "Reply-To" lines
# which point back to the mailing list - YES!
## FAQ: Startup mutt with collapsed threads:
## folder-hook . exec collapse-all
## TO show the number of messages in a collapsed thread
## you need to add "%M" to the "index_format", eg:
set index_format="%4C %Z %2M %[!%y%m%d] %-17.17F (%3l) %s"
## NOTE: Please read the comment about "source" at the end of this file!
##
## VARIABLES :
## See http://www.math.fu-berlin.de/~guckes/mutt/mutt.manual.html#variables
## All variables are described with their type, the version number of MUTT
## when they were introduced, and their default value.
## NOTE: The names of variables are defined in "init.c" (struct rc_option).
## The variables pgp and pgp_autosign are only available in mutt-pgp.
##
## Valid variable types are: Boolean, Number, Format_String, String.
## Documentation: http://www.math.fu-berlin.de/~guckes/mutt/manual.html#types
##
##
## Options/Variable settings -
## the manual to mutt-1.1.1i lists 195 options.
## They are all listed here for your convenience.
## Please take a look at the various descriptions
## If you have suggestions for improvements
## then let us know on comp.mail.mutt!
##
## A
# 6.3.1. abort_nosubject
# 6.3.2. abort_unmodified
# 6.3.3. alias_file The file to use for *saving* new aliases
# It's a frequent misconception that this
# file gets automatically sourced - wrong!
set alias_file=~/.mutt.aliases
# 6.3.4. alias_format
# 6.3.5. allow_8bit unset: convert all 8bit data to 7bit before sending.
set allow_8bit
# 6.3.6. alternates list of the users' *personal* addresses
# used by mutt to determine "personal" mail.
# will be set in the file ~/.mutt.personal
# 6.3.7. arrow_cursor
# Affects the display of the folder index.
#set: Show current mail with an arrow ("->")
# *unset: Show current mail with an inverse bar.
unset arrow_cursor
# 6.3.8. ascii_chars
set ascii_chars # set: use ASCII characters to build the thread tree
# 6.3.9. askbcc
# 6.3.10. askcc
# 6.3.11. attach_format
# 6.3.12. attach_sep
# 6.3.13. attach_split
# 6.3.14. attribution
# 6.3.15. autoedit
# 6.3.16. auto_tag
# 6.3.17. beep
# 6.3.18. beep_new
# 6.3.19. charset
# 6.3.20. check_new
# 6.3.21. collapse_unread
# 6.3.22. confirmappend
# 6.3.23. confirmcreate
# 6.3.24. copy
# 6.3.25. date_format
# 6.3.26. default_hook
# 6.3.27. delete
# 6.3.28. dsn_notify
# 6.3.29. dsn_return
# 6.3.30. edit_headers
# 6.3.31. editor
# 6.3.32. escape
# 6.3.33. fast_reply
# 6.3.34. fcc_attach
# 6.3.35. folder
# 6.3.36. folder_format
# 6.3.37. followup_to
# 6.3.38. force_name
# 6.3.39. forward_decode
# 6.3.40. forward_decrypt
# 6.3.41. forward_format
# 6.3.42. forward_quote
# 6.3.43. forward_weed
# 6.3.44. hdrs
# 6.3.45. header
# 6.3.46.
strange imap - sync - exit behavior
Hi, folks -- I'm using 0.95.7i with some patches while I wait for a bug resolution in 1.0 and/or 1.0.1 (working with Sec) and I use imap to connect to a mailbox to prune the spam out before my wife POPs down the contents. I've checked with my SA and confirmed that the imapd has not changed, so I have the famous "I didn't do anything and now it's broken" problem :-) I have previously connected, deleted anything that was spam, synced with '$', and exited with 'x' and had all of the 'N' flag remain. Even if I check a message and find that it isn't spam, I have been able to reset the New flag and then sync and exit. Today I went in to check and saw "Closing mailbox" when I exited. I popped back in and everything, even that which I had not read, was marked as read. I marked each as new, synced, and exited again. I checked again and they were cleared. I eventually had to ftp the mailbox down, open it with mutt the old fashioned way, fix the flags, and then ftp it back up. Any idea what could have changed? Should I try again with a debugging flag on? ## Mutt 0.95.7i (1999-08-17) Copyright (C) 1996-8 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.2.13 [using ncurses 4.2] Compile options: -DOMAIN -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP5 ++HAVE_PGP2 +HAVE_GPG -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS +COMPRESSED SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" ISPELL="/usr/bin/ispell" _PGPPATH="/usr/local/bin/pgp263ia" _PGPV2PATH="/usr/local/bin/pgp263ia" _PGPV3PATH="/usr/local/bin/pgp" To contact the developers, please mail to <[EMAIL PROTECTED]>. Feature patch: condense_pgp 0.95 by Stefan `Sec` Zehl Feature patch: patch-0.00.sec.patchlist.6 (DTG) Feature patch: patch-0.94.13.bj.current_shortcut.1 (DTG) Feature patch: patch-0.95.3.bj.ed_mtime.1 (DTG) Feature patch: patch-0.95.3.hb.save_alias.1 (DTG) Feature patch: patch-0.95.7.rr.compressed.1 (DTG) Feature patch: patch-0.95.bj.noquote_hdr_term.1 (DTG) ## TIA & HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millenium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Colour loss when running via an exec command...
On 01/20, Jean-Sebastien Morisset rearranged the electrons to read: > Try creating a "mutt-color" script with the following content: > > #!/bin/sh > TERM=xterm-color > export TERM > exec mutt $* Thanks!! This took care of the problem beautifully. Thanks, also, to everyone else who replied (including Marius Gedminas, who made me actually look further into using Eterm's themes--I'm still fairly new to using Eterms and always wondered what these .mutt.menu files I've seen other people using are :-) - Jamie PGP signature
PGP error messages
Hey, it's me again. Hopefully this will be my last letter with a problem! :-) 'mutt -v' says : Mutt 1.1.2i (2000-01-08) So I know it should be able to handle PGP without a problem. However, when I define a bunch of PGP settings in my .muttrc file as it says I should be able to, I get the following errors when starting mutt: Error in /home/jmnova3/.muttrc, line 102: pgp_v2: unknown variable Error in /home/jmnova3/.muttrc, line 103: pgp_v2_language: unknown variable Error in /home/jmnova3/.muttrc, line 104: pgp_v2_pubring: unknown variable Error in /home/jmnova3/.muttrc, line 105: pgp_v2_secring: unknown variable Error in /home/jmnova3/.muttrc, line 106: pgp_default_version: unknown variable Error in /home/jmnova3/.muttrc, line 107: pgp_receive_version: unknown variable Error in /home/jmnova3/.muttrc, line 108: pgp_send_version: unknown variable Error in /home/jmnova3/.muttrc, line 109: pgp_key_version: unknown variable source: errors in /home/jmnova3/.muttrc Press any key to continue... Now I *know* these variables work for other people, because I've looked through the example .rc files linked from the mutt.org website. What am I doing wrong? (For the record, however, I can view & sign PGP messages without a problem. It's just the variables that seem to be giving me trouble.) - Jamie
Re: PGP error messages
> Error in /home/jmnova3/.muttrc, line 102: pgp_v2: unknown variable
> Error in /home/jmnova3/.muttrc, line 103: pgp_v2_language: unknown variable
> Error in /home/jmnova3/.muttrc, line 104: pgp_v2_pubring: unknown variable
> Error in /home/jmnova3/.muttrc, line 105: pgp_v2_secring: unknown variable
> Error in /home/jmnova3/.muttrc, line 106: pgp_default_version: unknown variable
> Error in /home/jmnova3/.muttrc, line 107: pgp_receive_version: unknown variable
> Error in /home/jmnova3/.muttrc, line 108: pgp_send_version: unknown variable
> Error in /home/jmnova3/.muttrc, line 109: pgp_key_version: unknown variable
> source: errors in /home/jmnova3/.muttrc
> Press any key to continue...
>
> Now I *know* these variables work for other people, because I've looked
> through the example .rc files linked from the mutt.org website. What am
> I doing wrong?
Now I *know* these variables won't work for this version of mutt because
the pgp/gpg interface changed between 1.0 and 1.1 (or 0.95/0.96).
See doc/PGP-Notes.txt and contrib/{gpg,pgp2,pgp5}.rc, and the usual
funny manual.
sendmail -U
Browsing through sendmail(8) man page I stumbled upon this option: -U Initial (user) submission. This should always be set when called from a user agent such as Mail or exmh and never be set when called by a network delivery agent such as rmail. What does it do and why isn't it used in the default $sendmail value? Just curious. Marius Gedminas -- If two wrongs don't make a right, try three wrongs.
Re: Charset in mutt 1.0i
On Fri, Jan 21, 2000 at 01:02:42PM +0100, Dirk Pirschel wrote: > On Fri, 21 Jan 2000, Ryszard Lach wrote: > > > Hi! > > > > I have a problem with "charset" variable in mutt. Mutt seems to ignore this > > variable (I've set it to iso-8859-2), if $LANG environment variable isn't set to > > The charset variable only affects the Content-Type header of _sent_ > mails. (AFAIK) No, that's what send_charset does that in unstable versions. > > "pl_PL", and I'd like to keep it set to "C". Do you have any suggestions ? > > I use LANG=en_us.ISO-8859-1 as workaround to display the german "o "u "a. > Maybe you can use en_US-ISO-8859-2. I don't use LANG at all (so it defaults to "C", IIUC) but I set my LC_CTYPE to lt_LT.iso-8859-13 and everything works perfectly. BTW I also have charset set to "iso-8859-13" in .muttrc (and I have a couple of macros to change it an load the appropriate font if I encounter an occasional cyrillic mail). AFAIU Mutt does not use locale information for determining charset at all, it just uses it to determine which characters are printable (otherwise it displays them as quotation marks). Marius Gedminas -- Given enough eyeballs all bugs are shallow. -- Eric S. Raymonds, "The Cathedral and the Bazaar"
Re: can't filter sent emails to sent box
Jason Helfman <[EMAIL PROTECTED]> wrote: > > I am very new to mutt, and by emailing back and forth with fellow mutt > users, documentation and the like, I am unable to figure out -- based > on my .muttrc file --- why email I send out want to go to the record > of the name it is sent to...for instance, if i send an email to > [EMAIL PROTECTED] If you are new to Mutt, perhaps you would consider reading its manual. It has a lot of good information about the program. 6.3.156. save_name Type: boolean Default: no This variable controls how copies of outgoing messages are saved. When set, a check is made to see if a mailbox specified by the recipient address exists (this is done by searching for a mailbox in the ``folder'' directory with the username part of the recipient address). If the mailbox exists, the outgoing message will be saved to that mailbox, otherwise the message is saved to the ``record'' mailbox. Also see the ``force_name'' variable. 6.3.43. force_name Type: boolean Default: no This variable is similar to ``save_name'', except that Mutt will store a copy of your outgoing message by the username of the address you are sending to even if that mailbox does not exist. Also see the ``record'' variable. 6.3.146. record Type: path Default: "" This specifies the file into which your outgoing messages should be appended. (This is meant as the primary method for saving a copy of your messages, but another way to do this is using the ``my_hdr'' command to create a Bcc: field with your email address in it.) The value of record is overridden by the ``force_name'' and ``save_name'' variables, and the ``fcc-hook'' command. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
plus signs
In the body of my msgs I have some + signs that have a white box around them. What is this an issue of? - Jason Helfman Linux Advocate & User http://www.digitalklown.net/pages/linux.html Playwright/Poet/Lost "At any given moment, you may find the ticket to the circus that has always been in your possession." ---
Re: plus signs
Jason Helfman <[EMAIL PROTECTED]> wrote: > > In the body of my msgs I have some + signs that have a white box > around them. What is this an issue of? Allow me to read some more from the manual to you, so that you need not send further huge posts to the list: 6.3.75. markers Type: boolean Default: yes Controls the display of wrapped lines in the internal pager. If set, a ``+'' marker is displayed at the beginning of wrapped lines. Also see the ``smart_wrap'' variable. For extra credit, find the "color markers" section in the manual. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: problem with bounce
Raju K V <[EMAIL PROTECTED]> wrote: > > But when I bounce a message, the recepient gets the mail with broken > headers. Example: > > I am bouncing a mail with headers: > - SENT HEADERS - > From smtp Wed Jan 12 12:38 IST 2000 remote from tagore > >From [EMAIL PROTECTED] Tue Jan 11 22:55:10 PST 2000 > Received: from kmglmail.wipsys.soft.net (kmglmail.wipsys.soft.net [164.164.26.11]) The headers in the message, as stored in your mailbox, are wrong. The original envelope separator "From " has been changed to ">From ", which is not a valid header. Apparently, when you bounce this message through sendmail, it notices that this header is wrong, and breaks the headers at that point, then generates totally new headers based on the sender (you). Whatever MDA you are using, is at fault here. It has put the message into your mailbox, with invalid headers. If you fix the MDA, the bounce problem will go away. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: problem with bounce
David DeSimone writes: > Raju K V <[EMAIL PROTECTED]> wrote: > > > > But when I bounce a message, the recepient gets the mail with broken > > headers. Example: > > > > I am bouncing a mail with headers: > > - SENT HEADERS - > > From smtp Wed Jan 12 12:38 IST 2000 remote from tagore > > >From [EMAIL PROTECTED] Tue Jan 11 22:55:10 PST 2000 > > Received: from kmglmail.wipsys.soft.net (kmglmail.wipsys.soft.net [164.164.26.11]) > > > The headers in the message, as stored in your mailbox, are wrong. The > original envelope separator "From " has been changed to ">From ", which > is not a valid header. Apparently, when you bounce this message through > sendmail, it notices that this header is wrong, and breaks the headers > at that point, then generates totally new headers based on the sender > (you). > > Whatever MDA you are using, is at fault here. It has put the message > into your mailbox, with invalid headers. If you fix the MDA, the bounce > problem will go away. Possibly procmail of formail. But although escaping of bogus \nFrom lines is explained in the man pages, I cannot see how this possibly applies to this case. >From [EMAIL PROTECTED] Tue Jan 11 22:55:10 PST 2000
Re: PGP error messages
On 01/21, Lars Hecking rearranged the electrons to read:
> Now I *know* these variables won't work for this version of mutt because
> the pgp/gpg interface changed between 1.0 and 1.1 (or 0.95/0.96).
>
> See doc/PGP-Notes.txt and contrib/{gpg,pgp2,pgp5}.rc, and the usual
> funny manual.
Ugh...Forgive me for assuming the PGP information I was looking at was
current. I just realized it was for a previously-installed version I
had. I usually DO RTFM...Guess I was just reading the wrong FM this
time. :-)
Sorry to add yet another Email for you to sort through. I think I've
got it all sorted out, now. Thanks, again, for the help, guys.
- Jamie
Re: problem with bounce
[lengthy explanation] > I imagine the problem is in the sendmail config, something like this: > > Mlocal, P=/usr/bin/rmail, F=lsDFMAw5:/|@m, S=10/30, R=20/40, > T=DNS/RFC822/X-Unix, > A=rmail -d $u > > This is my particular setting for the "local" MDA, in my sendmail.cf. > If I remember my sendmail configuration rightly, it is the "F" option in > the "F=" section which determines that a "From " header will be added to > the message before it is piped into the MDA. Now, for your case, you > probably have P=/usr/bin/procmail, and since procmail creates its own > message separator, having sendmail add it is superfluous; in that case, > removing the "F" might be the way to handle this. I agree with and understand everything you wrote above, but according my copy of the bat book (1st ed only), the F flag in the F equate means "Need From: in header", i.e. concerns From: and Resent-From: headers, not the "From " mbox separator. > At any rate, since this can be fixed at your site, perhaps it is best to > do that, rather than coerce Mutt to adapt to your broken mail system. Yep.
Re: problem with bounce
Lars Hecking <[EMAIL PROTECTED]> wrote:
>
> > Whatever MDA you are using, is at fault here. It has put the message
> > into your mailbox, with invalid headers. If you fix the MDA, the bounce
> > problem will go away.
>
> Possibly procmail or formail. But although escaping of bogus \nFrom
> lines is explained in the man pages, I cannot see how this possibly
> applies to this case.
Then think on this:
The message is placed in your mailbox looking like this:
From whoever Jan 21 09:10:11
>From some-sender Jan 21 09:10:04
Received by some-mailer at Jan 21 09:09:49
Recevedd
From: some-sender@somewhere
To: whoever
Subject: Test Message
This is a test message.
The first "From " line is the message separator for mbox messges. The
next line is the "original" message separator. A message should NOT
have a message separator until it is being placed for final delivery.
Procmail knows this, so when it tries to put the message into your
mailbox, it escapes the bogus separator and inserts its own. However,
this does not really make an RFC-compliant message. We'll see what
effect this has, later.
So, when Mutt goes to read the message, it wants to separate the message
into headers and body. It does this by scanning down the header section
until a non-compliant line is reached, which is usually the blank line
at the end of the header section. Mutt, you see, is a "smart" mailer
and has seen such bogusly-written messages before. There is a comment
to that effect in the source:
/* some bogus MTAs will quote the original "From " line */
if (mutt_strncmp (">From ", line, 6) == 0)
{
loc = ftell (f);
continue; /* just ignore */
}
So, Mutt ignores that. But that is simply Mutt's behavior. Other
programs touch mail messages, so their behavior may be different.
So anyway, Mutt shows the message correctly. The problem comes when you
bounce the message. During a bounce, the message text, exactly as-is,
will be piped to $sendmail, and sendmail will take that message and send
it to the intended bounced recipient. However, sendmail also knows what
constitutes an RFC-compliant message, but it apparently does NOT have
the above bit of code, like Mutt does... It sees the ">From " line in
the message, and says, "Hmm, that's not RFC-compliant, it must be part
of the message BODY!" And so everything below that is considered text
of the message, and the message essentially has NO headers. Then, since
there are no headers, sendmail automatically comes up with some basic
headers, including yourself as the From: header, and so on.
So, it is the original mis-formatting of the message that is at fault.
I suppose Mutt *could* try to get a little smarter, and not pass such a
bogus message to $sendmail, but really, isn't it best to fix the ROOT
cause of things? Your MDA is misconfigured, and that causes this whole
problem.
I imagine the problem is in the sendmail config, something like this:
Mlocal, P=/usr/bin/rmail, F=lsDFMAw5:/|@m, S=10/30, R=20/40,
T=DNS/RFC822/X-Unix,
A=rmail -d $u
This is my particular setting for the "local" MDA, in my sendmail.cf.
If I remember my sendmail configuration rightly, it is the "F" option in
the "F=" section which determines that a "From " header will be added to
the message before it is piped into the MDA. Now, for your case, you
probably have P=/usr/bin/procmail, and since procmail creates its own
message separator, having sendmail add it is superfluous; in that case,
removing the "F" might be the way to handle this.
At any rate, since this can be fixed at your site, perhaps it is best to
do that, rather than coerce Mutt to adapt to your broken mail system.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
more than one e-mail address
Hello! I have 3 e-mail accounts, all on different systems (my ISP, university and softhome.net) with different usernames. On my home linux machine I again use different username (niki) and I downloaad mail form all 3 e-mail accounts to this local account with fetchmail. So all e-mail ends up in one inbox but that doesnt bother me that much. It is much more convinient than loging in 3 different local accounts to check each mailbox. I was wondering if it's possible to have mutt configured to put apropriate address in From: header ,when replying to a message, that depends on which original address message was received. For example if mail was received on [EMAIL PROTECTED] then put that address in From field in reply, but if it was received on [EMAIL PROTECTED] then put that address in From: header, etc etc. I set up 'alternates' in .muttrc and that part is working. Is there any other more elegant solution for handling multiple e-mail accounts on a single local account? The only idea I have is to use suffix (or prefix) with username on local machine and then have local MTA (exim in my case) filter that mail to apropriate folder depending on the suffix. For example: In .fetchmailrc poll pop.softhome.net with proto POP3 user "nix" there with password "xx" is niki-softhome here poll mail.uni.hr with proto POP3 user "nikola" there with password "xx" is niki-uni here and then setup MTA to deliver that mail to $HOME/.Mail/$suffix Set mailboxes variable in .muttrc, and appropriate send-hook for each mailbox (if that is possible). Thanks, Nikola -- Of all the things I've lost, I miss my mind the most.
Re: problem with bounce
On Fri, Jan 21, 2000 at 03:19:01PM -0600, David DeSimone wrote: > I imagine the problem is in the sendmail config, something like this: > > Mlocal, P=/usr/bin/rmail, F=lsDFMAw5:/|@m, S=10/30, R=20/40, > T=DNS/RFC822/X-Unix, > A=rmail -d $u > > This is my particular setting for the "local" MDA, in my sendmail.cf. > If I remember my sendmail configuration rightly, it is the "F" option in > the "F=" section which determines that a "From " header will be added to > the message before it is piped into the MDA. Now, for your case, you > probably have P=/usr/bin/procmail, and since procmail creates its own > message separator, having sendmail add it is superfluous; in that case, > removing the "F" might be the way to handle this. My /etc/sendmail.cf reads: Mlocal, P=/usr/bin/procmail, F=lsDFMAw5:/|@qShP, S=10/30,R=20/40, T=DNS/RFC822/X-Unix, A=procmail -a $h -d $u but everything works correctly, despite that `F' in `F='. I've never seen any bogus >From lines. Marius Gedminas -- "Only wimps use tape backup: _real_ men just upload their important stuff on ftp, and let the rest of the world mirror it ;)" (Linus Torvalds, about his failing hard drive on linux.cs.helsinki.fi)
Re: problem with bounce
Lars Hecking <[EMAIL PROTECTED]> wrote: > > I agree with and understand everything you wrote above, but according > my copy of the bat book (1st ed only), the F flag in the F equate > means "Need From: in header", i.e. concerns From: and Resent-From: > headers, not the "From " mbox separator. I couldn't find my Bat Book, and my memory is faulty; my apologies. I looked it up on the web: http://www.sendmail.org/~ca/email/doc8.8/op-sh-5.html#sh-5.4 and discovered that for procmail delivery, you probably want the "f" option (The mailer wants a "-f from" flag), and you probably even more want the "n" option (Do not insert a UNIX-style "From" line on the front of the message). -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
expiring messages
Hi What is the muttrc entry to expire incoming mail after say one hour (if that is indeed possible)? -- Eric Smith [EMAIL PROTECTED] 00 27 21 4265311 Where do you think you're going today?
Re: ansi colors without X
install slang (in the ports) and do this: cd /usr/ports/mail/mutt make -dUSE_NCURSES_PORT -dUSE_SLANG install you also need slang for default to work (at least I did) On Fri, Jan 21, 2000 at 12:43:59AM -0800i, Eugene Lee wrote: > On Thu, Jan 20, 2000 at 03:36:36PM -0700, Harold Oga wrote: > :On 03:05 PM 1/20/2000 , Eugene Lee wrote: > :>I have the latest version of Mutt on my FreeBSD 3.3 system. It works > :>fine, except that color support doesn't seem to work. I don't have X > :>on the system. But I continue to get these messages: > :> > :> Error in /usr/home/eugene/.muttrc, line 2: default: no such color > > [...] > > :> color quoted green default > > [...] > -- _ Patrick Seal|"Microsoft isn't evil, they just make <[EMAIL PROTECTED]> | really crappy operating systems." Hyperhost - http://www.hyperhost.net| -Linus Torvalds
Re: more than one e-mail address
Nikola Filipcic <[EMAIL PROTECTED]> wrote on Fri, 21 Jan 2000: > I was wondering if it's possible to have mutt configured to put apropriate address in > From: header ,when replying to a message, that depends on which original address > message was received. Yes, it's called the $reverse_name variable. Look it up in the manual. Alternatively, you can change your From header using send-hooks and set up "my_hdr From: ..." (or, if you're using the dev version, you can do "set from=..." in the hook). This changing only works based on the *destination* address though. You should note that $reverse_name and the 'send-hook ... "my_hdr From: ..."' approach don't work well together, so if you're not using the developement version, you should pick one method or another. > Is there any other more elegant solution for handling multiple e-mail > accounts on a single local account? > The only idea I have is to use suffix (or prefix) with username on local > machine and then have local MTA (exim in my case) filter that mail to > apropriate folder depending on the suffix. That would work too; Mutt supports nicely multiple incoming mail folders. You could have per-folder settings for each of these with a folder-hook, if you'd like. So you have 3 options to choose from, $reverse_name is probably the closest to what you had in mind. Regards, Mikko PS. Please use the address [EMAIL PROTECTED] when posting to the list. -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / 145 = 1! + 4! + 5!
Re: expiring messages
Eric Smith <[EMAIL PROTECTED]> wrote on Sat, 22 Jan 2000: > What is the muttrc entry to expire incoming mail after say one hour (if > that is indeed possible)? It's not possible to do it automatically (except perhaps when entering a folder), but you can create a macro that does something like: D~d >1h (delete all messages which were sent over an hour ago). Then you can do this with a single keypress. Hope this helps, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / Did you know that 7/5 people don't know how to use fractions?
Re: Text substitution
* Jon Walthour wrote on Thu, Jan 20, 2000 at 14:07 -0500: > server, just an IP address. So, if I sendmail to > [EMAIL PROTECTED], it disappears; if I send it to > [EMAIL PROTECTED], it works. Like I said, strange. AFAIK you have to use angle Brackets to skip DNS Lookups, i.e. joeblow@[198.1.2.3] oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.
problems sending mail
when i try to send mail to someone on the same server as myself, i always get amessage bask saying that the "user is unknown". for example, my address is [EMAIL PROTECTED], and when i try to send mail to say, [EMAIL PROTECTED], i get the message above. any suggestions?
