Re: removing Reply-To when composing
On Sat, Sep 02, 2000 at 02:26:38AM +0200, Attila Csosz <[EMAIL PROTECTED]> wrote: > How to control which fields get into the editor when composing? I don't want > the Bcc, and the Reply-To lines in the editor when composing messages. To my knowledge, there's no built in way. However, you can either tell your editor to remove them, or write a short script that strips those lines and then calls your editor, and then set editor=your-script. -- Bob Bell <[EMAIL PROTECTED]> - "Who is General Failure and why is he reading my hard disk?" -- Anonymous
Re: Creating mailboxes in 1.3.8
That bug has been fixed in CVS. Sorry about that, though. On Friday, 01 September 2000 at 17:44, Ben Beuchler wrote: > If I attempt to save mail to a non-existent IMAP folder, I get this > error: > > imap_copy_messages [a0894 NO [TRYCREATE] Mailbox does not exist.] > > instead of mutt nicely offering to create the folder for me. If, > however, I switch to the 'change folder' screen I can create IMAP > folders without difficulty via the 'C' command. > > For what it's worth, I'm using Courier IMAP v0.33a and mutt 1.3.8i. > > Thanks, > Ben > -- Don't make Godzilla mad! PGP signature
Re: A wish for a new configure flag.
On Fri, Sep 01, 2000 at 10:04:42PM -0500, Jeremy Blosser wrote: > Brian Salter-Duke [[EMAIL PROTECTED]] wrote: > > I know little or nothing about configure so could not start to do this > > myself. Would it be possible to have a configure flag called something > > like --compile-only?. This would merely compile mutt and nothing else. I > > find I often do a complete install and then with the same version I want > > to do something that changes mutt only - not the docs, not the language > > support, not mutt-docklock, etc. I may want to try ncurses after the > > first compile was with slang. I may want to try enabling another option > > such as pop3. I may want to apply a patch. Now in some cases one can get > > away without doing "make distclean" in other cases one has to go back > > to a new configure run. I believe it would be quite usefull. > > > > Of course it may already be possible and I have missed it! > > I think this is what 'make mutt' is for. This does not quite do what I want. If you have done "make distclean" and then done a new configure, you have lost libintl.a. "make mutt" does not create libintl.a. You have to "cd intl; make", and then "make mutt" works. Maybe the fact that this does not work is a bug in the construction of the main Makefile. This was with 1.2.5. Brian. > -- > Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ > -+-+-- > the crises posed a question / just beneath the skin > the virtue in my veins replied / that quitters never win -- Associate Professor Brian Salter-Duke (Brian Duke) [EMAIL PROTECTED] School of Biological, Environmental and Chemical Sciences, SITE, Northern Territory University, Darwin, NT 0909, Australia. Phone 08-89466702. Fax 08-89466847 http://www.smps.ntu.edu.au/school/compchem.html
Re: A wish for a new configure flag.
Brian Salter-Duke [[EMAIL PROTECTED]] wrote: > I know little or nothing about configure so could not start to do this > myself. Would it be possible to have a configure flag called something > like --compile-only?. This would merely compile mutt and nothing else. I > find I often do a complete install and then with the same version I want > to do something that changes mutt only - not the docs, not the language > support, not mutt-docklock, etc. I may want to try ncurses after the > first compile was with slang. I may want to try enabling another option > such as pop3. I may want to apply a patch. Now in some cases one can get > away without doing "make distclean" in other cases one has to go back > to a new configure run. I believe it would be quite usefull. > > Of course it may already be possible and I have missed it! I think this is what 'make mutt' is for. -- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- the crises posed a question / just beneath the skin the virtue in my veins replied / that quitters never win PGP signature
A wish for a new configure flag.
I know little or nothing about configure so could not start to do this myself. Would it be possible to have a configure flag called something like --compile-only?. This would merely compile mutt and nothing else. I find I often do a complete install and then with the same version I want to do something that changes mutt only - not the docs, not the language support, not mutt-docklock, etc. I may want to try ncurses after the first compile was with slang. I may want to try enabling another option such as pop3. I may want to apply a patch. Now in some cases one can get away without doing "make distclean" in other cases one has to go back to a new configure run. I believe it would be quite usefull. Of course it may already be possible and I have missed it! Cheers, Brian. -- Associate Professor Brian Salter-Duke (Brian Duke) [EMAIL PROTECTED] School of Biological, Environmental and Chemical Sciences, SITE, Northern Territory University, Darwin, NT 0909, Australia. Phone 08-89466702. Fax 08-89466847 http://www.smps.ntu.edu.au/school/compchem.html
A pop3 question.
I get a small amount of mail at work on a POP3 server and have been getting it to my unix machine, rather than my PC, when out of the office by fetchmail. Works fine. I have just tried compiling 1.3.8 with --enable-pop and that works fine too. However I have two questions:- 1. G is bound to fetch-mail but only in the index. How do I change this.? I tried bind generic F fetch-mail in muttrc and it told me on calling mutt that there was an error in muttrc with fetch-mail. I would like to use F in the index and in the folder index. What am I doing wrong? 2. The messages I get go into my ~/Mailbox, which I hardly use as procmail put everything to folders in ~/Mail. Is there any way of getting the mail to go somewhere else or better to feed it to procmail? Cheers, Brian. -- Associate Professor Brian Salter-Duke (Brian Duke) [EMAIL PROTECTED] School of Biological, Environmental and Chemical Sciences, SITE, Northern Territory University, Darwin, NT 0909, Australia. Phone 08-89466702. Fax 08-89466847 http://www.smps.ntu.edu.au/school/compchem.html
removing Reply-To when composing
How to control which fields get into the editor when composing? I don't want the Bcc, and the Reply-To lines in the editor when composing messages. Thanks Attila -- -- - Mail: [EMAIL PROTECTED]; Debian 2.2 Linux / 2.2.13 / exim- - Get my PGP key: gpg --keyserver keys.pgp.com --recv-key 0x2cc33acb -
Mutt+Cygwin [Re: M$ dog]
> > It boils down to mutt's UNIX-like behavior of expecting other pieces to > > be there; all mutt does is read mail, and it sucks less at that than > > anything else. The biggest problem people often quote is the lack of > > an MTA, since mutt does not talk directly to the MDA on the recipient > > machine via SMTP port 25, as I believe PINE does. It doesn't help that > > Win doesn't handle subshells gracefully and so things like PGP can be > > tricky as well, as I understand it. > > There's another problem: \r\n end-of-lines. Mutt doesn't use > O_TEXT/O_BINARY, and gets confused when CygWin translates \r\n to \n > thus unexpectedly reducing message size. At least I think that's why > Mutt segfaults in the pager on Win32. I have posted stack traces on > mutt-dev, but the developers have enough problems on Unix, and didn't > have time to investigate Win32 issues. Mutt compiles and runs right out of the box together with Cygwin and ncurses. The \r\n problem is probably that you have mounted your mail directory as "text"; mount it as "binary" and it works beautifully. If you then can do with ssmtp to send your mails you have no troubles. /Ulf -- [EMAIL PROTECTED]
Creating mailboxes in 1.3.8
If I attempt to save mail to a non-existent IMAP folder, I get this error: imap_copy_messages [a0894 NO [TRYCREATE] Mailbox does not exist.] instead of mutt nicely offering to create the folder for me. If, however, I switch to the 'change folder' screen I can create IMAP folders without difficulty via the 'C' command. For what it's worth, I'm using Courier IMAP v0.33a and mutt 1.3.8i. Thanks, Ben -- Ben Beuchler [EMAIL PROTECTED] MAILER-DAEMON (612) 321-9290 x101 Bitstream Underground www.bitstream.net
TERM problem
This is not a mutt problem per se but more a terminal problem whose only (current) symptom is mutt not sizing/coloring correctly - all other apps fine. So I am using this as the excuse to ask it here (where I know the answers will be). two machines - problem only with machine2: TERM=xtermTERM=linux ---- machine1 irrelevantmutt full size color *desired* machine2 mutt full size monchrome mutt 24 LINES and color What should I do to machine2 to get mutt full size and in colour - possibly migrate the linux terminfo? (I am accessing both machines with an ssh client putty.) thanx Eric Smith
Re: mutt and qmail
On Thu, Aug 31, 2000 at 12:10:31PM -0700, Jason Helfman wrote:
> don't you find the file structure of this just horrid though?
To be perfectly honest, I don't ever see the structure during normal
use. The *only* time I have to think about it is when I write a script
that manipulates the files in those directories (./cur, primarily).
My (shortened) 'subscribe' and 'mailboxes' lines are as follows. Note
that there are no references to ./cur or ./new or ./tmp.
subscribe qmail mutt-users freebsd-stable
mailboxes +Inbox +Bedtime +Qmail +Mutt-Users +FreeBSD-STABLE
When I hit , Mutt shows me the top-level Maildiers, 'Inbox',
'Bedtime', etc.
The only time I can imagine you'd notice the directory structure is if
you read your mail with /usr/bin/more!
On the other hand, what you don't see is what gives the advantages so
ably detailed by Charles and Mikko in other responses (thanks guys!).
It's just a choice; it's not the end of the world either way. For me, I
live in an apartment where the landlord turns the power off at random
intervals to "fix" things. I'd rather not lose the mail and Maildirs
can guarantee that.
> To have new/ tmp/ cur/ for every mailing list? I would like to and would
> perfer to use maildir for the mailing lists, I don't know why...
What shows up in Mutt is the normal index, with mail that is in the
./new directory threaded appropriately and marked with a 'N'. You don't
see ./new, ./cur or ./tmp. So, ultimately, who cares?
> What are the advantages to this... I have all my mailing lists still
The advantages have been explained in other messages (Charles and
Mikko). I won't make this long message even longer repeating them.
> going to mbox, whereas anything that doesn't pass through the filters
> goes to Maildir format. I would like to see the scripts that you have in
> both procmail and your backing procedure.
Sure. My $HOME/.qmail file reads:
| preline /usr/local/bin/procmail
A snippet from the message list recipes:
:0
* ^TO_qmail
Qmail/
:0
* ^TO.*stable
FreeBSD-STABLE/
:0
* ^TO_mutt-users
Mutt-Users/
Notice that, again, there is no reference to ./new, ./cur or ./tmp. This
is because procmail, as of version 3.14, delivers to Maildirs - it
understands how to move messages into ./new. It identifies destination
Maildirs by the trailing '/' on the folder name.
Finally, here's a very simple script I run from cron (around 3am Monday
mornings, IIRC) that just copies messages older than 3 weeks into a
gzipped tar with the same name as the Maildir. You may have noticed I
always capitalize my Maildirs - the script uses that assumption to
generate the list of Maildirs to archive ([A-Z]*). For any use other
than personal, this could be cleaned up/enhanced a lot. Anyhow, for what
it's worth...
#!/bin/sh
# mailarc.sh
tmpdir=$HOME/tmp/temp$$
mkdir $tmpdir
cd $HOME/Mail
for mdir in [A-Z]* ; do
/usr/bin/find $mdir/cur -mtime +21 -exec /bin/mv {} $tmpdir/ \;
archive=$HOME/Mail/archive/$mdir.tar
if [ -f $archive.gz ] ; then
createorappend=r ;
/usr/bin/gunzip $archive.gz ;
else
createorappend=c ;
fi
/usr/bin/tar -$createorappend -f $archive --directory $tmpdir .
/usr/bin/gzip $archive
rm -f $tmpdir/*
done
rmdir $tmpdir
I find this system quite workable. As always, YMMV :-)
Tim
--
Tim Legant
[EMAIL PROTECTED]
Re: defining a macro to "sz" an attachment
On 31-Aug-2000, Michael Elkins wrote: > On Thu, Aug 31, 2000 at 08:04:23AM -0500, John Buttery wrote: > > Basically, the end result is that if I have a file called > > "stressre1.exe" (for example) attached to an email, I can write a macro > > that when invoked will do "sz stressre1.exe" as if I had saved the > > attachment, exited mutt, and typed that at the shell. > > This is not currently possible. I'm not even sure how you would script that > sort of functionality either, because you'd have to have some language > constructs that say 'get-me-the-name-of-message-102-attachment-1', which > would be rather difficult. Your best bet is to just create a shell script > which does this that you can pipe a file to and executes what command you > want. You can just pick a temporary file name. Well, there's always the handy trick of defining specific mime types as handled by sz. I use this for my wife's login so that she can easily transfer pictures from her unix shell to her windows machine. I simply placed this line in ~/.mailcap: image/*; sz '%s' so when she selects an image from within mutt, it sz's it to her (which SecureCRT handles quite seamlessly). I presume you could tweak the "image/*" part to catch whatever particular type of file you want to sz. -- |David McNett |To ensure privacy and data integrity this message has| |[EMAIL PROTECTED]|been encrypted using dual rounds of ROT-13 encryption| |Birmingham, AL USA|Please encrypt all important correspondence with PGP!| PGP signature
