Re: Google Groups and Spam
Rocco Rutte wrote: Why this? TDMA knows whitelists which means that you can create a whitelist address for a list and subscribe with it. Indeed. Or, you can subscribe with a keyword address which only the MLM will know; list mail will shoot straight to your inbox with no whitelist to maintain. When you post, you can set your envelope sender to the keyword address and tag your From: address as dated. Unfortunately, since Majordomo is broken, I can't enjoy this convenience when posting to mutt-users. I have never used TDMA but I can't imagine that it can only check against the From: header. TMDA looks for a valid sender in From:, Reply-To:, Resent-From:, and the envelope sender address.
verify-key not a function
manual-6.html reads: verify-key c verify a PGP public key But when I enter: :bind pager 'V' verify-key I get verify-key: no such function in map -- Drew
New groups always displayed (VVV-NNTP)
I'm using the VVV-NNTP patch with mutt-1.3.28. How can I disable the displaying of new (not subscribed) groups every time I browse through my subscribed group list? I have to wade through the annoying lot every time I hit Shift-A. -- Drew
Re: New groups always displayed (VVV-NNTP)
To [EMAIL PROTECTED] wrote: How can I disable the displaying of new (not subscribed) groups every time I browse through my subscribed group list? Sigh. I missed show_new_news and show_only_unread in the manual. Maybe all the VVV additions should be moved to a special heading. I also missed http://marc.theaimsgroup.com/?l=mutt-usersm=100331572204846w=2 Thanks for the help! -- Drew
Re: New groups always displayed (VVV-NNTP)
Drew Raines wrote: Drew Raines wrote: How can I disable the displaying of new (not subscribed) groups every time I browse through my subscribed group list? Sigh. I missed show_new_news and show_only_unread in the manual. I retract my self-correction. Even with show_new_news unset, the new groups show up every time I view the group list. The value of nntp_poll matter not, either. -- Drew
VVV-NNTP patch send-hook
What's the equivalent of send-hook when using the NNTP patch? Is there a followup-hook? I'd like to add a header for only news postings. -- Drew
Re: VVV-NNTP patch send-hook
+ David T-G [EMAIL PROTECTED]: An approach that I recall as successful was to set up a send-hook that only triggered when there is no to: field and set the header in there, turning it off (or changing it) otherwise if to: can match anything. I believe the suggestion was something to the effect of send-hook ! . 'my_hdr Blah: foo' with the assumption that a news post would match because it contains nothing in its To: and Cc: fields. Unfortunately, this doesn't actually match any posts. send-hooks do apparenly affect [P]ost's because the following adds Blah: to news postings: send-hook . 'my_hdr Blah: foo' So I guess it's just a matter of figuring out a correct pattern. -- Drew
Re: howto move maildir msgs from new to cur when read?
[EMAIL PROTECTED]: I want mutt to move new messages from new to cur as soon as I've opened them in the pager. It seems that mutts default behavior is to move the messages when I close the mailbox. Why do you need to do this? What problem are you trying to solve?
Mutt 1.3.28 configure problem -- gcc 2.95/Solaris 7
I have built the past 10 releases of Mutt with the exact compiler and
configure options I'm using today. Why does it fail now? I'm still using
gcc, an ANSI-compliant compiler.
$ head -1 VERSION
1.3.28
$ cat CONFIGURE
./configure \
--prefix=/opt/pkgs/mutt-1.3.28 \
--with-slang=/opt/pkgs/slang-1.4.4
$ sh CONFIGURE
creating cache ./config.cache
checking for a BSD compatible install... ./install-sh -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... missing
checking host system type... sparc-sun-solaris2.7
checking for prefix... /opt/pkgs/mutt-1.3.28
checking for gcc... g++
checking whether the C compiler (g++ ) works... yes
checking whether the C compiler (g++ ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether g++ accepts -g... yes
checking for strerror in -lcposix... no
checking for g++ option to accept ANSI C... no
checking how to run the C preprocessor... g++ -E
checking for function prototypes... no
checking for ANSI C header files... yes
checking for string.h... yes
configure: error: Compiler not ANSI compliant
$ gcc --version
2.95.3
$ g++ --version
2.95.3
$ uname -sr
SunOS 5.7
$ pkginfo | fgrep gcc
application SMCgcc gcc
application SMClibgcc libgcc
Re: Mutt 1.3.28 configure problem -- gcc 2.95/Solaris 7
Dominik Mierzejewski [EMAIL PROTECTED]:
What's in the last lines of configure.log?
$ tail -15 config.log
char **argv;
int main() {
return f (e, argv, 0) != argv[0] || f (e, argv, 1) != argv[1];
; return 0; }
configure:1231: checking how to run the C preprocessor
configure:1252: g++ -E conftest.c /dev/null 2conftest.out
configure:1313: checking for function prototypes
configure:1326: checking for ANSI C header files
configure:1339: g++ -E conftest.c /dev/null 2conftest.out
configure:1406: g++ -o conftest -g -O2 conftest.c 15
configure:1433: checking for string.h
configure:1443: g++ -E conftest.c /dev/null 2conftest.out
Command parsing within my_hdr
Inserting a command within a my_hdr doesn't seem to work; should it? my_hdr Reply-To: `/path/to/some-command-output` mutt complains with ``/path/to/some-command-output: unknown command.'' -- Drew
Re: Command parsing within my_hdr
Knute [EMAIL PROTECTED]: my_hdr Reply-To: `/path/to/some-command-output` It wasn't designed to execute commands, though it could trigger a command to be done, depending on that header. Depends on how it is set up. Actually, the above does work. It fails within a send-hook (which is where I need it): send-hook . my_hdr Reply-To: `/path/to/some-command` -- Drew
Re: Command parsing within my_hdr
Knute [EMAIL PROTECTED]: my_hdr Reply-To: `/path/to/some-command-output` It wasn't designed to execute commands, though it could trigger a command to be done, depending on that header. Depends on how it is set up. Actually, the above does work. It fails within a send-hook (which is where I need it): send-hook . my_hdr Reply-To: `/path/to/some-command` -- Drew
Re: Command parsing within my_hdr
Mike Schiraldi [EMAIL PROTECTED]: send-hook . my_hdr Reply-To: '`/path/to/some-command`' I think it was a problem with my regex I was using for the send-hook. All the combinations of output redirections started working. Yeah, that should work. I've been doing that for months and haven't had a problem: send-hook . 'my_hdr X-Last-Reboot: `uptime.pl` I have another question, though. Shouldn't send-hook run the command every time I start to send a message that matches it? It seems to only run it when I source .muttrc. -- Drew
Re: Command parsing within my_hdr
Mike Schiraldi [EMAIL PROTECTED]: send-hook . my_hdr Reply-To: '`/path/to/some-command`' I think it was a problem with my regex I was using for the send-hook. All the combinations of output redirections started working. Yeah, that should work. I've been doing that for months and haven't had a problem: send-hook . 'my_hdr X-Last-Reboot: `uptime.pl` I have another question, though. Shouldn't send-hook run the command every time I start to send a message that matches it? It seems to only run it when I source .muttrc. -- Drew
Re: Command parsing within my_hdr
Michael Elkins [EMAIL PROTECTED]: Use single quotes instead. That will defer the execution until when the hook is activated instead of when the muttrc is parsed. Indeed it does. I usually do that, but didn't know why. I had changed it when trying to determine the problem. Thanks. -- Drew
Re: Re: /var/mail/sean is not a mailbox?
* Sean LeBlanc [EMAIL PROTECTED]: As for injecting SMTP into my machines MTA, I dunno. Without procmail, the data ended up in /var/mail/sean, and not hosed. I don't know if it went via sendmail or some other MTA (I never set up sendmail, either, btw). I doubt it was sendmail. That exerpt you posted earlier started with a Return-Path: header, which is indicative of a Maildir-style delivery. sendmail doesn't do those by default. If you follow the advice of adding the mda line in fetchmail, you should be all right. That will shoot your messages straight to procmail, which you could then debug further. Not knowing what's delivering your messages is making life difficult. -- Drew
Re: IMAP/SSL
* Justin R. Miller [EMAIL PROTECTED]: You need to both set a certificates files in your .muttrc (I think the variable is called certificates) and you need to touch that file so that it exists. Actually, it's certificate_file. Regardless, I tried both, and got: Error in /home/raines/.muttrc, line 14: certificate_file: unknown variable source: errors in /home/raines/.muttrc What gives? -- Drew # certificate_file # # Type: path # Default: # # This variable specifies the file where the certificates you trust are # saved. When an unknown certificate is encountered, you are asked if you # accept it or not. If you accept it, the certificate can also be saved in # this file and further connections are automatically accepted. # # You can also manually add CA certificates in this file. Any server # certificate that is signed with one of these CA certificates are also # automatically accepted. # # Example: set certificate_file=~/.mutt/certificates
Re: IMAP/SSL
* Ralf Hildebrandt [EMAIL PROTECTED]: Dunno. Works for me (the original poster) Ah... I hadn't compiled with SSL when I upgraded to 1.3.23. It works now. -- Drew
my_hdr From: problems
I fear this is something obvious, but I've tried everything I can think of in both 1.2.5 and 1.3.22.1. I can't get my_hdr From: to display anything other than Drew Raines [EMAIL PROTECTED] Everything else works: my_hdr Organization: my_hdr X-Some-Other-Header: ..just not the From: one. I even created a near-blank .muttrc, the only contents being a completely different header: my_hdr From: [EMAIL PROTECTED] (Not Even My Name) and it still displayed the former. What am I missing? -- Drew
Re: my_hdr From: problems
* darren chamberlain [EMAIL PROTECTED]: I think you have to do: my_hdr From [EMAIL PROTECTED] (Not Even My Name) not From:. Tells me it's an invalid header field if I do that. -- Drew
Re: my_hdr From: problems
* Not Even My Name [EMAIL PROTECTED]: my_hdr From: Not Even My Name [EMAIL PROTECTED] But why can't I use the other style? Elkins uses it in the 1.2.5 documentation every time he mentions an alias or my_hdr. Technically I should be able to put whatever I want, no? It shouldn't even have to include an email address... -- Drew
shell escape (!) oddity
I press ! to execute a shell command, and if I press enter at the prompt instead of a command, it kicks me out of mutt without saving. If this is the desirable behavior, will someone explain why? -- Drew
Re: shell escape (!) oddity
* Danny O'Brien [EMAIL PROTECTED]: You don't get kicked out - mutt forks a new shell. Type 'exit' or ctrl-D to return to your previous mutt enjoyment. Ah. That would explain why one day when I was confirming this behavior, there were many, many mutt processes running :) Thanks. -- Drew
pipe-message binding
For some reason, my pipe-message binding doesn't work. I checked the manual, and it's supposed to be mapped to '|' by default. If I do a '?' from the index, it is indeed listed as an unbound function. I tried manually setting it in my .muttrc with bind index '|' pipe-message bind pager '|' pipe-message but it remains unbound. Any ideas? I'm growing weary of typing :push pipe-message. I'm using 1.3.22.1, but I notice this behavior with 1.3.20 and 1.2.5 as well. -- Drew
Re: selective message deletion
* Charles Cazabon [EMAIL PROTECTED]: Or getmail at the link in my .sig. Charles I'll second that motion. getmail is much more straightforward to set up, with a cleaner configuration file. It doesn't have ridiculous default options like SMTP injection instead of MDA delivery, a la fetchmail. -- Drew
Re: alternates regexp
* Kyle Knack [EMAIL PROTECTED]: Apparently that doesn't work well (even with the '.' escaped), nor does: set alternates = (phineas@only-linux|skwerl@telocity|skwerl@eathlink|skerl-0@home) with or without quotes. Try removing the parentheses: set alternates=[EMAIL PROTECTED]|[EMAIL PROTECTED] My alternates setting works fine that way. -- Drew
Re: alternates regexp
* Drew Raines [EMAIL PROTECTED]: set alternates=[EMAIL PROTECTED]|[EMAIL PROTECTED] My alternates setting works fine that way. In addition, I have my '@' symbols escaped. set alternates=phineas\@only-linux.com|skwerl\@telocity -- Drew
folder-hook problem
Forgive me if this has been asked before, but what's wrong with this line
in my muttrc:
folder-hook outbox.*$ set index_format=%4C %Z %{%b/%d} %-20.20F (%4c) %s
It tells me that %Z is an unknown variable, and proceeds to only shows
message numbers in the index once I change to an outbox* folder (the %4C is
only working, I guess).
However, if I change to the folder and type
:set index_format=%4C %Z %{%b/%d} %-20.20F (%4c) %s
manually, everything is displayed the way I want it to.
I have tried it with 1.2.5 and 1.3.19 with the same result.
What gives?
--
Drew
Re: folder-hook problem
* Andre Wyrwa [EMAIL PROTECTED]:
Just a guess, but how about this one:
folder-hook outbox.*$ 'set index_format=%4C %Z %{%b/%d} %-20.20F (%4c) %s'
I am a moron. Yep, that works. I've seen a hundred people do that before
on this list, too.
Thanks, Andre.
--
Drew (banging head)
FCC lines header?
Okay, so I want to use maildirs. I can use the procmail hack to add the Lines header for incoming messages. What about outgoing messages? Can I pipe to safecat or a wrapper from a send-hook command? The manual didn't really suggest this, so I figured it's not recommended. Anybody have another approach? -- Drew
Re: Limiting Folder view
* Biju Chacko [EMAIL PROTECTED]: I would like to limit the list of mailboxes in the folder browser to those that have new mail. Is this possible? If so, how? Utilize the magical Tab key. -- Drew
Re: Limiting Folder view
* Benjamin Reed [EMAIL PROTECTED]: Just a suggestion, you may want to make it so that the capitalization is always uppercase in the manual, since in some places it's TAB and some it's tab. I saw it referenced as tab, so that's what I grepped for. grep -i [ ]tab[ ] -- Drew
Re: Mark as Read
* Carl B . Constantine [EMAIL PROTECTED]: How can I tell mutt to mark email as read. Wn This unsets the new flag. You could also tag multiple messages and ;Wn -- Drew
Re: Limiting Folder view
* Ailbhe Leamy [EMAIL PROTECTED]: Utilize the magical Tab key. My only real problem with this is that I want it to display only those mailboxes which actually contain new mail. You're allowed to press it more than once. -- Drew
Re: Limiting Folder view
* Drew Raines [EMAIL PROTECTED]: * Ailbhe Leamy [EMAIL PROTECTED]: My only real problem with this is that I want it to display only those mailboxes which actually contain new mail. You're allowed to press it more than once. My apologies to the list. I see what you mean now. I was thinking that after the second tab mutt displays folders with new mail, but it displays `mailboxes' whether or not they contain new mail. The suggestion about the reverse-date setting sounds appropriate. -- Drew
Re: viewable headers
* Richard G. Ball [EMAIL PROTECTED]: I have a number of headers that I'd like to have mutt (V1.2.5i) show (without having to see *all* of the headers) but I can't find any way to tell mutt to do this. Is this not available? It is available. Look in the manual for ignore and unignore commands. http://www.mutt.org/doc/manual.txt A common approach is to ignore all the headers, and then unignore the ones you want to see: ignore * unignore Date: From: To: CC: -- Drew
Re-read muttrc?
Is there anyway to restart mutt or have it reread the muttrc within the program? -- Drew
