Re: Decrypting GPG-encoded messages
On Sat, Feb 09, 2002 at 05:37:19AM -0500, [EMAIL PROTECTED] wrote: I agree that what you wish to accomplish (having mutt automatically encrypt a file that you attach for sending) should be possible. My suggestion there is to get the procedure nailed down manually and then try working on converting it to a batch. I can't tell from your messages whether or not you've done the former and where your problems are coming up. Sorry, perhaps I haven't explained myself well enough. I currently have two problems (with mutt and GPG anyway), hence two threads. The first one (concerning this thread) is unrelated to the batching/scripting problem. I am simply unable to send a GPG-encrypted mail. I create the mail as usual, but just before hitting 'y' to send, I hit 'p' for the PGP menu, and then 'e' to encrypt, and 'y' to send the mail. It appears to encrypt the message OK - output log is as follows: gpg: using secondary key 633D8B16 instead of primary key DC303048 gpg: No trust check due to --always-trust option gpg: reading from `/tmp/mutt-tabby-24101-130' gpg: writing to `-' gpg: ELG-E/RIJNDAEL encrypted for: 633D8B16 David Smith (STMicroelectronics) [EMAIL PROTECTED] Press any key to continue... However, when I receive the 'encrypted' mail, it comes as two parts as per the pgp/mime standard - the first attachment is correct, but the second (which should contain the message) is about 6 blank lines base-64 encoded (i.e. I can push the attachment through 'mimencode -d', and I get 6 blank lines out). I've tried running the command specified in pgp_encrypt_only_command from the command line, and it works OK. I've even tried modifying the pgp_encrypt_only_command so that it pipes the output from GPG through tee before giving it back to mutt - the output comes out from GPG OK, but mutt simply isn't attaching it. GPG signing works fine - I can sign mails (like this one), but I just can't encrypt them. However, I have myself done much the same thing. I always had multiple files and batched them up (since this was a backup script), so I just collected them into a tar file, encrypted it with a special backups key, and then sent that file as an attachment; when I got to work (where there was lots of drive space :-) it was a simple matter of detaching the file and then extracting the tar file; that was driven by script (to make the proper directory and such) and all I had to do was provide the passphrase. I don't know what sort of work you have to do at home, but if it involves sending files back to work you probably aren't in read-only mode, and so a tar file might work well for you. Another thing I did once things got too large for mailing was to put the encrypted tar file into an ftp dir and have a script connecting every five minutes watching for it to pull it over; all I had to do was drop the batch into place and it would soon enough get copied over. You could do this in two directions :-) There are two things I want to do. The first is to continue to work as normal - sending mails with or without attachments from work to home and vice-versa - but with all mail over the link GPG-encrypted. I know that I can use hooks to specify that all mail to a particular address should be PGP-encrypted, so I'm assuming that I can just set up mutt so that I don't really see any difference (except that I'll have to type in the passphrase when I want to read a mail). The second is that I want to write a script - something like 'mail_to_home' that can be added to any script that I'm running, to send an arbitrary file to my home address - usually a logfile or something similar. My work involves large CPU and memory-intensive runs (between 6 and 24 hours each), and it's a real bummer to come in the next morning to find out that the jobs you set running just before leaving the night before crashed after 5 minutes because you spelt a variable name wrong. Being able to send selected files home allows me to check how things are running, so I can decide whether I need to go and fix something. Also, as projects reach their conclusion, managers get increasingly interested in the results of a run - if you set the run off on a Friday night, then they'll want to know on Saturday if it's bad - if it is, then they'll want to use the weekend to try to fix the problem, but if it's good, then you can have a nice quiet weekend... Of course, the contents of the files are technically confidential, so I'd rather not mail them in plaintext. It's also potentially useful when not in the office - most of the people around here are not GPG-aware, so the best way of getting them to mail a file to you securely is to give them a script that they can just run on the file. I suspect that I may solve the second problem outside of mutt with a PERL script using the relevant MIME packages. I'm not really bothered about automated reception - the whole point is that I will be sitting wherever the reception point
Re: Decrypting GPG-encoded messages
On Mon, Feb 11, 2002 at 09:34:36AM +, [EMAIL PROTECTED] wrote: GPG signing works fine - I can sign mails (like this one), but I just can't encrypt them. Of course, it helps if I actually do sign a mail when I say that I'm going to... -- David Smith Tel: +44 (0)1454 462380 (direct) STMicroelectronicsFax: +44 (0)1454 617910 1000 Aztec WestTINA (ST only): (065) 2380 Almondsbury Home: 01454 616963 BRISTOLMobile: 07932 642724 BS32 4SQ Work Email: [EMAIL PROTECTED] Home Email: [EMAIL PROTECTED] msg24406/pgp0.pgp Description: PGP signature
Re: errors while compiling mutt-1.3.27
Maarten den Braber muttered: * Dr. Sharukh K. R. Pavri. [EMAIL PROTECTED] [020210 15:33]: Ok, did that, here's what I get: --- [root@farzaan mutt-1.3.27]# make install ./patchlist.sh ./PATCHES patchlist.c /bin/sh: ./patchlist.sh: Permission denied make: *** [patchlist.c] Error 126 - patchlist.c is an empty file in the mutt source directory. What are the permissions of patchlist.sh? It normally gives this error (Permission denied) when the file is not executable. Try doing chmod u+x patchlist.sh. patchlist.sh *is* executable. Or rather I should say *was*. I couldn't wait so I downloaded 1.3.27 at a friend's place (he has cable internet). I am now running 1.3.27 but I would still like to know why I got these errors. Also, are there any specific steps that need to be taken when patching mutt either using diff's or third-party patches? regards, Sharukh. -- Dr. Sharukh K. R. Pavri Mumbai, India.
Re: People who don't wrap their lines
Nick,
On Thursday Feb 07, 2002 Nick Wilson [EMAIL PROTECTED] spake thusly:
* and then Philip Mak declared
I'm having trouble reading messages from people who don't wrap their
lines. They have it so that one paragraph is a very long line, but it
No. hehe, but a nice gentlemen from 'the rolling hils of south carolina'
sent me this handy little vim macro:
map C-l {!}par 72
}j
But this wouldn't do much of anything when reading a message in mutt
would it? Or do you have your pager set as vim?
Thanks,
Chris
--
Christopher S. Swingley phone: 907-474-2689
Computer / Network Manager email: [EMAIL PROTECTED]
IARC -- Frontier ProgramGPG and PGP keys at my web page:
University of Alaska Fairbanks www.frontier.iarc.uaf.edu/~cswingle
perfect_maildir
I have used Philip Mak's code from perfect_maildir http://www.mail-archive.com/mutt-users@mutt.org/msg21872.html and combined it with the mb2md script by Robin Whittle. So the result is a mb2md script plus header flags, I'm sure this could be combined with that date program for supporting Outlook users as well. Thanks. -Mike #!/usr/bin/perl # # Robin Whittle 15 July 2001. Copyright Public Domain. Tab = 4 columns. # Michael Best 09 February 2002. [EMAIL PROTECTED] # # Reads a directory full of Mbox format mailboxes and creates a set of # Maildir format mailboxes. Some details of this are to suit Courier # IMAP's naming conventions for Maildir mailboxes. # # http://www.inter7.com/courierimap/ # # This is intended to automate the conversion of the old # /var/spool/mail/blah file - with one call of this script - and to # convert one or more mailboxes in a specifed directory with separate # calls with other command line arguments. # # Run this as the user - in these examples blah. # # Tested on RedHat 7.2 Perl 5.6.0 # # The original script mb2md's web abode is http://www.firstpr.com.au/web-mail/ . # # I knew nothing of Perl before I wrote this. I used the man and FAQ pages # at http://www.perldoc.com and a chapter preview from http://www.cgi-perl.com. # # The Mbox - Maildir inner loop is from qmail's script mbox2maildir, which # was kludged by Ivan Kohler in 1997 from convertandcreate (public domain) # by Russel Nelson. Both these convert a single mailspool file. # # The mail flag conversion code came out of a post to mutt-users by # Philip Mak 25 December 2001. [EMAIL PROTECTED] # http://www.mail-archive.com/mutt-users@mutt.org/msg21872.html # # The qmail distribution has a maildir2mbox.c program. # # # - # # # mb2md MBROOT MBDIR [DEST] # # # MBROOT Directory, relative to the user's home directory, #which is where the the MBDIR directory is located. # # # MBDIRDirectory, relative to MBROOT where the Mbox files #are. There are two special cases: # #1 - None # #2 - Inbox # #If it is set to None then mailboxes in the MBROOT #directory will be converted and placed in the #DEST directory. (Typically the Inbox directory #which in this instance is also functioning as a #folder for other mailboxes.) # #If this is set to Inbox then the source will #be the single mailbox at /var/spool/mail/blah for #user blah and the destination mailbox will be the #DEST mailbox itself. # #Except in this Inbox case, the MBDIR directory #name will be encoded into the new mailboxes' names. #See the examples below. # #This script will not work with maibox files which #contain spaces in their names. # #Expect trouble if an files in MBDIR directory #are not proper Mbox mailbox files. # #This does not save an UW IMAP dummy message file #at the start of the Mbox file. Small changes #in the code could adapt it for looking for #other distinctive patterns of dummy messages too. # #Don't let the source directory you give as MBDIR #contain any .s in its name, unless you want to #create subfolders from the IMAP user's point of #view. See the example below. # # # DEST Directory relative to user's home directory where the #Maildir format directories will be created. #If not given, then the destination will be ~/Maildir . #Typically, this is what the IMAP server sees as the #Inbox and the folder for all user mailboxes. # # # # Example # === # # We have a bunch of directories of Mbox mailboxes located at # /home/blah/oldmail/ # # /home/blah/oldmail/f # /home/blah/oldmail/g # /home/blah/oldmail/xxx/ # /home/blah/oldmail/xxx/ # /home/blah/oldmail/xxx/ # /home/blah/oldmail/xxx/ # /home/blah/oldmail//huey # /home/blah/oldmail//duey # /home/blah/oldmail//louie # # With the UW IMAP server, f and g would have appeared in the root # of this mail server, along with the Inbox. , etc, would have # appeared in a folder called xxx from that root, and xxx was just a folder # not a mailbox for storing messages. # # We also have the mailspool Inbox at: # # /var/spool/mail/blah # # # To convert these, as user blah, we give the first command: # #mb2md xyz Inbox # # In this case, the first argument is irrelevant - xyz is ignored. # # The main Maildir directory will be created if it does not exist. #
Re: How can I underline the current index entry?
On Sun, Feb 10, 2002 at 08:30:50AM +, Benjamin Smith wrote:
Why is this? This is a mutt limitation isn't it, as other ncurses apps
(w3m) can colour *and* underline, perhaps this should get placed on a
TODO list?
Try the following patch. It's a hack that lets you use underline when you
prefix one of the color names with an underscore:
color _brightred yellow
should get you underlined bold read fg on yellow bg.
--- color.c~Thu Jan 24 04:10:48 2002
+++ color.c Sun Feb 10 21:56:53 2002
@@ -305,6 +305,13 @@ parse_color_name (const char *s, int *co
{
char *eptr;
+ /* XXX hack to allow underline with colors */
+ if (*s == '_')
+ {
+*attr |= A_UNDERLINE;
+s++;
+ }
+
if (mutt_strncasecmp (s, bright, 6) == 0)
{
*attr |= brite;
Re: Decrypting GPG-encoded messages
Dave -- ...and then Dave Smith said... % % On Sat, Feb 09, 2002 at 05:37:19AM -0500, [EMAIL PROTECTED] wrote: % I agree that what you wish to accomplish (having mutt automatically % encrypt a file that you attach for sending) should be possible. My ... % % Sorry, perhaps I haven't explained myself well enough. % % I currently have two problems (with mutt and GPG anyway), hence two threads. Ah. Now I get it. % % The first one (concerning this thread) is unrelated to the batching/scripting % problem. I am simply unable to send a GPG-encrypted mail. I create the Hokay. This certainly will require some debugging, but I haven't had to debug much and so I won't be much of a resource for you here. Sorry! Now to see who else chimes in with ideas... % ... % GPG signing works fine - I can sign mails (like this one), but I just can't % encrypt them. I noted your reply with a wry grin :-) % ... % There are two things I want to do. The first is to continue to work as ... % The second is that I want to write a script - something like 'mail_to_home' % that can be added to any script that I'm running, to send an arbitrary file Yeah; good idea. ... % selected files home allows me to check how things are running, so I can % decide whether I need to go and fix something. No VPN from home? Ouch! % % It's also potentially useful when not in the office - most of the people % around here are not GPG-aware, so the best way of getting them to mail a % file to you securely is to give them a script that they can just run on % the file. Yeah. That will work regardless of what MUA they use, too. % % I suspect that I may solve the second problem outside of mutt with a % PERL script using the relevant MIME packages. Sounds likely. Best of luck! 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! msg24411/pgp0.pgp Description: PGP signature
alias expansion questions
How do I do the following in mutt 1.2.5i (I don't system admin the machine I email from)? Say I have an alias in my alias list that reads alias theguys [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] I want to send an email to the alias theguys so when the emails are sent each recipient only sees their name in the to: header So I put theguys in the to: field but joe sees [EMAIL PROTECTED] in the to: field jack sees [EMAIL PROTECTED] in the to: field etc I realise I could send the message To: myself and bcc the group alias but that is not quite the same thing. Also, and alternatively, can mutt keep the alias in the to: field but still email the list of the expanded alias --- I realise that system wide aliases can be set up but you have to be sysadmin to do this. This would ALSO be a nice feature to have. -other emailers can do it I believe Perhaps these 2 features are planned for a future release? -- Aleks Owczarek
forwarding attachments
I realise to forward attachments along with the text (that you want to edit) one has to 1) select the email you want to forward then press v to go to the attachments menu 2) tag each attachment and the text part (body) of the email by pressing t on each element in the list of the attachments menu 3) press ; (which tells mutt you want to do something with these tagged attachments) THEN 4) press f to forward the email and the editor of your choice should spring to life This is really useful and flexible but Now, if any mutt developers are reading this. Please make this convoluted process easier by adding a forward-with-attachments variable or am i missing something? ps: Set mime_forward=ask-yes is not what some people want - it includes the whole of the email as one attachment to the new email. -- Aleks Owczarek
Re: errors while compiling mutt-1.3.27
Sharukh -- ...and then Dr. Sharukh K. R. Pavri. said... % ... % patchlist.sh *is* executable. Or rather I should say *was*. I couldn't Interesting. % wait so I downloaded 1.3.27 at a friend's place (he has cable internet). I % am now running 1.3.27 but I would still like to know why I got these Good :-) % errors. Also, are there any specific steps that need to be taken when I haven't ever seen it, so I wonder if it's a problem that crept in by using diffs to get from .24 to .27. Certainly the PATCHES functionality was [re-]added in that gap; it looks awfully suspicious. Without you to test and poke, though, I doubt any of us will be able to come up with an answer for you. % patching mutt either using diff's or third-party patches? I haven't used the diff method to change versions, but it really should be straightforward and I can't think of any special procedures. When applying third-party patches, things can get hairy. You might surf over to http://mutt.justpickone.org/ and take a look at the build cocktail directory and some of the files at the top. You can see how I put together the whole mess in 00.makeme.sh, and any patch that ends in dtg has been tweaked to fit my installation. % % regards, HTH HAND % % Sharukh. % -- % Dr. Sharukh K. R. Pavri % Mumbai, India. :-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! msg24414/pgp0.pgp Description: PGP signature
Re: alias expansion questions
Aleks -- ...and then Aleks Owczarek said... % % How do I do the following in mutt 1.2.5i (I don't system admin the % machine I email from)? FWIW you could build and locally install your own copy of 1.3.27, but if you note to your SysAdmin that 1.2.5 has a security hole and that it would be as effective to build 1.3.27 when building 1.2.5.1 you might get the latest version on the system :-) 1.3.27 would be good practice for the forthcoming 1.4.0, too; it's due RSN. % % Say I have an alias in my alias list that reads % alias theguys [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Good enough. % % I want to send an email to the alias theguys so when the emails are % sent % each recipient only sees their name in the to: header Nope; that would require three different messages to three different destinations. % % So I put theguys in the to: field but % joe sees [EMAIL PROTECTED] in the to: field % jack sees [EMAIL PROTECTED] in the to: field % etc % % I realise I could send the message To: myself and bcc the group % alias but that is not quite the same thing. It isn't, but that's pretty much the way you'd have to do it. % % Also, and alternatively, can mutt keep the alias in the to: field % but still email the list of the expanded alias % --- I realise that system wide aliases can be set % up but you have to be sysadmin to do this. % This would ALSO be a nice feature to have. % -other emailers can do it I believe Let's see... So you want the headers to look like To: TheGuys Bcc: joe@, jack@, tony@ or perhaps just To: TheGuys: joe@, jack@, tony@; The second entry is your key, and you'll find that the first entry will actually look like To: TheGuys :; when it's properly written. If you want the first entry's behavior, you can probably whip up a send-hook command that will act when sending to all three of these fellows and rewrite the To: and Bcc: headers appropriately. I don't believe there's a way to recognize an alias itself but instead the resolved addresses, so that might get sticky. % % Perhaps these 2 features are planned for a future release? The former won't (can't!) happen, and the latter is already possible :-) % % -- % Aleks Owczarek 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! msg24415/pgp0.pgp Description: PGP signature
Re: mutt and NFS
Ken, et al -- ...and then Ken Weingold said... % % On Sat, Feb 9, 2002, Paul Ackersviller wrote: ... % saw once when I tried a performance tweak on one of my filesystems. % Some filesystems have a mount option noatime to not update file access ... % Is it possible the filesystem in question has this behaviour? % % Would I see that in the fstab options? If so, the nfs mount is simply % set with options 'defaults'. And this doesn't always happen, so % that's why it's hard to troubleshoot, you know? The best way to tell would be to check the output of mount on your client machine and exportfs on your server, but ... That's an always thing, so it's extremely unlikely that that's the problem since yours is intermittent, can be fixed manually with touch, and usually resolves itself within a few minutes. Hey, you're not using a cache fs, are you? % % % -Ken 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! msg24416/pgp0.pgp Description: PGP signature
Re: alias expansion questions
Aleks -- You'll have to watch for my real reply on the mailing list, since ... you need to fix your M-F-T: header to include your domain; amazingly enough I got a there is no aleks here return from my MTA ;-) :-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! msg24417/pgp0.pgp Description: PGP signature
Re: How can I underline the current index entry?
Michael Elkins [EMAIL PROTECTED] said something to this effect on 02/11/2002: On Sun, Feb 10, 2002 at 08:30:50AM +, Benjamin Smith wrote: Why is this? This is a mutt limitation isn't it, as other ncurses apps (w3m) can colour *and* underline, perhaps this should get placed on a TODO list? Try the following patch. It's a hack that lets you use underline when you prefix one of the color names with an underscore: color _brightred yellow should get you underlined bold read fg on yellow bg. I wasn't very interested in being able to do underlined colors until I applied the patch; it's pretty cool. Is something like this going to be in 1.4.0? (darren) -- Morality works best when chosen, not when mandated. -- Larry Wall
Re: mmutt 1.3.27i and MH mail folders - no new mail!
On 17:28 11 Feb 2002, Cameron Simpson [EMAIL PROTECTED] wrote: | I just upgraded to mutt-1.3.27i, mostly to use message-hook. | Anyway, my mail folders are all MH style folders. New mail arrives, | but it doesn't get the N flag. Somewhat disconcerting. Well, to answer my own question: It seems that mutt's MH code doesn't do much to the .mh_sequences file unless it has stuff in it and gets used. So now I deliver my email with MH's rcvstore program, thus: :0w * pattern to match the mutt mailing lists here ... | /usr/lib/nmh/rcvstore +mail -unseen and have set up my .mh_profile to say: Path: private/mail Unseen-sequence: unseen which is needed to have rcvstore update the sequence info. And now mutt shows my nice N flags on my new messages again. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ Sorry wrong coincidence. You mention being a grad student. Irritable and sarcastic are then redundant. It is fortunately curable by finishing your thesis. - Bob Grumbine [EMAIL PROTECTED]
Re: [Announce] lbdb 0.26
On 11/02/02, from the brain of Roland Rosenfeld tumbled: I just released a new version of the little brother's database with the following changes: lbdb (0.26) unstable; urgency=low * m_finger: Suppress lines where real name is '???' (some versions of finger seem to use this for non existing users) (Closes: #112127). * m_wanderlust: new module to read ~/.addesses file from WanderLust MUA. Module provided by Gergely Nagy [EMAIL PROTECTED]. (Closes: #133209). * Quote the search string in m_yppasswd, m_nispasswd and m_getent as mentioned by Gary Johnson [EMAIL PROTECTED]. * Add CVS Id tags to all modules. -- Roland Rosenfeld [EMAIL PROTECTED] Mon, 11 Feb 2002 20:23:42 +0100 Tscho Roland One thing I've never been able to figure out. I installed from a .deb file and didn't do much tweaking after that but how do duplicates get removed from my m_inmail.list file that is maintained when I receive emails. Am I supposed to run a cron job? If so, can someone point me to an appropriate script? -- Michael Montagne [EMAIL PROTECTED] http://www.boora.com
Re: [Announce] lbdb 0.26
On Mon, Feb 11, 2002 at 05:41:18PM -0800, Michael Montagne wrote: One thing I've never been able to figure out. I installed from a .deb file and didn't do much tweaking after that but how do duplicates get removed from my m_inmail.list file that is maintained when I receive emails. Am I supposed to run a cron job? If so, can someone point me to an appropriate script? This is handled by the m_inmail script whenever you query your m_inmail.list. The m_inmail script invokes lbdb-munge, which in turn invokes either munge or munge-keeporder. These last two are awk scripts that, in conjunction with lbdb-munge, read in your entire m_inmail.list file, keeping only the latest copy of each address, then re-write all the kept lines back to m_inmail.list. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
forwarding attachments (PLEASE READ before replying)
I realise to forward attachments along with the text (that you want to edit) one has to 1) select the email you want to forward then press v to go to the attachments menu 2) tag each attachment and the text part (body) of the email by pressing t on each element in the list of the attachments menu 3) press ; (which tells mutt you want to do something with these tagged attachments) THEN 4) press f to forward the email and the editor of your choice should spring to life This is really useful and flexible but Now, if any mutt developers are reading this. Please make this convoluted process easier by adding a forward-with-attachments variable or am i missing something? ps: Set mime_forward=ask-yes is NOT what some people want - it includes the whole of the email as one attachment to the new email (if you say yes that is to the ask). pps: apologies if this is sent twice as I have just subscribed to the mail-list -- ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** Aleks L. Owczarek Department of Mathematics and Statistics University of Melbourne, Vic, 3010, Australia. e-mail: [EMAIL PROTECTED] ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
Re: forwarding attachments (PLEASE READ before replying)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Said Aleks Owczarek on Tue, Feb 12, 2002 at 02:38:08PM +1100: Now, if any mutt developers are reading this. Please make this convoluted process easier by adding a forward-with-attachments variable or am i missing something? I believe mime_forward will do what you want. I have this: message-hook . set mime_forward=no message-hook ~h multipart set mime_forward=ask-yes - -- [!] Justin R. Miller [EMAIL PROTECTED] PGP 0xC9C40C31 -=- http://codesorcery.net http://drcnet.org/wol/222.html#superbowlads -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8aJUL94d6K8nEDDERAqniAKCLFs8hQjPg2En0Zg7PWzbic1hKUACfRZaX 3GrmHJ/3zAdcpMd3hwknbrw= =LUsz -END PGP SIGNATURE-
Re: forwarding attachments (PLEASE READ before replying)
On Mon, Feb 11, 2002 at 11:07:40PM -0500, Justin R. Miller wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Said Aleks Owczarek on Tue, Feb 12, 2002 at 02:38:08PM +1100: Now, if any mutt developers are reading this. Please make this convoluted process easier by adding a forward-with-attachments variable or am i missing something? I believe mime_forward will do what you want. I have this: message-hook . set mime_forward=no message-hook ~h multipart set mime_forward=ask-yes -END PGP SIGNATURE- unfortunately that doesn't do it I have already tried ... -- ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** Aleks L. Owczarek Department of Mathematics and Statistics University of Melbourne, Vic, 3010, Australia. e-mail: [EMAIL PROTECTED] ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
Re: alias expansion questions
On Mon, Feb 11, 2002 sometime, David T-G wrote: Let's see... So you want the headers to look like To: TheGuys Bcc: joe@, jack@, tony@ or perhaps just To: TheGuys: joe@, jack@, tony@; The second entry is your key, and you'll find that the first entry will actually look like To: TheGuys :; when it's properly written. If you want the first entry's behavior, you can probably whip up a send-hook command that will act when sending to all three of these fellows and rewrite the To: and Bcc: headers appropriately. I don't believe there's a way to recognize an alias itself but instead the resolved addresses, so that might get sticky. % % Perhaps these 2 features are planned for a future release? The former won't (can't!) happen, and the latter is already possible :-) Actually I didn't understand your above reply but worked it out anyway... For anyone reading this later... All you do is put anything in the to: field to begin with. Then after editing your message add the real alias to the bcc: field and then edit out the to: field with either nothing (that is make it blank) or TheGuys:; In the first case mutt adds undisclosed recipients:; in the to: field ps: The first behaviour mentioned in my original post can be obtained by a shell script using mailx so it sort of can happen :-) -- ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** Aleks L. Owczarek Department of Mathematics and Statistics University of Melbourne, Vic, 3010, Australia. e-mail: [EMAIL PROTECTED] ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
