Re: enhanced list support idea
Hi Derrick, Problem : Sometimes a message received via a mailing list, but doesn't mention the list in any of the recipient headers. (eg a member bounced an off-list reply back to the list) Mutt's list-reply function doesn't recognize any lists in that case. Solution (my idea) : For MLMs that include a List-Post: header, I think it would be useful if mutt would (or could) use that to derive the address of the list. I'd just say that this List-Post: header is highly MLM dependent. If you're planning to implement this, you should certainly provide the user a mean to specify the different headers fields which can be used. For instance, set list_regexp=(X-Mailing-List|X-BeenThere|List-Id|List-Post|X-List) My 0.2 eurocents, -- Cedric
Fcc default to domain name
How would I set the default Fcc to the domain name of the recipient, omitting the tld part (.com or whatever). This would also be useful as a default save-hook. -- Eric Smith
Re: bouncing w/ mutt-1.3.28i
On Fri, Jul 12, 2002 at 09:18:21PM -0500, David T-G wrote: One thing I didn't see revisited was your subscription problem. Are you now subscribed? Do you want to be? I've figured it out now. Worked fine from the new address. When you bounce a message, mutt takes the message as it was received by you and hands it back to sendmail with a new addressee so that sendmail can put it on its way. This is just like a .forward file in that sense (though it's done manually, of course); nothing in the message envelope is changed, and new headers are added. So, does mutt add a Resent-To: header or does it not? If it does, there is evidence that this does not work sometimes. I'm trying to lay my hands on such a message. When you resend a message, all of the transit-related headers (Received:) are thrown away, the identification headers (From:) are available to change as necessary, and the body is wrapped in a new envelope. I'm almost certain that it's completely a new message, with the Message-ID: regenerated on your system, too. Does that mean that mutt won't be able to sort it into the correct thread? All you're doing is using the old message as a template for an entirely new message that happens to look very similar (usually). What is it that you used to do, and what is it that you really want to do? I used to bounce mails and I want to bounce mails. Not that I care what actually happens with the mail, but bouncing a message requires two keystrokes (b type new address ret) while resending requires 12 (esce : w q ret t ctrla k type new address ret y). Hm, can I pass keystrokes into vi with a macro? But at the moment it doesn't look like I can continue to use 'bounce' since the list of Received: headers is getting too long with this mail server. You sound as though you've been doing this for a while, so please forgive the basic level of my explanations and questions, No offense taken. I try to avoid fiddling with the mail system as much as possible, so my knowledge of how mail transport works exactly is limited. but 'b'ouncing hasn't changed since I met mutt at 0.88 and I can't imagine, particularly since it also works the same way in elm, that it was *ever* any different. Well, I belive you. What else could have changed to cause my troubles? BTW, I'd like to setup my mail system to send external mails over a different server than internal ones (because our servers are blacklisted). What mailer would you recommend (exim, sendmail, postfix, ...?) I'm currently using exim. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe
Re: bouncing w/ mutt-1.3.28i
Dominik --
...and then Dominik Vogt said...
%
% On Fri, Jul 12, 2002 at 09:18:21PM -0500, David T-G wrote:
% One thing I didn't see revisited was your subscription problem. Are you
% now subscribed? Do you want to be?
%
% I've figured it out now. Worked fine from the new address.
Yay!
%
% When you bounce a message, mutt takes the message as it was received by
% you and hands it back to sendmail with a new addressee so that sendmail
% can put it on its way. This is just like a .forward file in that sense
% (though it's done manually, of course); nothing in the message envelope
% is changed, and new headers are added.
%
% So, does mutt add a Resent-To: header or does it not? If it does,
% there is evidence that this does not work sometimes. I'm trying
% to lay my hands on such a message.
AFAIK it does, but see the explanations on envelopes and headers in a
sub-thread for more info; they speak from knowledge whereas I speak from
gee, I think it works that way :-)
%
% When you resend a message, all of the transit-related headers (Received:)
...
% with the Message-ID: regenerated on your system, too.
%
% Does that mean that mutt won't be able to sort it into the correct
% thread?
I don't think the References: are tossed, but it's a new message and so
it should get a new Message-ID: and so it changes.
%
...
% What is it that you used to do, and what is it that you really want to
% do?
%
% I used to bounce mails and I want to bounce mails. Not that I
OK.
% care what actually happens with the mail, but bouncing a message
% requires two keystrokes (b type new address ret) while
Yep.
% resending requires 12 (esce : w q ret t ctrla
% k type new address ret y). Hm, can I pass keystrokes into
% vi with a macro? But at the moment it doesn't look like I can
There are lots of ways to handle that. You could set your editor to
something else (/bin/true) for the moment. You could still use vi but
temporarily change $editor to vi +wq %s or the like to automatically
save and exit. You could use the recent patch that lets you define an
esc-e editor separate from your regular editor so you don't have to muck
with temporarily changing things at all.
% continue to use 'bounce' since the list of Received: headers is
% getting too long with this mail server.
That's really odd. Your mail server should let a message go through a
million hops if it has to. What about the [admittedly absurd] case of
someone at the tail of a long UUCP connection because he doesn't have
access to a real ISP yet? What about the [slightly less] absurd case of
mail out of a company that allows SMTP mail but strictly enforces some
sort of heirarchical mail server path to better track down offenders?
%
% You sound as though you've been doing this for a while, so please
% forgive the basic level of my explanations and questions,
%
% No offense taken. I try to avoid fiddling with the mail system as
% much as possible, so my knowledge of how mail transport works
% exactly is limited.
Fair enough :-)
%
% but 'b'ouncing
% hasn't changed since I met mutt at 0.88 and I can't imagine, particularly
% since it also works the same way in elm, that it was *ever* any different.
%
% Well, I belive you. What else could have changed to cause my
% troubles?
Sounds like your mail server (the easy answer, of course!).
%
% BTW, I'd like to setup my mail system to send external mails over
% a different server than internal ones (because our servers are
% blacklisted). What mailer would you recommend (exim, sendmail,
% postfix, ...?) I'm currently using exim.
I'm a qmail guy, but all of them have their fans right here on this
list. I think the topic has come up a couple of times somewhat
recently; you might check the archives for various pros and cons.
I do know that qmail is extremely {capable,small,fast,secure}, but
can also be extremely challenging to get to know.
%
% Bye
%
% Dominik ^_^ ^_^
%
% --
% Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382
% Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe
HTH 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.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
msg29651/pgp0.pgp
Description: PGP signature
Re: bouncing w/ mutt-1.3.28i
* David T-G [EMAIL PROTECTED] [2002-07-15 05:58 -0500]: % with the Message-ID: regenerated on your system, too. % % Does that mean that mutt won't be able to sort it into the correct % thread? I don't think the References: are tossed, but it's a new message and so it should get a new Message-ID: and so it changes. The MID header is left unchanged, mutt adds: Resent-From: Nicolas Rachinsky [EMAIL PROTECTED] Resent-Date: Mon, 15 Jul 2002 13:08:43 +0200 Resent-Message-ID: [EMAIL PROTECTED] Resent-To: Nicolas Rachinsky nicolas % continue to use 'bounce' since the list of Received: headers is % getting too long with this mail server. That's really odd. Your mail server should let a message go through a million hops if it has to. What about the [admittedly absurd] case of someone at the tail of a long UUCP connection because he doesn't have access to a real ISP yet? What about the [slightly less] absurd case of mail out of a company that allows SMTP mail but strictly enforces some sort of heirarchical mail server path to better track down offenders? No, not a million. I can't remeber the (default)limit at the moment, but I think it's somwhere between 15 and 200. Nicolas
Re: bouncing w/ mutt-1.3.28i
On Mon, Jul 15, 2002 at 01:12:33PM +0200, Nicolas Rachinsky wrote: * David T-G [EMAIL PROTECTED] [2002-07-15 05:58 -0500]: % with the Message-ID: regenerated on your system, too. % % Does that mean that mutt won't be able to sort it into the correct % thread? I don't think the References: are tossed, but it's a new message and so it should get a new Message-ID: and so it changes. The MID header is left unchanged, mutt adds: Resent-From: Nicolas Rachinsky [EMAIL PROTECTED] Resent-Date: Mon, 15 Jul 2002 13:08:43 +0200 Resent-Message-ID: [EMAIL PROTECTED] Resent-To: Nicolas Rachinsky nicolas Okay, if the Resent-To: header should have been added, something must have gone wrong. This are the headers of one of my bounced messages (bounced to [EMAIL PROTECTED]): snip -- Content-Type: message/rfc822 Content-Disposition: inline X-From-Line: [EMAIL PROTECTED] Tue Jul 09 22:48:30 2002 Return-path: [EMAIL PROTECTED] Envelope-to: [EMAIL PROTECTED] Delivery-date: Tue, 09 Jul 2002 22:48:30 +0400 (removed tons of Received: headers) Date: Tue, 9 Jul 2002 17:17:30 +0200 From: Dominik Vogt [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: test, please ignore Message-ID: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Resent-By: Forwarder [EMAIL PROTECTED] X-Resent-For: [EMAIL PROTECTED] X-Resent-To: [EMAIL PROTECTED], [EMAIL PROTECTED] Precedence: list X-Majordomo: 1.94.jlt7 Sender: uucp [EMAIL PROTECTED] Lines: 17 Xref: AK2614.spb.edu junk:4849 MIME-Version: 1.0 snip -- No Resent-To: header anywhere. Any good explanation for taht? Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe
problems with =?unknown-8bit?b?5Pb8?=
I can't see these letters, they are replaced by a ?. Does anyone know where I have to fix this? Thanks in advance, Manuel --
problems with =?unknown-8bit?b?5Pb8?=
I can't see these letters, they are replaced by a ?. Does anyone know where I have to fix this? Thanks in advance, Manuel --
Re: problems with
On Mon, 15 Jul 2002, Manuel Hendel wrote: I can't see these letters, they are replaced by a ?. Does anyone know where I have to fix this? Does exporting the LANG variable (in ~/.bash_profile) fix this? Eg: export LANG=de_DE ...or something like that. See /usr/lib/locale for more locale values. -- Lee J. Moore [EMAIL PROTECTED] Benefit the community and reply to the list msg29656/pgp0.pgp Description: PGP signature
Re: problems with äöü
Try searching the archives for Umlaut
--lpr
On Mon, 15 Jul 2002, Lee J. Moore wrote:
On Mon, 15 Jul 2002, Manuel Hendel wrote:
I can't see these letters, they are replaced by a ?. Does anyone
know where I have to fix this?
Does exporting the LANG variable (in ~/.bash_profile) fix this?
Eg:
export LANG=de_DE
...or something like that. See /usr/lib/locale for more locale
values.
--
Lukas Ruf
http://www.lpr.chhttp://www.maremma.ch
http://www.{{topsy,nodeos}.net,{promethos,netbeast}.org}
Re: from, realname, my_hdr From:
On Sun, Jul 14, 2002 at 10:08:47PM -0500, Derrick 'dman' Hudson wrote: On Sun, Jul 14, 2002 at 09:37:03PM -0400, Daniel J Peng wrote: | I just installed Debian woody with Mutt 1.3.28i, and I've discovered a | puzzling behavior that wasn't in the Mutt that came with Mandrake 8.0 | nor any other Mutt I've ever used. I made a simple muttrc with just | | set from=[EMAIL PROTECTED] | set realname=Daniel J. Peng | | Now I expected that when I started writing an email in Mutt, Mutt | would construct a default From header consisting of my email and | realname, but instead the From header is completely blank. What happens if you add set use_from to it? Hrm.. That works. Thanks!! When was this option added? I haven't seen it in the ChangeLog.. | If I type :set from or :set realname, my email and realname do | appear properly. That's odd. Well, what I meant is that my email and realname appear in the status line as from=[EMAIL PROTECTED] and realname=Daniel J. Peng -- I do not find in orthodox Christianity one redeeming feature. -- Thomas Jefferson Linux peng 2.4.18-686 #1 Sun Apr 14 11:32:47 EST 2002 i686 unknown 08:17:58 up 1 day, 4:03, 3 users, load average: 0.06, 0.04, 0.01
Re: problems with ???
On Mon, Jul 15, 2002 at 12:46:29PM +0100, Lee J. Moore wrote: Does exporting the LANG variable (in ~/.bash_profile) fix this? Eg: export LANG=de_DE ...or something like that. See /usr/lib/locale for more locale values. No it's getting more worse. I did a export LANG=de_DE before that I could see the aöü I wrote but not the one in your reply. Now I can't see either. manuel --
Re: problems with äöü
On Mon, Jul 15, 2002 at 02:07:45PM +0200, Lukas Ruf wrote: Try searching the archives for Umlaut Thanks, I found the right answers. It's working now. manuel -- The best and most beautiful things in the world cannot be seen or even touched. They must be felt.
Re: bouncing w/ mutt-1.3.28i
* Dominik Vogt [EMAIL PROTECTED] [2002-07-15 13:33 +0200]: On Mon, Jul 15, 2002 at 01:12:33PM +0200, Nicolas Rachinsky wrote: * David T-G [EMAIL PROTECTED] [2002-07-15 05:58 -0500]: % with the Message-ID: regenerated on your system, too. % % Does that mean that mutt won't be able to sort it into the correct % thread? I don't think the References: are tossed, but it's a new message and so it should get a new Message-ID: and so it changes. The MID header is left unchanged, mutt adds: Resent-From: Nicolas Rachinsky [EMAIL PROTECTED] Resent-Date: Mon, 15 Jul 2002 13:08:43 +0200 Resent-Message-ID: [EMAIL PROTECTED] Resent-To: Nicolas Rachinsky nicolas Okay, if the Resent-To: header should have been added, something must have gone wrong. This are the headers of one of my bounced messages (bounced to [EMAIL PROTECTED]): snip -- snip -- No Resent-To: header anywhere. Any good explanation for taht? I just tried. Either Puretec or gmx removes them. If I bounce to a local address (touching only localhost), they stay, if I bounce via puretec and GMX, they are removed. I'm sorry, but at the moment I've n time to investigate further. Nicolas
Re: problems with äöü
* Manuel Hendel [EMAIL PROTECTED] [07-15-02 07:38]: On Mon, Jul 15, 2002 at 02:07:45PM +0200, Lukas Ruf wrote: Try searching the archives for Umlaut Thanks, I found the right answers. It's working now. It would really be nice for the other lurkers in the list for you to post the solution. Afterall, think of the number of additional posts that would be required for everyone to solve their own individual problems instead of accomplishing this by merely reading your success story. tks for your expected cooperation and consideration. missing you Sven -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org
Re: enhanced list support idea
Hi, * Derrick 'dman' Hudson [02-07-14 03:11:36 +0200] wrote: Problem : Sometimes a message received via a mailing list, but doesn't mention the list in any of the recipient headers. (eg a member bounced an off-list reply back to the list) Mutt's list-reply function doesn't recognize any lists in that case. These are BCCs to lists which is really bad. If someone BCCs a mail to a list he/she should write a few words why the original receipent doesn't need to know why it's going to a list, too. Anyway, how often does that happen and is it worth to spent time on working around this? Solution (my idea) : For MLMs that include a List-Post: header, I think it would be useful if mutt would (or could) use that to derive the address of the list. See Cedric's answer. There's an RfC specifying those headers and I've only seen Mailman adding them. It could be difficult to parse them. I can think of several ways of handling this -- 1) use List-Post: by default. Doesn't require setting 'lists'. 2) use List-Post: if no 'lists'/'subscribe' addresses are found using current methods 3) use List-Post: in addition to current method 4) a configuration option to choose from the above. In which form of reply do you want the address to be used? Normal reply, group reply or list reply? This is really important since I don't believe anybody does a BCC to a list without purpose. What do you do if the Reply-To: and Mail-Followup-To: headers don't mention the list, too? If the sender doesn't want answers to go to the list, too, a user may run into trouble by accidently sending a reply to the list. Do people think this is a good idea? Generally, yes since there's an RfC for those headers. But on the other hand, there're already 5 headers it has to take care of with the different reply methods: From:, To:, Cc:, Reply-To: and Mail-Followup-To:. The current reply behaviour has to be adjusted by giving more details than your 3 methods, I think. Can it be added to the wishlist? If you want to do, just use flea(1) to report a bug with a severity of 'whishlist'. bye, Rocco
reverse_name and send-hook
I just posted this to comp.mail.mutt but I don't think all that many people read the newsgroup, especially the developers. I'm doing some tricky things with send-hooks to set the From: and Reply-To: fields based on the outgoing email address (mainly for mailing lists). This works great, but it means I also need the following two lines: send-hook '.' 'unmy_hdr Reply-To:' send-hook '.' 'unmy_hdr From:' In addition, I have a similar pair of lines (which come after the lines above but before all the send-hooks for mailing lists) which set the From: and Reply-To: to a reflector when sending mail outside my organization. Given that setup, essentially every mail to any address outside my organization gets a custom From: and Reply-To: field. The problem is that I want reverse_name to supersede all send-hooks. If I send something to a mailing list with a particular address and receive a personal reply from someone, I want my reply to be sent out with the same address I use to send to the mailing list. This is what reverse_name is all about. Unfortunately, the person I am sending to will almost certainly be outside my organization and, therefore, match the send-hooks that set the fields to the reflector, overriding what reverse_name would have done for me. I can't find anything in the documentation to fix this. I suppose the simplest thing would be a ~something which would match if reverse_name had set something, but no such thing seems to exist. Any ideas? --Greg
Re: Exploit.IFrame.FileDownload virus??
On Mon, Jul 15, 2002 at 10:57:42AM -0500, Rich wrote: According to F-Secure Web site, this is a virus that exploits a flaw in Internet Explorer, and by extension mail readers that use it, such as Outlook. No surprise there! The only surprise to me is that 250k infected file which appeared in my c:/tmp. What kind of things does Mutt park there, and where could that big file have come from?? Surely Mutt would not have uncompressed anything without telling me...? There is a new variant of a virus called Frethem.K that sends a text file and file called decrypt-password.exe. This virus exploits IE and Outlooks function to be able to run the executable just when the message is viewed. There should have been another attatchment with you mail. We just started getting hit with it at my work this morning. You can check out http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_FRETHEM.K to read more about it. Maybe the 250k file in c:\tmp was the attachment? Does Mutt cache such things in the TMPDIR? Tom -- Dr. Thomas Baker[EMAIL PROTECTED] Institutszentrum Schloss Birlinghoven mobile +49-171-408-5784 Fraunhofer-Gesellschaft work +49-30-8109-9027 53754 Sankt Augustin, Germanyfax +49-2241-144-1408
Re: problems with äöü
Hi, what's send_charset set to? I have set send_charset=us-ascii:iso-8559-1:iso-8559-15:utf-8 so mutt will use the most minimal charset needed. Your mail is us-ascii, so high chararcters are dropped. Ciao, Viktor -- Viktor Rosenfeld WWW: http://www.informatik.hu-berlin.de/~rosenfel/ msg29673/pgp0.pgp Description: PGP signature
Re: Fcc default to domain name
Eric -- ...and then Eric Smith said... % % How would I set the default Fcc to the domain name of the % recipient, omitting the tld part (.com or whatever). % This would also be useful as a default save-hook. You'd have to use DGC's fmtpipe patch and write a little script to handle it. I have fcc-save-hook . $HOME/.mutt/fcc-save-pipe.sh %_%O | in my .mutt/muttrc file and the script, a very basic example, is attached to get you started. % % -- % Eric Smith :-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.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! #!/bin/sh #set -x ### # quick hack to catch addresses and see where to put the file # leave all of the fcc-save-hook logic in muttrc and then pass this # %O thanks to the fmtpipe patch and we'll strip from there # someday we might get clever enough to move all of the logic in HERE # and then handle the problem of # fcc-save-hook bob =Work/%O # fcc-save-hook sue =Play/%O # To: bob, sue == =Play/bob (ouch!) # but let's take one thing at a time... # how to suppress newline? if [ `echo -n foo` = -n foo ] ; then ECHOC=\c ; else ECHON=-n ; fi case $1 in *-dated-* ) # tmda dated addresses echo $ECHON =$1$ECHOC | sed s/-dated.*// ;; choice-consulting ) # my fcc-save-hooks should do this... echo $ECHON =F.choice$ECHOC ;; * ) # everything else echo $ECHON =$*$ECHOC | tr ' ' '_'# debugging, but just in case ;; esac msg29674/pgp0.pgp Description: PGP signature
Re: problems with äöü
Hi, * Viktor Rosenfeld [02-07-15 21:11:57 +0200] wrote: Your mail is us-ascii, so high chararcters are dropped. There aren't umlauts in the body, they appear in the header. For the body someone just needs a character set and an encoding. Headers may not contain 8bit characters but have to be clean 7bit. Thus, any non-7bit-stuff in headers has to be encoded, see RfC 2047. The question mark in his mail is an ordinary question mark (ascii: 63, hex: 0x3F). bye, Rocco [just to clear this up]
Re: About outgoing mail
I've successfully switched from XIMIAN Evolution to mutt. I would say - this is my _real_evolution :) Thanks for all your help, folks ! Have a nice time, - Ivo On Sun, Jul 14, 2002 at 03:56:11PM +0200, Thorsten Haude wrote: Hi, * eim [EMAIL PROTECTED] [02-07-14 15:14]: I have three mail adresses (profiles) so I want to filter my outgoing mail, written by one of the three profiles in an apropiate mbox folder for the given profile. Eg: If I write a mail with [EMAIL PROTECTED] is it possible to record this sent mail not in the default record mbox but in a different /sent/eim mbox ? And the same for [EMAIL PROTECTED] and [EMAIL PROTECTED] I change my address for each mailing list, so this may be a good start: send-hook '~t [EMAIL PROTECTED]' 'my_hdr From: [EMAIL PROTECTED]' You should be able to replace this with a hook on your own. Untested: send-hook '~f [EMAIL PROTECTED]' 'set record=/sent/eim' You should add default hooks if you want to keeo the default behavior for any setting. send-hook . 'set record=default' Thorsten -- Politik kann man in diesem Lande definieren als die Durchsetzung wirtschaftlicher Zwecke mit Hilfe der Gesetzgebung. - Kurt Tucholsky -- »« »« »« »« »« »« »« »« »« »« »« »« »« »« »« Ivo Marino[EMAIL PROTECTED] UN*X Developer, running Debian GNU/Linux irc.OpenProjects.net #debian http://eimbox.org/~eim http://eimbox.org »« »« »« »« »« »« »« »« »« »« »« »« »« »« »«
Re: reverse_name and send-hook
Gregory Seidman ([EMAIL PROTECTED]) muttered: I'm doing some tricky things with send-hooks to set the From: and Reply-To: fields based on the outgoing email address (mainly for mailing lists). This works great, but it means I also need the following two lines: send-hook '.' 'unmy_hdr Reply-To:' send-hook '.' 'unmy_hdr From:' In addition, I have a similar pair of lines (which come after the lines above but before all the send-hooks for mailing lists) which set the From: and Reply-To: to a reflector when sending mail outside my organization. Given that setup, essentially every mail to any address outside my organization gets a custom From: and Reply-To: field. The problem is that I want reverse_name to supersede all send-hooks. If I send something to a mailing list with a particular address and receive a personal reply from someone, I want my reply to be sent out with the same address I use to send to the mailing list. This is what reverse_name is all about. Unfortunately, the person I am sending to will almost certainly be outside my organization and, therefore, match the send-hooks that set the fields to the reflector, overriding what reverse_name would have done for me. I can't find anything in the documentation to fix this. I suppose the simplest thing would be a ~something which would match if reverse_name had set something, but no such thing seems to exist. I have send-hooks which set a special From: for some recipients, too. I also have a default send-hooks unsetting my_hdr From: and I have $reverse_name set - works like charm. Please post your setup since I figure it's not mutt to blame here. To give you an example: set alternates = (Michael.Tatge|michael_tatge) set realname=Michael Tatge set from=[EMAIL PROTECTED] set use_from# create From: Header set reverse_name# use given To: as From: when # replying set envelope_from ## send-hooks send-hook . 'unmy_hdr From:' # If sending to localhost or LAN: send-hook '(~t knecht | ~t mydomain | ~t localhost)' \ 'my_hdr From: Michael Tatge [EMAIL PROTECTED]' HTH, Michael -- We all know Linux is great...it does infinite loops in 5 seconds. (Linus Torvalds about the superiority of Linux on the Amterdam Linux Symposium) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
search-next annoyance
hi there, i'm getting pretty annoyed by the behavior of search-next; this is how i use mutt pretty often, and it doesn't exactly help to make it easier: starting in index: search~b patternenter display-message searchpatternenter exit search-next display-message search-next at this moment, instead of just jumping to the next match, mutt prompts me for the pattern. it's obviously trying to be helpful, but in fact does just the opposite. i just want it to do what i told it, which is search for the next match, not create a new search. is there a knob i've overlooked? i'm running 1.5.1i, but iirc it behaved this way since i started using it (which isn't a terribly long period): 1.2.5i, couple of 1.3.2x revisions, one 1.4.x iirc (just a few days), and now 1.5.1i thanks -- FreeBSD 4.6-STABLE 9:46PM up 2 days, 12 hrs, 4 users, load averages: 0.12, 0.03, 0.01
SpamAssassin
I just wanted to give another 1000 thumbs up for SpamAssassin. It plain rocks. I was able to take everything out of my procmailrc except for my list filters and stuff to /dev/null, and it really does take care of everything. My procmailrc is a fraction of the size, and so muich cleaner. -Ken
Re: SpamAssassin
On 07-15-2002 at 16:13 EDT, Ken Weingold [EMAIL PROTECTED] wrote: I just wanted to give another 1000 thumbs up for SpamAssassin. It Hmmm, offtopic, I believe. -- David Collantes - http://www.bus.ucf.edu/david/ College of Business Administration, University of Central Florida Success is never final. Failure is never fatal. It is courage that counts
Re: SpamAssassin
Don't forget to mention that it consumes less resources that way ,-) --lpr
Viewing both text and image
I'm on a list where most of the traffic consists of a paragraph or two of text and an accompanying chart as an image attachment. I really need to be able to see the image as I read the text, and it'd be nice to be able to do that within Mutt. I haven't figured out how to get the image to xv without going into the ``v'' attachment menu, which hides the text part of the mail. Is there a way to view two attachments simultaneously, or some other trick to do this job? I tried tagging both the text and the image in the attachment menu and doing ;enter but that only selected the one attachment with the cursor on it. TIA, Jim
Re: SpamAssassin
On Mon, Jul 15, 2002, David Collantes wrote: On 07-15-2002 at 16:13 EDT, Ken Weingold [EMAIL PROTECTED] wrote: I just wanted to give another 1000 thumbs up for SpamAssassin. It Hmmm, offtopic, I believe. I don't think so. It's been a topic of much discussion on this list. -Ken
Re: Wrong Signature with GPG - gpg.rc
Hello Thorsten, On Thursday, July 11, 2002 at 11:24:36 PM +0200, Thorsten Haude wrote: [-- PGP output follows (current time: Don 11 Jul 2002 23:06:04 CEST) --] gpg: Warnung: Sensible Daten könnten auf Platte ausgelagert werden. gpg: Unterschrift vom Son 09 Jun 2002 19:12:09 CEST, DSA Schlüssel ID 7B9F4700 gpg: FALSCHE Unterschrift von David T-G [EMAIL PROTECTED] [-- Ende der PGP-Ausgabe --] Found this one list message, and it verifies correctly here. Please copy it to a temporary mailbox, gzip it and send it to me privately attached. I also see another error, where Mutt displays an empty line between the (correct) GPG output and the marker: '[-- Ende der PGP-Ausgabe --]' and won't verify the mail. Happens only, but always, with traditional PGP? Then setting $pgp_good_sign correctly should solve it. Otherwise, try the wrapper script given in [EMAIL PROTECTED] some monthes ago. Bye!Alain.
Re: Mail lists rejecting attachments
Hi Ray, On Monday, July 1, 2002 at 2:51:32 PM -0700, Ray wrote: One of the mailing lists that I am subscribed to has recently started rejecting all of my posts and complaining that attachments are not allowed. I'm just sending plain old text but presumably the mail list software doesn't like the mime related headers. Perhaps the unnecessary Content-Disposition: inline field Mutt insists to set in simple mails? Mutt should not announce default values. Try it by removing this line before sending to the said list, perhaps with a wrapper script to $sendmail. Bye!Alain.
Display in 'To:' in 'sent' folder only...
I use mutt 1.3.28 (the Debian package). When viewing the list of messages in my 'sent' mailbox (where I copy my sent messages), it displays the 'From:' line. This is not very useful, since I already know that all messages in this mailbox are from me. This has been happening ever since I switch from mutt 1.3.20. Is there a way that I can get it to revert to the previous behavior? I couldn't find anything in the manual about this, specifically. To illustrate, here is a sample sent mailbox. I upgraded to 1.3.28 after sending message 3 and before 4. Even now, under 1.3.28, the messages are displayed like this (messages written before the upgrade are shown with the 'To:' line). 1 Jan 01 Bob ( 23) In order to have your advice... 2 Jan 01 Cats ( 48) Whose base are belong to whom? 3 Jan 02 Thaddeus ( 34) That jazz singer... 4 Jan 03 Dhruva B. Reddy ( 23) wzup 5 Jan 04 Dhruva B. Reddy ( 64) In order to have your advice... 6 Jan 11 Dhruva B. Reddy ( 48) Please, I really do need your advice! ... Thanks, Dhruva
Re: Viewing both text and image
On Mon, Jul 15, 2002 at 01:41:57PM -0700, Jim Osborn wrote: I'm on a list where most of the traffic consists of a paragraph or two of text and an accompanying chart as an image attachment. I really need to be able to see the image as I read the text, and it'd be nice to be able to do that within Mutt. I haven't figured out how to get the image to xv without going into the ``v'' attachment menu, which hides the text part of the mail. The way I handle this is to use a mailcap entry for image/* that runs xv in the background. Then I can launch xv from the attachment menu and immediately return to reading the message text while still viewing the image. Here's my mailcap entry: image/*; mutt_bgrun xv %s; test=RunningX A simpler approach would be to just use something like this: image/*; xv %s sleep 5 where the sleep time is set to give xv enough time to load the image before mutt overwrites it. You can get mutt_bgrun from my web page, http://www.spocom.com/users/gjohnson/mutt/mutt_bgrun HTH, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
Re: Display in 'To:' in 'sent' folder only...
On 07/15/02 14:55 -0600, Dhruva B. Reddy wrote: I use mutt 1.3.28 (the Debian package). When viewing the list of messages in my 'sent' mailbox (where I copy my sent messages), it displays the 'From:' line. This is not very useful, since I already know that all messages in this mailbox are from me. This has been happening ever since I switch from mutt 1.3.20. Is there a way that I can get it to revert to the previous behavior? I couldn't find anything in the manual about this, specifically. I do what you're seeking with a folder hook. My ~/.muttrc includes: folder-hook outbox 'set index_format=%4C %Z %d %-20.20t (%3l) %s' which produces: 575 07/07/02 14:54 -0400 To Joe Foo( 11) New Red Hat Beta Announcement See the manual for index_format to suit your needs. John
Re: Exploit.IFrame.FileDownload virus??
On Mon, Jul 15, 2002 at 04:56:04PM +0200 I heard the voice of Thomas Baker, and lo! it spake thus: saying Your password is 12zxjkjl123kjl12jz. But the size of each of the messages, according to Mutt, was 65k. that use it, such as Outlook. No surprise there! The only surprise to me is that 250k infected file which appeared P'raps it's the size difference that's kicking you. Are you sure that the message was 65k bytes, not 65k lines? -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: Wrong Signature with GPG - gpg.rc
Hi, * Alain Bench [02-07-15 23:15:53 +0200] wrote: On Thursday, July 11, 2002 at 11:24:36 PM +0200, Thorsten Haude wrote: I also see another error, where Mutt displays an empty line between the (correct) GPG output and the marker: '[-- Ende der PGP-Ausgabe --]' and won't verify the mail. Happens only, but always, with traditional PGP? Then setting $pgp_good_sign correctly should solve it. I was pointed to bug #856 which makes mutt think a signature is bad if $pgp_good_sign didn't match. But it cannot match if it is empty (other regexp implementations return a match of an empty regexp against a non-empty string; mutt doesn't). This only affects $pgp_check_traditional which should be fixed by the attached patch (not by me and untested but it made into the debian package for mutt). The bug report was rejected with the hint to set $pgp_good_sign correctly. But IMO it should work without setting it, too. bye, Rocco --- pgp.c-orig Sun Nov 25 15:09:03 2001 +++ pgp.c Sun Nov 25 15:09:08 2001 -384,9 +384,13 rc = pgp_copy_checksig (pgperr, s-fpout); if (rc == 0) have_any_sigs = 1; - if (rc || rv) + /* Sig is bad if gpg_good_sign-pattern did not match || + * pgp_decode_command returned not 0 + * Sig _is_ correct if gpg_good_sign= pgp_decode_command + * returned 0 */ + if (rc==-1 || rv) maybe_goodsig = 0; } safe_fclose (pgperr);
Re: Display in 'To:' in 'sent' folder only...
John Dhruva -- ...and then John P Verel said... % % On 07/15/02 14:55 -0600, Dhruva B. Reddy wrote: ... % messages in my 'sent' mailbox (where I copy my sent messages), it % displays the 'From:' line. This is not very useful, since I already ... % % I do what you're seeking with a folder hook. My ~/.muttrc includes: % % folder-hook outbox 'set index_format=%4C %Z %d %-20.20t (%3l) %s' You can get that with %F instead of %Z (and no folder-hook settings) as long as your $alternates is set correctly. My guess is that $alternates got mangled somehow. HTH 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.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg29691/pgp0.pgp Description: PGP signature
Re: Display in 'To:' in 'sent' folder only...
I tried this, along with: reset alternates and: set alternates= in my local .muttrc file. But my 'sent' mailbox still shows the 'From:' line. On Mon, 15 Jul 2002 at 16:39:43 -0500, David T-G soliloquized thusly: John Dhruva -- ...and then John P Verel said... % % On 07/15/02 14:55 -0600, Dhruva B. Reddy wrote: ... % messages in my 'sent' mailbox (where I copy my sent messages), it % displays the 'From:' line. This is not very useful, since I already ... % % I do what you're seeking with a folder hook. My ~/.muttrc includes: % % folder-hook outbox 'set index_format=%4C %Z %d %-20.20t (%3l) %s' You can get that with %F instead of %Z (and no folder-hook settings) as long as your $alternates is set correctly. My guess is that $alternates got mangled somehow.
Re: Display in 'To:' in 'sent' folder only...
This seems to do what I want. Thanks, John. On Mon, 15 Jul 2002 at 17:26:23 -0400, John P Verel soliloquized thusly: On 07/15/02 14:55 -0600, Dhruva B. Reddy wrote: I use mutt 1.3.28 (the Debian package). When viewing the list of messages in my 'sent' mailbox (where I copy my sent messages), it displays the 'From:' line. This is not very useful, since I already know that all messages in this mailbox are from me. This has been happening ever since I switch from mutt 1.3.20. Is there a way that I can get it to revert to the previous behavior? I couldn't find anything in the manual about this, specifically. I do what you're seeking with a folder hook. My ~/.muttrc includes: folder-hook outbox 'set index_format=%4C %Z %d %-20.20t (%3l) %s' which produces: 575 07/07/02 14:54 -0400 To Joe Foo( 11) New Red Hat Beta Announcement See the manual for index_format to suit your needs. John
Re: Display in 'To:' in 'sent' folder only...
I spoke too soon--it works the same for me when I switch to the 'sent' mailbox, but then I get the same behavior when I switch back to 'inbox', i.e., it shows the 'To:' line. On Mon, 15 Jul 2002 at 17:26:23 -0400, John P Verel soliloquized thusly: On 07/15/02 14:55 -0600, Dhruva B. Reddy wrote: I use mutt 1.3.28 (the Debian package). When viewing the list of messages in my 'sent' mailbox (where I copy my sent messages), it displays the 'From:' line. This is not very useful, since I already know that all messages in this mailbox are from me. This has been happening ever since I switch from mutt 1.3.20. Is there a way that I can get it to revert to the previous behavior? I couldn't find anything in the manual about this, specifically. I do what you're seeking with a folder hook. My ~/.muttrc includes: folder-hook outbox 'set index_format=%4C %Z %d %-20.20t (%3l) %s' which produces: 575 07/07/02 14:54 -0400 To Joe Foo( 11) New Red Hat Beta Announcement See the manual for index_format to suit your needs. John
Re: Display in 'To:' in 'sent' folder only...
Hi, * Dhruva B. Reddy [02-07-16 00:10:30 +0200] wrote: This seems to do what I want. Thanks, John. Good. And: how did you reply to the message? Your mail shows neither an In-Reply-To: nor a References: header, i.e. it breaks threading which mutt usally (generallly?) _not_ does. bye, Rocco
Re: reverse_name and send-hook
Michael Tatge sez: } Gregory Seidman ([EMAIL PROTECTED]) muttered: } I'm doing some tricky things with send-hooks to set the From: and Reply-To: } fields based on the outgoing email address (mainly for mailing lists). This } works great, but it means I also need the following two lines: } } send-hook '.' 'unmy_hdr Reply-To:' } send-hook '.' 'unmy_hdr From:' } } In addition, I have a similar pair of lines (which come after the lines } above but before all the send-hooks for mailing lists) which set the From: } and Reply-To: to a reflector when sending mail outside my organization. [...] } I have send-hooks which set a special From: for some recipients, too. } I also have a default send-hooks unsetting my_hdr From: and I have } $reverse_name set - works like charm. } Please post your setup since I figure it's not mutt to blame here. } } To give you an example: [...] The crucial difference is the reflector. I have the following: send-hook '((~f gss) | (~f [EMAIL PROTECTED])) (~C @)' 'my_hdr Reply-To: [EMAIL PROTECTED]' send-hook '((~f gss) | (~f [EMAIL PROTECTED])) (~C @)' 'my_hdr From: Gregory Seidman [EMAIL PROTECTED]' (Note the the NOSPAM is simply to avoid email from spammers scraping the archives.) This basically says that anything coming from me and being sent to any address with an @ in it (i.e. not on the local cluster) should set the Reply-To and From fields. It looks like the solution may be to set $from to the reflector and use a hook to set From to the local address for local mail. Is there any other way? I'd *really* like a pattern for whether reverse_name has found something or not. } HTH, } Michael --Greg
Re: Display in 'To:' in 'sent' folder only...
Dhruva -- You should always keep the list in the loop; you're more likely to get an answer that way :-) ...and then Dhruva B. Reddy said... % % I tried this, along with: % % reset alternates % % and: % % set alternates= % % in my local .muttrc file. But my 'sent' mailbox still shows the 'From:' line. Well, did you try set alternates=[EMAIL PROTECTED] yet? HTH 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.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg29697/pgp0.pgp Description: PGP signature
Re: Display in 'To:' in 'sent' folder only...
For that message I hit 'r' (reply to sender). For this one I hit 'g' (reply to all). On Tue, 16 Jul 2002 at 00:14:48 +0200, Rocco Rutte soliloquized thusly: Hi, * Dhruva B. Reddy [02-07-16 00:10:30 +0200] wrote: This seems to do what I want. Thanks, John. Good. And: how did you reply to the message? Your mail shows neither an In-Reply-To: nor a References: header, i.e. it breaks threading which mutt usally (generallly?) _not_ does. bye, Rocco
Re: Display in 'To:' in 'sent' folder only...
Hi, * Dhruva B. Reddy [02-07-16 00:17:11 +0200] wrote: I spoke too soon--it works the same for me when I switch to the 'sent' mailbox, but then I get the same behavior when I switch back to 'inbox', i.e., it shows the 'To:' line. Correct. You need two folder-hooks to do it. One for all folders (showing the From:) and for your sent-folder: folder-hook . 'set index_format=... %f ...' folder-hook +sent 'set index_format=... %t ...' ...or you just set up $alternates to match all your addresses so that you can just use: set index_format=... %F ... bye, Rocco
Re: Display in 'To:' in 'sent' folder only...
Interesting. On this list, I do not include the 'In-Reply-To:' field unless I hit 'g'. I will remember this. On Tue, 16 Jul 2002 at 00:14:48 +0200, Rocco Rutte soliloquized thusly: Hi, * Dhruva B. Reddy [02-07-16 00:10:30 +0200] wrote: This seems to do what I want. Thanks, John. Good. And: how did you reply to the message? Your mail shows neither an In-Reply-To: nor a References: header, i.e. it breaks threading which mutt usally (generallly?) _not_ does. bye, Rocco
Re: Display in 'To:' in 'sent' folder only...
As suggested by David, I set 'alternates' to my e-mail address and that has the desired effect. Thank you all for your responses! Dhruva On Tue, 16 Jul 2002 at 00:21:06 +0200, Rocco Rutte soliloquized thusly: Hi, * Dhruva B. Reddy [02-07-16 00:17:11 +0200] wrote: I spoke too soon--it works the same for me when I switch to the 'sent' mailbox, but then I get the same behavior when I switch back to 'inbox', i.e., it shows the 'To:' line. Correct. You need two folder-hooks to do it. One for all folders (showing the From:) and for your sent-folder: folder-hook . 'set index_format=... %f ...' folder-hook +sent 'set index_format=... %t ...' ...or you just set up $alternates to match all your addresses so that you can just use: set index_format=... %F ... bye, Rocco
Re: Display in 'To:' in 'sent' folder only...
Hi, * Dhruva B. Reddy [02-07-16 00:28:52 +0200] wrote: On Tue, 16 Jul 2002 at 00:14:48 +0200, Rocco Rutte soliloquized thusly: Good. And: how did you reply to the message? Your mail shows neither an In-Reply-To: nor a References: header, i.e. it breaks threading which mutt usally (generallly?) _not_ does. Interesting. On this list, I do not include the 'In-Reply-To:' field unless I hit 'g'. I will remember this. You can also do: subscribe [EMAIL PROTECTED] and then you can hit 'L'. You might be interested in reading the manual (look for ``Handling Mailing Lists''). Right after sending the mail I remembered that I once had problems with David's mails which I received without References: but with In-Reply-To: (allthough others received it correctly). It still may be my mailpath. bye, Rocco
Re: bouncing w/ mutt-1.3.28i
On Mon, Jul 15, 2002 at 05:58:01AM -0500, David T-G wrote: | % continue to use 'bounce' since the list of Received: headers is | % getting too long with this mail server. | | That's really odd. Your mail server should let a message go through a | million hops if it has to. It's a crude, but effective, loop detection mechanism (mentioned in RFC 821 as well). When the MTA sees what it thinks is an excessive number of Received: headers it figures a mail loop has occured and bounces the message instead. -D -- Through love and faithfulness sin is atoned for; through the fear of the Lord a man avoids evil. Proverbs 16:6 http://dman.ddts.net/~dman/ msg29703/pgp0.pgp Description: PGP signature
Re: bouncing w/ mutt-1.3.28i
--Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alas! Derrick 'dman' Hudson spake thus: On Mon, Jul 15, 2002 at 05:58:01AM -0500, David T-G wrote: It's a crude, but effective, loop detection mechanism (mentioned in RFC 821 as well). When the MTA sees what it thinks is an excessive number of Received: headers it figures a mail loop has occured and bounces the message instead. Wouldn't it be more effective to check the Received headers to see if it's gone through the same server twice, and /then/ bounce the mail? It's not a mail loop if it just has a lot of servers to go through. --=20 Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- Today is the last day of your life so far. --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9M3RtPTh2iSBKeccRAlo6AJ4uxO4NQ6okJb2xKULPkOspAgsEkwCeOCXD 7yp0u8W1hcOFrgqtyXxxA9A= =qtH2 -END PGP SIGNATURE- --Q68bSM7Ycu6FN28Q--
Re: bouncing w/ mutt-1.3.28i
Hi, * Rob 'Feztaa' Park [02-07-16 03:34:04 +0200] wrote: Alas! Derrick 'dman' Hudson spake thus: It's a crude, but effective, loop detection mechanism (mentioned in RFC 821 as well). When the MTA sees what it thinks is an excessive number of Received: headers it figures a mail loop has occured and bounces the message instead. Wouldn't it be more effective to check the Received headers to see if it's gone through the same server twice, and /then/ bounce the mail? RfC 2821 suggests using dump counting. It's not a mail loop if it just has a lot of servers to go through. After reading a little in RfC 2821 it made me sick, escpecially section 6.2. ,[ rfc2821.txt ]- | | 6.2 Loop Detection | | Simple counting of the number of Received: headers in a | message has proven to be an effective, although rarely | optimal, method of detecting loops in mail systems. SMTP | servers using this technique SHOULD use a large rejection | threshold, normally at least 100 Received entries. Whatever | mechanisms are used, servers MUST contain provisions for | detecting and stopping trivial loops. `- (esp. ``SHOULD use a large...'', this has to read: ``MUST use at least 100...'') ...whatever the authors consider a mechanism to detect a trivial loop to be. If I had to write software detecting loops I would only check Received: headers. It needs some more than just this: virtual domains, Received: headers can be faked, etc. But by simply counting the number of hops the mail went through is not really clever allthough it's unlikely that there're 100 relays within a mail route. But the number of hops is not necessarily low, content filters (like virus scanners: 10 hops with 3 filters each make already 30 hops). bye, Rocco
