grepmail-users Mailing List for grepmail
Brought to you by:
coppit
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2002 |
Jan
(1) |
Feb
|
Mar
|
Apr
(8) |
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2004 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(11) |
Jul
|
Aug
(2) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
2009 |
Jan
(8) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: David C. <da...@co...> - 2010-01-29 03:10:29
|
On Tue, 26 Jan 2010, Gary . wrote: > What is the purpose of the grepmail cache? I'm presuming to allow search > performance to be increased? Right. > Assuming that is so, how do I use it? It's on by default. You don't usually have to even think about it. :) David _____________________________________________________________________ David Coppit http://coppit.org/ |
From: Gary . <gre...@ga...> - 2010-01-26 19:51:40
|
What is the purpose of the grepmail cache? I'm presuming to allow search performance to be increased? Assuming that is so, how do I use it? Today I tried to initialize the cache by doing what is kind of suggested in the man page ("This is useful if you want to initialize the cache without printing any output.") $ grepmail -MRb -e \(\) * in the directory where I keep my email. It got boring after about three hours of running without any feedback as to progress. Was I doing the right thing? Once initialized, do I somehow have to keep the cache up to date? |
From: David C. <da...@co...> - 2009-08-10 01:22:33
|
On Fri, 10 Apr 2009, Robert Holtzman wrote: > I'm running grepmail 5.3033-2 on Ubuntu 8.04. > > Trying to run the app and got this: > > [holtzm@localhost]~$ grepmail -bBR 'not connecting' /home/holtzm/mail > > /home/holtzm/mail/network > Use of uninitialized value in print at /usr/bin/grepmail line 1663. > Use of uninitialized value in print at /usr/bin/grepmail line 1663. > Use of uninitialized value in print at /usr/bin/grepmail line 1664. > Use of uninitialized value in print at /usr/bin/grepmail line 1665. > Use of uninitialized value in print at /usr/bin/grepmail line 1666. It looks like you have an email in your mailbox that seems to be missing some pretty important headers: print Get_Header_Field($email_header,'From ',$endline); print Get_Header_Field($email_header,'Date:',$endline); print Get_Header_Field($email_header,'From:',$endline); print Get_Header_Field($email_header,'Subject:',$endline); If you run into this again, first update your version of Mail::Mbox::MessageParser with a command like "sudo cpan Mail::Mbox::MessageParser". If it still persists, first try to anonymize the mailbox using the anonymize_mailbox program that is in the grepmail distribution. The problem should still persist after anonymizing the mailbox, in which case you can email the mailbox to me for further debugging. David _____________________________________________________________________ David Coppit http://coppit.org/ |
From: Robert H. <ho...@co...> - 2009-04-11 05:08:33
|
I'm running grepmail 5.3033-2 on Ubuntu 8.04. Trying to run the app and got this: [holtzm@localhost]~$ grepmail -bBR 'not connecting' /home/holtzm/mail > /home/holtzm/mail/network Use of uninitialized value in print at /usr/bin/grepmail line 1663. Use of uninitialized value in print at /usr/bin/grepmail line 1663. Use of uninitialized value in print at /usr/bin/grepmail line 1664. Use of uninitialized value in print at /usr/bin/grepmail line 1665. Use of uninitialized value in print at /usr/bin/grepmail line 1666. There were messages in /home/holtzm/mail/network but it looks like too few. Looked at /usr/bin/grepmail but not being a programmer I saw no problems. I have used this app in the past and it always performed flawlessly. Any thoughts, ideas, comments or help appreciated. -- Bob Holtzman "If you think you're getting free lunch, check the price of the beer" |
From: David C. <da...@co...> - 2009-01-31 08:15:42
|
On Sun, 25 Jan 2009, Dan Pritts wrote: > On Sat, Jan 24, 2009 at 02:03:12AM -0700, Robert Holtzman wrote: >> >> I think I must be losing it in my old age. I completely forgot the -R >> option (You wrote -r. Did you mean -R?) > > presumably. ;) Yeah, it's -R. It's sad to say that it's been so many years since I was knee-deep in grepmail that I had to check the man page. :( David _____________________________________________________________________ David Coppit http://coppit.org/ |
From: Dan P. <da...@in...> - 2009-01-26 02:21:07
|
On Sat, Jan 24, 2009 at 02:03:12AM -0700, Robert Holtzman wrote: > > I think I must be losing it in my old age. I completely forgot the -R > option (You wrote -r. Did you mean -R?) presumably. ;) > Your mail is being read by tight lipped > Homeland Security agents who fail to see > the humor in Doctor Strangelove POE danno -- Dan Pritts, Sr. Systems Engineer Internet2 office: +1-734-352-4953 | mobile: +1-734-834-7224 Imagination. Collaboration. Innovation. May your New Year be filled with Discovery! http://www.Internet2.edu/NewYear2009/ |
From: Robert H. <ho...@co...> - 2009-01-24 09:03:00
|
On Fri, 23 Jan 2009, Dan Pritts wrote: ,> On Fri, Jan 23, 2009 at 11:32:03AM -0700, Robert Holtzman wrote: >> On Fri, 23 Jan 2009, Dan Pritts wrote: >> >>> The syntax you are using searches the file saved-mutt >>> for the string mutt. >>> >>> You probably want something like >>> >>> grepmail -b mutt /var/spool/mail/holtzman > saved-mutt >>> >>> Substitute the actual location of your inbox folder for the /var/spool/mail >>> file i mention. > > a clarification, when i said "folder" i meant mbox file, sometimes called > a mail folder. I didn't mean a directory on the filesystem. > >> That's a little confusing because one of the examples in the man page is >> >> grepmail -hb "Pilot" saved-mail* > > that will search all files beginning with "saved-mail" for the string > "Pilot" in the header. It will output the results to standard output > (which is what your original command did, too, but since it was searching > an empty file it didn't find anything). > >> subject is in before I search? I was under the impression the entire >> contents of the /mail directory would be searched. Could you please >> clarify this? > > It'll search whatever file(s) you tell it to. If you want multiple files > you just specify that; or you can use the -r option to do it recursively on a > directory and all the files and directories in it. > > e.g.: > > grepmail -b mutt /home/holtzm/mail/* > saved-mutt > > grepmail -br mutt /home/holtzm/mail > saved-mutt > > The previous two are not identical; the first will only search files > in /home/holtzm/mail, whereas the second will recurse subdirectories. I think I must be losing it in my old age. I completely forgot the -R option (You wrote -r. Did you mean -R?) Thanks again. -- Bob Holtzman Your mail is being read by tight lipped Homeland Security agents who fail to see the humor in Doctor Strangelove |
From: Dan P. <da...@in...> - 2009-01-24 00:37:45
|
On Fri, Jan 23, 2009 at 11:32:03AM -0700, Robert Holtzman wrote: > On Fri, 23 Jan 2009, Dan Pritts wrote: > > > The syntax you are using searches the file saved-mutt > > for the string mutt. > > > > You probably want something like > > > > grepmail -b mutt /var/spool/mail/holtzman > saved-mutt > > > > Substitute the actual location of your inbox folder for the /var/spool/mail > > file i mention. a clarification, when i said "folder" i meant mbox file, sometimes called a mail folder. I didn't mean a directory on the filesystem. > That's a little confusing because one of the examples in the man page is > > grepmail -hb "Pilot" saved-mail* that will search all files beginning with "saved-mail" for the string "Pilot" in the header. It will output the results to standard output (which is what your original command did, too, but since it was searching an empty file it didn't find anything). > subject is in before I search? I was under the impression the entire > contents of the /mail directory would be searched. Could you please > clarify this? It'll search whatever file(s) you tell it to. If you want multiple files you just specify that; or you can use the -r option to do it recursively on a directory and all the files and directories in it. e.g.: grepmail -b mutt /home/holtzm/mail/* > saved-mutt grepmail -br mutt /home/holtzm/mail > saved-mutt The previous two are not identical; the first will only search files in /home/holtzm/mail, whereas the second will recurse subdirectories. cd /home/holtzm/mail grepmail -b mutt foo bar ack baz > saved-mutt Note that if you do: cd /home/holtzm/mail grepmail -b mutt * > saved-mutt You may hit an infinite recursion; your shell may create "saved-mutt" before it expands the *. This is a shell issue, not a grepmail issue. danno |
From: Robert H. <ho...@co...> - 2009-01-23 18:32:01
|
On Fri, 23 Jan 2009, Dan Pritts wrote: > The syntax you are using searches the file saved-mutt > for the string mutt. > > You probably want something like > > grepmail -b mutt /var/spool/mail/holtzman > saved-mutt > > Substitute the actual location of your inbox folder for the /var/spool/mail > file i mention. That's a little confusing because one of the examples in the man page is grepmail -hb "Pilot" saved-mail* which would apply to me except I am only searching the bodies of the emails. Taking your advice: [holtzm@localhost]~$ grepmail -b mutt /home/holtzm/mail > saved-mutt grepmail: Skipping directory: '/home/holtzm/mail' and grepmail -b mutt /home/holtzm/mail/INCOMING > saved-mutt Success, but does this mean I have to know what mailbox the search subject is in before I search? I was under the impression the entire contents of the /mail directory would be searched. Could you please clarify this? Thanks for the reply and a great app. -- Bob Holtzman "If you think you're getting free lunch, check the price of the beer" |
From: Dan P. <da...@in...> - 2009-01-23 16:17:48
|
The syntax you are using searches the file saved-mutt for the string mutt. You probably want something like grepmail -b mutt /var/spool/mail/holtzman > saved-mutt Substitute the actual location of your inbox folder for the /var/spool/mail file i mention. On Wed, Jan 21, 2009 at 02:59:30PM -0700, Robert Holtzman wrote: > Forgot the attachment the first time. Sorry. > > Not sure if this list is active or not but I'll give it a try anyway. > > Back in July 2008 I installed grepmail and it worked flawlessly. Today I > sent myself a test email containing the word > mutt, created the file ~/saved-mutt then ran "grepmail -bD mutt > saved-mutt". Nothing was written to ~/saved-mutt. The > debug messages told me nothing (probably my lack of knowledge). I have > attached the debug file. |
From: Robert H. <ho...@co...> - 2009-01-21 22:27:23
|
Forgot the attachment the first time. Sorry. Not sure if this list is active or not but I'll give it a try anyway. Back in July 2008 I installed grepmail and it worked flawlessly. Today I sent myself a test email containing the word mutt, created the file ~/saved-mutt then ran "grepmail -bD mutt saved-mutt". Nothing was written to ~/saved-mutt. The debug messages told me nothing (probably my lack of knowledge). I have attached the debug file. Any help would be appreciated. Thanks. -- Bob Holtzman "If you think you're getting free lunch, check the price of the beer" |
From: Robert H. <ho...@co...> - 2009-01-21 22:27:20
|
Not sure if this list is active or not but I'll give it a try anyway. Back in July 2008 I installed grepmail and it worked flawlessly. Today I sent myself a test email containing the word mutt, created the file ~/saved-mutt then ran "grepmail -bD mutt saved-mutt". Nothing was written to ~/saved-mutt. The debug messages told me nothing (probably my lack of knowledge). I have attached the debug file. Any help would be appreciated. Thanks. -- Bob Holtzman "If you think you're getting free lunch, check the price of the beer" |
From: Dan P. <da...@in...> - 2007-11-06 19:47:42
|
If the mailbox happenes to be accessible via IMAP, you might look at using the mailutil program that comes with the UW imapd distribution. That way imap would handle all the locking for you. On Tue, Nov 06, 2007 at 12:13:54PM -0500, David Coppit wrote: > On Tue, 6 Nov 2007, Michiel van Es wrote: > > > I have a question, I want to use grepmail in a cronjob script to check a mbox file and remove > > al mails older then 1 month (or 2 weeks). > > I am not a guru with shell/bash scripting but perhaps someone has a little tip for me? > > The problem is that you'll want to lock the file during the operation so > that new incoming mails won't get lost. But something like this (untested) > should work: > > #!/bin/sh > > lock_mailbox_somehow(); > grepmail -d 'since 1 month ago' mailbox > tempmailbox; > mv tempmailbox > mailbox > unlock_mailbox_somehow(); > |
From: David C. <da...@co...> - 2007-11-06 17:14:24
|
On Tue, 6 Nov 2007, Michiel van Es wrote: > I have a question, I want to use grepmail in a cronjob script to check a mbox file and remove > al mails older then 1 month (or 2 weeks). > I am not a guru with shell/bash scripting but perhaps someone has a little tip for me? The problem is that you'll want to lock the file during the operation so that new incoming mails won't get lost. But something like this (untested) should work: #!/bin/sh lock_mailbox_somehow(); grepmail -d 'since 1 month ago' mailbox > tempmailbox; mv tempmailbox > mailbox unlock_mailbox_somehow(); David _____________________________________________________________________ David Coppit da...@co... The College of William and Mary http://coppit.org/ This time, let's elect a representative instead of a leader. |
From: Michiel v. Es <mic...@in...> - 2007-11-06 14:02:29
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> Hi,<br> <br> I have a question, I want to use grepmail in a cronjob script to check a mbox file and remove al mails older then 1 month (or 2 weeks).<br> I am not a guru with shell/bash scripting but perhaps someone has a little tip for me?<br> <br> Thanks for your help.<br> <br> Kind regards,<br> <br> Michiel<br> <!--[if !mso]> <STYLE>v\:* { BEHAVIOR: url(#default#VML) } o\:* { BEHAVIOR: url(#default#VML) } w\:* { BEHAVIOR: url(#default#VML) } .shape { BEHAVIOR: url(#default#VML) } </STYLE> <![endif]--><!--[if gte mso 9]><xml> <o:DocumentProperties> <o:Author>Michiel van Es</o:Author> <o:LastAuthor>Michiel van Es</o:LastAuthor> <o:Revision>2</o:Revision> <o:TotalTime>1</o:TotalTime> <o:Created>2005-10-14T11:41:00Z</o:Created> <o:LastSaved>2005-10-14T11:42:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>40</o:Words> <o:Characters>229</o:Characters> <o:Company>info.nl</o:Company> <o:Lines>1</o:Lines> <o:Paragraphs>1</o:Paragraphs> <o:CharactersWithSpaces>268</o:CharactersWithSpaces> <o:Version>11.6568</o:Version> </o:DocumentProperties> </xml><![endif]--><!--[if gte mso 9]><xml> <w:WordDocument> <w:Zoom>140</w:Zoom> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <w:ValidateAgainstSchemas/> <w:SaveIfXMLInvalid >false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" LatentStyleCount="156"> </w:LatentStyles> </xml><![endif]--> </body> </html> |
From: Michael C. T. <mc...@to...> - 2005-10-27 04:11:16
|
On Wed, Oct 26, 2005 at 11:39:53PM -0600, Justin Gombos wrote: > Is it possible to force grepmail to recurse into directories, rather > than skipping them? $ man grepmail | grep -C1 recurs Reformatting grepmail(1p), please wait... -R Causes grepmail to recurse any directories encountered. |
From: Justin G. <mi...@ve...> - 2005-10-27 03:36:13
|
Is it possible to force grepmail to recurse into directories, rather than skipping them? |
From: David C. <da...@co...> - 2005-08-08 12:34:47
|
On Sun, 7 Aug 2005, Justin Gombos wrote: > grepmail -iY \^TO:.*janedoe Mail/sent-mail/* Try this: grepmail -iY '^TO:' janedoe Mail/sent-mail/* The -Y flag specifies the header(s) you want to search. The pattern is separate. I'll make the docs more clear. Thanks, David _____________________________________________________________________ David Coppit da...@co... The College of William and Mary http://coppit.org/ "They have computers, and they may have other weapons of mass destruction." Former Attorney General Janet Reno, speaking at LLNL of modern criminals |
From: Justin G. <mi...@bi...> - 2005-08-07 21:34:26
|
I'm trying to find all messages I sent to "janedoe" using the following commandline, and it comes up with nothing: grepmail -iY \^TO:.*janedoe Mail/sent-mail/* Shouldn't that hit on every email addressed to: "Jane Doe" <ja...@is...> Can anyone see whether I did something wrong? I also tried it this way, with the same results: grepmail -iY '^TO:.*janedoe' Mail/sent-mail/* |
From: Justin G. <mi...@bi...> - 2005-06-22 03:05:38
|
* Dan Pritts <da...@in...> [2005-06-20 18:57]: > > To get around UTF-8 problems you might try setting LANG=C before you > start the installation process for Date::Manip and then doing the > same thing before you start grepmail. Of course if plain ascii > doesn't work for you, this won't help. Thanks Dan. That was right on the money. Everything went smooth once I set that variable. It's nice to finally see grepmail work. It works well with Moritz's mutt wrapper script. |
From: Dan P. <da...@in...> - 2005-06-20 16:09:58
|
On Fri, Jun 17, 2005 at 08:13:49PM -0600, Justin Gombos wrote: > DB<1> print @INC > /usr/lib/perl5/5.8.0/i386-linux-thread-multi/usr/lib/perl5/5.8.0/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/usr/lib/perl5/site_perl/5.8.0/usr/lib/perl5/site_perl/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/usr/lib/perl5/vendor_perl/5.8.0/usr/lib/perl5/vendor_perl/usr/lib/perl5/5.8.0/i386-linux-thread-multi/usr/lib/perl5/5.8.0. > DB<2> > > There are no delimiters between paths. Could this be my problem? Any Mine works, and I have the same lack of delimiters. So probably not your problem. To get around UTF-8 problems you might try setting LANG=C before you start the installation process for Date::Manip and then doing the same thing before you start grepmail. Of course if plain ascii doesn't work for you, this won't help. danno |
From: Justin G. <mi...@bi...> - 2005-06-18 02:01:41
|
The 'make test' stage of the automatic install for date::manip results in copious errors, like: Malformed UTF-8 character (1 byte, need 3, after start byte 0xe8) at /root/.cpan/build/DateManip-5.44/blib/lib/Date/Manip.pm line 7212. Malformed UTF-8 character (unexpected non-continuation byte 0x6c, immediately after start byte 0xfa) at /root/.cpan/build/DateManip-5.44/blib/lib/Date/Manip.pm line 7215. This problem is common enough that the documentation acknowledges it, and suggests the manual install. The manual install involves running the debugger and getting the value of @INC. So here's what results: [DateManip-5.44]# perl -d Manip.pm Loading DB routines from perl5db.pl version 1.19 Editor support available. Enter h or `h h' for help, or `man perldebug' for more help. Date::Manip::(Manip.pm:12): $OS="Unix"; DB<1> print @INC /usr/lib/perl5/5.8.0/i386-linux-thread-multi/usr/lib/perl5/5.8.0/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/usr/lib/perl5/site_perl/5.8.0/usr/lib/perl5/site_perl/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/usr/lib/perl5/vendor_perl/5.8.0/usr/lib/perl5/vendor_perl/usr/lib/perl5/5.8.0/i386-linux-thread-multi/usr/lib/perl5/5.8.0. DB<2> There are no delimiters between paths. Could this be my problem? Any suggestions on where to fix this? I did not find an INC variable or these contents in Manip.pm. |
From: David C. <da...@co...> - 2005-06-06 01:19:41
|
On Sun, 5 Jun 2005, Justin Gombos wrote: > Failed 6/18 test scripts, 66.67% okay. 14/322 subtests failed, 95.65% okay. By Tuesday I'll be releasing new versions of almost all my packages. I did address some test problems, so this may already be fixed. Let me know if the new version doesn't fix it. Regards, David _____________________________________________________________________ David Coppit da...@co... The College of William and Mary http://coppit.org/ "Children today are tyrants. The contradict their parents, gobble their food, and tyrannize their teachers." - Socrates, 469-399BC |
From: Dan P. <da...@in...> - 2005-06-05 18:27:52
|
On Sun, Jun 05, 2005 at 09:47:19AM -0400, David Coppit wrote: > Dan't solution is the best one. You can even tell the CPAN module not to > prompt you when it wants to install dependent modules. (There's also > CPAN2, a newer alternative to CPAN.) one thought - if you are using a system that provides some perl modules as "packages" (typical of linux distros) or "ports" (bsd systems), someone may have already set this up for you and all you'll need to do is use the installation system for these packages/ports. It should automatically grab all the perl stuff you need too - if everything's working properly, sigh. This next may be obvious but may not be.... Also note if you are using something that you've installed via the CPAN module, when you upgrade perl you'll have to install it again and it probably won't happen automatically. This is not necessarily true but often is - if you're using a vendor-supplied perl and they come out with a minor bugfix this probably won't break cpan installed stuff. If you're wondering why someone would bother with all this perl module dependency crap, the reason is that it makes it a LOT easier for someone like David to write something like grepmail - rather than having to start from scratch, he can use the building blocks that others have contributed. danno -- dan pritts - systems administrator - internet2 734/352-4953 office 734/834-7224 mobile |
From: Dan P. <da...@in...> - 2005-06-05 18:20:45
|
On Sun, Jun 05, 2005 at 09:52:48AM -0600, Justin Gombos wrote: > configured. Apparently it wasn't, because it launched the interview > again. it's saved per user so if you did spamassassin as root and grepmail as yourself it wouldn't have carried over. > Configuration settings didn't stick even within the same > session. It would ask me to enter paths for tools like gzip multiple > times. I also configured it to follow dependancies automatically, yet > it prompted me for every package. I'm guessing that whatever directory you told it to use to hold the configuration isn't writeable. (told it, accepted the default, whatever) Or maybe you've got a full disk or something like that. the default will typically be your home directory/.cpan the configuration file is in , eg on my old system: /usr/lib/perl5/5.6.1/CPAN/Config.pm /home/danno/.cpan/CPAN/MyConfig.pm > Here are the test results that it reported for one of the packages: can't help you here although i have a feeling that if you reconfigure the cpan module properly (so configuration sticks) the builds will work better. danno -- dan pritts - systems administrator - internet2 734/352-4953 office 734/834-7224 mobile |