Re: SMTP
* Suresh Ramasubramanian [EMAIL PROTECTED] [000714 14:05]: Marius Gedminas proclaimed on mutt-users that: It's not that I advocate adding SMTP support to Mutt [2], but I just wonder, why two programs following the same Unix philosophy (do one thing well) choose so different solutions [3] for so similair tasks -- handing an email to an MTA. Setting the DS flag on your local sendmail and smarthosting through your ISP's smtp server is the nearest to what you want ;) Is there any other way? I have a shell account in a box with no root, I can't use envelop_from to set aproper From line, and the best way is to talk Port 25.. Anyone's got a program/script/whatever that can convert sendmail commands to Port 25 speak? -- Regards: Wari Wahab Don't worry about avoiding temptation -- as you grow older, it starts avoiding you. -- The Old Farmer's Almanac
Re: SMTP
Wari Wahab proclaimed on mutt-users that: Is there any other way? I have a shell account in a box with no root, I can't use envelop_from to set aproper From line, and the best way is to talk Port 25.. Anyone's got a program/script/whatever that can convert sendmail commands to Port 25 speak? Try ssmtp (simple smtp). Search google / freshmeat ;) -- Suresh Ramasubramanian + [EMAIL PROTECTED] Just because your doctor has a name for your condition doesn't mean he knows what it is.
Re: SMTP
On 2000-07-14 00:17:20 +0200, Marius Gedminas wrote: I mean -- both Mutt and fetchmail require an MTA[1], but fetchmail uses SMTP to access it (IIRC to avoid problems with different command line arguments for different MTAs etc.). Mutt also needs an MTA, but it goes with the command line solution. And there are problems with this solution -- witness the recent questions about RFC-822 addresses containing spaces and the requirement for special wrapper scripts to make them work with qmail. Which was needed since qmail decided to behave different from any other mail transport agent around. Sorry, but this isn't our problem. About supporting SMTP: This would be considerably more complex than the current approach. -- Thomas Roessler [EMAIL PROTECTED]
Re: PGP/MIME
On 2000-07-13 16:01:18 -0400, Daniel J Peng wrote: What exactly was wrong with the old way of signing e-mails, with "-BEGIN PGP SIGNED MESSAGE-" and such? What is the benefit to PGP/MIME? Try any of the following things with old-style PGP: - Encrypt an iso-8859-1 message and decrypt and display it on the Macintosh. This will result in garbled non-us-ascii characters. - Encrypt and sign a message consisting of plain text, image, and plain text with a different character set. You just can't express this with application/pgp. Finally, I suppose you are referring to certain versions of Outlook Express ignoring "Content-Disposition: inline" headers on individual parts of multipart messages, with the result that these content parts aren't displayed. Frankly, that's not our problem. Ask Microsoft to get this right. (The fact that "opening" these text/plain attachments produces the normal "uh-oh, opening this may be dangerous" dialog, is just another sign for the nonsense going on there.) -- Thomas Roessler [EMAIL PROTECTED]
Re: SMTP
Marius -- ...and then Marius Gedminas said... % I mean -- both Mutt and fetchmail require an MTA[1], but fetchmail uses % SMTP to access it (IIRC to avoid problems with different command line % arguments for different MTAs etc.). Mutt also needs an MTA, but it goes % with the command line solution. And there are problems with this Very true. % solution -- witness the recent questions about RFC-822 addresses % containing spaces and the requirement for special wrapper scripts to % make them work with qmail. Well, people should know better than to use spaces for anything other than separating options ;-) % % --- % [1] It can be argued, that fetchmail needs an MDA, not an MTA... but the % thing listening on port 25 is usually an MTA. Yeah. % % On Thu, Jul 13, 2000 at 11:44:34AM -0400, David T-G wrote: % The mutt equivalent of fetchmail talking to SMTP would be mutt talking to % port 25 only on your machine, and therefore only after you had set up an % MTA already. % % Exactly. And this leads to the next trick question: what's the % difference between talking to localhost:25 or remotehost:25? :) I saw this coming, but didn't want to work around it at the time. Yes, I know that it doesn't really matter where the port is. That's why I said "equivalent" :-) % % It's not that I advocate adding SMTP support to Mutt [2], but I just % wonder, why two programs following the same Unix philosophy (do one % thing well) choose so different solutions [3] for so similair tasks -- % handing an email to an MTA. Perhaps because it's just philosophy, which is subject to endless debate! % % --- % [2] Well, that would be a nice thing to have if I try to compile it on % WinNT again ;) Hey, now, this *would* be nice :-) % [3] I know that fetchmail can feed the email to an external program % instead of localhost:25, but the default way is SMTP. % % BTW in the standard Unix world (MDA/MUA/MTA), where does fetchmail fit % in? It doesn't; it's for the nonstandard world of dialups and goofy accounts and no forwarding and whatnot. At least, that's my casual answer for today :-) % % Marius Gedminas % -- % All those who believe in psychokinesis raise my 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 millennium" 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: FBI's e-mail snooping 'Carnivore'
Randall, et al -- ...and then Randall Hopper said... % Coming to an ISP near you (if it hasn't already). Yeah. Ugh. % % I heartly encourage fellow Mutt users to PGP by default to your friends % that have given you public keys, and encourage them to do the same. % % send-hook (bill|sarah)@home.com "set pgp_autoencrypt" Thanks for the example! % % And thanks to all those who maintain our favorite mailer which makes tricks % like this so configurably easy! And a hearty second :-) % % (Use Netscape or Outlook? You have to be kidding. ;-) *grin* % % -- % Randall Hopper % [EMAIL PROTECTED] ...and then Randall Hopper said... % Randall Hopper: % |Coming to an ISP near you (if it hasn't already). % % Forgot the news URLs. Here are a few: % % http://www.theregister.co.uk/content/1/11902.html % http://www.deja.com/=dnc/[ST_rn=ps]/getdoc.xp?AN=645793204 % http://www.deja.com/=dnc/[ST_rn=ps]/getdoc.xp?AN=645793498 % http://www.deja.com/=dnc/[ST_rn=ps]/getdoc.xp?AN=645332783 These are worth keeping in just to make sure folks see them. For those who don't like Deja (like me), there's always http://cryptome.org/fbi-sucks.htm as posted on the freenet-chat list. So far, I've seen three people there using mutt (1.0i or 1.2i) :-) :-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 millennium" 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: trash folder
Dennis -- ...and then Dennis Robertson said... % On Thu, Jul 13, 2000 at 02:14:10PM +0200, Dirk Huebner wrote: % % Add this into your keybind-file. % ,--+ % | macro index d "s=trashenter"ยท % | macro pager d "s=trashenter" % `--+ % % When I open this message the symbol at the end of the macro index line is For me, in fact, it's a cap Pi symbol! % a ?. When I print the message it becomes a 7. Now in pico it is a dot. This % is the first time I have observed this behaviour. Can anyone suggest a fix, % please. It's all in the language and locale. You should probably just get rid of it and let your editor handle the newline mapping for you. % % -- % Dennis Robertson 2/2 Sylvia Street NOOSAVILLE QLD 4566 % Phone: 61 7 54742343 Mob: 0419 535539 :-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 millennium" 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: PGP/MIME
Daniel -- ...and then Daniel J Peng said... % Are there any mail clients around other than Mutt that sign and % encrypt messages the way Mutt does? Nobody I know is able to read my Don't know, but I'd be surprised if - there weren't any at all - any were well-known in the Windoze world % signed messages or verify my signatures, and the signatures seem to Hey, it worked for me! :-) % cause problems with some mailreaders. For instance, the message body % shows up blank, and what I wrote only shows up in a text attachment % (which, sadly enough, some people fail to notice and completely miss % what I wrote). Yeah; that's a common problem. % % I read the rationale (or rather, what I believe to be the rationale) % for this in PGP-Notes.txt, in the answer to the question, "I don't % like that PGP/MIME stuff, but want to use the old way of PGP-signing % my mails. Can't you include that with mutt?" I don't understand why Well, there's nothing that says you can't do it with macros; a few different versions have been posted to this list, and a few patches out there even make it easier to do. And, in fact, it's my understanding that it now *is* included; since you're using 1.2.4, check out the contributed pgp6.rc (at least) for the pgp_clearsign_command setting. I haven't yet played with 1.2.4 to see how you get the pgp_clearsign_command instead of the pgp_sign_command (I'm still converting my old muttrc and pgp to new muttrc and gpg) but it certainly provides some hope; I plan to use whatever magic it is in a hook when trading email with those poor LookOut! users (like my dad) who cannot handle real signatures because the text body then becomes an attachment -- which is then not quoted, but just included, in their reply. % "Application/pgp is not really suited to a world with MIME, % non-textual body parts and similar things." What exactly was wrong % with the old way of signing e-mails, with "-BEGIN PGP SIGNED % MESSAGE-" and such? What is the benefit to PGP/MIME? I don't have a great answer to give you, having happily accepted PGP/MIME myself, but I do know that lots of forwarders, remailers, and listservers tend to put things in the body of the message instead of in the headers (where any such silly screwing around *should* go), and that will definitely screw up your signature and, for all I know, maybe even the ability to decrypt. % % -- Cute sig, though a little long... :-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 millennium" 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
No @ in alias?
Hi *, I have defined some aliases in the form alias name@home ... alias name@work ... but mutt does not expand them. Is this a feature or a bug? -Dirk
attachments when using IMAP
I have folder and spooldir set to an IMAP-type path, since I don't keep
any mail locally. This works very nicely (mmm, 1.2.4i good) except that
if I try to add a local attachment to a message I'm composing, mutt
looks for the file on the IMAP server rather than looking on the local
filesystem.
This kind of sucks :)
Am I doing something stupid? Or is this really a problem?
Build is stock 1.2.4i with --with-imap on OpenBSD 2.7/i386; muttrc
below.
Joe
# $Id:$
#
# built on mutt 1.2.4i
# look-and-feel
unset confirmappend
set ascii_chars=yes
set beep_new=yes
set delete=yes
set fast_reply
set mime_forward="ask-yes"
unset markers
unset mbox
unset menu_scroll
unset move
set pager_context=4
set pager_index_lines=4
set pager_stop
unset mark_old
unset strict_threads
set autoedit=yes
set fast_reply=yes
set edit_headers=yes
folder-hook . set sort=threads
bind index x sync-mailbox
# imap
set imap_user="jabley"
set folder={maggie.automagic.org}INBOX
set spoolfile={maggie.automagic.org}INBOX
mailboxes {maggie.automagic.org}INBOX
# multiple personality disorder
set
alternates="jabley@(tsnz.net|patho.gen.nz|automagic.org|quicksilver.co.nz|2day.com)"
folder-hook . my_hdr "fcc: {maggie.automagic.org}INBOX.out.general"
folder-hook . my_hdr "From: Joe Abley [EMAIL PROTECTED]"
folder-hook in.netlink my_hdr "fcc: {maggie.automagic.org}INBOX.out.netlink"
folder-hook in.netlink my_hdr "From: Joe Abley [EMAIL PROTECTED]"
folder-hook in.qsi my_hdr "fcc: {maggie.automagic.org}INBOX.out.qsi"
folder-hook in.qsi my_hdr "From: Joe Abley [EMAIL PROTECTED]"
folder-hook in.2day my_hdr "fcc: {maggie.automagic.org}INBOX.out.2day"
folder-hook in.2day my_hdr "From: Joe Abley [EMAIL PROTECTED]"
# aliases
set alias_file="~/.mutt-aliases"
source "~/.mutt-aliases"
Re: attachments when using IMAP
On Sat, Jul 15, 2000 at 01:27:21AM +1200, Joe Abley wrote: I have folder and spooldir set to an IMAP-type path, since I don't keep any mail locally. This works very nicely (mmm, 1.2.4i good) except that if I try to add a local attachment to a message I'm composing, mutt looks for the file on the IMAP server rather than looking on the local filesystem. Yeah. That's expected behavior. If you specify an absolute path, it looks for it locally. Ie: ~/downloads/mutt.5.0.tgz will grab it from you local system rather than the remote server. Ben -- Ben Beuchler [EMAIL PROTECTED] Hostmaster/Postmaster (612)-321-9290 x101 Bitstream Underground www.bitstream.net
Re: SMTP
Marius Gedminas [EMAIL PROTECTED] wrote: I mean -- both Mutt and fetchmail require an MTA[1], but fetchmail uses SMTP to access it (IIRC to avoid problems with different command line arguments for different MTAs etc.). Mutt also needs an MTA, but it goes with the command line solution. [1] It can be argued, that fetchmail needs an MDA, not an MTA... but the thing listening on port 25 is usually an MTA. So don't use fetchmail. My own 'getmail' does it's delivery directly into Maildirs or mbox files. It's not that I advocate adding SMTP support to Mutt [2], but I just wonder, why two programs following the same Unix philosophy (do one thing well) choose so different solutions [3] for so similair tasks -- handing an email to an MTA. Because fetchmail is a good implementation of a broken design. Charles -- --- Charles Cazabon [EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: attachments when using IMAP
On Sat, Jul 15, 2000 at 01:27:21AM +1200, Joe Abley wrote:
I have folder and spooldir set to an IMAP-type path, since I don't keep
any mail locally. This works very nicely (mmm, 1.2.4i good) except that
if I try to add a local attachment to a message I'm composing, mutt
looks for the file on the IMAP server rather than looking on the local
filesystem.
Mine isn't. See later.
# imap
set imap_user="jabley"
set folder={maggie.automagic.org}INBOX
Mine's set folder = ~/Mail
set spoolfile={maggie.automagic.org}INBOX
mailboxes {maggie.automagic.org}INBOX
Since I'm using IMAP, too, this doesn't seem to pose a problem. Of course I
don't store my mail on the server where I have a quota. :)
Perhaps you could change your $folder variable if you want to send an
attachment.
# multiple personality disorder
set
alternates="jabley@(tsnz.net|patho.gen.nz|automagic.org|quicksilver.co.nz|2day.com)"
:) sounds familiar
Kai
--
x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x
Kai Blin(mailto:[EMAIL PROTECTED]) Webmaster
Inst. of Human Genetics Dept. of Molecular Genetics
Wilhelmstr 27 phone (49)7071-2974890
D 72074 Tuebingen, Germany fax (49)7071-295233
http://www.uni-tuebingen.de/uni/thm/molgen/molgen.html
Do molecular biologists wear designer genes?
x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x
Re: PGP/MIME
On 000713, at 16:01:18, Daniel J Peng wrote: Are there any mail clients around other than Mutt that sign and encrypt messages the way Mutt does? Newer versions of Eudora understand PGP/MIME. It may even be able to send PGP/MIME messages. -- David Ellement
How do I automate mutt in a script?
I am writing a script which uses mutt to create an email with an attachment with "mutt -a atfile.doc -s subject [EMAIL PROTECTED]". But it always brings up the vi screen to enter the message for my body. Is there a way for me to create text files with default message bodies, and use the mutt command to automatically compose an email without prompting me for any input? Any help will be appreciated. Gerald
Re: How do I automate mutt in a script?
Gerald -- ...and then Gerald Manipon said... % I am writing a script which uses mutt to create an email with an attachment % with % "mutt -a atfile.doc -s subject [EMAIL PROTECTED]". But it always brings up the Goodie. % vi screen % to enter the message for my body. Is there a way for me to create text % files with % default message bodies, and use the mutt command to automatically compose an Sure, just like every other unix mail program I've ever seen. And mutt even has it documented for you: 6.1 ... Mutt also supports a ``batch'' mode to send prepared messages. Simply redirect input from the file you wish to send. For example, mutt -s "data set for run #2" [EMAIL PROTECTED] ~/run2.dat This command will send a message to ``[EMAIL PROTECTED]'' with a subject of ``data set for run #2''. In the body of the message will be the contents of the file ``~/run2.dat''. As always, you can use /dev/null is you don't want to have any message body, or send the input in on stdin with something like echo "this is the useless message body" | mutt ... % email % without prompting me for any input? Any help will be appreciated. You can start by checking in the manual; it has all sorts of great information. % % Gerald HTH HAND Boy, I hope that this is in the mutt-newbie FAQ when it comes around... :-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 millennium" 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
multipart/alternative formatting
There seems to be some "funkiness" in the handling of
multipart/alternative messages. In particular, the attachments
which are Content-Type: text/plain and Content-Transfer-Encoding:
quoted-printable. These frequently come from Outlook (Express) users.
This is how mutt displays a single line of the message:
i'm using linux mandrake about 3 month it like me, the firts time install LM in
+a machine with Win98, now i want to install it with WinNT,
This is how the same line looks in the message:
i'm using linux mandrake about 3 month it like me, the firts time =
install LM in a machine with Win98, now i want to install it with WinNT,
The '=' sign is a sort of "soft-return" that gets dropped in the
decoding process, resulting in abnormally long lines.
At present, I am dealing with the problem via procmail (see below),
but I guess my question is, "Shouldn't these soft returns be preserved
by the receiving client (i.e. mutt)?"
# Force multipart/alternative to appropriate column widths
:0
* ^Content-Type.*multipart/alternative
{
:0 fbBw
* ^Content-Transfer-Encoding:.*quoted-printable
| sed -e "s/=$//g"
}
--
_
_|_|_
( ) *Anton Graham
/v\ / [EMAIL PROTECTED]
/( )X
(m_m) GPG ID: 18F78541
Penguin Powered!
Re: Digression: mutt and mixmaster
On Jul 13, 2000, Christian R Molls and Ronny Haryanto wrote something like: * Howard Arons [EMAIL PROTECTED] [000713 20:48]: Er, where in Mutt's documentation is there a reference to this "--with-mixmaster option"? I've read the INSTALL or CONFIGURE files, and I don't find it. What other config options have I missed? Try ./configure --help You two are right on the money; ./configure --help was what I was looking for. Now, why is there no mention of the --help argument in the README, INSTALL or CONFIGURE files, I wonder? INSTALL says to tun 'configure' and lists the most useful options, but a mention of --help would be a good idea, IMHO. Thanks for your help. Howard Arons -- Powered by SuSE Linux 6.3 -- Kernel upgraded to 2.2.16 Communications by Mutt 1.2.4i
Re: multipart/alternative formatting
Anton --
...and then Anton Graham said...
%
% There seems to be some "funkiness" in the handling of
% multipart/alternative messages. In particular, the attachments
% which are Content-Type: text/plain and Content-Transfer-Encoding:
% quoted-printable. These frequently come from Outlook (Express) users.
... and that's because they are most frequently the ones who need the
most help. Even though it's marked text/plain, that doesn't mean that
LookOut! users aren't depending on their mailer to autoformat their lines
based on fluctuating window width and such...
%
% This is how mutt displays a single line of the message:
%
% i'm using linux mandrake about 3 month it like me, the firts time install LM in
% +a machine with Win98, now i want to install it with WinNT,
Right; that '+' char is to let you know that mutt had to break the line
for display but it's actually connected to the apparent one above. See
sections 6.3.80 and 6.3.181 of the manual.
%
%
% This is how the same line looks in the message:
%
% i'm using linux mandrake about 3 month it like me, the firts time =
% install LM in a machine with Win98, now i want to install it with WinNT,
Yep; that's the Q-P encoding.
%
% The '=' sign is a sort of "soft-return" that gets dropped in the
% decoding process, resulting in abnormally long lines.
Well, yes and no; it indicates that the mailer which sent it had to break
the line there because it wanted to try to keep it at a reasonable
length, and mutt [properly] reassembles the lines into one long one.
%
% At present, I am dealing with the problem via procmail (see below),
% but I guess my question is, "Shouldn't these soft returns be preserved
% by the receiving client (i.e. mutt)?"
The answer is that they are :-)
%
% # Force multipart/alternative to appropriate column widths
% :0
% * ^Content-Type.*multipart/alternative
% {
% :0 fbBw
% * ^Content-Transfer-Encoding:.*quoted-printable
% | sed -e "s/=$//g"
Are you sure that that shouldn't be "s/= $//" (and you certainly don't
need the /g if you're targeting the end of the line!)? When I have q-p
messages whose lines have been broken, that's what I get...
% }
%
% --
%_
% _|_|_
% ( ) *Anton Graham
% /v\ / [EMAIL PROTECTED]
% /( )X
% (m_m) GPG ID: 18F78541
% Penguin Powered!
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.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" 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: attachments when using IMAP
On Fri, Jul 14, 2000 at 05:17:21PM +0200, Kai Blin wrote:
On Sat, Jul 15, 2000 at 01:27:21AM +1200, Joe Abley wrote:
I have folder and spooldir set to an IMAP-type path, since I don't keep
any mail locally. This works very nicely (mmm, 1.2.4i good) except that
if I try to add a local attachment to a message I'm composing, mutt
looks for the file on the IMAP server rather than looking on the local
filesystem.
Mine isn't. See later.
# imap
set imap_user="jabley"
set folder={maggie.automagic.org}INBOX
Mine's set folder = ~/Mail
set spoolfile={maggie.automagic.org}INBOX
mailboxes {maggie.automagic.org}INBOX
Since I'm using IMAP, too, this doesn't seem to pose a problem. Of course I
don't store my mail on the server where I have a quota. :)
I never keep mail locally. I read mail from the imap server from about
a hundred different places, and I need to keep everything central.
Anything stored locally is effectively lost :)
Perhaps you could change your $folder variable if you want to send an
attachment.
Aaah, I see. So here's the thing:
1. I want folder={maggie.automagic.org}INBOX when I do a "c" to change
folders;
2. I want folder=~ when I do an "a" to add an attachment to a message.
I had a brief moment of clarity and tried this:
macro index c ":set folder={maggie.automagic.org}INBOX^M:change-folder^M"
macro index escc ":set folder={maggie.automagic.org}INBOX^M:change-folder-readonly^M"
macro compose a ":set folder=~^M:attach-file"
but it doesn't seem to work (:change-folder isn't something that mutt
seems to understand). Anybody give me a hand?
Thanks :)
Joe
Re: attachments when using IMAP
On Sat, Jul 15, 2000 at 08:41:12AM +1200, Joe Abley wrote:
Aaah, I see. So here's the thing:
1. I want folder={maggie.automagic.org}INBOX when I do a "c" to change
folders;
2. I want folder=~ when I do an "a" to add an attachment to a message.
I had a brief moment of clarity and tried this:
macro index c ":set folder={maggie.automagic.org}INBOX^M:change-folder^M"
macro index escc ":set
folder={maggie.automagic.org}INBOX^M:change-folder-readonly^M"
macro compose a ":set folder=~^M:attach-file"
but it doesn't seem to work (:change-folder isn't something that mutt
seems to understand). Anybody give me a hand?
I read the manual a bit more and did this instead, which is at least
understood:
# change folder according to whether I'm browsing folders or files
macro index c ":set folder={maggie.automagic.org}INBOX\nchange-folder"
macro index escc ":set
folder={maggie.automagic.org}INBOX\nchange-folder-readonly"
macro compose a ":set folder=~\nattach-file"
This doesn't seem to make any difference to the use of "a?" in the
compose menu, though -- I still get presented with a list of IMAP
folders.
Sorry about the noise. It's just that this is the only thing stopping
me discarding the bloated walrus of pine, so I'm keen to get it working.
Joe
Re: multipart/alternative formatting
On Fri, 14 Jul 2000, David T-G wrote:
... and that's because they are most frequently the ones who need the
most help.
Of course :p
Even though it's marked text/plain, that doesn't mean that LookOut!
users aren't depending on their mailer to autoformat their lines
based on fluctuating window width and such...
I still think that text/plain should be just that: plain :)
Right; that '+' char is to let you know that mutt had to break the line
for display but it's actually connected to the apparent one above. See
sections 6.3.80 and 6.3.181 of the manual.
Yes, I understand that, and appreciate it when receiving preformatted
data as it shows me that the line is a continuation of the previous
without requiring me to scroll right through a 230 character line.
%
% # Force multipart/alternative to appropriate column widths
%:0
% * ^Content-Type.*multipart/alternative
% {
%:0 fbBw
% * ^Content-Transfer-Encoding:.*quoted-printable
% | sed -e "s/=$//g"
Are you sure that that shouldn't be "s/= $//" (and you certainly don't
need the /g if you're targeting the end of the line!)? When I have q-p
messages whose lines have been broken, that's what I get...
Actually, the '=' seems to be hanging at the end without a trailing
space on the ones I receive. (And you're right, I don't need the /g,
it's there through force of habit :)
--
_
_|_|_
( ) *Anton Graham
/v\ / [EMAIL PROTECTED]
/( )X
(m_m) GPG ID: 18F78541
Penguin Powered!
PGP signature
