Re: Suppressing headers
On 2009.12.24 14:34:32 +, Patrick Shanahan wrote: > * Rem P Roberti [12-24-09 14:32]: > > > > OK...I think that it was a permissions problem. I screwed around with > > the permissions on my /home directory, and somehow the permissions on > > .muttrc were set so that only root had rw permission. I just had to do > > a reboot and it looks as though everything is working normally again. > > Reboot??? Wasn't necessary, just restart mutt or "source" the ~/.muttrc > file. > Yeah...I know. I had to reboot for reasons I'm not willing to divulge at this time :) Rem
Re: Suppressing headers
On 2009.12.24 11:17:21 +, Rem Roberti wrote: > On 2009.12.24 09:47:48 +, Jason Helfman wrote: > > You may want to try something like this: > > > > ignore * > > unignore from date subject to cc mail-followup-to x-operating-system > > > > It works for me. > > > > On Thu, Dec 24, 2009 at 09:45:44AM -0800, Rem P Roberti thus spake: > > >I have this in my .muttrc: > > > > > > > > >ignore * > > >unignore From: Date: To: Cc: Subject: Reply-To: > > >hdr_order Date: From: To: Cc: Subject: Reply-To: > > > > > > > > >but for some reason I am now getting a full complement of headers. How > > >can I fix that? > > > > > >Rem > > > > > > > > > I guess my reply didn't go through. Anyway, I'm using the same .muttrc > on my laptop, and it works fine. I'm still scratching my head as to why > it's having those header problems on the desktop machine. > OK...I think that it was a permissions problem. I screwed around with the permissions on my /home directory, and somehow the permissions on .muttrc were set so that only root had rw permission. I just had to do a reboot and it looks as though everything is working normally again. I hope. Rem
Suppressing headers
I have this in my .muttrc: ignore * unignore From: Date: To: Cc: Subject: Reply-To: hdr_order Date: From: To: Cc: Subject: Reply-To: but for some reason I am now getting a full complement of headers. How can I fix that? Rem
Re: Is Fetchmail still in vogue?
On 2009.12.21 15:54:36 +, Mun wrote: > Hi all, > > My e-mail methodology will be changing shortly and I will be serviced > via an Exchange server (as opposed to e-mail delivered directly to my > Linux workstation). > > Due to my own personality flaws I am planning on using Fetchmail > (configured for IMAP use) to retrieve my e-mail from the Exchange server > to my local Linux (Red Hat Enterprise Linux 5) box. The main reason for > this is that I want a copy of all of my e-mail to reside on my own > computer. > > A couple of questions come to mind: > >1) Is Fetchmail still in "vogue"? Or is there a better application > that I should use to retrieve my e-mail? > >2) It appears that 'fetchmailconf' has been obsoleted. That is, Red > Hat no longer provides it in there Fetchmail RPM. Does anyone > know if there is a replacement? > > Thanks in advance. > > -- Take a look at Getmail. I've found it to be a much better retrieval program than Fetchmail. Rem
Re: Muttprint
On 2009.12.17 15:00:49 +, Patrick Shanahan wrote:
> * Rem P Roberti [12-17-09 12:38]:
> >
> > I guess we are making progress. I did all of the above (I already
> > had .muttrc set correctly) and now when I try and print I get this
> > nice blue sysinstall-like window telling me:
> >
> > Line 636: Error while running dvips
> > No such file or directory
> >
> > Now it is true, there is no dvips installed on the box. So I thought
> > that going to /usr/ports/print/dvips and doing an install would solve
> > the problem. However when I try and do that I get a lengthy error
> > message. If dvips is indeed necessary, and you would like to see the
> > error message, I will send it along.
>
> Well, you are on a different distro that I, openSUSE 11.2. I suspect you
> need to install texlive-latex or some combination of texlive and latex as
> the dvips binary is needed:
> dvips - convert a TeX DVI file to PostScript
>
> 14:56 wahoo:~ > rpm -q --requires muttprint
> LaTeX
> psutils
> perl
> perl-Text-Iconv
> perl-TimeDate
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> rpmlib(CompressedFileNames) <= 3.0.4-1
> /usr/bin/env { from coreutils }
> libc.so.6()(64bit)
> libc.so.6(GLIBC_2.2.5)(64bit)
> libc.so.6(GLIBC_2.3)(64bit)
> libc.so.6(GLIBC_2.3.4)(64bit)
> rpmlib(PayloadIsLzma) <= 4.4.6-1
>
> your system's requirements will be different as you do not use rpm. I
> suspect you are on a debian derivative, synaptics *should* provide a list
> of the required supporting packages. I don't know how you installed
> muttprint, but I would have expected your system to have complained that
> a required package was missing.
>
> let me know if I can help more.
There were dependencies missing, so I installed them manually. Now when
I try to print I get the blue screen with this:
Line 759: Could not print with lpr -Plp
No such file or directory
I'm stumped
Rem
Re: Muttprint
On 2009.12.17 16:43:03 +, Rem P Roberti wrote: > On 2009.12.17 19:31:40 +, Patrick Shanahan wrote: > > * Rem P Roberti [12-17-09 19:20]: > > > On 2009.12.17 15:00:49 +, Patrick Shanahan wrote: > > > > > > > > your system's requirements will be different as you do not use rpm. I > > > > suspect you are on a debian derivative, synaptics *should* provide a > > > > list > > > > of the required supporting packages. I don't know how you installed > > > > muttprint, but I would have expected your system to have complained that > > > > a required package was missing. > > > > > > > > let me know if I can help more. > > > > > > Well this is getting a bit more convoluted. I went and checked > > > the dependencies list and there were indeed some that were missing. So I > > > manually installed them. Now when I try to print I get the blue window > > > telling me this: > > > > > > Line 759: Could not print with lpr -Plp > > > No such file or directory > > > > > > I'm stumped > > > > Sounds like a lot of problems. Why are you "manually" installing > > packages when you have apps specifically designed to handle the > > dependency problems you are having? > Good question. This is a FreeBSD box and I have never had to do this > before. > > > What system are you on and how are you installing? > > What dependencies were missing? > divipsk-tetex and open-motif. There may have been one more. > > > > You may need to "reinstall" lp/cups (my lp* cmds are provided by > > cups-client). > > > > what does "lpstat -a" yield? > lpstat -a yields "Photosmart7760 accepting requests since Dec 11 12:21:13 > 2009" > > > > Do you have cups installed? > Cups is installed and working perfectly. The named printer is working > perfectly, and was installed via CUPS. All is well! One of the dependencies that was missing was teTeX, but I couldn't install it either directly from the ports or via portupgrade -rR of muttprint itself. Then I got the bright idea of using portmaster instead of portupgrade and portmaster installed teTeX and another dependency that muttprint needed. Now everthing is working and the print output looks great. Rem
Re: Muttprint
On 2009.12.17 19:31:40 +, Patrick Shanahan wrote: > * Rem P Roberti [12-17-09 19:20]: > > On 2009.12.17 15:00:49 +, Patrick Shanahan wrote: > > > > > > your system's requirements will be different as you do not use rpm. I > > > suspect you are on a debian derivative, synaptics *should* provide a list > > > of the required supporting packages. I don't know how you installed > > > muttprint, but I would have expected your system to have complained that > > > a required package was missing. > > > > > > let me know if I can help more. > > > > Well this is getting a bit more convoluted. I went and checked > > the dependencies list and there were indeed some that were missing. So I > > manually installed them. Now when I try to print I get the blue window > > telling me this: > > > > Line 759: Could not print with lpr -Plp > > No such file or directory > > > > I'm stumped > > Sounds like a lot of problems. Why are you "manually" installing > packages when you have apps specifically designed to handle the > dependency problems you are having? Good question. This is a FreeBSD box and I have never had to do this before. > What system are you on and how are you installing? > What dependencies were missing? divipsk-tetex and open-motif. There may have been one more. > You may need to "reinstall" lp/cups (my lp* cmds are provided by > cups-client). > > what does "lpstat -a" yield? lpstat -a yields "Photosmart7760 accepting requests since Dec 11 12:21:13 2009" > Do you have cups installed? Cups is installed and working perfectly. The named printer is working perfectly, and was installed via CUPS. Rem
Re: Muttprint
On 2009.12.17 16:18:15 +, Rem P Roberti wrote:
> On 2009.12.17 15:00:49 +, Patrick Shanahan wrote:
> > * Rem P Roberti [12-17-09 12:38]:
> > >
> > > I guess we are making progress. I did all of the above (I already
> > > had .muttrc set correctly) and now when I try and print I get this
> > > nice blue sysinstall-like window telling me:
> > >
> > > Line 636: Error while running dvips
> > > No such file or directory
> > >
> > > Now it is true, there is no dvips installed on the box. So I thought
> > > that going to /usr/ports/print/dvips and doing an install would solve
> > > the problem. However when I try and do that I get a lengthy error
> > > message. If dvips is indeed necessary, and you would like to see the
> > > error message, I will send it along.
> >
> > Well, you are on a different distro that I, openSUSE 11.2. I suspect you
> > need to install texlive-latex or some combination of texlive and latex as
> > the dvips binary is needed:
> > dvips - convert a TeX DVI file to PostScript
> >
> > 14:56 wahoo:~ > rpm -q --requires muttprint
> > LaTeX
> > psutils
> > perl
> > perl-Text-Iconv
> > perl-TimeDate
> > rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> > rpmlib(CompressedFileNames) <= 3.0.4-1
> > /usr/bin/env { from coreutils }
> > libc.so.6()(64bit)
> > libc.so.6(GLIBC_2.2.5)(64bit)
> > libc.so.6(GLIBC_2.3)(64bit)
> > libc.so.6(GLIBC_2.3.4)(64bit)
> > rpmlib(PayloadIsLzma) <= 4.4.6-1
> >
> > your system's requirements will be different as you do not use rpm. I
> > suspect you are on a debian derivative, synaptics *should* provide a list
> > of the required supporting packages. I don't know how you installed
> > muttprint, but I would have expected your system to have complained that
> > a required package was missing.
> >
> > let me know if I can help more.
>
> Well this is getting a bit more convoluted. I went and checked
> the dependencies list and there were indeed some that were missing. So I
> manually installed them. Now when I try to print I get the blue window
> telling me this:
>
> Line 759: Could not print with lpr -Plp
> No such file or directory
>
> I'm stumped
>
> Rem
Oops. I thought the first send failed. Sorry for the duplication.
Rem
Re: Muttprint
On 2009.12.17 15:00:49 +, Patrick Shanahan wrote:
> * Rem P Roberti [12-17-09 12:38]:
> >
> > I guess we are making progress. I did all of the above (I already
> > had .muttrc set correctly) and now when I try and print I get this
> > nice blue sysinstall-like window telling me:
> >
> > Line 636: Error while running dvips
> > No such file or directory
> >
> > Now it is true, there is no dvips installed on the box. So I thought
> > that going to /usr/ports/print/dvips and doing an install would solve
> > the problem. However when I try and do that I get a lengthy error
> > message. If dvips is indeed necessary, and you would like to see the
> > error message, I will send it along.
>
> Well, you are on a different distro that I, openSUSE 11.2. I suspect you
> need to install texlive-latex or some combination of texlive and latex as
> the dvips binary is needed:
> dvips - convert a TeX DVI file to PostScript
>
> 14:56 wahoo:~ > rpm -q --requires muttprint
> LaTeX
> psutils
> perl
> perl-Text-Iconv
> perl-TimeDate
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> rpmlib(CompressedFileNames) <= 3.0.4-1
> /usr/bin/env { from coreutils }
> libc.so.6()(64bit)
> libc.so.6(GLIBC_2.2.5)(64bit)
> libc.so.6(GLIBC_2.3)(64bit)
> libc.so.6(GLIBC_2.3.4)(64bit)
> rpmlib(PayloadIsLzma) <= 4.4.6-1
>
> your system's requirements will be different as you do not use rpm. I
> suspect you are on a debian derivative, synaptics *should* provide a list
> of the required supporting packages. I don't know how you installed
> muttprint, but I would have expected your system to have complained that
> a required package was missing.
>
> let me know if I can help more.
Well this is getting a bit more convoluted. I went and checked
the dependencies list and there were indeed some that were missing. So I
manually installed them. Now when I try to print I get the blue window
telling me this:
Line 759: Could not print with lpr -Plp
No such file or directory
I'm stumped
Rem
Re: Muttprint
* Rem P Roberti [12-17-09 00:04]: I have just installed muttprint on a new FreeBSD box and am having a bit of difficulty getting it to work. The printer is an HP Photosmart 7760 which has been installed via CUPS, and is otherwise working just fine. The problem, I think, is that I have yet to land upon the correct command to be included with "PRINT_COMMAND" in my .muttprintrc. No matter what I try I get this error message: in ~/.muttrc set set print_command="muttprint" open an xterm box and do: lpstat -a it will return the system name of your printer then, in ~/.muttprintrc PRINTER= PRINT_COMMAND="lpr -P$PRINTER" That should allow you to print. If you want to change the font or what is included in the header, etc, look at the sample muttrpintrc files provided in the package and "man muttprint". my ~/.muttrpint is available for viewing at: http://wahoo.no-ip.org/~pat/muttrpintrc note that I have made several changes and commented out previous lines. gud luk, I guess we are making progress. I did all of the above (I already had .muttrc set correctly) and now when I try and print I get this nice blue sysinstall-like window telling me: Line 636: Error while running dvips No such file or directory Now it is true, there is no dvips installed on the box. So I thought that going to /usr/ports/print/dvips and doing an install would solve the problem. However when I try and do that I get a lengthy error message. If dvips is indeed necessary, and you would like to see the error message, I will send it along. Thanks for your help. Rem
Muttprint
I have just installed muttprint on a new FreeBSD box and am having a bit of difficulty getting it to work. The printer is an HP Photosmart 7760 which has been installed via CUPS, and is otherwise working just fine. The problem, I think, is that I have yet to land upon the correct command to be included with "PRINT_COMMAND" in my .muttprintrc. No matter what I try I get this error message: Press any key to continue...dvips: not found cannot remove path when cwd is /tmp/muttprint-1bUYGw for /tmp/muttprint-1bUYGw: at /usr/local/lib/perl5/5.8.9/File/Temp.pm line 901 A couple of years back I had muttprint working just fine with an lpd setup, but so far no joy with this one. Any help much appreciated. Rem
Re: Where did these headers come from?
On 2009.03.01 11:08:55 +, Rem P Roberti wrote: > On 2009.03.01 13:25:40 +, Ed Blackman wrote: > > On Sun, Mar 01, 2009 at 09:41:50AM -0800, Rem P Roberti wrote: > > >I installed muttprint a while back, and I'm quite satisfied with its > > >performance. However, I discovered that once I print an email Mutt then > > >starts to include every (and I do mean every) header when an email is > > >viewed. A page of headers. It's as though the 'ignore' statement in > > >.muttrc is no longer active. The only way I can fix the problem is by > > >closing and reopening Mutt. Anyone know what's going on here? > > > > Maybe your macro for muttprint unsets 'weed'? If you type ':set ?weed' > > before printing in a new Mutt session, what does Mutt respond with? > > After printing? > > > > If mutt responds with "weed is set" before and "weed is unset" after, > > that's the problem, and I can think of two solutions. > > > > Manual: use after printing to toggle it back. > > It's bound to 'h' by default. > > > > Automatic: change your muttprint macro to save and restore the value of > > weed. Add "set my_weed=$weedunset > > weed" to the beginning of the macro and "set > > weed=$my_weed" at the end. I'm guessing at the content of the > > macro, but that should work. > > > What you describe is precisely what happens: muttprint unsets 'weed'. > Since I don't have a dedicated macro for muttprint (I just hit 'p' to > print), and since hitting 'h' is such an easy solution to toggle back > weed, I think that I will just stay with that for the time being. I'm > pretty new to mutt and muttprint, and haven't explored dedicated macros > (except for my abook macro). I will say that that seems like a much > more elegant solution :) Whoa. It turns out that there is a macro in my .muttrc. Here it is: macro index p " " Rem
Re: Where did these headers come from?
On 2009.03.01 13:25:40 +, Ed Blackman wrote: > On Sun, Mar 01, 2009 at 09:41:50AM -0800, Rem P Roberti wrote: > >I installed muttprint a while back, and I'm quite satisfied with its > >performance. However, I discovered that once I print an email Mutt then > >starts to include every (and I do mean every) header when an email is > >viewed. A page of headers. It's as though the 'ignore' statement in > >.muttrc is no longer active. The only way I can fix the problem is by > >closing and reopening Mutt. Anyone know what's going on here? > > Maybe your macro for muttprint unsets 'weed'? If you type ':set ?weed' > before printing in a new Mutt session, what does Mutt respond with? > After printing? > > If mutt responds with "weed is set" before and "weed is unset" after, > that's the problem, and I can think of two solutions. > > Manual: use after printing to toggle it back. > It's bound to 'h' by default. > > Automatic: change your muttprint macro to save and restore the value of > weed. Add "set my_weed=$weedunset > weed" to the beginning of the macro and "set > weed=$my_weed" at the end. I'm guessing at the content of the > macro, but that should work. > What you describe is precisely what happens: muttprint unsets 'weed'. Since I don't have a dedicated macro for muttprint (I just hit 'p' to print), and since hitting 'h' is such an easy solution to toggle back weed, I think that I will just stay with that for the time being. I'm pretty new to mutt and muttprint, and haven't explored dedicated macros (except for my abook macro). I will say that that seems like a much more elegant solution :) Thank you for you help. Rem
Where did these headers come from?
I installed muttprint a while back, and I'm quite satisfied with its performance. However, I discovered that once I print an email Mutt then starts to include every (and I do mean every) header when an email is viewed. A page of headers. It's as though the 'ignore' statement in .muttrc is no longer active. The only way I can fix the problem is by closing and reopening Mutt. Anyone know what's going on here? Rem
Re: No mail notification
> > > This works for all of my many mailboxes except for one...and for the > > life of me I'm stumped as to why mutt won't notify me about that one > > box. > > Well, I guess the basics are: what might possibly be different about > this new mailbox? That's the problem. So far I don't see any differences. > How is it stored (how are the others stored): mbox > or maildir? Maildir. And it is stored thus: /$HOME/Mail/bsd-hams. And, just like all of my other mailboxes, this one is noted in my .muttrc thus: mailboxes $HOME/Mail/bsd-hams > Is it on a different filesystem? Are other programs > currently checking its contents? No, and no. I'm famous for making little typos that screw up the works, but so far I haven't found one. --Rem
Re: No mail notification
> > This is the first time this has happened. I just installed a new
> > mailbox for mail coming from a new list subscription. Everthing works
> > including Procmail which places the mail in the right place. The only
> > thing that doesn't work is that I don't get any notification of new mail
> > for this mailbox. I checked my .muttrc, and the entries for this new
> > mailbox are correct, which is to say just the same as the entries for
> > all the other mailboxes. Still no notifications of new mail. Any ideas
> > on what might be wrong? At this point all I can do is remember to check
> > in the mailbox from time to time for new mail.
> >
>
>
> How do you get new mail notification for the other mailboxes?
Whenever new mail arrives Mutt just lets me know. I get a notification
at the bottom of the screen like this:
New mail in =gimp
If I have mail in numerous different mailboxes and I hit the "c" key I
would get a notification like this:
Open mailbox ('?' for list) =muttusers
This would, of course, tell me that I now have mail from this list. And
I could, in this manner, cycle through all of my mailboxes that contain
new mail. This works for all of my many mailboxes except for one...and
for the life of me I'm stumped as to why mutt won't notify me about that
one box.
--Rem
No mail notification
This is the first time this has happened. I just installed a new mailbox for mail coming from a new list subscription. Everthing works including Procmail which places the mail in the right place. The only thing that doesn't work is that I don't get any notification of new mail for this mailbox. I checked my .muttrc, and the entries for this new mailbox are correct, which is to say just the same as the entries for all the other mailboxes. Still no notifications of new mail. Any ideas on what might be wrong? At this point all I can do is remember to check in the mailbox from time to time for new mail. --Rem
Re: using mutt with comcast
> Hello, > > Has anyone had any success using mutt to send email using the comcast smtp > service? > > I have comcast as my ISP, and while according to comcast I should be able to > use > > smtp.comcast.net:25 as my smtp host, whenever I try to send email, I get an > error saying that it is an invalid smtp host. > > Has anyone gotten this to work? > I have comcast residential internet service in Arizona USA. > Comcast is my provider, but port 25 does not work here. I have to use port 587. I am using Mutt in conjunction with msmtp. --Rem
Re: Where did this line come from?
> > On 07 Feb 09 16:03, Rem P Roberti wrote: > > I must be getting senile. Either I have never noticed this before, or I > > inadvertently messed something up in my .muttrc. Observe: > > > > -N F- 1/1: Rem P Roberti test -- (all) > > Date: Sat, 7 Feb 2009 15:56:40 -0800 > > ... > > > > Where on earth did the first line in the header (preceding the date) > > come from? > > It is Mutt's statusbar and you certainly did set the variable > status_on_top to "yes" so the statusbar ist displayed ... on the > top. > > See: > > - L- 3/9: Rem P Roberti Where did this line come from? -- (all) > From: Rem P Roberti > To: Mutt List > Subject: Where did this line come from? > > If you see this line while viewing a message in the pager it probably > *looks like* a header because you changed the coloring. > > Best regards, > David > Well...you are quite right. I see now that it is indeed the status bar. But for the life of me I don't remember actually seeing the status bar info showing up again right above the header. Nor do I really understand its purpose, because it looks as thought the information being displayed is essentially the same as the information displayed in the message list. ---Rem
Where did this line come from?
I must be getting senile. Either I have never noticed this before, or I inadvertently messed something up in my .muttrc. Observe: -N F- 1/1: Rem P Roberti test -- (all) Date: Sat, 7 Feb 2009 15:56:40 -0800 From: Rem P Roberti To: remeg...@comcast.net Subject: test Where on earth did the first line in the header (preceding the date) come from? Rem
Re: Printing with Mutt
> > I'm working on different computer, so I may have missed, but what do you > > have in .muttrc for print_command? > > OK, In .muttrc I have the following: > > set print_command="muttprint" > #set print="yes" > set print_split > > macro index p " > " > macro pager p " > " > > (Mind the line-wrap) > > in .muttprintrc I have the following: > PRINT_COMMAND="lpr -P$PRINTER" > > This gave an error: > lpr: The printer or class was not found. > Muttprint Version 0.72d -- Error > == > > Line 759: Could not print with lpr -Plp: > > So I changed it to: > PRINT_COMMAND="CUPS" > > Which also gave an error - this time: > Muttprint Version 0.72d -- Error > == > > Line 759: Could not print with lpr -P lp -o media=A4 : > > > I just finished setting up Muttprint and I had to have set print="yes" uncommented in my .muttrc, and also I had to change PRINT_COMMAND="lpr -P$PRINTER" to simply PRINT_COMMAND="lpr" in order for Muttprint to work. Rem
Re: Delivering system mail
On 2009.01.30 08:57:47 +, Tolga wrote: > > > Rem P Roberti yazm: > >On 2009.01.29 20:12:32 +, Patrick Shanahan wrote: > > > >>* Rem P Roberti [01-29-09 18:31]: > >> > >>>I have a mailbox (~/Mail/system) to which I would like my system mail to > >>>be placed. I haven't been able to figure out how to accomplish that. I > >>>have correctly configured /etc/aliases so that root's mail is delivered > >>>to user, but I don't seem to be able to come up with a procmail recipe > >>>that will do the trick. Any help would be appreciated. > >>> > >>:0: > >>* ^TO_.*root > >> system > >> > >> > >Thanks for the response, Patrick. I get line two, but wouldn't line three > >of the > >recipe have to read $HOME/Mail/system/? > > > >Rem > > > Add MAILDIR=$HOME/Mail at the beginning of your .procmailrc and amend > the recipe Patrick gave to > > :0: > * ^TO_.*root > system/ > > Ok...I guess we are a bit too far afield for this list. Perhaps I should take the issue to the procmail list. Suffice to say that so far nothing has worked. As I indicated earlier root's mail is being forwarded to user, so I know that isn't the problem. The above recipe failed to put last night's system mail into ~/Mail/system. I went back and checked my .muttrc to make sure that "system" was listed as a mailbox, and it is. Nevertheless, this morning I was greeted with ubiquitous "you have mail" at user's command prompt. Rem
Re: Delivering system mail
On 2009.01.29 20:12:32 +, Patrick Shanahan wrote: > * Rem P Roberti [01-29-09 18:31]: > > I have a mailbox (~/Mail/system) to which I would like my system mail to > > be placed. I haven't been able to figure out how to accomplish that. I > > have correctly configured /etc/aliases so that root's mail is delivered > > to user, but I don't seem to be able to come up with a procmail recipe > > that will do the trick. Any help would be appreciated. > > :0: > * ^TO_.*root > system > Thanks for the response, Patrick. I get line two, but wouldn't line three of the recipe have to read $HOME/Mail/system/? Rem
Delivering system mail
I have a mailbox (~/Mail/system) to which I would like my system mail to be placed. I haven't been able to figure out how to accomplish that. I have correctly configured /etc/aliases so that root's mail is delivered to user, but I don't seem to be able to come up with a procmail recipe that will do the trick. Any help would be appreciated. Rem
Re: Printing with Mutt
All is well! I took a good look at the .muttprinrc and saw that the print_command option was incorrectly set. Now everything seems to be working fine, and the printout looks great! Rem
Re: Printing with Mutt
Well, it's gotten a little different. I copied the sample-muttprintrc-en file to ~/.muttprinrc, and now when I try and print this is the error message I get: Press any key to continue...cannot remove path when cwd is /tmp/muttprint-HLua4y for /tmp/muttprint-HLua4y: at /usr/local/lib/perl5/5.8.9/File/Temp.pm line 901 It's tough being a unix newbie. Rem
Re: Printing with Mutt
> Here is a small tutorial for muttprint: > http://www.linux-magazine.com/w3/issue/48/Formatting_Email_with_Muttprint.pdf Well, I had the feeling that it wasn't going to just work straight out of the box. I got muttprint installed, and placed the recommended options and macros in my .muttrc, but when I try to print I get this error message: Muttprint Version 0.72d -- Error | | == | | | | Line 759: Could not print with lpr -Plp: | | No such file or directory | | | | -- | | If this message does not help you, write to the maintainer of Muttprint | | (lukas@lpr.ch) and include a detailed error description. | | Please make sure that you've read the whole documentation and checked | | for updates before you write! *** Press Ctrl-L after terminating | | this process if the screen is not redrawed correctly! Sorry for the formatting ugliness. Any ideas on what to do next? Rem
Re: Printing with Mutt
> > Here is a small tutorial for muttprint: > http://www.linux-magazine.com/w3/issue/48/Formatting_Email_with_Muttprint.pdf Thank you! Rem
Re: Printing with Mutt
> * Rem P Roberti [01-29-09 00:06]: > > I have a laser printer installed on my FreeBSD system which I installed > > via cups, and the printer works fine. However, when I print a message > > from within Mutt the left margin is only about 3/16" and a couple of > > characters are always missing from the beginning of all lines. > > You need to set the margins via your printer software, cups. I do not > know FreeBSD, but try: > localhost:631 > in your browser of choice. > > > The printer defaults to letter size paper and, as I said, it prints > > fine from all other applications. Is there a way to control how Mutt > > formats a page for printing? > > afaik, mutt does not "format" for printing, but there is a utility > that prettifies email for printing, muttprint. I like it. I'll take a look at that. The printer was set up via localhost:631, but there are no options that I know of that allow you adjust margins, only the types of media. Rem
Printing with Mutt
I have a laser printer installed on my FreeBSD system which I installed via cups, and the printer works fine. However, when I print a message from within Mutt the left margin is only about 3/16" and a couple of characters are always missing from the beginning of all lines. The printer defaults to letter size paper and, as I said, it prints fine from all other applications. Is there a way to control how Mutt formats a page for printing? TIA... Rem
[no subject]
test
Re: printer installation
In case I haven't already done this, the problem with my inability to print using a CUPS installed printer has been solved. CUPS installs its own set of lp binaries (FreeBSD 7.0) in /usr/local/bin, as opposed to the common lp binaries which reside in /usr/bin. My solution to the problem was to simply change the path which is spelled out in my bash configuration file, so that /usr/local/bin is read first. That seems to have solved the problem, and I am now able to print directly from Mutt with, so far, no problems. Cheers, Rem
Re: User's inbox
> above shows that your printer is "GENERIC PostScript Printer". Is > that what http://localhost:631 reports? Yes. > > What distro are you running? Have you *ever* been able to print from > the cl? What printer and what name is assigned in cups? Actually, I'm running FreeBSD 7.0, and I have never been able to print from the command line while using a CUPS installed printer. Localhost:631 does indeed report the printer as GENERIC PostScript Printer. > ps: this conversation may be off-topic or vary loosely on-topic as it > pertains to/originated with printing from mutt. True. And although my main concern is to be able to print from Mutt, the whole discussion about printer installation may be pulling us off-topic.
Re: User's inbox
> > > > lp-cups does not seem to exist on this installation. > > nor mine, openSUSE 10.1 > > > When I try to print from Mutt now I get the error message: > > > > lpr: lp: unknown printer > > > > I can't print from the command line, although printing works fine with > > my X apps. > > what does "lpoptions" report? > what does "lpq" report? > > have you tried the web based cups control? > http://localhost:631 > > it sounds like you do not have a printer defined that lp is aware of. Localhost:631 shows my postscript printer installed and accepting jobs. The output of lpoptions: media=Letter sides=one-sided finishings=3 copies=1 job-hold-until=no-hold job-priority=50 number-up=1 auth-info-required=none job-sheets=none,none printer-info='GENERIC PostScript Printer' printer-is-accepting-jobs=1 printer-is-shared=1 printer-location printer-make-and-model='Generic PostScript Printer Foomatic/Postscript (recommended)' printer-state=3 printer-state-change-time=1215794769 printer-state-reasons=none printer-type=12316 The output of lpq reveals: lpq: printer not found As stated earlier, if I use X apps (Thunderbird for example) I have no problem printing. Rem
Re: User's inbox
> You can replace the 'normal' /usr/bin/lp (or wherever it is) with > lp-cups, what got installed with your cups-package. Easy way is to > #mv lp lp.backup > and then copy lp-cups to this directory and just rename it to 'lp. > > Try: > #lp-cups textfile.txt and it should work. lp-cups does not seem to exist on this installation. When I try to print from Mutt now I get the error message: lpr: lp: unknown printer I can't print from the command line, although printing works fine with my X apps. Rem
Re: User's inbox
> > I have a fundamental lack of understanding on something. I am using > > Mutt with FreeBSD 7.0. I have a number of mailboxes designated in my > > muttrc that Procmail delivers to...for example: > > > All of those mailboxes, with the exception of "inbox", are actual > > folders. > > Okay... > > > Inbox, on the other hand is not a folder, but rather a file, to > > which are appended all of the email which is not put in named > > folders by Procmail. > > okay > > > Why is it that the inbox cannot itself have its own folder instead > > of just being a file? > > It *can*; you just have to configure things correctly. I'm guessing, > since mutt has no such restrictions, that this is a problem in your > procmailrc. Make sure that the inbox delivery line ends in a slash > (/), so that procmail knows that it needs to be in Maildir format. > (also, you'll need to move the existing inbox out of the way, > otherwise procmail will get mad). > > > You know, a folder containing cur, new, and tmp. > > That's a Maildir. Thank you for your prompt reply. I shall play with those ideas. Totally unrelated: my printer is installed with CUPS, so lpd is not enabled. Can Mutt print from this kind of a setup? Thanks again for your help. Rem
User's inbox
I have a fundamental lack of understanding on something. I am using Mutt with FreeBSD 7.0. I have a number of mailboxes designated in my muttrc that Procmail delivers to...for example: mailboxes $HOME/Mail/muttusers mailboxes $HOME/Mail/freebsd mailboxes $HOME/Mail/jep mailboxes $HOME/Mail/steve mailboxes $HOME/Mail/cups mailboxes $HOME/Mail/abiword mailboxes $HOME/Mail/system mailboxes $HOME/Mail/procmail mailboxes $HOME/Mail/spam mailboxes $HOME/Mail/xan mailboxes $HOME/Mail/elinks mailboxes $HOME/Mail/mfolder mailboxes $HOME/Mail/mark mailboxes $HOME/Mail/kim mailboxes $HOME/Mail/postfix mailboxes $HOME/Mail/walt mailboxes $HOME/Mail/inbox All of those mailboxes, with the exception of "inbox", are actual folders. Inbox, on the other hand is not a folder, but rather a file, to which are appended all of the email which is not put in named folders by Procmail. Why is it that the inbox cannot itself have its own folder instead of just being a file? You know, a folder containing cur, new, and tmp. Normally, I wouldn't care about all of this, but I am using Mairix to do indexing and searching of email, and Mairix, to the best of my knowledge, will not index a file. So I guess I'm asking why I can't set up my inbox just like any of the mailboxes that Procmail delivers to. Whew! Does that make any sense? Rem
Re: Procmail error
> > On Mon, Jul 07, 2008 at 10:52:08PM -0700, Rem P Roberti wrote: > > > > > > Never get mail as root. In fact never use root unless you really have > > > > to, but that is a more general point. > > > > > > > Understood. But I thought this entry (root: rem) in my aliases file > > > would take care of that. > > > > > > > in root's crontab use fetch the mail and let procmail as root > > sort those files into your users mailbox/maildir files? > > > > No wonder those files belong to root and your user cannot > > open them. > > > > This line is for a different purpose! > > > > All of the daily status mails your box sends to root, will be > > sent to your users spoolfile instead. > > > > As long as you do not spool those fetched email, no alias will > > be used ever. > > I'm missing something here. It's user's crontab that is used to invoke > getmail, and retrieve the pop mail. So I'm still in the dark as to why > "those files belong to root..." and my user can't retrieve them? Problem solved. I added "allow_root_commands = True" to the [destination] entries in the getmailrc and that fixed it. Rem
Re: Procmail error
> On Mon, Jul 07, 2008 at 10:52:08PM -0700, Rem P Roberti wrote: > > > > Never get mail as root. In fact never use root unless you really have > > > to, but that is a more general point. > > > > > Understood. But I thought this entry (root:rem) in my aliases file > > would take care of that. > > > > in root's crontab use fetch the mail and let procmail as root > sort those files into your users mailbox/maildir files? > > No wonder those files belong to root and your user cannot > open them. > > This line is for a different purpose! > > All of the daily status mails your box sends to root, will be > sent to your users spoolfile instead. > > As long as you do not spool those fetched email, no alias will > be used ever. I'm missing something here. It's user's crontab that is used to invoke getmail, and retrieve the pop mail. So I'm still in the dark as to why "those files belong to root..." and my user can't retrieve them? Rem
Re: Procmail error
> > > > I have mutt installed on two other freebsd computers. I fetch pop mail > > via getmail, and procmail puts things where they belong. I just > > installed freebsd 7.0 on another computer with what I thought were the > > exact same settings for all of the mail programs involved. When I try > > to retrieve mail I get this error message: > > > > Delivery error (command procmail 3695 error (127, exec of command > > procmail failed (refuse to invoke external commands as root or GID 0 by > > default))) > > > > I'm a relative newbie here and would appreciate it if someone could give > > me a heads up on this. > > Never get mail as root. In fact never use root unless you really have > to, but that is a more general point. > Understood. But I thought this entry (root:rem) in my aliases file would take care of that. Rem
Procmail error
I have mutt installed on two other freebsd computers. I fetch pop mail via getmail, and procmail puts things where they belong. I just installed freebsd 7.0 on another computer with what I thought were the exact same settings for all of the mail programs involved. When I try to retrieve mail I get this error message: Delivery error (command procmail 3695 error (127, exec of command procmail failed (refuse to invoke external commands as root or GID 0 by default))) I'm a relative newbie here and would appreciate it if someone could give me a heads up on this. Rem
Re: Sent mail
> > > Thanks for responding, Kyle. I found the problem. Somewhere along > > the line, while I was messing around with my .muttrc file, I changed > > the set force_name= variable to yes instead of no. And, as you > > know, that overode my set record=~/Mail/sent. For the time being I > > am happy to have the copies of outgoing mail appended to /Mail/sent. > > So, all is well again. I am curious about one thing, however. It > > seems that having a dedicated "sent" mailbox is verboten. Why is > > that? > > What do you mean? You set $record to something; is that not your > dedicated "sent" mailbox? That's not forbidden at all! > > ~Kyle You're right...I'm confusing the issue. "Sent," as defined by $record, is indeed my dedicated "sent" mailbox. But it is itself a file to which all of the copies of outgoing mail are appended. All of my other mailboxes, including inbox, are directories, which are refered to in .muttrc by "mailboxes ". And all of these are read to via Procmail. I guess I'm asking why should not "sent" be handled in the same manner. Rem
Re: Sent mail
> > On Friday, January 4 at 04:02 PM, quoth Rem P Roberti: > > I don't know how this happened, but Mutt is now creating individual > > folders for mail that I have sent, in which it places copies of sent > > mail. Before this time Mutt always put copies of outgoing mail in a > > central "sent" folder. I did do some "tweaking" of the .muttrc file, > > but when this new situation arose I put everything back to its original > > state. At any event, this has motivated me to learn the proper > > manner in which to handle sent mail, and any help would be appreciated. > > "Proper" sent mail handling depends on your preferences. What would > you like to have happen? Thanks for responding, Kyle. I found the problem. Somewhere along the line, while I was messing around with my .muttrc file, I changed the set force_name= variable to yes instead of no. And, as you know, that overode my set record=~/Mail/sent. For the time being I am happy to have the copies of outgoing mail appended to /Mail/sent. So, all is well again. I am curious about one thing, however. It seems that having a dedicated "sent" mailbox is verboten. Why is that? Cheers, Rem
Sent mail
I don't know how this happened, but Mutt is now creating individual folders for mail that I have sent, in which it places copies of sent mail. Before this time Mutt always put copies of outgoing mail in a central "sent" folder. I did do some "tweaking" of the .muttrc file, but when this new situation arose I put everything back to its original state. At any event, this has motivated me to learn the proper manner in which to handle sent mail, and any help would be appreciated. Rem
Re: Incoming Mail
> > >Nope...no spaces. The culprit these days is a mailbox I have set up > >for > >Amazon. I do a lot of business there, and so I created a mailbox > >specifically for that mail. Here is the recipe: > > > >:0 > >* ^From:[EMAIL PROTECTED] > >|[EMAIL PROTECTED] > >$HOME/Mail/amazon/ > > > >Pretty straightforward. But no notification from Mutt when mail > >arrives. > > How many mailboxes is mutt monitoring? Is there any pattern to the > ones that it doesn't see? I found the error. All of my mail is placed within the "Mail" directory of my home directory. When I made an entry in my .muttrc for the mailbox in question, I incorrectly wrote "Mail" with a lower case "m" when indicating the path. That was it. Thanks for taking the time to help. Boy, those syntax errors can really bite you. Rem
Re: Incoming Mail
> > On Sunday, December 16 at 12:10 PM, quoth Rem P Roberti: > >I have a number of mailboxes on my system, with procmail recipes > >directing mail to those mailboxes. When new mail arrives Mutt usually > >notifies me that there is mail in the selected mailboxes. But there are > >a couple of mailboxes which Mutt always misses, and I am at a loss for > >why that would be true. Any ideas would be appreciated. > > All on the same filesystem? Hm. Are there spaces in the name of these > mailboxes? I'm just guessing here... Nope...no spaces. The culprit these days is a mailbox I have set up for Amazon. I do a lot of business there, and so I created a mailbox specifically for that mail. Here is the recipe: :0 * ^From:[EMAIL PROTECTED] |[EMAIL PROTECTED] $HOME/Mail/amazon/ Pretty straightforward. But no notification from Mutt when mail arrives. Rem
Incoming Mail
I have a number of mailboxes on my system, with procmail recipes directing mail to those mailboxes. When new mail arrives Mutt usually notifies me that there is mail in the selected mailboxes. But there are a couple of mailboxes which Mutt always misses, and I am at a loss for why that would be true. Any ideas would be appreciated. Rem
Mairix search results
Mairix is installed and working. I have tried to create a macro which would allow me to view the results of the search in the mailbox (mfolder) that I have created for Mairix finds. Here it is: macro generic f "=mfolder " "Search results" When I invoke the macro I get this message: change-folder>=mfolder is not a mailbox. What am I doing wrong? Rem
Re: Using Mairix
On 2007.10.19 00:41:16 +, Eyolf strem wrote: > On 18.10.2007 (14:28), Rem P Roberti wrote: > > > > Thanks for the macros, but something is still wrong. Mairix > > successfully carries out its search, but when I try to retrieve the > > results I get this message: > > > > You asked search results to go to the folder '/home/rem/Mail/mfolder'. > > That folder appears to be one of the indexed mail folders! > > For your own good, I refuse to output search results to an indexed mail > > folder. > > Press any key to continue... > > > > I'm not an expert on mairix, but it sounds as if you have not omitted > the search output folder, which makes mairix abort, because it would > otherwise result in an infinte loop. You would need to have > > > > omit=mairix > > (or, in your case, omit=mfolder) in .mairixrc > > e omit=mfolder solved the problem which I last referred to. Thanks. However, no results are yet readable from the Mutt index. Results do indeed show up in the cur subdirectory of mfolder, a linked entry pointing to the actual message, but when I select the mfolder from the Mutt index nothing is there. Rem >
Re: Using Mairix
On 2007.10.18 16:55:37 +, Eyolf strem wrote: > On 17.10.2007 (20:50), Rem P Roberti wrote: > > I just installed Mairix, and the program works fine, except that I don't > > seem to be able to access the mfolder from within Mutt. When I do a > > search Mairix creates the requiste "mfolder" containing cur, new, and > > tmp, and the result of the search is placed in the "new" subdirectory. > > But I am unable to access the results of the search in the Mutt index. > > The mfolder shows up in the index, but it is empty. Anyone tell me what > > I am doing wrong? > > I remember having the same kind of problem in the beginning, but I > can't remember how I solved it. I *think* it was down to having a bad > syntax in my search terms, so that the search didn't catch anything. > Perhaps also because I hadn't set the search areas properly. > Here's what I have in my .mairixrc: > > base=~/Mail > maildir=*... > omit=spam > omit=trash > omit=mairix > database=~/.mutt/mairix-db > mfolder=mairix > > And the macros in .muttrc: > > macro index,pager \em "mairix " "Run a Mairix search" > macro index,pager \ef "=mairix\n" "Search results" > > On that note: can someone tell me if there is a way to combine the two > into one? I would like to go automatically to the mairix folder once > the search is over, instead of having to go there manually. Is that > possible? > > Eyolf Thanks for the macros, but something is still wrong. Mairix successfully carries out its search, but when I try to retrieve the results I get this message: You asked search results to go to the folder '/home/rem/Mail/mfolder'. That folder appears to be one of the indexed mail folders! For your own good, I refuse to output search results to an indexed mail folder. Press any key to continue... The result does indeed go into one of the subdirectories of mfolder, but nothing shows up in Mutt's index. Rem
Using Mairix
I just installed Mairix, and the program works fine, except that I don't seem to be able to access the mfolder from within Mutt. When I do a search Mairix creates the requiste "mfolder" containing cur, new, and tmp, and the result of the search is placed in the "new" subdirectory. But I am unable to access the results of the search in the Mutt index. The mfolder shows up in the index, but it is empty. Anyone tell me what I am doing wrong? Rem
No thread indicator
I just recently noticed that I no longer have threads indicated in the the index. I'm not sure how that happened but I would like to fix it. Rem
Global delete
Is there a way to do a global delete of messages listed in a mailbox index? Rem
Mailbox setup
Like most folks I have separate recipes and mailboxes for my most frequently received email. I also created a recipe for email addressed to me for which there is no specific mailbox. That mail is directed to #HOME/Mail/inbox. What is happening in some cases is that email that has a proprietary mailbox and recipe is going to the inbox instead. Basically what I was trying to achieve was to have general email go the inbox instead of having to read it in /var/mail/rem. I obviously failed, but the solution isn't yet apparent to me. I realize that this is basically a procmail question, but so far that list has been unresponsive in my attempts to subscribe. Rem
Re: Procmail
On 2007.10.13 05:33:27 +, Chris Bannister wrote: > On Tue, Oct 09, 2007 at 10:23:58AM -0700, Rem P Roberti wrote: > > index. Otherwise, how would one get the chance to reply? Also, is it > > possible to have the filtered messages placed in their respective > > folders without all of the headers? > > Maybe you want something like this in your .muttrc: > > # What headers are displayed > ignore * > unignore From Date Subject To Cc User-agent > > # What order the headers are displayed > unhdr_order * > hdr_order User-agent From Date To Cc Subject > > All this is in the manual. If you press from within mutt do you get > the manual? > > -- > Chris. > == I have that hdr info in my .muttrc, and everything seems to be working quite well right now. I've been plugging away trying to learn all this stuff, and it's slowly paying off. Thanks for your help. And, yes, does produce the manual. Rem
Re: Procmail Nesting
On 2007.10.10 17:46:58 +, Kyle Wheeler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wednesday, October 10 at 03:29 PM, quoth Rem P Roberti:
> > Is it possible to use curly braces to nest conditions? For example,
> > there are two addresses that can be used for the FreeBSD mailing
> > list to which I subscribe, and I would like to incorporate them both
> > into the same recipe.
>
> This is really a procmail question... which you should probably be
> asking on a procmail-users list.
>
> But the short answer is that yes, you can nest conditions, like so:
>
> :0 H
> * basecondition
> {
> :0 H
> * subcondition1
> deliversomewhere
>
> :0 H
> * subcondition2
> deliverelsewhere
> }
>
> But the situation you describe sounds more like something you'd use
> stronger conditions for, like so:
>
> :0 H
> * From:.*(address1|address2)
> FreeBSDmailbox
>
> ~Kyle
Thanks Kyle...and, yes, it's about time that I joined the procmail list.
Rem
Procmail Nesting
Is it possible to use curly braces to nest conditions? For example, there are two addresses that can be used for the FreeBSD mailing list to which I subscribe, and I would like to incorporate them both into the same recipe. Rem
Re: Procmail
On 2007.10.09 18:23:23 +, Kyle Wheeler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tuesday, October 9 at 05:15 PM, quoth Joseph: > >If you have mbox it should be: > >:0: > >* ^From:[EMAIL PROTECTED] > >$HOME/Mail/user > > In case it's not clear, the reason to use .* instead of just a space > is that the way From headers are typically sent is like this: > > From: <[EMAIL PROTECTED]> > > or > > From: User Name <[EMAIL PROTECTED]> > > ...and so you can have lots of cruft in between the "From:" and the > email address EVEN IF MUTT DOESN'T SHOW IT TO YOU. Mutt makes the From > header look a little prettier than the raw email, and that can be > deceptive. :) > > If you want to see the email in the form that procmail does, try > pressing the e key in mutt when you view a message (don't save any > inadvertent changes when you close your editor, though!). > > ~Kyle My thanks again to both of you. Creating my .procmailrc recipe in the manner suggested by Joseph did the trick. What I don't understand is that since the variable MAILDIR=$HOME/Mail exists at the beginning of .procmailrc why is it necessary to state the full path to the target mailbox in the recipe? Rem
Re: Procmail
Back at it (Kyle, are you out there?). I've been trying to set up individual mailboxes for folks I receive mail from frequently. I create the mailbox in .muttrc (mailboxes $HOME/Mail/user), and then a recipe like this in .procmailrc: :0: * ^From: [EMAIL PROTECTED] user But the mail isn't getting filtered to the named mailboxes. Procmail is making me feel a little stupid. Rem
Re: Procmail
On 2007.10.09 12:50:53 +, Kyle Wheeler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tuesday, October 9 at 10:23 AM, quoth Rem P Roberti: > > Boy, I'm missing something here. Ok...I did have the syntax wrong, > > and now that I have the path to my mailboxes correctly stated in > > .muttrc Mutt does indeed give me a message at the bottom of the > > screen telling me that a message has arrived in the named folder. > > Excellent! Progress! :) > > > However, I was under the impression that the incoming messages would > > also be listed in the index. > > ... ummm, they are. When you view the contents of the folder they were > delivered to. > > Let me try to put this another way: mutt's index of messages is the > index of a single folder. Mutt can only ever view messages from a > single folder at a time. If you have new messages delivered to a > folder you aren't looking at, mutt will happily inform you that there > are new messages in that folder, but to see them you have to go view > that folder. Mutt will not simply add them to the index of whatever > folder you happen to be viewing currently, because to do so would be > to misrepresent the contents of the folder you're currently viewing > (and really, how would that play out, if mutt behaved the way you seem > to be assuming it does? Would all new messages in your defined > mailboxes listed in the indexes of EVERY folder that you view? How > disconcerting would *that* be?!?). > > This is the same behavior as virtually every other mail client in > existence: if you establish a rule to automatically file mail away in > a folder, by definition, it does not appear in your INBOX (if it did, > what would be the point of filing it?). > > > Otherwise, how would one get the chance to reply? > > You go open up the folder containing the new mail, read the message, > and reply to it; the same way you reply to all other mail. > > > Also, is it possible to have the filtered messages placed in their > > respective folders without all of the headers? > > That's between you and your MDA (procmail), but in general, it > depends. Some folder formats (e.g. mbox) rely on at least some of the > headers existing. What would be the point of stripping off headers? > Some misguided attempt to save a few bytes of storage? > > ~Kyle > - -- > Our lives begin to end the day we become silent about things that > matter. > -- Martin Luther King Jr. Oh, brother! I didn't realize that you could get to the individual folders from within Mutt by c. You want to laugh...I responded to your last couple of posts by cut and paste! Things are beginning to come together. Rem
Re: Procmail
>I suspect you probably are just missing some syntax. For example, >mutt's mailboxes take full paths, not just names that are relative to >some other setting. So, for example, if procmail is saving messages to >$HOME/testing then you need to tell mutt: > mailboxes $HOME/testing >Otherwise, if you just have "mailboxes testing", mutt will look for a >file named "testing" in whatever the current directory is. >~Kyle Boy, I'm missing something here. Ok...I did have the syntax wrong, and now that I have the path to my mailboxes correctly stated in .muttrc Mutt does indeed give me a message at the bottom of the screen telling me that a message has arrived in the named folder. However, I was under the impression that the incoming messages would also be listed in the index. Otherwise, how would one get the chance to reply? Also, is it possible to have the filtered messages placed in their respective folders without all of the headers? Sorry this is taking so long to sink in. Rem
Re: Procmail
>What do you mean that mutt "never sees it"---if you open that mailbox, >is the new message missing? Is it not marked "new"? What's the >problem? Is what marked "new"? >If you're upset that mutt didn't inform you "hey! There's new mail in >a mailbox you aren't looking at!", keep in mind that mutt only keeps >tabs on the mailboxes that you tell it to keep tabs on. So, if you >want to be notified when new email is delivered to the mailbox >"testing", then you have to specify in your muttrc: >mailboxes testing Well...I did put a "mailboxes testing" entry in my .muttrc, along with one for the Mutt users group, and for the FreeBSD users group. And all mail for those entities is going to their respective folders, but Mutt does not notify me of any arrivals. I have the feeling that something crucial is missing from my .muttrc file, but I don't know what. Rem
Procmail
Bit of a problem here setting up Procmail. I have a test entry in my .procmailrc thus: :0: * ^Subject: test testing When I send a test message to myself with "test" as Subject, Procmail does indeed filter the mail, creating the "testing" folder and putting the mail there. But the mail goes directly to the target folder without Mutt ever seeing it. No indication from Mutt that the mail was received. Anyone help me with this? TIA. Rem
Re: Procmail
On 2007.10.09 12:18:12 +, Dilip M wrote: > On 10/9/07, Rem P Roberti <[EMAIL PROTECTED]> wrote: > > ...snip... > > > getmail version 4.7.6 > > Python version 2.5.1 (r251:54863, Sep 16 2007, 14:19:57) > > [GCC 3.4.6 [FreeBSD] 20060305] > > > > Unhandled exception follows: > > File "/usr/local/bin/getmail", line 506, in main > > destination_func = getattr(destinations, destination_type) > > AttributeError: 'module' object has no attribute 'MDA external' > > Have you mentioned "MDA external" in destination section? > > Ex: > [destination] > type = MDA_external > > > Please also include configuration information from running getmail > > with your normal options plus "--dump". > > Can you include that o/p? :) > > -- > :wq! Syntax police! I didn't have an underscore after MDA. I shall try again in the morning with the correct syntax. Rem
Procmail
I am in the process of trying to set up Procmail, and I thought that the .procmail file, and my getmailrc were configured properly. But when I try to retrieve mail I get this error message: Exception: please read docs/BUGS and include the following information in any bug report: getmail version 4.7.6 Python version 2.5.1 (r251:54863, Sep 16 2007, 14:19:57) [GCC 3.4.6 [FreeBSD] 20060305] Unhandled exception follows: File "/usr/local/bin/getmail", line 506, in main destination_func = getattr(destinations, destination_type) AttributeError: 'module' object has no attribute 'MDA external' Please also include configuration information from running getmail with your normal options plus "--dump". Anyone help me on this one? Rem
Re: Eporting from alias folder
On 2007.10.08 08:52:11 +, Chris Bannister wrote: > On Sat, Oct 06, 2007 at 11:26:07PM +0100, Jerry Walker wrote: > > Hi Rem, > > > > On Sat 6 Oct 2007 12:58, Rem P Roberti wrote: > > > Still searching for a way to export aliases from my alias folder to Abook > > > via Mutt. Anyone know how to do > > > that? > > > > Use "abook --convert ...". Try "abook --help" for more details. > > That looks like a mass migration all at once. Seems there is no way to > do selective migration, also how can one be sure it won't clobber > existing entries in the abook database? > > Seems like the only safe way is to manually do it. > > Of course you have: > > macro index,pager A "abook --add-email" > > for new mail. > > Consider using lbdb, set it up, then add: > > set query_command = "lbdbq %s" > > to your .muttrc > > -- > Chris. Thanks for the info, Chris. Abook is working for me, so I think that I will stay there. But I have incorporated the macro you sent into my .muttrc. Thanks again. Rem
Re: Exporting from alias folder
On 2007.10.07 01:25:56 +, Jerry Walker wrote: > On Sat 6 Oct 2007 16:51, Rem P Roberti wrote: > > > It is very easy to create an alias from a received message just > > by using the "a" command. This puts the new alias in my .mail_aliases > > folder, which resides in my home directory. My understanding is that > > you can transfer selected aliases from that folder to Abook, and that > > process can be carried off from within Mutt itself. Then you can just > > prune the .mail_aliases folder for whatever aliases are not to be kept > > permanently. > > Can't help you there I'm afraid. Since I started using Abook I stopped > using the standard Mutt alias file. I found a Perl script written by Brian > Foley > <[EMAIL PROTECTED]> which writes the details straight into Abook. I've > remapped my "a" key to call that. > > > I'm sure that the solution to this problem is a slam dunk but, as I > > said, I suffer from the dreaded curse of the newbies. > > You gotta start somewhere! > > > Thanks again for your help. > >You're welcome. Total no-brainer on my part. Right after I fired off the last post I discovered that Abook can import directly from the Mutt alias folder. All is well in Newbieland. Thanks again. Rem
Re: Exporting from alias folder
On 2007.10.07 00:26:04 +, Jerry Walker wrote: > Hi, > > On Sat 6 Oct 2007 16:04, Rem P Roberti wrote: > > On 2007.10.06 23:26:07 +, Jerry Walker wrote: > > > On Sat 6 Oct 2007 12:58, Rem P Roberti wrote: > > > > Still searching for a way to export aliases from my alias folder to > > > > Abook via Mutt. Anyone know how to do > > > > that? > > > > > > Use "abook --convert ...". Try "abook --help" for more details. > > > > > Sorry to be dense about this, but how is "abook --convert" invoked from > > within Mutt? Is this something that > > has to be configured via .muttrc? > > Yep. You can bind a key to a macro that runs the appropriate command. For > example I have > > macro generic a "abook\n" "Run Abook" > > in my .muttrc to run abook from Mutt. That works swell, Jerry, and I appreciate the newbie help. Still, I have the feeling that my original question was not well put, so I will try it again. It is very easy to create an alias from a received message just by using the "a" command. This puts the new alias in my .mail_aliases folder, which resides in my home directory. My understanding is that you can transfer selected aliases from that folder to Abook, and that process can be carried off from within Mutt itself. Then you can just prune the .mail_aliases folder for whatever aliases are not to be kept permanently. I'm sure that the solution to this problem is a slam dunk but, as I said, I suffer from the dreaded curse of the newbies. Thanks again for your help. Rem
Re: Exporting from alias folder
On 2007.10.06 23:26:07 +, Jerry Walker wrote: > Hi Rem, > > On Sat 6 Oct 2007 12:58, Rem P Roberti wrote: > > Still searching for a way to export aliases from my alias folder to Abook > > via Mutt. Anyone know how to do > > that? > > Use "abook --convert ...". Try "abook --help" for more details. > > Good luck, > > Will. Sorry to be dense about this, but how is "abook --convert" invoked from within Mutt? Is this something that has to be configured via .muttrc? Rem
Eporting from alias folder
Still searching for a way to export aliases from my alias folder to Abook via Mutt. Anyone know how to do that? Rem
Re: Spellcheck
> > Believe it or not, I actually do know where the "i" key is, but what > > I couldn't figure out was how to use it. > > I know; I was having fun at your expense. I suppose humor doesn't > translate well in email, even with smileys. Sorry, I didn't mean to > offend. > > > What I expected to be able to do was to invoke the spell checker > > directly from within vi, which is no doubt possible, but which so > > far eludes me. > > Ah! Of course, this is indeed quite possible, but nothing you do to > your mutt configuration files will really affect vi much (except the > value of $editor, for obvious reasons). > > How to run a spellchecker in vi depends on what version of vi you're > using. Ancient standards-compatible vi may not have a good way. If > you're using vim (as most vi folk are), then the technique depends on > what version of vim you're using. If you're using version 7.0 and > beyond, all you need to do is run > > :set spell > > (in vim) and it will spellcheck whatever you're editing. If you're > using an older version, you'd have to do something like this: > > :!ispell % > > I used to (before I got vim7) have the following spelling macro in my > vimrc: > > autocmd FileType mail command aspe ':w:!aspell -e -c %:e' > > Which allowed me to trigger aspell (an ispell alternative with a nicer > interface) on my email by executing > > :aspe > > If you're using something like vile or elvis or one of the other > vi-like programs, you'd have to check with their documentation to see > what would work. > > > Nevertheless, once you pointed out to me where the real > > compose screen exists, I find that I really do have a workable spell > > checker. > > Excellent! :) > > ~Kyle Not to worry...no offence was taken. Besides, one of my best assests is a rather thick skin. So, ispell works well enough (although I have heard that aspell is better), but you have motivated me to look into vim. I have become rather attached to vi, and have taken some pains to learn to use it. Unfortunately, there is now only vim and vim6 in the FreeBSD ports collection. Rem
Re: Spellcheck
On 2007.10.05 16:15:42 +, Kyle Wheeler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Friday, October 5 at 01:15 PM, quoth Rem P Roberti: > >On 2007.10.05 21:55:32 +, Michael Tatge wrote: > >> * On Fri, Oct 05, 2007 Rem P Roberti ([EMAIL PROTECTED]) muttered: > >> > > >> > I have "set ispell="/usr/local/bin/ispell"" appended to my .muttrc file > >> > >> So hit "i" in the compose menu to run $ispell. > >> As of lately I use vim's built-in spell checker which is quite neat IMO. > >> > > > >Boy, I really am missing something here. Hit "i"? Compose menu? I'm lost. > > The compose menu is the screen that shows up when you tell mutt to > send an email, just after you finish editing that email. > > The "i" key is the one on the US qwerty keyboard right between the "u" > and "o" keys, above and slightly to the left of the "k" key. ;) > > The ispell setting in mutt is for being able to trigger ispell to > spell check your email before you send it. Mutt does not, however, > force you to check your messages, it just makes it convenient for you > to check them if you desire. By default, the key to do that is the "i" > key (you can, of course, change what key triggers ispell). > > But, let's phrase this another way: what were you *expecting* the > ispell setting in mutt to do? > > ~Kyle Believe it or not, I actually do know where the "i" key is, but what I couldn't figure out was how to use it. That, of course, was because I didn't understand that the compose menu was the screen that followed after doing the edits in vi. What I expected to be able to do was to invoke the spell checker directly from within vi, which is no doubt possible, but which so far eludes me. Nevertheless, once you pointed out to me where the real compose screen exists, I find that I really do have a workable spell checker. Rem N.B. I am a refugee from Windows, so the going has been a bit dicey. But I have learned enough about my system (FreeBSD), and the programs therein to report to you that the die is cast, and there is no turning back.
Re: Spellcheck
On 2007.10.05 21:55:32 +, Michael Tatge wrote: > * On Fri, Oct 05, 2007 Rem P Roberti ([EMAIL PROTECTED]) muttered: > > > > I have "set ispell="/usr/local/bin/ispell"" appended to my .muttrc file > > So hit "i" in the compose menu to run $ispell. > As of lately I use vim's built-in spellchecker which is quite neat IMO. > Boy, I really am missing something here. Hit "i"? Compose menu? I'm lost. Rem
Spellcheck
I have "set ispell="/usr/local/bin/ispell"" appended to my .muttrc file, and "map : !ispell %: e %" appended to my .exrc file. But I am unable to get ispell to play. Is this set up incorrect? Rem
Re: Importing to Abook
On 2007.10.05 09:15:19 +, Michael Tatge wrote: > * On Fri, Oct 05, 2007 Rem P Roberti ([EMAIL PROTECTED]) muttered: > > Hi Everyone. Thank God for this list. I have been searching for a > > way to import addresses from my alias folder to Abook. I know there > > is a way to do it, but so far I have been unable to find the solution. > > A heads up will be most appreciated. > > See abook's --convert switch > > HTH, > > Michael I checked out the info that is contained in the FreeBSD man page, but am unsure of how to invoke the switch. Rem
Importing to Abook
Hi Everyone. Thank God for this list. I have been searching for a way to import addresses from my alias folder to Abook. I know there is a way to do it, but so far I have been unable to find the solution. A heads up will be most appreciated. Rem
Re: Mutt and Abook
On 2007.10.05 00:05:52 +, Kyle Wheeler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Thursday, October 4 at 09:52 PM, quoth Rem P Roberti: > >Can someone please point me toward some info on how I can utilize abook > >from within Mutt. I would like to be able to both use the Abook > >entries, and add new addresses via Mutt. > > http://wiki.mutt.org/?MuttGuide/Aliases > > ~Kyle Thank you! Rem
Mutt and Abook
Can someone please point me toward some info on how I can utilize abook from within Mutt. I would like to be able to both use the Abook entries, and add new addresses via Mutt. Rem
Re: No outgoing mail
On 2007.10.04 14:54:17 +, Kyle Wheeler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Thursday, October 4 at 11:31 AM, quoth Rem P Roberti: > > I had just finished modifying my .muttrc file to source my alias > > folder, and now every time that I try to send an email I get an > > error message stating: Aborted unmodified message. > > That message happens whenever your editor has not updated the > timestamp on the temporary file containing your message. This could > happen because you've done something silly like move/copy that > temporary file elsewhere, or because your filesystem isn't handling > dates right, or any number of reasons. Perhaps in editing your .muttrc > you accidentally changed your $editor setting? > > ~Kyle Okay...newbie eats crow. I did change my editor setting in .muttrc, and there was a bigtime syntax error in the line. Thanks for pointing me in the right direction. Rem
No outgoing mail
Help! I have no idea what I did, but I am no longer able send mail via Mutt. I had just finished modifying my .muttrc file to source my alias folder, and now every time that I try to send an email I get an error message stating: Aborted unmodified message. This happens whether or not I try to send using an alias. Nothing was changed (as far as I can tell) to either my getmail or postfix configurations, and I have no trouble sending with Elm. As I say, I haven't a clue what I did to create this condition, but I sure do need to fix it. Any help is much appreciated. Rem
Re: Saving without headers
On Wed, Oct 03, 2007 at 02:24:44PM -0700, Gary Johnson wrote: > On 2007-10-03, Rem P Roberti <[EMAIL PROTECTED]> wrote: > > > Thanks for the reply. I could not find a reference to the > > decode-save function. Perhaps you could give me a heads up as > > to where I could look for more info. > > You're welcome. Unfortunately, the only mention of it in the mutt > manual is this one line: > >decode-save ESC s make decoded copy (text/plain) and delete > > which also appears in the index and pager help screens. The same is > true for the decode-copy function. You may have to resort to > experimentation or reading the code. > > Regards, > Gary Once again, thank you for the reply. Well, the ESC s seems to want to work, but when I try save a message it tells me that the directory I want to append the message to is not a mailbox. Obviously I have forgotten to do something to my .muttrc file that has to do with mailboxes, but I haven't quite figured that out yet. Rem
Re: Saving without headers
On Wed, Oct 03, 2007 at 01:19:07PM -0700, Gary Johnson wrote: > On 2007-10-03, Rem P Roberti <[EMAIL PROTECTED]> wrote: > > Can someone please tell if it is possible to save mail to a > > folder with only selected headers, or without any headers at > > all. I've been trying to find the answer in my Muttrc file, so > > far without success. > > The decode-save function may do what you want. It is bound to > s by default. It seems to obey 'weed' and the 'ignore' list, > but it also seems to include a few headers that I normally ignore. > In any case, it saves far fewer headers than the normal save-message > function does. > > HTH, > Gary Thanks for the reply. I could not find a reference to the decode-save function. Perhaps you could give me a heads up as to where I could look for more info. Rem
Saving without headers
Can someone please tell if it is possible to save mail to a folder with only selected headers, or without any headers at all. I've been trying to find the answer in my Muttrc file, so far without success. TIA, Rem
