Re: Reducing duplication
Date: Tue, 20 Aug 2002 15:31:28 -0600 From: Rob 'Feztaa' Park [EMAIL PROTECTED] Subject: Re: Reducing duplication To: Mutt Users List [EMAIL PROTECTED] Alas! darren chamberlain spake thus: Or skip your sent-mail folder altogether. I wanted to avoid this for portability; if I just skip my own sent mail folder, then I'm limiting the script to my own machine. I want it to work for other people as well ;) make it a parameter, then. (not an answer either, sorry) -- FreeBSD 4.6-STABLE 9:06AM up 14:59, 7 users, load averages: 0.00, 0.00, 0.00
Re: CC: folder-hook with same From:
Michael Tatge [EMAIL PROTECTED] wrote: Umm, I'm puzzled. If I use the -F /dev/null how do I get the folder-hook readen which don't work properly. Enter them? Source a file which contains these hooks only? Hmm removing the list from 'set alternates' helped *blush*, thanks for your patience. -- ++ytti
Re: Reducing duplication
Rob -- ...and then Feztaa said... % % Hey all ;) Hi! % % I have a bit of a problem -- Oooh, this just *begs* a smartass response... % ... % So what I want to know is, is there a way to get mutt to save messages % to sent-mail only if it's not addressed to a mailing list that I'm % subscribed to? I don't think you'll be able to do it except with long fcc-hook rules, which means you probably want to parse your muttrc file(s) to generate them. Something like fcc-hook . =%O# store in original target fcc-hook mutt-users /dev/null fcc-hook lfs-general /dev/null fcc-hook yetanotherlist /dev/null ... and so you'd be sure to write your subscribe line so that the list To: address matched so that you could parse it out. Personally I think it would be easier to just let mutt write the fcc as usual but make =mutt-users a symlink to /dev/null for each target address whose mail you don't want to store. Then, again, I'm the kind that keeps his outgoing posts regardless of whether or not I keep the incoming version :-) % % -- % Rob 'Feztaa' Park % http://members.shaw.ca/feztaa/ % -- % Darth Vader sleeps with a Teddywookie. 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! msg30395/pgp0.pgp Description: PGP signature
Re: Complex fcc-hook?
Ryan -- Gee, it must be fcc-hook day on the list... ...and then Ryan Sorensen said... % % I have procmail and mutt set up so mails for lists are automatically put % in =lists/listname, and mutt recognizes every subdirectory name in that % directory as a list. Not bad. % % listname is the part before the @, like mutt-users for this one. Hokay. % % Default save for other things, people, mainly, is in =people/name, where % again, name is the part before the @. OK. % % How can I create fcc-hooks to put sent mail in the right directories? I'd try something like fcc-save-hook . =people/%O# use original target but in this subdir fcc-save-hook (list1|list2|...) =lists/%O for starters. Since you have all of your list mail separated out, you could have a script walk the directory and generate the list hook(s), and all you have to do is ensure that you get the first list post (if you post before you receive) saved into the right directory and then let your muttrc handle it all again. 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! msg30396/pgp0.pgp Description: PGP signature
Re: New mail notification problems
Ken, et al -- ...and then Ken Weingold said... % ... % % I don't have a setting for mark_old at all. I see sometimes something % flash about new mail, but the status bar never says anything, or % moving the indicator bar or something makes it disappear. Could the % server (Panix) be running something that is messing up mutt with % respect to reporting new mail? It's certainly possible... Forgive the upcoming review of how mutt determines the new-mail-ness of a folder, but since this has been discussed numerous times and the question still comes up it seems worth it. When a mail folder is read, it access time (atime) is updated. That clears the count, so to speak, and mutt figures that that's the last time the folder was seen and so that's the time to beat for new mail. When a mail folder is written, such as by new mail delivery, the modification time (mtime) is updated. mutt compares the mtime with the atime and if the former is later then it figures you have had new mail arrive and it so marks the folder. This method of checking is a good thing, because it doesn't matter how big the folder is; the time to check is fixed. It is not so good, though, because anything that updates the atime will break it. Past experience has shown that there are *lots* of things that can update the atime. Your mission, should you choose to accept it, is to find what's doing that and stop it. It could be your shell, a biff program, a backup program, or who knows what. You can test out this theory by using touch to update the atime backwards or the mtime forwards to force the new mail condition and then have mutt look at it and see whether or not it's flagged. Hey, it's possible that your mutt has a problem; let's find out. You may recall your own problems with this on your nfs-mounted mail spool some time back. Another possibility is that the disk server's clock and the login server's clock are not in sync. % % Thanks. HTH HAND % % % -Ken Man, it must be put things in quotes day here at my house. Weird. :-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! msg30397/pgp0.pgp Description: PGP signature
Re: octal character display
* Richard Curnow [EMAIL PROTECTED] [2002-06-17 13:27 (CEST)] Yes, yes, old thing, but I do reply this because I've been two months offline (due to relocation) and is a question that raises in the list many times. ./configure --without-wc-funcs --enable-locales-fix --prefix=whatever --with-slang If I don't use --without-wc-funcs, the system's mbrtowc() and friends are used, which don't seem to play ball. (In this case, the octal string comes from pager.c:1071). Presumably the system's mbrtowc() and isprint() are both saying 8th bit set is bad based on something in the locale. But what? If I strace mutt, I can't even find any accesses being attempted to files in /usr/share/i18n/locale/... or /usr/share/locale/..., which suggests glibc isn't even trying any locale lookups. BTW this is slackware 8.0, (glibc 2.2.3 I think), if anyone else is trying to experiment in this area. Anyway, problem solved (if not very elegantly). FYI, and perhaps to improve a FAQ... I've had the very same problem, and the very same dirty-hack did solve it, but then I upgraded, and I thought that it wasn't nice to do that for every upgrade/update, so... I looked for the real problem that is written somewhere in the glibc-dev doc (IIRC). I haven't correctly installed the new locales debian package, as glibc 2.2 introduced some little changes there (AFAIK). I did it the right way and then I was unable to get the error back. -- ais GnuPG key: 0x5C4839A5 Registered LiNUX user #93375 ~ You can't assign IP address 127.0.0.1 to the loopback adapter, because it is a reserved address for loopback devices (Microsoft Windows XP - P R O F E S S I O N A L) msg30398/pgp0.pgp Description: PGP signature
Re: Complex fcc-hook?
msg.pgp Description: PGP message
mailbox limitation
Greetings! How many messages can normally display/work with mutt ? -- Best regards, Oleg Lukashin mailto:[EMAIL PROTECTED]
Re: not a mailbox - check the folder
* Sven Guckes ([EMAIL PROTECTED]) wrote: because that file/folder is not a mailbox. ;-) does the same happen when you try to start mutt on the folder directly? mutt -f ~/mail/Inbox does that file start with From_? or does it happen to start with an empty line? but if you are using maildir style then try: mutt -f ~/mail/Inbox/ more info! Sven Problem is solved. There was an unknown (for me) error. I've erased old inbox and after creating new all things become working. Still have no idea what to happen... maybe I'd to check them with diff -ruN. -- Best regards, Oleg Lukashin mailto:[EMAIL PROTECTED]
Re: mailbox limitation
On Wed, Aug 21, 2002 at 04:06:13PM +0400, Oleg Lukashin wrote: How many messages can normally display/work with mutt ? I've used mailboxes with over 50,000 messages with no problem at all. A bit slot to open (depending on the machine of course), but quite usable. -- Dan Boger [EMAIL PROTECTED] msg30402/pgp0.pgp Description: PGP signature
Re: New mail notification problems
On Wed, Aug 21, 2002, David T-G wrote: You may recall your own problems with this on your nfs-mounted mail spool some time back. Another possibility is that the disk server's clock and the login server's clock are not in sync. Different server completely. :) Thanks for the explanation, David. I will look into it. -Ken
Re: send-hook and subject
+[ Asi hablaba Aaron Schrab ([EMAIL PROTECTED]): | | At 16:39 -0300 20 Aug 2002, Fernan Aguero [EMAIL PROTECTED] wrote: |Is it possible to use a send hook to set the subject? | | No. To quote the manual: | | ] Note: the send-hook's are only executed ONCE after getting the initial | ] list of recipients. Adding a recipient after replying or editing the | ] message will NOT cause any send-hook to be executed. Also note that | ] my_hdr commands which modify recipient headers, or the message's | ] subject, don't have any effect on the current message when executed | ] from a send-hook. | +] Thanks Martin and Aaron. Setting/unsetting autoedit does not help. I had already tried that, and edit_headers also ... Seems that it is not possible. I will stop experimenting. Still I'm curious why once in a very while, the subject will get set by the send hook ... a bug? Thanks for your reply, Fernan -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan -BEGIN GEEK CODE BLOCK- Version: 3.1 GS d- s:+ a C++ BU++ P+++ L- E- W+++ N o? K? w- !O M+ !V PS+ PE Y+ PGP t- 5? X- R- tv+ b++ DI+ !D G e h r+++ y+++ --END GEEK CODE BLOCK--
Re: Mutt color limitations
On Wed, Aug 21, 2002 at 12:57:21AM +0100, Lee J. Moore wrote: | 'brightwhite' creates *bold* white text, whereas 'white' creates | grey text FWIW, I've seen in the gnome-terminal palette that white really is grey, and brightwhite is really white. The solution there is to tweak the terminal so that the palette matches what I want it to be. I, for one, would like the flexibility that lots of colors allow, in particular for vim's syntax highlighting of xml and email. However it seems that X is required for that (gvim does a better job than 'vim'). -D -- All a man's ways seem innocent to him, but motives are weighed by the Lord. Proverbs 16:2 http://dman.ddts.net/~dman/ msg30405/pgp0.pgp Description: PGP signature
mutt and mail archives
Hi again, I have currently about 300 M in my ~/mail dir. Perhaps many of you have still more. Not that disk space is scarce ... but I'd like to keep old mail in an organized mail archive (perhaps using the same organization of mailboxes, but also separated by year/month whatever). Before reinventing the wheel I've been searching the net for some scripts and it seems that there are some that could be useful (I'm using maildir). Now my question is, in the event I need to access/search this archives is mutt able to read compressed files? If so, what would be the recommended storage (so that mutt will read them later)? I'm open to suggestions about other alternatives. Thanks, Fernan -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan -BEGIN GEEK CODE BLOCK- Version: 3.1 GS d- s:+ a C++ BU++ P+++ L- E- W+++ N o? K? w- !O M+ !V PS+ PE Y+ PGP t- 5? X- R- tv+ b++ DI+ !D G e h r+++ y+++ --END GEEK CODE BLOCK--
mutt-nntp from cron
Hi! I'm using Orjan's nntp-patch and am very happy with it. As I'm on a dial-up connection most of the time, I'm using the offline mode which spools outgoing posts to a file, and NNTPPost delivers it when triggered from a script in /etc/ppp/ip-up.d/ (Debian). Another script there fetches mail, executing /usr/bin/mutt -R -F /etc/muttnewsrc as user, with /etc/muttnewsrc being folder-hook . push Bxy so mutt starts read-only non-changing mailboxes, doing B which fetches the news, and then quits non-changing. So this works, the same when /usr/bin/mutt -R -F /etc/muttnewsrc is executed from the command line as user. The problem is, it doesn't work when executed from a user's crontab. I edit it with crontab -e and add */2 * * * * /usr/bin/mutt -R -F /etc/muttnewsrc /dev/null 21 (one line). The /dev/null 21 part is to prevent cron from sending mail on job execution. What am I missing here? -Andre msg30407/pgp0.pgp Description: PGP signature
Re: mutt and mail archives
On Wed, Aug 21, 2002 at 11:06:42AM -0300, Fernan Aguero wrote: Now my question is, in the event I need to access/search this archives is mutt able to read compressed files? If so, what would be the recommended storage (so that mutt will read them later)? there is a compressed-folder patch, linked from mutt.org - I've used it successfully for a few years now :) HTH! -- Dan Boger [EMAIL PROTECTED] msg30408/pgp0.pgp Description: PGP signature
Re: Mutt color limitations
On Wed, 21 Aug 2002, Derrick 'dman' Hudson wrote: On Wed, Aug 21, 2002 at 12:57:21AM +0100, Lee J. Moore wrote: | 'brightwhite' creates *bold* white text, whereas 'white' creates | grey text FWIW, I've seen in the gnome-terminal palette that white really is grey, and brightwhite is really white. The solution there is to tweak the terminal so that the palette matches what I want it to be. As I said, the background colour can appear as black, despite the fact that it's suppose to be white. Changing the foreground colour will bizarrely change the background colour to one that wasn't stated, for god knows what reason. As for the terminal, this is the Gnome2 Terminal in which you can switch easily between it's own palette (Linux Console), Xterm, Rxvt, and even custom. Switching between them updates the colours in running apps in front of your eyes. Also - there is no difference whether I'm using other (non-Gnome) terminals. Mutt will not accept color8 and above, nor even things like lightgray, which a few documents I've read claim Mutt *should* accept when compiled with slang. On the contrary, slrn renders all sixteen colours without a problem. [..] -- Lee J. Moore http://www.leej.dsl.pipex.com -- Powered by Gentoo (Portage 2.0.28) msg30409/pgp0.pgp Description: PGP signature
Re: send-hook and subject
* Fernan Aguero [EMAIL PROTECTED] [2002-08-21 10.51 -0300]: This is weird. I have 'unset autoedit' in my muttrc, and the send-hook 'send-hook @visit\.se$ my_hdr Subject: shazam! However, it doesn't work unless I specifically type :unset autoeditenter in mutt. Strange. Is this just me? Can anyone verify this? -- _ Martin Karlsson ( ) \ ASCII Ribbon Campaign / \Against HTML and proprietary attachments in e-mail msg30410/pgp0.pgp Description: PGP signature
Re: Reducing duplication
--EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alas! David T-G spake thus: % So what I want to know is, is there a way to get mutt to save messages % to sent-mail only if it's not addressed to a mailing list that I'm % subscribed to? =20 I don't think you'll be able to do it except with long fcc-hook rules, which means you probably want to parse your muttrc file(s) to generate them. Something like =20 fcc-hook . =3D%O# store in original target fcc-hook mutt-users /dev/null fcc-hook lfs-general /dev/null fcc-hook yetanotherlist /dev/null ... =20 and so you'd be sure to write your subscribe line so that the list To: address matched so that you could parse it out. That ought to be easy. I'm already using a perl script to generate my muttrc, all I have to do is take my 'subscribe' array and use it in the fcc hooks ;) Personally I think it would be easier to just let mutt write the fcc as usual but make =3Dmutt-users a symlink to /dev/null for each target addre= ss whose mail you don't want to store. Then, again, I'm the kind that keeps his outgoing posts regardless of whether or not I keep the incoming version :-) Huh? You want me to make a file that's either a file or a symlink depending on what's accessing it? --=20 Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- You've got to have a gimmick if your band sucks. -- Gary Giddens --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9Y+x6PTh2iSBKeccRAuMWAJwI2Gm2YRXyKNkmUIxaLcBSmgXq5wCfRJae 6BqJjJ+17VAdC01yWAORz3Y= =SfJm -END PGP SIGNATURE- --EVF5PPMfhYS0aIcm--
Re: Reducing duplication
--CE+1k2dSO48ffgeK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! David T-G spake thus:
I don't think you'll be able to do it except with long fcc-hook rules,
which means you probably want to parse your muttrc file(s) to generate
them. Something like
=20
fcc-hook . =3D%O# store in original target
fcc-hook mutt-users /dev/null
fcc-hook lfs-general /dev/null
fcc-hook yetanotherlist /dev/null
...
=20
and so you'd be sure to write your subscribe line so that the list To:
address matched so that you could parse it out.
I managed to get it working like this:
foreach my $ml (subscribe)
{
print fcc-hook $ml /dev/null\n;
}
print fcc-hook . =3Darchives/$datestring-sent-mail\n;
Thanks ;)
--=20
Rob 'Feztaa' Park
http://members.shaw.ca/feztaa/
--
Oh no, not again.
-- Manoj Srivastava
--CE+1k2dSO48ffgeK
Content-Type: application/pgp-signature
Content-Disposition: inline
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9Y++9PTh2iSBKeccRApsHAJ9Z5CPWWN+BrJpiobYl4sL3taYL6QCfQYsF
0UAvAR/jlSF4UsxdPwTbj2Q=
=ZU90
-END PGP SIGNATURE-
--CE+1k2dSO48ffgeK--
Re: mutt and mail archives
* Fernan Aguero [EMAIL PROTECTED] [2002-08-21 14:05]: I have currently about 300 M in my ~/mail dir. .. Not that disk space is scarce ... but I'd like to keep old mail in an organized mail archive (perhaps using the same organization of mailboxes, but also separated by year/month whatever). Before reinventing the wheel I've been searching the net for some scripts and it seems that there are some that could be useful (I'm using maildir). i wonder what you're searching for as whatever is too vague an order for a program to store data. anyway, i have 5678 folder by now (no, i'm not making up that numer) and messages are simply stored by username. adding more folder by sperating them into months does not sound like a good diea to me. ;-) Sven
Re: New mail notification problems
* On Mon, 19 Aug 2002, John Iverson wrote: The only known issue (afaik) about Mutt *not* reporting new mail is when the user has unset mark_old in their configuration. In this case a message that would ordinarily be marked as old is still new, but won't be detected with the file modification/access time heuristic. I don't know if it's related, but I've noticed the following behavior which was briefly discussed here before: When you switch from Mailbox A (index or pager view) to the folder list view, Mutt won't show the N flag next to Mailbox A when there is new mail in it. It doesn't seem to matter whether the new mail was already there or if it arrives while in folder list view. If you then switch to Mailbox B and back to folder view, the N flag for Mailbox A works again (but now Mailbox B has the same issue). Can anyone say whether this is a feature or bug? I'm using Maildir folders with set mark_old=no, if that's relevant. How about this question, then: Does anyone's Mutt correctly indicate new mail in Mailbox A in the above scenario? If it's normal behavior and not a bug in my setup, I suspect Mutt considers that you are still viewing Mailbox A until you choose another one, and this has something to do with it. But the mailbox browser screen is misleading in this case, to me. Maybe a special current mailbox symbol next to Mailbox A would be better than just nothing, which wrongly indicates the lack of new mail. -- John
Re: Complex fcc-hook?
On Wed, Aug 21, 2002 at 04:09:59AM -0700, Ryan Sorensen wrote: For an odd reason, fcc-save-hook seems to be order dependent.. The default hook'll override the specific one there. folder-hook doesn't seem to do the same thing. It took me a few minutes to try changing the order to the one they are now. The purpose of an fcc-save-hook is to select a mailbox. You can only Fcc to one mailbox, so mutt stops searching the list of fcc-save-hooks at the first hook whose pattern match succeeds. The purpose of a folder-hook is to execute a command. You can execute several commands when changing folders, so mutt searches the entire list of folder-hooks and executes every hook whose pattern match succeeds. This means that if some folder-hooks set the same variable to different values, the _last_ one in the list whose pattern match succeeds wins, whereas the _first_ fcc-save-hook in the list whose pattern match succeeds wins. This also means that the order of folder-hooks should be from more general patterns to more specific patterns (e.g., the default hook should be first), whereas the order of fcc-save-hooks should be from more specific patterns to more general patterns (e.g., the default hook should be last). HTH, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
Re: mutt-nntp from cron
* Andre Berger [EMAIL PROTECTED] [2002-08-21 14:29]: .. The problem is, it doesn't work when executed from a user's crontab. I edit it with crontab -e and add */2 * * * * /usr/bin/mutt -R -F /etc/muttnewsrc /dev/null 21 (one line). The /dev/null 21 part is to prevent cron from sending mail on job execution. What am I missing here? */2? hmm... perhaps you should run it *with* some output so you can see the error message? and why not use something like slrnpull to get new news? Sven
