Re: why did no one pick up maintainership of procmail?
On Fri, May 20, 2016 at 4:23 PM, Patrick Shanahan <p...@opensuse.org> wrote: > * Xu Wang <xuwang...@gmail.com> [05-20-16 16:14]: >> procmail seems so useful and I do not know of a good replacement for >> some of its resources. I use the formail tool quite often. >> >> I find it strange that such a useful tool never gained a maintainer. >> Here is a useful message: >> http://marc.info/?l=openbsd-ports=141634350915839=2 >> but to me it explains why the author had to leave, not why no one picked it >> up. >> >> Is procmail fundamentally flawed or it is just that no one has found >> the time and love to commit to maintaining it again? >> >> Of course I do not judge. I have not done anything to help (except >> this complaint!). I am just curious. >> >> Please let me know if such an email is off-topic (I suppose this does >> not have direct relevance to mutt) and I will refrain from similar >> questions in the future. > > There is a procmail list and there is traffic there: > List-Subscribe: > <http://mailman.rwth-aachen.de/mailman/listinfo/procmail>, > <mailto:procmail-requ...@lists.rwth-aachen.de?subject=subscribe> Thank you, I will check it up. Kind regards, Xu
Re: why did no one pick up maintainership of procmail?
* Xu Wang <xuwang...@gmail.com> [05-20-16 16:14]: > procmail seems so useful and I do not know of a good replacement for > some of its resources. I use the formail tool quite often. > > I find it strange that such a useful tool never gained a maintainer. > Here is a useful message: > http://marc.info/?l=openbsd-ports=141634350915839=2 > but to me it explains why the author had to leave, not why no one picked it > up. > > Is procmail fundamentally flawed or it is just that no one has found > the time and love to commit to maintaining it again? > > Of course I do not judge. I have not done anything to help (except > this complaint!). I am just curious. > > Please let me know if such an email is off-topic (I suppose this does > not have direct relevance to mutt) and I will refrain from similar > questions in the future. There is a procmail list and there is traffic there: List-Subscribe: <http://mailman.rwth-aachen.de/mailman/listinfo/procmail>, <mailto:procmail-requ...@lists.rwth-aachen.de?subject=subscribe> -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://linuxcounter.net
why did no one pick up maintainership of procmail?
procmail seems so useful and I do not know of a good replacement for some of its resources. I use the formail tool quite often. I find it strange that such a useful tool never gained a maintainer. Here is a useful message: http://marc.info/?l=openbsd-ports=141634350915839=2 but to me it explains why the author had to leave, not why no one picked it up. Is procmail fundamentally flawed or it is just that no one has found the time and love to commit to maintaining it again? Of course I do not judge. I have not done anything to help (except this complaint!). I am just curious. Please let me know if such an email is off-topic (I suppose this does not have direct relevance to mutt) and I will refrain from similar questions in the future. Kind regards, xu
inbuilt pop and procmail
Hello, I am using the inbuilt pop and smtp for gmail. Is there a way to forward all received emails from pop server to procmail instead of putting those to the spoolfile? Thanks Sri
Re: inbuilt pop and procmail
* Srikrishan Malik srikrishanma...@gmail.com [06-24-14 02:02]: I am using the inbuilt pop and smtp for gmail. Is there a way to forward all received emails from pop server to procmail instead of putting those to the spoolfile? Not directly using mutt, but a simple matter using fetchmail or another mail retrieval agent. I use fetchmail. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://linuxcounter.net
Re: inbuilt pop and procmail
On Tue, Jun 24, 2014 at 04:47:45PM -0400, Patrick Shanahan wrote: * Srikrishan Malik srikrishanma...@gmail.com [06-24-14 02:02]: I am using the inbuilt pop and smtp for gmail. Is there a way to forward all received emails from pop server to procmail instead of putting those to the spoolfile? Not directly using mutt, but a simple matter using fetchmail or another mail retrieval agent. I use fetchmail. Yeah, I shifted to that mode last night. I tried to change code to call procmail after a mail is fetched, but it does not seem that simple. I will try again when I get some time. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://linuxcounter.net
Re: inbuilt pop and procmail
* Srikrishan Malik srikrishanma...@gmail.com [06-24-14 23:30]: On Tue, Jun 24, 2014 at 04:47:45PM -0400, Patrick Shanahan wrote: * Srikrishan Malik srikrishanma...@gmail.com [06-24-14 02:02]: I am using the inbuilt pop and smtp for gmail. Is there a way to forward all received emails from pop server to procmail instead of putting those to the spoolfile? Not directly using mutt, but a simple matter using fetchmail or another mail retrieval agent. I use fetchmail. Yeah, I shifted to that mode last night. I tried to change code to call procmail after a mail is fetched, but it does not seem that simple. I will try again when I get some time. iiuc, mutt's internal pop is actually reading mail on the server somewhat similar to imap, ie: you do not really have a local copy stored, ie: mutt is not a MRA, but a mail reader/client. I guess you could pipe the current email to procmail for local storage, ie: | formail -ds procmail this would use the procmail recipies and store mail accordingly. But you can save or copy the current email to the file/directory of your choice, also . -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://linuxcounter.net
Re: inbuilt pop and procmail
On Wed, Jun 25, 2014 at 08:59:59AM +0530, Srikrishan Malik wrote: On Tue, Jun 24, 2014 at 04:47:45PM -0400, Patrick Shanahan wrote: * Srikrishan Malik srikrishanma...@gmail.com [06-24-14 02:02]: I am using the inbuilt pop and smtp for gmail. Is there a way to forward all received emails from pop server to procmail instead of putting those to the spoolfile? Not directly using mutt, but a simple matter using fetchmail or another mail retrieval agent. I use fetchmail. Yeah, I shifted to that mode last night. I tried to change code to call procmail after a mail is fetched, but it does not seem that simple. I will try again when I get some time. I use fetchmail to get email from a pop server. It is fed to procmail via a ~/.forward file. The contents are | /usr/bin/procmail. HTH, Jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (609) 477-8330 (C)
Re: 100,000 messages, and counting., procmail mailinglist to new inbox recipe
Most importantly, there is a nice procmail recipe in that procmailrc that
creates list inboxes automatically
as soon as you sign up for a mailing list, procmail will create it as a new
inbox for you automatically... pretty cool
:0:
* ^((List-Id|X-(Mailing-)?List):(.*[]\/[^]*))
{
LISTID=$MATCH
:0:
* LISTID ?? ^\/[^@\.]*
lists/$MATCH
}one inbox for each mailig list, switch to them with 'c?'
- Original Message -
From: Michael Ole Olsen g...@gmx.net
To: Michael Ole Olsen g...@gmx.net; mutt-users@mutt.org; Alan
Mackenzie a...@muc.de
Sent: Monday, February 17, 2014 9:43 PM
Subject: Re: 100,000 messages, and counting.
https://svn.rlogin.dk/dotfiles/muttrc
https://svn.rlogin.dk/dotfiles/procmailrc
Some inspriation for many mboxes perhaps
Spamassassin,procmail for every mbox,priority mails etc.
Mutt watching each inbox, only alerting on new mails in those inboxes that
I care about
Send hooks / alternate identities etc. in muttrc (so by pressing 8 I
change to 'trading' mbox, and my email changes when I reply to certain
mails - ebay i.e., as they only allow you to reply from your ebay email)
by pressing 'v' when I send I can chose between 20+ emails I got and it
will use msmtp to send with, from those new emails after chosing
Had one mbox for facebook too, but unsubscribed from that..
facebook mbox... who wants that stuff in their regular inbox
Same goes for anything that has 'order','bestellung','invoice' in title,
goes into my 'trading' inbox so I don't have to have it floating in my
inbox
will get an announcement in mutt that I can press 'c' to change to trading
inbox and view the mail
Procmail is also nice for creating a 'p5911' priority title for your
emails
if you receive important emails, then they will never be sent into spam by
spamassassin if they have that in the title
Spamassassin feeds on my spam once a day, 500MB and learns from it, so
very few spam make it into my inbox, maybe 1 a day max
Procmail is very helpful with mutt, wouldn't be without it..
- Original Message -
From: Michael Ole Olsen g...@gmx.net
To: mutt-users@mutt.org; Alan Mackenzie a...@muc.de
Sent: Monday, February 17, 2014 9:22 PM
Subject: Re: 100,000 messages, and counting.
Split between mailboxes and logrotate your mailboxes too(with a custom
script that checks size and does stuff to it)
I only got inbox of 5000, 150MB mailbox after 10+ years in mutt, but spam
is 500MB and root is 50k so I never open it, takes too long to open,
spam takes many seconds too
Maildir is really the best thing there is for large mailboxes, it only
opens headers usually, no need to read the whole file when opening the
mail box
I got maybe 30-40 mboxes, one for each mailing list, inbox, auction
sites(trading),sent,spam,root,work inbox,work inbox2 etc.
Mutt will watch those that you specify are important... no need to read
all mailinglists everyday(too much info)
make mutt watch those mboxes which are important and alert you so you can
change to them with 'c'
If you rotate your mailboxes you can write a custom script that greps all
rotated mailboxes too for finding your stuff
.. or you could just use Maildir, mbox is not good for large mboxes
If you don't use maildir you can keep upgrading servers/disks every year
to make it fast enough to open your mailboxes
but maildir only fetches headers, so much faster, it even caches headers,
reducing load time a lot
I use procmail to forward into different mailboxes, then I make mutt
watch those
Many inboxes, many emails in the same client, that is what mutt does well
(with send-hooks/folder-hooks)
Then I combine all my own emails into one inbox, but work emails/trading
stuff etc. into separate inboxes
I was switching to Maildir due to this problem you mention(mbox is not
good for large files unless you got plenty ram/fast disks)
unfortunately my inbox file must have been corrupted, so it could not be
converted... due to disk crashes
so now I am still with mbox 5 years later, even slower than before :)
- Original Message -
From: Alan Mackenzie a...@muc.de
To: mutt-users@mutt.org
Sent: Monday, February 17, 2014 8:58 PM
Subject: Re: 100,000 messages, and counting.
Hi, Bastian.
On Mon, Feb 17, 2014 at 08:42:16PM +0100, bastian-muttu...@t6l.de wrote:
On 17Feb14 18:50 +, Alan Mackenzie wrote:
My inbox has now reached the grand total of 100,000 messages
(_exactly_
100,000, coincidentally enough). This is partly a result of me
being
subscribed to too many mailing lists, and partly of me not getting
around to clearing things out.
mbox or maildir?
mbox. I've never used maildir, but it strikes me that it would be
slower, not counting the initial 12s loading time.
(Yes, I know I could do clever things to split incoming messages
amongst
several mailboxes, but I don't _want_ to.)
I also have just two mailboxes.
inbox and trash! That's enough.
For sorting/splitting there is mairix
Re: procmail vs dovecote (was Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?)
On Sat, Nov 10, 2012 at 10:37:04PM +, Tony's unattended mail wrote: However, I find dovecot deliver (which uses the sieve language for filtering) to be much more readable/writable than procmail. Sieve does not include regular expressions -- I shit you not. Dovecote needs regular expression capability to be shoe-horned in by some hokey plugin. Regular expressions are quite fundamental to a mail filtering language that has an appropriate amount of expressive power. It's bizarre that sieve is presented as a thought out successor to procmail complete with an RFC, and yet it excludes something as essential as regular expressions. I'm resisting sieve because the C-style makes the code look cluttered, and it lacks expressive power. The one aspect that may compel a switch to sieve is the fact that it is MIME-aware. MIME predates procmail, and it's a shame that procmail has become unmaintained. OTOH, I might rather have third party tools for MIME than third party tools for regular expressions. I simply have a custom script written in Python, hence I have all the RE and/or other technology I need without much effort. My filter rules *aren't* written in Python or any language as such, they are in a format that is as user-friendly (well, me friendly) as possible and are thus a straight text file with very little special syntax. The *program* takes care of that, it's what computers are good at, why should I faff about with funny characters, layout, etc. when the computer can do it all for me. My filter file has the following format:- cheddar Li cheddar-us...@lists.halon.org.uk daboLi dabo-us...@leafe.comdabo-users dbacruising Li dbacruis...@lists.shire.net dbamain Li dbam...@lists.shire.net dbamatters Li dbaassociationmatt...@lists.shire.net dbasocial Li dbasoc...@lists.shire.net dia Li dia-l...@gnome.org digitempLi digit...@googlegroups.com dnsmasq Li dnsmasq-disc...@lists.thekelleys.org.uk Dnsmasq-discuss Where the first column is both the mutt alias for the list *and* the directory (under Li) where the incoming list mail is stored. The second column is a destination directory (some things get directed to a Ju - junk - hierarchy). The third column is a string to match in either To: or Cc:. The fourth (optional) column is a string to remove from the subject line if found between []. My Python script to implement all this is only a 100 lines or so of code in total. When I subscribe to a new mailing list I just add the appropriate line to the above filter file and that's it, nothing else to do at all. A couple of very simple scripts get what's needed from the file to provide (as I said) a mutt alias for the list and to add the list to provide what is needed for mutt 'lists', 'subscribe' and 'mailboxes'. ... and as I was saying the filter file itself is in an incredibly simple format, no XML, no indenting, no block structure, no funny characters required. About the only 'special' thing is that you can add comments by having lines starting with a #. -- Chris Green
procmail vs dovecote (was Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?)
However, I find dovecot deliver (which uses the sieve language for filtering) to be much more readable/writable than procmail. Sieve does not include regular expressions -- I shit you not. Dovecote needs regular expression capability to be shoe-horned in by some hokey plugin. Regular expressions are quite fundamental to a mail filtering language that has an appropriate amount of expressive power. It's bizarre that sieve is presented as a thought out successor to procmail complete with an RFC, and yet it excludes something as essential as regular expressions. I'm resisting sieve because the C-style makes the code look cluttered, and it lacks expressive power. The one aspect that may compel a switch to sieve is the fact that it is MIME-aware. MIME predates procmail, and it's a shame that procmail has become unmaintained. OTOH, I might rather have third party tools for MIME than third party tools for regular expressions.
Re: procmail vs dovecote (was Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?)
/ Tony's unattended mail wrote on Sat 10.Nov'12 at 22:37:04 + / However, I find dovecot deliver (which uses the sieve language for filtering) to be much more readable/writable than procmail. Sieve does not include regular expressions -- I shit you not. Dovecote needs regular expression capability to be shoe-horned in by some hokey plugin. Regular expressions are quite fundamental to a mail filtering language that has an appropriate amount of expressive power. It's bizarre that sieve is presented as a thought out successor to procmail complete with an RFC, and yet it excludes something as essential as regular expressions. I'm resisting sieve because the C-style makes the code look cluttered, and it lacks expressive power. The one aspect that may compel a switch to sieve is the fact that it is MIME-aware. MIME predates procmail, and it's a shame that procmail has become unmaintained. OTOH, I might rather have third party tools for MIME than third party tools for regular expressions. For what it's worth, I have used both of the above and now I only use procmail. Some experienced folk like Cameron have made very good points about its problems, but for me, it does the job nicely. I've been using it for about 3 years, maybe more and i still am learning about its complexities but it's a good tool in my opinion. I once had a set up that used procmail recipies in conjunction with dovecot deliver and that worked great for me. But I work from home all the time now so have no need for dovecot or any other IMAP server, not yet anyway.
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Thu, Nov 08, 2012 at 03:17:35AM +0200, Nikola Petrov wrote: No it doesn't deliver them to you. It sort of filters them online on the server. You can then use something like offlineimap to deliver them locally to you. I use imapfilter + offlineimap + notmuch + mutt and I am far from happy with my setup at the moment. So what would you prefer? -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Fri, Nov 09, 2012 at 02:49:48PM +0200, Nikola Petrov wrote: On Fri, Nov 09, 2012 at 11:17:06PM +1300, Chris Bannister wrote: On Thu, Nov 08, 2012 at 03:17:35AM +0200, Nikola Petrov wrote: No it doesn't deliver them to you. It sort of filters them online on the server. You can then use something like offlineimap to deliver them locally to you. I use imapfilter + offlineimap + notmuch + mutt and I am far from happy with my setup at the moment. So what would you prefer? Hi, I am not sure I understand your question? Ummm, Is What would make you more happy? a better question? -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Thu, Nov 08, 2012 at 03:17:35AM +0200, Nikola Petrov wrote: On Wed, Nov 07, 2012 at 05:35:45PM +, Chris Green wrote: I am using imapfilter with lua configuration file for my imap account. That does the job for me and I like the fact that I declare my filters with actual code(be it lua, python or what not) How does that actually work? I've found its home at https://github.com/lefcha/imapfilter but the documentation doesn't really tell me what it does (maybe my fault!). Does it move E-Mails around on the IMAP server, or does it collect them from the IMAP server and deliver them to you locally? Or does it do something else? No it doesn't deliver them to you. It sort of filters them online on the server. You can then use something like offlineimap to deliver them locally to you. I use imapfilter + offlineimap + notmuch + mutt and I am far from happy with my setup at the moment. OK, thanks for the description, I don't think it's quite where I want to be. -- Chris Green
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Wed, Nov 07, 2012 at 04:33:58PM -0600, David Champion wrote: * On 07 Nov 2012, Derek Martin wrote: On Wed, Nov 07, 2012 at 08:48:08PM +, Chris Green wrote: server retrying if my SMTP server isn't running (or connected). That's one of the reasons I'd quite like to move away from SMTP. It *should* be OK but I'm relying on the other end to behave properly. It will. It has to. If it didn't, e-mail on the internet would be horribly unreliable. I hate to break it to you, but :) I've used IMAP pickup in the past and it's OK for some IMAP servers. A year or two ago my employer moved my mailbox to MS Exchange. Exchange doesn't (necessarily?) hand you the exact e-mail it received. It parses incoming mail, stores the parsed components, and reconstructs the message the best it can figure when you pick it up via IMAP or POP. Along the way it might modify or remove some components for no good reason; for example, multipart/alternative with text/plan and text/html invisibly becomes just a text/html message. I've also heard of its breaking crypto, although I haven't seen that myself for a while. So I forward my mail via SMTP away from my employer now. Yes, I realise there are good and bad places that deliver mail to you! :-) If I move from SMTP delivery to collecting it myself (from POP3 or IMAP) it will be from exactly the same source, my Tsohost web hosting service which (in many people's opinions) is excellent. All I have to do is change the ultimate destination of all my E-Mail from zbmc.eu (whose MX record points at my home LAN) to a POP3 mailbox on the TsoHost servers and then collect from that POP3 mailbox. I'm thinking in fact that I'm going to stay with much the same system as I already have but my Python filter script will collect E-Mail direct from the Tsohost POP3 server instead of having it fed into its standard input by the .forward. I already have *another* Python script that collects mail from a Tsohost POP3 box so I know how to do that already, all I need to do is merge a few bits of existing code. -- Chris Green
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
/ Chris Green wrote on Thu 8.Nov'12 at 10:51:59 + / On Wed, Nov 07, 2012 at 04:33:58PM -0600, David Champion wrote: * On 07 Nov 2012, Derek Martin wrote: On Wed, Nov 07, 2012 at 08:48:08PM +, Chris Green wrote: server retrying if my SMTP server isn't running (or connected). That's one of the reasons I'd quite like to move away from SMTP. It *should* be OK but I'm relying on the other end to behave properly. It will. It has to. If it didn't, e-mail on the internet would be horribly unreliable. I hate to break it to you, but :) I've used IMAP pickup in the past and it's OK for some IMAP servers. A year or two ago my employer moved my mailbox to MS Exchange. Exchange doesn't (necessarily?) hand you the exact e-mail it received. It parses incoming mail, stores the parsed components, and reconstructs the message the best it can figure when you pick it up via IMAP or POP. Along the way it might modify or remove some components for no good reason; for example, multipart/alternative with text/plan and text/html invisibly becomes just a text/html message. I've also heard of its breaking crypto, although I haven't seen that myself for a while. So I forward my mail via SMTP away from my employer now. Yes, I realise there are good and bad places that deliver mail to you! :-) If I move from SMTP delivery to collecting it myself (from POP3 or IMAP) it will be from exactly the same source, my Tsohost web hosting service which (in many people's opinions) is excellent. All I have to do is change the ultimate destination of all my E-Mail from zbmc.eu (whose MX record points at my home LAN) to a POP3 mailbox on the TsoHost servers and then collect from that POP3 mailbox. I'm thinking in fact that I'm going to stay with much the same system as I already have but my Python filter script will collect E-Mail direct from the Tsohost POP3 server instead of having it fed into its standard input by the .forward. I already have *another* Python script that collects mail from a Tsohost POP3 box so I know how to do that already, all I need to do is merge a few bits of existing code. -- Chris Green Hi Chris, personally, i'd stick with what your current set-up. Since I set up my own mta and security software i've never been happier with it. I much prefer the flexibility of being able to control almost all aspects of my mail delivery, reading and sending; including the DNS configuration etc... What I did do, though, is look into OS's and software that provide the security we all need, whether collecting mail from remote IMAP storage or POP3, or having it routed directly using smtp. I stick with BSD systems and use a number of different security software on my end to deal with zombies, malware filtering, spam filtering, etc. They are all generally well documented as you no doubt know, and certainly great efforts have been made to make installation and configuration of these software easy(-ish). The only downfall I think is the time involved with setting up and upgrading and monitoring these things. So, do you have the time and will to invest in doing that? As you've written some nice tools already, it sounds like you know what you're doing so stick with it i'd say. Plus, for me, I find it great fun and interesting learning about these things. I've learned loads by getting stuck in and engrossed in it all. Some people, however, have been there and done that and simply just can't be bothered with it anymore and/or would rather spend their time on something else. Jamie
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
fetchmail + maildrop works for me. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. pgpGksnsN8kgQ.pgp Description: PGP signature
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Wed, Nov 07, 2012 at 10:48:45AM -0600, Derek Martin wrote: On Wed, Nov 07, 2012 at 02:15:41PM +, Chris Green wrote: What does everyone else here do for collecting mail and filtering mail with mutt? Fetchmail and procmail. Ugly, but ubiquitous and reliable. A friend pointed me at something better for mail filtering, but I can't recall what it was... mainly because I haven't gotten around to looking into it, on account of the fact that my current solution works well and requires no learning curve. Learning a new mail filter system is very low on the priority list. I'm guessing 'sieve'. Haven't tried it. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. pgpY9juePS2uk.pgp Description: PGP signature
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Thu, Nov 08, 2012 at 01:03:07PM +, Jamie Paul Griffin wrote: Hi Chris, personally, i'd stick with what your current set-up. Ditto. I don't currently do this but that's only because port 25 is blocked by my ISP. I've run my mail this way before and would do it again if it were a practical option. -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience. pgpYNShC3vIom.pgp Description: PGP signature
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
* Derek Martin inva...@pizzashack.org [11-08-12 12:06]: On Thu, Nov 08, 2012 at 01:03:07PM +, Jamie Paul Griffin wrote: Hi Chris, personally, i'd stick with what your current set-up. Ditto. I don't currently do this but that's only because port 25 is blocked by my ISP. I've run my mail this way before and would do it again if it were a practical option. Why not change postfix master.cf to use another port 1024? Not a big thing, one line to edit and restart postfix. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Thu, Nov 08, 2012 at 11:06:35AM -0600, Derek Martin wrote: On Thu, Nov 08, 2012 at 01:03:07PM +, Jamie Paul Griffin wrote: Hi Chris, personally, i'd stick with what your current set-up. Ditto. I don't currently do this but that's only because port 25 is blocked by my ISP. I've run my mail this way before and would do it again if it were a practical option. Er, we're talking (or at least I'm talking) about mail delivery *from* your ISP to your computer at home (or wherever). Your ISP blocking port 25 won't affect this at all, it's your receiving computer that needs to have port 25 open. -- Chris Green
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
/ Chris Green wrote on Thu 8.Nov'12 at 18:13:10 + / On Thu, Nov 08, 2012 at 11:06:35AM -0600, Derek Martin wrote: On Thu, Nov 08, 2012 at 01:03:07PM +, Jamie Paul Griffin wrote: Hi Chris, personally, i'd stick with what your current set-up. Ditto. I don't currently do this but that's only because port 25 is blocked by my ISP. I've run my mail this way before and would do it again if it were a practical option. Er, we're talking (or at least I'm talking) about mail delivery *from* your ISP to your computer at home (or wherever). Your ISP blocking port 25 won't affect this at all, it's your receiving computer that needs to have port 25 open. -- Chris Green Yes as far as I know, the ISP blocking port 25 thing is for sending mail out, in which case you can use your mta to send through a smarthost. Receiving I set up DNS to forward mail to my IP, and port forwarding on my router at home to the machine that has an smtp daemon listening on port 25 or as Patrick said, listening on a different port like the submission port for example.
What are the current fetchmail/getmail and/or procmail/maildrop utilities?
I currently have my mail delivered to my desktop system using SMTP as the system is on all the time and has a static IP. However I always get paranoid when I reconfigure it and/or do other maintenance so I'm considering moving back to a fetchmail/getmail based system. I also have a fairly complex mail filtering script I wrote myself in Python which is fed mail via .forward. What's the current state of the art way to collect mail and deliver it through a filtering system to mutt? If I can do this all in one program than so much the better but I'm happy with two programs if that would work better. I can stay with my existing filter system but, again, if I can consolidate things into one, easier to maintain, chunk then I'd be happy. I *don't* like procmail configuration files, they're one of the reasons I wrote my own. What does everyone else here do for collecting mail and filtering mail with mutt? -- Chris Green
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Wed, Nov 07, 2012 at 02:15:41PM +, Chris Green wrote: What does everyone else here do for collecting mail and filtering mail with mutt? Fetchmail and procmail. Ugly, but ubiquitous and reliable. A friend pointed me at something better for mail filtering, but I can't recall what it was... mainly because I haven't gotten around to looking into it, on account of the fact that my current solution works well and requires no learning curve. Learning a new mail filter system is very low on the priority list. -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience. pgpcLHQgiAmm9.pgp Description: PGP signature
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Wed, Nov 07, 2012 at 02:15:41PM +, Chris Green wrote: I currently have my mail delivered to my desktop system using SMTP as the system is on all the time and has a static IP. However I always get paranoid when I reconfigure it and/or do other maintenance so I'm considering moving back to a fetchmail/getmail based system. I also have a fairly complex mail filtering script I wrote myself in Python which is fed mail via .forward. What's the current state of the art way to collect mail and deliver it through a filtering system to mutt? If I can do this all in one program than so much the better but I'm happy with two programs if that would work better. I can stay with my existing filter system but, again, if I can consolidate things into one, easier to maintain, chunk then I'd be happy. I *don't* like procmail configuration files, they're one of the reasons I wrote my own. What does everyone else here do for collecting mail and filtering mail with mutt? I am using imapfilter with lua configuration file for my imap account. That does the job for me and I like the fact that I declare my filters with actual code(be it lua, python or what not) Best, Nikola
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Wed, Nov 07, 2012 at 07:17:46PM +0200, Nikola Petrov wrote: On Wed, Nov 07, 2012 at 02:15:41PM +, Chris Green wrote: I currently have my mail delivered to my desktop system using SMTP as the system is on all the time and has a static IP. However I always get paranoid when I reconfigure it and/or do other maintenance so I'm considering moving back to a fetchmail/getmail based system. I also have a fairly complex mail filtering script I wrote myself in Python which is fed mail via .forward. What's the current state of the art way to collect mail and deliver it through a filtering system to mutt? If I can do this all in one program than so much the better but I'm happy with two programs if that would work better. I can stay with my existing filter system but, again, if I can consolidate things into one, easier to maintain, chunk then I'd be happy. I *don't* like procmail configuration files, they're one of the reasons I wrote my own. What does everyone else here do for collecting mail and filtering mail with mutt? I am using imapfilter with lua configuration file for my imap account. That does the job for me and I like the fact that I declare my filters with actual code(be it lua, python or what not) How does that actually work? I've found its home at https://github.com/lefcha/imapfilter but the documentation doesn't really tell me what it does (maybe my fault!). Does it move E-Mails around on the IMAP server, or does it collect them from the IMAP server and deliver them to you locally? Or does it do something else? -- Chris Green
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Nov 07, 2012 at 02:15 PM +, Chris Green wrote: I *don't* like procmail configuration files, they're one of the reasons I wrote my own. What does everyone else here do for collecting mail and filtering mail with mutt? I use getmail and dovecot deliver. Getmail is great, fast, and flexible (and supports the OS X keychain, which I like). Dovecot is a bit overkill for just a filtering solution since it's a full IMAP server. However, I find dovecot deliver (which uses the sieve language for filtering) to be much more readable/writable than procmail. An added bonus is that my main IMAP account has sieve on the server, so I can filter mail remotely there using the same syntax as I do with my other accounts using getmail. I've looked into other solutions that are more compatible with offlineimap, like imapfilter (which I believe moves message server side, but is run from as a remote client) and a few other lesser known local solutions, like maildirproc, but in the end, sieve was the most straight forward for my setup.
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Wed, Nov 07, 2012 at 01:04:17PM -0500, Tim Gray wrote: On Nov 07, 2012 at 02:15 PM +, Chris Green wrote: I *don't* like procmail configuration files, they're one of the reasons I wrote my own. What does everyone else here do for collecting mail and filtering mail with mutt? I use getmail and dovecot deliver. Getmail is great, fast, and I had a look at dovecot deliver, I make take another look. flexible (and supports the OS X keychain, which I like). Dovecot is a bit overkill for just a filtering solution since it's a full IMAP server. However, I find dovecot deliver (which uses the sieve language for filtering) to be much more readable/writable than procmail. An added bonus is that my main IMAP account has sieve on I think anything is more readable than procmail! :-) the server, so I can filter mail remotely there using the same syntax as I do with my other accounts using getmail. I've looked into other solutions that are more compatible with offlineimap, like imapfilter (which I believe moves message server side, but is run from as a remote client) and a few other lesser known local solutions, like maildirproc, but in the end, sieve was the most straight forward for my setup. There seem to be very few currently maintained MDA/filters. Thanks. -- Chris Green
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
/ Nikola Petrov wrote on Wed 7.Nov'12 at 19:17:46 +0200 / On Wed, Nov 07, 2012 at 02:15:41PM +, Chris Green wrote: I currently have my mail delivered to my desktop system using SMTP as the system is on all the time and has a static IP. However I always get paranoid when I reconfigure it and/or do other maintenance so I'm considering moving back to a fetchmail/getmail based system. May I ask what it is that you are worried about using smtp delivery - I take it you have various protective measures in place with your configuration?
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Wed, Nov 07, 2012 at 08:16:42PM +, Jamie Paul Griffin wrote: / Nikola Petrov wrote on Wed 7.Nov'12 at 19:17:46 +0200 / On Wed, Nov 07, 2012 at 02:15:41PM +, Chris Green wrote: I currently have my mail delivered to my desktop system using SMTP as the system is on all the time and has a static IP. However I always get paranoid when I reconfigure it and/or do other maintenance so I'm considering moving back to a fetchmail/getmail based system. May I ask what it is that you are worried about using smtp delivery - I take it you have various protective measures in place with your configuration? No specific protective measures at all, it just relies on the sending server retrying if my SMTP server isn't running (or connected). That's one of the reasons I'd quite like to move away from SMTP. It *should* be OK but I'm relying on the other end to behave properly. -- Chris Green
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Wed, Nov 07, 2012 at 10:48:45AM -0600, Derek Martin wrote: On Wed, Nov 07, 2012 at 02:15:41PM +, Chris Green wrote: What does everyone else here do for collecting mail and filtering mail with mutt? Fetchmail and procmail. Ugly, but ubiquitous and reliable. Same here. I keep meaning to hook in an adaptive spam filter, but I haven't bothered so far. Maybe mutt just makes it so easy to quickly triage my mail that it hasn't seemed worth it. -pd -- Peter Davis The Tech Curmudgeon http://www.techcurmudgeon.com
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Wed, Nov 07, 2012 at 08:48:08PM +, Chris Green wrote: No specific protective measures at all, it just relies on the sending server retrying if my SMTP server isn't running (or connected). That's one of the reasons I'd quite like to move away from SMTP. It *should* be OK but I'm relying on the other end to behave properly. It will. It has to. If it didn't, e-mail on the internet would be horribly unreliable. -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience. pgpJffX3FQ2q2.pgp Description: PGP signature
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Wed, Nov 07, 2012 at 05:35:45PM +, Chris Green wrote: On Wed, Nov 07, 2012 at 07:17:46PM +0200, Nikola Petrov wrote: On Wed, Nov 07, 2012 at 02:15:41PM +, Chris Green wrote: I currently have my mail delivered to my desktop system using SMTP as the system is on all the time and has a static IP. However I always get paranoid when I reconfigure it and/or do other maintenance so I'm considering moving back to a fetchmail/getmail based system. I also have a fairly complex mail filtering script I wrote myself in Python which is fed mail via .forward. What's the current state of the art way to collect mail and deliver it through a filtering system to mutt? If I can do this all in one program than so much the better but I'm happy with two programs if that would work better. I can stay with my existing filter system but, again, if I can consolidate things into one, easier to maintain, chunk then I'd be happy. I *don't* like procmail configuration files, they're one of the reasons I wrote my own. What does everyone else here do for collecting mail and filtering mail with mutt? I am using imapfilter with lua configuration file for my imap account. That does the job for me and I like the fact that I declare my filters with actual code(be it lua, python or what not) How does that actually work? I've found its home at https://github.com/lefcha/imapfilter but the documentation doesn't really tell me what it does (maybe my fault!). Does it move E-Mails around on the IMAP server, or does it collect them from the IMAP server and deliver them to you locally? Or does it do something else? No it doesn't deliver them to you. It sort of filters them online on the server. You can then use something like offlineimap to deliver them locally to you. I use imapfilter + offlineimap + notmuch + mutt and I am far from happy with my setup at the moment. Best, Nikola
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
* On 07 Nov 2012, Derek Martin wrote: On Wed, Nov 07, 2012 at 08:48:08PM +, Chris Green wrote: server retrying if my SMTP server isn't running (or connected). That's one of the reasons I'd quite like to move away from SMTP. It *should* be OK but I'm relying on the other end to behave properly. It will. It has to. If it didn't, e-mail on the internet would be horribly unreliable. I hate to break it to you, but :) I've used IMAP pickup in the past and it's OK for some IMAP servers. A year or two ago my employer moved my mailbox to MS Exchange. Exchange doesn't (necessarily?) hand you the exact e-mail it received. It parses incoming mail, stores the parsed components, and reconstructs the message the best it can figure when you pick it up via IMAP or POP. Along the way it might modify or remove some components for no good reason; for example, multipart/alternative with text/plan and text/html invisibly becomes just a text/html message. I've also heard of its breaking crypto, although I haven't seen that myself for a while. So I forward my mail via SMTP away from my employer now. -- David Champion • d...@bikeshed.us
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Wed, Nov 07, 2012 at 04:33:58PM -0600, David Champion wrote: * On 07 Nov 2012, Derek Martin wrote: On Wed, Nov 07, 2012 at 08:48:08PM +, Chris Green wrote: server retrying if my SMTP server isn't running (or connected). That's one of the reasons I'd quite like to move away from SMTP. It *should* be OK but I'm relying on the other end to behave properly. It will. It has to. If it didn't, e-mail on the internet would be horribly unreliable. I hate to break it to you, but :) I've used IMAP pickup in the past and it's OK for some IMAP servers. Right, we're talking about SMTP delivery to a machine that's sometimes down or unreachable... Very reliable. :) Presumably that's exactly why you're using SMTP to deal with your exchange problem! -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience. pgpjzCLzrNrxL.pgp Description: PGP signature
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
/ David Champion wrote on Wed 7.Nov'12 at 16:33:58 -0600 / * On 07 Nov 2012, Derek Martin wrote: On Wed, Nov 07, 2012 at 08:48:08PM +, Chris Green wrote: server retrying if my SMTP server isn't running (or connected). That's one of the reasons I'd quite like to move away from SMTP. It *should* be OK but I'm relying on the other end to behave properly. It will. It has to. If it didn't, e-mail on the internet would be horribly unreliable. I hate to break it to you, but :) I've used IMAP pickup in the past and it's OK for some IMAP servers. A year or two ago my employer moved my mailbox to MS Exchange. Exchange doesn't (necessarily?) hand you the exact e-mail it received. It parses incoming mail, stores the parsed components, and reconstructs the message the best it can figure when you pick it up via IMAP or POP. Along the way it might modify or remove some components for no good reason; for example, multipart/alternative with text/plan and text/html invisibly becomes just a text/html message. I've also heard of its breaking crypto, although I haven't seen that myself for a while. So I forward my mail via SMTP away from my employer now. -- David Champion • d...@bikeshed.us Yes i think the benefits of using your own smtp delivery are worth it.
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Wed, Nov 07, 2012 at 11:21:59PM +, Jamie Paul Griffin wrote: Yes i think the benefits of using your own smtp delivery are worth it. I can only agree. And to avoid issues when my landline is down I have a VM on a big hoster that on one side delivers all my locally generated mails to avoid the dialin IP address problem. And on the other side it acts as the backup MX that stores my mails until my landline is back online and it can be delivered at my home. regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On 07Nov2012 14:15, Chris Green c...@isbd.net wrote: | I also have a fairly complex mail filtering script I wrote myself in | Python which is fed mail via .forward. | | What's the current state of the art way to collect mail and deliver it | through a filtering system to mutt? If I can do this all in one program | than so much the better but I'm happy with two programs if that would | work better. I can stay with my existing filter system but, again, if I | can consolidate things into one, easier to maintain, chunk then I'd be | happy. | | I *don't* like procmail configuration files, they're one of the reasons | I wrote my own. | | What does everyone else here do for collecting mail and filtering mail | with mutt? I collect email with getmail and deliver it to my spool folder. I file mail with mailfiler, a python program of my own, to monitor the spool, spool-in, spool-out and spool-spam-subj maildirs. It understands extremely easy to write and read filter rules, eg: =spam SPAM-SUBJ subject:/^You have 24 hours left to TRIPLE your deposits !=me,$EMAIL_IPHONE . to,cc:(ME) from:(FAMILY|FRIENDS|[...snipped: other mail group names]) muttMutt-Usersmutt-users@mutt.org The first rule uses a regexp on the subject header and diverts matching messages to my spam mail folder/septic-tank. The second rule does proper address parsing of the named headers and (in the example above) checks addresses against sets of addresses in my maildb. Almost instant, and very reliable. The ! means issue an alert, for important messages. The third rule also does a proper address parse of to/cc/bcc and if mitt-us...@mutt.org is there, saves the message in the mutt folder with the Mutt-Users X-Label header added. I've actually described my setup at some length on the list just recently, here and here: http://www.mail-archive.com/mutt-users@mutt.org/msg45217.html http://www.mail-archive.com/mutt-users@mutt.org/msg45215.html outlining my setup, why I don't use procmail, what I used to do to beat procmail into order in the past, etc. In short, the rules for spool divert spam and copy other messages to spool-in. The rules for spool-in file messages into my main inbox and multitudinous other folders for mailing lists. spool-out is for cross filing copies of my outbound email. Aside: spool-spam-subj is for recording the subject lines of all messages filed there as to be considered spam. So I've got a mutt macro to save a repetitious spam to that folder, and the rules there add a new rule to my spam filter:-) Mailfiler notices rule updates on the fly. Because mailfiler runs in the background, polling very regularly (1Hz, and the machine load for that is insignificant), if I modify my rules all I need to do to refile a message via the rules is to save it into spool-in again. And off it goes. Of course there is a log file to tail to watch this stuff happen. There's a man page for the mailfiler rule syntax here: https://bitbucket.org/cameron_simpson/css/src/tip/man/mailfiler.5.pod and for mailfiler itself here: https://bitbucket.org/cameron_simpson/css/src/tip/man/mailfiler.1.pod Source code: https://bitbucket.org/cameron_simpson/css/src/tip/lib/python/cs/app/mailfiler.py Cheers, -- Cameron Simpson c...@zip.com.au On 12/22/07, Brian Hansen greencopperm...@gmail.com wrote: 2. Rather than auditing a lot of code, correcting a lot of coding mistakes, like the OpenBSD security team has done, and still do, why not shift from C to something, just as fast and powerfull as C, but more secure? Again like Ada. (to completely avoid the possibilities of those errors). why did you write your email in english? esperanto is simpler and less error-prone. - Ted Unangst ted.unan...@gmail.com in misc.openbsd.org
mutt + exchange woes (Was: Re: What are the current fetchmail/getmail and/or procmail/maildrop) utilities?
On Wed, Nov 07, 2012 at 04:33:58PM -0600, David Champion wrote: I've used IMAP pickup in the past and it's OK for some IMAP servers. A year or two ago my employer moved my mailbox to MS Exchange. Exchange doesn't (necessarily?) hand you the exact e-mail it received. It parses incoming mail, stores the parsed components, and reconstructs the message the best it can figure when you pick it up via IMAP or POP. Along the way it might modify or remove some components for no good reason; for example, multipart/alternative with text/plan and text/html invisibly becomes just a text/html message. I've also heard of its breaking crypto, although I haven't seen that myself for a while. I haven't had it break crypto, but I'm one of 2 people at the company doing pgp signatures and both of us send *only* text/plain. I have had it give me text/plain only when there was an html part, which normally I wouldn't complain about, but if someone used an html link in their email, I *never* see the link or the url. So I forward my mail via SMTP away from my employer now. I would love to do this, if for no other reason than I can have better server-side filtering, but I very highly doubt the company would go for it. Otherwise, mutt seems to work just fine with exchange. I do need to set up lbdb to pull from our exchange server at some point, but fortunately I interact with only a very small subset of the company, so my aliases file suffices for this, and if I need to look up someone's address I can always open up OWA. -Jeremy pgpvBZQTthinp.pgp Description: PGP signature
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?
On Thu, Nov 08, 2012 at 01:06:54AM +0100, Andre Klärner wrote: On Wed, Nov 07, 2012 at 11:21:59PM +, Jamie Paul Griffin wrote: Yes i think the benefits of using your own smtp delivery are worth it. I can only agree. And to avoid issues when my landline is down I have a VM on a big hoster that on one side delivers all my locally generated mails to avoid the dialin IP address problem. And on the other side it acts as the backup MX that stores my mails until my landline is back online and it can be delivered at my home. IMO, a better way to do this would be to have your current backup MX be your primary (and only?) and set it to have a high retry time, possibly even setting up something like ETRN[1] to trigger the remote MTA to flush its queue to you. You may also be able to configure your mail server to have a separate retry time for incoming vs outgoing mail. I *think* postfix can do this? Seems like something it would be able to do. [1]: http://www.postfix.org/ETRN_README.html I'm sure other MTAs support ETRN, but that was the first hit on google, and I'm a postfix user (retired qmail user, and qmail does *not* support ETRN) so it seemed prudent :) -Jeremy pgpAgBZsvGkf0.pgp Description: PGP signature
Re: What are the current fetchmail/getmail and/or procmail/maildrop utilities?]
Doh! My reply went to Peter instead of list! Bad mutt! On Wed, Nov 07, 2012 at 04:00:19PM -0500, Peter Davis wrote: On Wed, Nov 07, 2012 at 10:48:45AM -0600, Derek Martin wrote: On Wed, Nov 07, 2012 at 02:15:41PM +, Chris Green wrote: What does everyone else here do for collecting mail and filtering mail with mutt? Fetchmail and procmail. Ugly, but ubiquitous and reliable. Same here. I keep meaning to hook in an adaptive spam filter, but I haven't bothered so far. Maybe mutt just makes it so easy to quickly triage my mail that it hasn't seemed worth it. /me too - the weirdnesses of procmail do my head in (too many things which get routed to deviant mailboxes, and a general need to allow multiple mailboxes for anything, such as lkml, which exceeds about 51 MB), but I have a setup which works _adequately_ [ had to add a 4th lkml mailbox at the end of last month : my mailboxes get rolled-over at the start of the month ]. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce
Re: mutt + exchange woes (Was: Re: What are the current fetchmail/getmail and/or procmail/maildrop) utilities?
* On 07 Nov 2012, Jeremy Kitchen wrote: I haven't had it break crypto, but I'm one of 2 people at the company doing pgp signatures and both of us send *only* text/plain. My memory is fuzzy but I think it was more complex multipart signed messages that it broke. I have had it give me text/plain only when there was an html part, which normally I wouldn't complain about, but if someone used an html link in their email, I *never* see the link or the url. I may have it backwards. OTOH it may have both problems. Otherwise, mutt seems to work just fine with exchange. I do need to set up lbdb to pull from our exchange server at some point, but fortunately I interact with only a very small subset of the company, so my aliases file suffices for this, and if I need to look up someone's address I can always open up OWA. True, mutt does pretty well. If you're compelled to use Exchange, mutt remains a good option. You can set a query_command that looks people up in AD, theoretically. I've never done this but I suspect that I could. Maybe that's functionally what you mean to do with lbdb, though? (Our campus uses both AD and LDAP, and LDAP is used for first-pass mail routing, so I'm querying it alone for now. -- David Champion • d...@bikeshed.us
Re: Procmail threads filtering with notmuch
Hi Will, Thanks again for your ideas. On 04/10/12 16:04, Will Fiveash wrote: I use procmail and some shell scripts to basically do the same. Here is my .procmail rule: # Process killed threads, save killed threads in killedthreads mbox :0: * ? $HOME/bin/isthreadkilled killedthreads I have adapted you script to use notmuch index and included it in my procmail rule: :0: * ? formail -c -x In-Reply-To: -x References: \ | tr -s ' ' '\n\n' \ | sed -e '/^\([^].*\|.*[^]\|\)$/ d' -e 's/[]//g' -e 's/^/id:/' \ | xargs -r -n 1 notmuch search --output=files \ | fgrep Archive /dev/null Archive/ -- Alexis signature.asc Description: Digital signature
Re: Procmail threads filtering with notmuch
On Thu, Oct 11, 2012 at 10:12:16PM +0200, Alexis Letessier wrote: Hi Will, Thanks again for your ideas. On 04/10/12 16:04, Will Fiveash wrote: I use procmail and some shell scripts to basically do the same. Here is my .procmail rule: # Process killed threads, save killed threads in killedthreads mbox :0: * ? $HOME/bin/isthreadkilled killedthreads I have adapted you script to use notmuch index and included it in my procmail rule: :0: * ? formail -c -x In-Reply-To: -x References: \ | tr -s ' ' '\n\n' \ | sed -e '/^\([^].*\|.*[^]\|\)$/ d' -e 's/[]//g' -e 's/^/id:/' \ | xargs -r -n 1 notmuch search --output=files \ | fgrep Archive /dev/null Archive/ I don't see my script stuff in there so I'm thinking you probably need to redirect your thanks to Marco. If you are using some of my stuff, you're welcome. -- Will Fiveash
Re: Procmail threads filtering with notmuch
You're right Will, I have used tr and sed expressions from Marco and only a part of your procmail recipe (* ? script). Thanks to you two then ;) On 11/10/12 15:30, Will Fiveash wrote: I don't see my script stuff in there so I'm thinking you probably need to redirect your thanks to Marco. If you are using some of my stuff, you're welcome. -- Alexis signature.asc Description: Digital signature
Re: Procmail threads filtering with notmuch
On Thu, Oct 11, 2012 22:43:39 PM +0200, Alexis Letessier wrote: You're right Will, I have used tr and sed expressions from Marco and only a part of your procmail recipe (* ? script). Thanks to you two then ;) You're welcome! Glad the stuff was useful. For the record, the procmail recipe in my blog post is NOT mine (as duly noted in the post itself and/or in the code). Basically, I had the idea, then whined on the procmail list about it until Sean Straw, procmail guru, became interested and wrote the real code in a couple minutes :-) Marco
Re: Procmail threads filtering with notmuch
M. Fioretti wrote: You're welcome! Glad the stuff was useful. For the record, the procmail recipe in my blog post is NOT mine (as duly noted in the post itself and/or in the code). Basically, I had the idea, then whined on the procmail list about it until Sean Straw, procmail guru, became interested and wrote the real code in a couple minutes :-) There's a procmail list? Could you post or email me the s*bscribe info? Thanks! Joyce
Re: Procmail threads filtering with notmuch
On Thu, Oct 11, 2012 14:39:28 PM -0700, J Wermont wrote: M. Fioretti wrote: You're welcome! Glad the stuff was useful. For the record, the procmail recipe in my blog post is NOT mine (as duly noted in the post itself and/or in the code). Basically, I had the idea, then whined on the procmail list about it until Sean Straw, procmail guru, became interested and wrote the real code in a couple minutes :-) There's a procmail list? of course there is, is not a secret http://www.procmail.org/era/lists.html Marco
Re: Procmail threads filtering with notmuch
[ Will Fiveash wrote on Thu 4.Oct'12 at 16:04:47 -0500 ] On Thu, Oct 04, 2012 at 10:54:39AM +0200, M. Fioretti wrote: On Thu, October 4, 2012 10:47 am, Alexis Letessier wrote: I use notmuch to index all my emails but i need some kind of database or something to redirect threads that i already filtered out. Is this a strange idea or should i change my workflow? Any ideas on how this could be implemented? I do the same thing with a custom procmail recipe explained here on my blog: http://freesoftware.zona-m.net/how-ignore-uninteresting-threads-in-mailing-lists/ I use procmail and some shell scripts to basically do the same. Here is my .procmail rule: # Process killed threads, save killed threads in killedthreads mbox :0: * ? $HOME/bin/isthreadkilled killedthreads To mark a thread/subthread for killing I use this with mutt: macro pager \\k ESCt;|killthread\n;save-message=killedthreads\ndelete-subthread Kill this subthread I've attached both the isthreadkilled and killedthreads scripts. Note, these are run on Solaris and will need to be edited slightly to work on other platforms. -- Will Fiveash Thanks Will - I've also found this stuff helpful, cheers for sharing it. Jamie
Procmail threads filtering with notmuch
Hello, I receive all my emails in one box and filter out non interesting mails in an Archive with mutt. I have some rules to dispatch mailing lists directly in some mailboxes with procmail but my rules are quite simple. I would like threads that i previously dispatched in my archive mailbox to continue to be dispatched by procmail base on thread id (or something else). I use notmuch to index all my emails but i need some kind of database or something to redirect threads that i already filtered out. Is this a strange idea or should i change my workflow? Any ideas on how this could be implemented? Thanks for your answers, -- Alexis signature.asc Description: Digital signature
Re: Procmail threads filtering with notmuch
On Thu, October 4, 2012 10:47 am, Alexis Letessier wrote: I use notmuch to index all my emails but i need some kind of database or something to redirect threads that i already filtered out. Is this a strange idea or should i change my workflow? Any ideas on how this could be implemented? I do the same thing with a custom procmail recipe explained here on my blog: http://freesoftware.zona-m.net/how-ignore-uninteresting-threads-in-mailing-lists/ Marco http://mfioretti.com
Re: Procmail threads filtering with notmuch
Hi Marco, Your two blog articles on the subject are really helpful. I will try to adapt the procmail recipe to match message-id based on notmuch search results in order to filter out unwanted threads: ~ % notmuch search --output=files 'id:14d85b32...@dem006.intra.tt' or 'id:ADFADSFADF' /home/alex/mail/archive/cur/1349367640.16199_0.local On 04/10/12 10:54, M. Fioretti wrote: On Thu, October 4, 2012 10:47 am, Alexis Letessier wrote: I use notmuch to index all my emails but i need some kind of database or something to redirect threads that i already filtered out. Is this a strange idea or should i change my workflow? Any ideas on how this could be implemented? I do the same thing with a custom procmail recipe explained here on my blog: http://freesoftware.zona-m.net/how-ignore-uninteresting-threads-in-mailing-lists/ Marco http://mfioretti.com Thanks a lot! -- Alexis signature.asc Description: Digital signature
Re: Procmail threads filtering with notmuch
On Thu, Oct 04, 2012 at 10:54:39AM +0200, M. Fioretti wrote: On Thu, October 4, 2012 10:47 am, Alexis Letessier wrote: I use notmuch to index all my emails but i need some kind of database or something to redirect threads that i already filtered out. Is this a strange idea or should i change my workflow? Any ideas on how this could be implemented? I do the same thing with a custom procmail recipe explained here on my blog: http://freesoftware.zona-m.net/how-ignore-uninteresting-threads-in-mailing-lists/ I use procmail and some shell scripts to basically do the same. Here is my .procmail rule: # Process killed threads, save killed threads in killedthreads mbox :0: * ? $HOME/bin/isthreadkilled killedthreads To mark a thread/subthread for killing I use this with mutt: macro pager \\k ESCt;|killthread\n;save-message=killedthreads\ndelete-subthread Kill this subthread I've attached both the isthreadkilled and killedthreads scripts. Note, these are run on Solaris and will need to be edited slightly to work on other platforms. -- Will Fiveash #!/bin/ksh -p # For use by procmail to kill mail threads, procmail will pipe mail message in via stdin. # Will return 0 if the In-Reply-To: or References: ID is in the killedthreads file. killthreadfile='/export/home/wfiveash/app_support/var/mail/killedthreads' tmpfile=$(/usr/bin/mktemp -t iskilled.XX) integer rc=1 # Copy message from stdin to tmpfile cat $tmpfile if [[ -s $tmpfile ]] then /usr/bin/formail -c -x In-Reply-To: $tmpfile |\ /usr/gnu/bin/grep -qsF -f $killthreadfile rc=$? if [[ $rc -ne 0 ]] then /usr/bin/formail -c -x References: $tmpfile |\ /usr/gnu/bin/grep -qsF -f $killthreadfile rc=$? fi fi [[ $rc -eq 0 ]] /usr/bin/formail -c -x Message-ID: $tmpfile $killthreadfile rm -f $tmpfile exit $rc #!/bin/ksh -p killthreadfile='/export/home/wfiveash/app_support/var/mail/killedthreads' # Will get the message-ID for multiple messages on stdin formail -s 'formail -c -x Message-ID' | sed -e 's/^ */ /' $killthreadfile
Re: bad path given to procmail
On Sat, Sep 10, 2011 at 11:38:37AM -0400, Patrick Shanahan wrote: * Gérard Robin g.rob...@free.fr [09-10-11 09:54]: Effectively I had in my .procmailrc : DEFAULT=/var/spool/mail/user1 but perhaps user1 can't write in /var/spool/mail. do: ls -d /var/spool/mail /var/spool/mail should have rwx for everyone. That's system- and mailer-dependent behavior. It's not relevant to the thread any longer, but there are two common schemes for this. One is for the spool directory to have permissions 1777, and let everyone write there. The other is to make the MDA SGID and make use of group permissions to write there. Arguments about as to why each is better than the other... -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience. pgp3ofc04PVys.pgp Description: PGP signature
Re: bad path given to procmail
On Fri, Sep 09, 2011 at 01:24:15PM -0700, Robert Holtzman wrote: On Fri, Sep 09, 2011 at 01:11:52PM +0200, G�rard Robin wrote: Hello, I have put a path like this in procmailrc: :0 * ^tomutt-us...@mutt.org MUTT/U11/mutt-`date +%m-%y` but I had not yet created the directory MUTT/U11 and when I downloaded my messages the messages from the list mutt-users were lost. Is it possible to avoid losing the messages in this case ? i.e. when the path doesn't exist. Read your .procmailrc file. You will se this: # Messages that fall through all your procmail recipes are delivered # to your default INBOX. To find out yours, run 'procmail -v' I'd not come across this before, so checked... and in my setup the output for 'default INBOX' is incorrect. It states: Default rcfile: $HOME/.procmailrc It may be writable by your primary group Your system mailbox:/var/mail/athan But I have: 11:00:37 0$ grep DEFAULT .procmailrc DEFAULT=$MAILDIR/.catchall/ So if you have a DEFAULT setting in .procmailrc, check that. -- - Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/ Finger athan(at)fysh.org for PGP key And it's me who is my enemy. Me who beats me up. Me who makes the monsters. Me who strips my confidence. Paula Cole - ME signature.asc Description: Digital signature
Re: bad path given to procmail
On Sat, Sep 10, 2011 at 11:02:32AM +0100, Athanasius wrote: Date: Sat, 10 Sep 2011 11:02:32 +0100 From: Athanasius m...@miggy.org To: mutt-users@mutt.org Subject: Re: bad path given to procmail User-Agent: Mutt/1.5.18 (2008-05-17) On Fri, Sep 09, 2011 at 01:24:15PM -0700, Robert Holtzman wrote: On Fri, Sep 09, 2011 at 01:11:52PM +0200, G???rard Robin wrote: Hello, I have put a path like this in procmailrc: :0 * ^tomutt-us...@mutt.org MUTT/U11/mutt-`date +%m-%y` but I had not yet created the directory MUTT/U11 and when I downloaded my messages the messages from the list mutt-users were lost. Is it possible to avoid losing the messages in this case ? i.e. when the path doesn't exist. Read your .procmailrc file. You will se this: # Messages that fall through all your procmail recipes are delivered # to your default INBOX. To find out yours, run 'procmail -v' I'd not come across this before, so checked... and in my setup the output for 'default INBOX' is incorrect. It states: Default rcfile: $HOME/.procmailrc It may be writable by your primary group Your system mailbox:/var/mail/athan But I have: 11:00:37 0$ grep DEFAULT .procmailrc DEFAULT=$MAILDIR/.catchall/ So if you have a DEFAULT setting in .procmailrc, check that. Thank you to everyone who responded to me. Effectively I had in my .procmailrc : DEFAULT=/var/spool/mail/user1 but perhaps user1 can't write in /var/spool/mail. I set DEFAULT like this: DEFAULT=$MAILDIR/SAVED and I have created the directory ~/Mail/SAVED and now when procmail doesn't find a location the mail goes in SAVED. -- Gérard signature.asc Description: Digital signature
Re: bad path given to procmail
* Gérard Robin g.rob...@free.fr [09-10-11 09:54]: Effectively I had in my .procmailrc : DEFAULT=/var/spool/mail/user1 but perhaps user1 can't write in /var/spool/mail. do: ls -d /var/spool/mail /var/spool/mail should have rwx for everyone. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: bad path given to procmail
On Sat, Sep 10, 2011 at 11:38:37AM -0400, Patrick Shanahan wrote: Date: Sat, 10 Sep 2011 11:38:37 -0400 From: Patrick Shanahan ptilopt...@gmail.com To: mutt-users@mutt.org Subject: Re: bad path given to procmail User-Agent: Mutt/1.5.21 (2010-09-15) * Gérard Robin g.rob...@free.fr [09-10-11 09:54]: Effectively I had in my .procmailrc : DEFAULT=/var/spool/mail/user1 but perhaps user1 can't write in /var/spool/mail. do: ls -d /var/spool/mail /var/spool/mail should have rwx for everyone. ls -dal /var/spool/mail lrwxrwxrwx 1 root root 7 31 juil. 2010 /var/spool/mail - ../mail ls -al /var/spool/mail/user1 -rw-rw 1 user1 mail 8334392 10 sept. 17:03 /var/spool/mail/user1 I restored DEFAULT=/var/spool/mail/user1 and it works like expected. it is a mystery ?? -- Gérard
Re: bad path given to procmail
On Sat, Sep 10, 2011 at 11:02:32AM +0100, Athanasius wrote: ..snip.. I'd not come across this before, so checked... and in my setup the output for 'default INBOX' is incorrect. It states: Default rcfile: $HOME/.procmailrc It may be writable by your primary group Your system mailbox:/var/mail/athan But I have: 11:00:37 0$ grep DEFAULT .procmailrc DEFAULT=$MAILDIR/.catchall/ So if you have a DEFAULT setting in .procmailrc, check that. I do but it's only because I don't want mail that is not caught by the filters to go to my system mailbox which is /var/mail/username. Instead I set up a DEFAULT mailbox which is $HOME/mail/INCOMING. Also I notice that your DEFAULT mailbox is a hidden (dot) file. Don't know if that is a problem, but you might try unhiding it. The above may not addresses your problem. Post the contents of your .procmailrc file. If you wish you can delete the filters. -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Re: bad path given to procmail
Hello Gérard Robin,
Am 2011-09-09 13:11:52, hacktest Du folgendes herunter:
Hello,
I have put a path like this in procmailrc:
:0
* ^tomutt-us...@mutt.org
This is wrong. If you mean the Macro, it must be
* ^to_mutt-us...@mutt.org
but is you mean the To: header then it has to be
* ^To:.*mutt-users@mutt\.org
MUTT/U11/mutt-`date +%m-%y`
but I had not yet created the directory MUTT/U11 and when I downloaded
my messages the messages from the list mutt-users were lost.
Is it possible to avoid losing the messages in this case ? i.e. when the
path doesn't exist.
Look into /var/mail/${USERNAME}
Thanks, Greetings and nice Day/Evening
Michelle Konzack
--
# Debian GNU/Linux Consultant ##
Development of Intranet and Embedded Systems with Debian GNU/Linux
itsystems@tdnet Franceitsystems@tdnet
Owner Michelle KonzackOwner Michelle Konzack
Apt. 917 (homeoffice) Gewerbe Straße 3
50, rue de Soultz 77694 Kehl/Germany
67100 Strasbourg/France Tel: +49-177-9351947 mobil
Tel: +33-6-61925193 mobil Tel: +49-176-86004575 office
http://www.itsystems.tamay-dogan.net/ http://www.flexray4linux.org/
http://www.debian.tamay-dogan.net/ http://www.can4linux.org/
Jabber linux4miche...@jabber.ccc.de
ICQ#328449886
Linux-User #280138 with the Linux Counter, http://counter.li.org/
signature.pgp
Description: Digital signature
bad path given to procmail
Hello, I have put a path like this in procmailrc: :0 * ^tomutt-us...@mutt.org MUTT/U11/mutt-`date +%m-%y` but I had not yet created the directory MUTT/U11 and when I downloaded my messages the messages from the list mutt-users were lost. Is it possible to avoid losing the messages in this case ? i.e. when the path doesn't exist. tia -- Gérard
Re: bad path given to procmail
* Gérard Robin g.rob...@free.fr [09-09-11 07:15]: Hello, I have put a path like this in procmailrc: :0 * ^tomutt-us...@mutt.org MUTT/U11/mutt-`date +%m-%y` but I had not yet created the directory MUTT/U11 and when I downloaded my messages the messages from the list mutt-users were lost. Is it possible to avoid losing the messages in this case ? i.e. when the path doesn't exist. The *only* way I know of to loose mail via procmail is to direct to /dev/null. You have the mail somewhere. Your recipe is faulty and probably did not handle the mail from mutt-users, * ^TO.*mutt-users@mutt.org there is usually a [space] after TO in the header which you have not allowed and the .* will consider that and others. I prefer: * ^Sender:.*mutt.org (not used by all mailing lists) but ^TO.* will work fine. * ^to_mutt-us...@mutt.org even better see man procmailrc man procmailex -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net
Re: bad path given to procmail
On Fri, Sep 09, 2011 at 01:11:52PM +0200, G�rard Robin wrote: Hello, I have put a path like this in procmailrc: :0 * ^tomutt-us...@mutt.org MUTT/U11/mutt-`date +%m-%y` but I had not yet created the directory MUTT/U11 and when I downloaded my messages the messages from the list mutt-users were lost. Is it possible to avoid losing the messages in this case ? i.e. when the path doesn't exist. Read your .procmailrc file. You will se this: # Messages that fall through all your procmail recipes are delivered # to your default INBOX. To find out yours, run 'procmail -v' -- Bob Holtzman If you think you're getting free lunch, check the price of the beer. Key ID: 8D549279 signature.asc Description: Digital signature
Re: Gmail Spam headers for procmail?
On Mon, Aug 16, 2010 at 04:13:58AM +0200, Michelle Konzack wrote:
Am 2010-08-13 08:22:42, hacktest Du folgendes herunter:
Does anyone know here if there's a way to have Gmail add a header onto
email marked as Spam?
You cant, since it is the last crap I have ever seen!
However you can fetch the messages by using
[ '~/.fetchmailrc' ]
poll pop.gmail.com proto IMAPS
usermygmailusername
passmypasswordhere
is localusr
folder INBOX
options mda /usr/bin/procmail -a INBOX -d %T
poll pop.gmail.com proto IMAPS
usermygmailusername
passmypasswordhere
is localusr
folder INBOX.Spam
options mda /usr/bin/procmail -a SPAMFOLDER -d %T
And at the begining of your
[ '~/.procmailrc' ]-
MAILFDIR=${HOME}/Maildir
DEFAULT=${MAILFDIR}/
POLLTYPE=$1
:0
* ? test ${POLLTYPE} = SPAMFOLDER
.Spam/
ATTENTION: You have to switch to IMAPS to get it.
Thanks, Greetings and nice Day/Evening
Michelle Konzack
This is wonderful, it works exactly how I want! I had to edit the config
a bit to get it to work (maybe you did this intentionally to get me to
learn a bit? :)). Here is the edited working config (procmail worked
fine, fetchmail needed to be edited a bit):
# inbox
poll imap.gmail.com proto IMAP
user'usernamehere'
pass'password'
is 'localuser'
folder INBOX
options mda /usr/bin/procmail -d %T
keep
ssl
sslcertck
sslcertpath /etc/ssl/certs
# spam box
poll imap.gmail.com proto IMAP
user'usernamehere'
pass'password'
is 'localuser'
folder [Gmail]/Spam
options mda /usr/bin/procmail -a SPAMFOLDER -d %T
keep
ssl
sslcertck
sslcertpath /etc/ssl/certs
Thank you again, this problem has been solved.
Re: Gmail Spam headers for procmail?
Hello Harry Strongburg, Am 2010-08-16 05:13:28, hacktest Du folgendes herunter: This is wonderful, it works exactly how I want! I had to edit the config a bit to get it to work (maybe you did this intentionally to get me to learn a bit? :)). Here is the edited working config (procmail worked fine, fetchmail needed to be edited a bit): Hehehe Thank you again, this problem has been solved. Perfect. Thanks, Greetings and nice Day/Evening Michelle Konzack -- # Debian GNU/Linux Consultant ## Development of Intranet and Embedded Systems with Debian GNU/Linux itsyst...@tdnet France EURL itsyst...@tdnet UG (limited liability) Owner Michelle KonzackOwner Michelle Konzack Apt. 917 (homeoffice) 50, rue de Soultz Kinzigstraße 17 67100 Strasbourg/France 77694 Kehl/Germany Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil Tel: +33-9-52705884 fix http://www.itsystems.tamay-dogan.net/ http://www.flexray4linux.org/ http://www.debian.tamay-dogan.net/ http://www.can4linux.org/ Jabber linux4miche...@jabber.ccc.de ICQ#328449886 Linux-User #280138 with the Linux Counter, http://counter.li.org/ signature.pgp Description: Digital signature
Re: How to re-procmail emails without modifying read/unread status
On Fri, Aug 06, 2010 at 10:54:16PM +0200, Michelle Konzack wrote: Hello Christian Ebert, Am 2010-08-05 15:45:48, hacktest Du folgendes herunter: As Erik is using Maildir even that wouldn't help much as the messages would be delivered to Maildir/new/ . And if he had looked into the archive of the procmail list, he would know how to make files read. Including modifying the courrierimapuidb That is false attribution. Erik proposed a possible workaround. It is in fact Yue Wu who has the problem, and therefore might wish to consult the archives. That can be seen in the archives, if one cares to look. Erik (Who is in fact using mbox.) -- To err is humor.
Re: How to re-procmail emails without modifying read/unread status
Hi Yue, * Yue Wu vano...@gmail.com [06. Aug. 2010]: On Thu, Aug 05, 2010 at 03:45:48PM +0100, Christian Ebert wrote: * Erik Christiansen on Friday, August 06, 2010 at 00:38:37 +1000 On Thu, Aug 05, 2010 at 09:18:45PM +0800, Yue Wu wrote: I don't only want to redeliver my emails, but also not let all redelivered mails become into the unread status. I'm using maildir format, and tried with the following script: for j in $(find $2 -type d | grep cur) ; do ( cd $j ; for i in * ; do cat $i | formail -ds procmail ; done) ; done But after redeliverd, all emails are new, i.e. unread in mutt, that's not what I want. Since they have been redelivered, it's hard to blame mutt for indicating that. Since you are running a script over each one anyway, you could perhaps remember the value of the Status: header in each email, and restore it after redelivery. While formail will munge headers for you, I haven't tried fighting mutt to set the Status: header. You might need to do that faking post-delivery. As Erik is using Maildir even that wouldn't help much as the messages would be delivered to Maildir/new/ . But if I want to re-orgnize my emails with a different rule, how do you do it in such case? Orgnizing all mails to be unread then mark the old ones to be read is very tedious if mails is many. I think there are three possible solutions: a) don't refile with procmail, refile with mutt instead. The pattern matching capabilities of mutt are very powerful but naturally limited to a single folder if you want zu refile from several folders this would be a problem. But this is also scriptable. b) refile with procmail *and* tag emails as refiled, for instance using the X-Label: -Header. - The unread them - in mutt - manually: does not scale when many mail folders are involved - via a folder-hook and pattern matching. May be slow for large mail folders and happens even when no refiling - once via a shell script c) don't refile them use searching strategies on your emails via mairix and don't bother with the location of the emails. Ciao, Gregor -- -... --- .-. . -.. ..--.. ...-.-
Re: How to re-procmail emails without modifying read/unread status
On Fri, Aug 06, 2010 at 10:48:05AM +0800, Yue Wu wrote: In my case, after re-procmail, every email will be unread, I can't recorgnize which are those I've read, I have to look those emails one by one and recall if it's really read or unread by me. In the script or procmail recipe that refiles them, read in the current read or unread status, and write another header with that status (eg, X-Refiled: read). After you refile, use mutt header matching to update the status accordingly. If you're going to do this more than once, you'll want to make a final pass to remove that header, so it doesn't mess you up on the next pass. Ed signature.txt Description: Digital signature
Re: How to re-procmail emails without modifying read/unread status
Hello Christian Ebert, Am 2010-08-05 15:45:48, hacktest Du folgendes herunter: As Erik is using Maildir even that wouldn't help much as the messages would be delivered to Maildir/new/ . And if he had looked into the archive of the procmail list, he would know how to make files read. Including modifying the courrierimapuidb I have posted the solution several times... Thanks, Greetings and nice Day/Evening Michelle Konzack -- # Debian GNU/Linux Consultant ## Development of Intranet and Embedded Systems with Debian GNU/Linux itsyst...@tdnet France EURL itsyst...@tdnet UG (limited liability) Owner Michelle KonzackOwner Michelle Konzack Apt. 917 (homeoffice) 50, rue de Soultz Kinzigstraße 17 67100 Strasbourg/France 77694 Kehl/Germany Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil Tel: +33-9-52705884 fix http://www.itsystems.tamay-dogan.net/ http://www.flexray4linux.org/ http://www.debian.tamay-dogan.net/ http://www.can4linux.org/ Jabber linux4miche...@jabber.ccc.de ICQ#328449886 Linux-User #280138 with the Linux Counter, http://counter.li.org/ signature.pgp Description: Digital signature
Re: How to re-procmail emails without modifying read/unread status
Hello Yue Wu,
Am 2010-08-05 21:18:45, hacktest Du folgendes herunter:
for j in $(find $2 -type d | grep cur) ; do (
cd $j ;
for i in * ;
do cat $i | formail -ds procmail ;
done) ;
done
But after redeliverd, all emails are new, i.e. unread in mutt, that's not what
I want.
What about with:
for j in $(find $2 -type d | grep cur) ; do
cd ${j}
for i in * ; do
formail -I X-Re-Filter: true ${i} |procmail
done
done
and then in Procmail do at the beginning
:0
* ^X-Re-Filter: true
{
TRAP='DIR=$(dirname ${LASTFOLDER} |sed 's|/new$|/cur|') ; FILE=$(basename
${LASTFOLDER}) ; mv ${LASTFOLDER} ${DIR}/${FILE}:2,S'
:0fw
| formail -I X-Re-Filter:
}
Thanks, Greetings and nice Day/Evening
Michelle Konzack
--
# Debian GNU/Linux Consultant ##
Development of Intranet and Embedded Systems with Debian GNU/Linux
itsyst...@tdnet France EURL itsyst...@tdnet UG (limited liability)
Owner Michelle KonzackOwner Michelle Konzack
Apt. 917 (homeoffice)
50, rue de Soultz Kinzigstraße 17
67100 Strasbourg/France 77694 Kehl/Germany
Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil
Tel: +33-9-52705884 fix
http://www.itsystems.tamay-dogan.net/ http://www.flexray4linux.org/
http://www.debian.tamay-dogan.net/ http://www.can4linux.org/
Jabber linux4miche...@jabber.ccc.de
ICQ#328449886
Linux-User #280138 with the Linux Counter, http://counter.li.org/
signature.pgp
Description: Digital signature
Re: How to re-procmail emails without modifying read/unread status
* Yue Wu vano...@gmail.com [08-05-10 08:39]: Sometimes I want to filter my emails with new rule of procmail, archived list has the way to re-procmail, but all re-procmailed mails will be at the new unread status. My question is, how to re-procmail without changing the read/unread status of emails? You don't say the type of mail system, but I use mbox and the following works for me. formail -ds procmail [mbox-file] will redeliver your mbox-file based of the present procmail rules splitting digest messages. Use only -d if you do not want the splitting. formail -ds procmail -m newrules.rc mbox-file will redeliver based on the rules contained in newrules.rc. Prepend paths where necessary. I would use duplicate files or work inside a sandbox environment for testing first. gud luk, -- Patrick Shanahan Plainfield, Indiana, USAHOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://counter.li.org
Re: How to re-procmail emails without modifying read/unread status
On Thu, Aug 05, 2010 at 08:50:22AM -0400, Patrick Shanahan wrote: * Yue Wu vano...@gmail.com [08-05-10 08:39]: Sometimes I want to filter my emails with new rule of procmail, archived list has the way to re-procmail, but all re-procmailed mails will be at the new unread status. My question is, how to re-procmail without changing the read/unread status of emails? You don't say the type of mail system, but I use mbox and the following works for me. formail -ds procmail [mbox-file] will redeliver your mbox-file based of the present procmail rules splitting digest messages. Use only -d if you do not want the splitting. I don't only want to redeliver my emails, but also not let all redelivered mails become into the unread status. I'm using maildir format, and tried with the following script: for j in $(find $2 -type d | grep cur) ; do ( cd $j ; for i in * ; do cat $i | formail -ds procmail ; done) ; done But after redeliverd, all emails are new, i.e. unread in mutt, that's not what I want. -- Regards, Yue Wu Key Laboratory of Modern Chinese Medicines Department of Traditional Chinese Medicine China Pharmaceutical University No.24, Tongjia Xiang Street, Nanjing 210009, China
Re: How to re-procmail emails without modifying read/unread status
On Thu, Aug 05, 2010 at 09:18:45PM +0800, Yue Wu wrote: I don't only want to redeliver my emails, but also not let all redelivered mails become into the unread status. I'm using maildir format, and tried with the following script: for j in $(find $2 -type d | grep cur) ; do ( cd $j ; for i in * ; do cat $i | formail -ds procmail ; done) ; done But after redeliverd, all emails are new, i.e. unread in mutt, that's not what I want. Since they have been redelivered, it's hard to blame mutt for indicating that. Since you are running a script over each one anyway, you could perhaps remember the value of the Status: header in each email, and restore it after redelivery. While formail will munge headers for you, I haven't tried fighting mutt to set the Status: header. You might need to do that faking post-delivery. Erik -- Due to circumstances beyond our control, we regret to inform you that circumstances are beyond our control.-Paul Benoit
Re: How to re-procmail emails without modifying read/unread status
* Erik Christiansen on Friday, August 06, 2010 at 00:38:37 +1000 On Thu, Aug 05, 2010 at 09:18:45PM +0800, Yue Wu wrote: I don't only want to redeliver my emails, but also not let all redelivered mails become into the unread status. I'm using maildir format, and tried with the following script: for j in $(find $2 -type d | grep cur) ; do ( cd $j ; for i in * ; do cat $i | formail -ds procmail ; done) ; done But after redeliverd, all emails are new, i.e. unread in mutt, that's not what I want. Since they have been redelivered, it's hard to blame mutt for indicating that. Since you are running a script over each one anyway, you could perhaps remember the value of the Status: header in each email, and restore it after redelivery. While formail will munge headers for you, I haven't tried fighting mutt to set the Status: header. You might need to do that faking post-delivery. As Erik is using Maildir even that wouldn't help much as the messages would be delivered to Maildir/new/ . c -- theatre - books - texts - movies Black Trash Productions at home: http://www.blacktrash.org/ Black Trash Productions on Facebook: http://www.facebook.com/blacktrashproductions
Re: How to re-procmail emails without modifying read/unread status
On Thu, Aug 05, 2010 at 03:45:48PM +0100, Christian Ebert wrote: * Erik Christiansen on Friday, August 06, 2010 at 00:38:37 +1000 On Thu, Aug 05, 2010 at 09:18:45PM +0800, Yue Wu wrote: I don't only want to redeliver my emails, but also not let all redelivered mails become into the unread status. I'm using maildir format, and tried with the following script: for j in $(find $2 -type d | grep cur) ; do ( cd $j ; for i in * ; do cat $i | formail -ds procmail ; done) ; done But after redeliverd, all emails are new, i.e. unread in mutt, that's not what I want. Since they have been redelivered, it's hard to blame mutt for indicating that. Since you are running a script over each one anyway, you could perhaps remember the value of the Status: header in each email, and restore it after redelivery. While formail will munge headers for you, I haven't tried fighting mutt to set the Status: header. You might need to do that faking post-delivery. As Erik is using Maildir even that wouldn't help much as the messages would be delivered to Maildir/new/ . But if I want to re-orgnize my emails with a different rule, how do you do it in such case? Orgnizing all mails to be unread then mark the old ones to be read is very tedious if mails is many. -- Regards, Yue Wu Key Laboratory of Modern Chinese Medicines Department of Traditional Chinese Medicine China Pharmaceutical University No.24, Tongjia Xiang Street, Nanjing 210009, China
Re: How to re-procmail emails without modifying read/unread status
On Fri, Aug 06, 2010 at 08:34:01AM +0800, Yue Wu wrote: Orgnizing all mails to be unread then mark the old ones to be read is very tedious if mails is many. Really? How about T ~N ;N ? Or in long form: tag-pattern pattern = new messages = ~N tag-prefixtoggle-new Optionally use ~O for old messages. -- Monte
Re: How to re-procmail emails without modifying read/unread status
On Thu, Aug 05, 2010 at 10:51:28PM -0300, Monte Stevens wrote: On Fri, Aug 06, 2010 at 08:34:01AM +0800, Yue Wu wrote: Orgnizing all mails to be unread then mark the old ones to be read is very tedious if mails is many. Really? How about T ~N ;N ? Or in long form: tag-pattern pattern = new messages = ~N tag-prefixtoggle-new Optionally use ~O for old messages. In my case, after re-procmail, every email will be unread, I can't recorgnize which are those I've read, I have to look those emails one by one and recall if it's really read or unread by me. -- Regards, Yue Wu Key Laboratory of Modern Chinese Medicines Department of Traditional Chinese Medicine China Pharmaceutical University No.24, Tongjia Xiang Street, Nanjing 210009, China
Re: Notify-send doesn't work with procmail?
On 2010-07-23, He Wen wrote: Hi, Every one! I try to use notify-send to send a message to my desktop when a new mail arrives, but i find notify-send dosen't work with procmail: In my procmailrc, I have: # notification :0 ic: | play /usr/share/sounds/gnome/default/alerts/drip.ogg; notify-send -i 'evolution' New Mail Arrives Only the sound could be heard, but no notifcation popped out. I can't figure out what's wrong with it. Could anyone help me? Thank you ^^ I'm not familiar with notify-send, but I imagine that it's an X application and needs to know the identity of the display on which to display itself. The process that runs procmail is not associated with any display, so notify-send doesn't know what display to use. You might try executing echo $DISPLAY at the shell prompt of some X terminal, then setting DISPLAY to that value in the command that invokes notify-send, something like this. # notification :0 ic: | play /usr/share/sounds/gnome/default/alerts/drip.ogg; DISPLAY=:0.0 notify-send -i 'evolution' New Mail Arrives Unfortunately I don't have a way to test that at the moment. HTH, Gary
Re: Notify-send doesn't work with procmail?
Thank you! It does works now. I though that $DISPLAY would be defaultly set to :0.0. Well, obviously I had been wrong :-(. After adding DISPLAY=:0.0 to the procmailrc file, it works. Thank you again^^ On Thu, Jul 22, 2010 at 11:03:10PM -0700, Gary Johnson wrote: I'm not familiar with notify-send, but I imagine that it's an X application and needs to know the identity of the display on which to display itself. The process that runs procmail is not associated with any display, so notify-send doesn't know what display to use. You might try executing echo $DISPLAY at the shell prompt of some X terminal, then setting DISPLAY to that value in the command that invokes notify-send, something like this. # notification :0 ic: | play /usr/share/sounds/gnome/default/alerts/drip.ogg; DISPLAY=:0.0 notify-send -i 'evolution' New Mail Arrives Unfortunately I don't have a way to test that at the moment. HTH, Gary -- He Wen School of Electrical Engineering Computer Science Peking University Beijing 100871 China
Notify-send doesn't work with procmail?
Hi, Every one! I try to use notify-send to send a message to my desktop when a new mail arrives, but i find notify-send dosen't work with procmail: In my procmailrc, I have: # notification :0 ic: | play /usr/share/sounds/gnome/default/alerts/drip.ogg; notify-send -i 'evolution' New Mail Arrives Only the sound could be heard, but no notifcation popped out. I can't figure out what's wrong with it. Could anyone help me? Thank you ^^ -- He Wen School of Electrical Engineering Computer Science Peking University Beijing 100871 China
Re: Notify-send doesn't work with procmail?
On Fri, Jul 23, 2010 at 12:03:26PM +0800, He Wen wrote: Hi, Every one! I try to use notify-send to send a message to my desktop when a new mail arrives, but i find notify-send dosen't work with procmail: In my procmailrc, I have: # notification :0 ic: | play /usr/share/sounds/gnome/default/alerts/drip.ogg; notify-send -i 'evolution' New Mail Arrives Only the sound could be heard, but no notifcation popped out. I can't figure out what's wrong with it. Could anyone help me? Thank you ^^ Try substituting a for the ;, or ? ie. | play /usr/share/sounds/gnome/default/alerts/drip.ogg notify-send -i Also, make sure notify-send is within your $PATH. ie: $ whereis notify-send /usr/local/bin/notify-send $ echo $PATH /bin:/usr/bin: export PATH=$PATH:/usr/local/bin But I'm sure some procmail junky will find you're error better then I!
Re: Is there a modernized procmail?
On Sun, Apr 04, 2010 at 07:08:18AM +0800, Yue Wu wrote: Hi, list, Is there one modernized procmail? The biggest complain on procmail is that it doesn't support multibyte charactors at all(w/o dirty trick). Or maybe there is one better replacement for filtering the mails? I'm seaking the infos to make my mutt work with imap(offlineimap?). -- Regards, Yue Wu Key Laboratory of Modern Chinese Medicines Department of Traditional Chinese Medicine China Pharmaceutical University No.24, Tongjia Xiang Street, Nanjing 210009, China As far as offline imap goes there are some good ressources for it around the web. And for online imap, well if you only have one account google should be enough, if there are more you might want to look through the list archives for these three mails (there may be minor errors in the names, but they are all called something along the lines of what I've written): Multiple imap accounts Need help on setting multiple accounts imap and mailboxes -- Zeerak Waseem pgpanVvhjMqVF.pgp Description: PGP signature
Is there a modernized procmail?
Hi, list, Is there one modernized procmail? The biggest complain on procmail is that it doesn't support multibyte charactors at all(w/o dirty trick). Or maybe there is one better replacement for filtering the mails? I'm seaking the infos to make my mutt work with imap(offlineimap?). -- Regards, Yue Wu Key Laboratory of Modern Chinese Medicines Department of Traditional Chinese Medicine China Pharmaceutical University No.24, Tongjia Xiang Street, Nanjing 210009, China
Re: Is there a modernized procmail?
On Sun, Apr 04, 2010 at 07:08:18AM +0800, Yue Wu wrote: Hi, list, Is there one modernized procmail? The biggest complain on procmail is that it doesn't support multibyte charactors at all(w/o dirty trick). Or maybe there is one better replacement for filtering the mails? I'm seaking the infos to make my mutt work with imap(offlineimap?). -- I think it comes down to maildrop. http://www.courier-mta.org/maildrop/maildropfilter.html -- Kind Regards, Freeman http://bugs.debian.org/release-critical/
Procmail recipes with maildir mailboxes
In the past, when I used mutt, I was using mbox type mailboxes. Never had any problems with recipes like this: ## begin example :0: * ^(From|Cc|To):.*gnome /home/tim/Mail/Gnome ## end example OR ## begin example :0: * ^To:.vim_...@googlegroups.com /home/tim/Mail/Vim ## end example :) To the best of my memory. Now I am using maildir type mailboxes, and I'm seeing erratic deliveries. Frequently messages are delived to the root of the mail folder, rather than the /new. So I'm a noob all over again. Question: Should I end my action line target with a '/' or explicitly point to /home/tim/Mail/new - as an example? Should anyone feel that this should be better posted to a procmail support, please point me to the correct place for signup. thanks -- Tim t...@johnsons-web.com http://www.akwebsoft.com
Re: Procmail recipes with maildir mailboxes
* Tim Johnson on Sunday, June 07, 2009 at 16:50:38 -0800 In the past, when I used mutt, I was using mbox type mailboxes. Never had any problems with recipes like this: ## begin example :0: :0 with Maildir you don't need locking, but * ^(From|Cc|To):.*gnome /home/tim/Mail/Gnome /home/tim/Mail/Gnome/ ^ the terminating directory slash. You might want to poke around a bit in man 5 procmailrc for things like $MAILDIR, $DEFAULT etc. c -- Was heißt hier Dogma, ich bin Underdogma! [ What the hell do you mean dogma, I am underdogma. ] _F R E E_ _V I D E O S_ http://www.blacktrash.org/underdogma/ http://www.blacktrash.org/underdogma/index-en.html
Re: Procmail recipes with maildir mailboxes
* Christian Ebert blacktr...@gmx.net [090607 17:11]: :0 with Maildir you don't need locking, but * ^(From|Cc|To):.*gnome /home/tim/Mail/Gnome /home/tim/Mail/Gnome/ ^ the terminating directory slash. You might want to poke around a bit in man 5 procmailrc for things like $MAILDIR, $DEFAULT etc. Yes. Good stuff there. Will read closely. thanks -- Tim t...@johnsons-web.com http://www.akwebsoft.com
Re: Keeping all headers on edited messages piped thru procmail?
On 1 Jan 2009 23:29 -0500, by r...@panix.com (rj): # # Generate a Lines: header (needed for maildir mailbox # format) using procmail's scoring mechanism. Only # message-body lines are counted (not the headers): It doesn't answer your question, but since when does maildir need a Lines: header? I did a quick scan over a few fairly large maildir mailboxes that I have, with messages created by a number of different MUAs, and mutt certainly has no problem dealing with mailboxes where no or only very few messages have such a header. -- Michael Kjörling .. mich...@kjorling.se .. http://michael.kjorling.se * . No bird soars too high if he soars with his own wings . * * ENCRYPTED email preferred -- OpenPGP key ID: 0x 758F8749 BDE9ADA6 * * ASCII Ribbon Campaign: Against HTML mail, proprietary attachments * signature.asc Description: Digital signature
Re: Keeping all headers on edited messages piped thru procmail?
On 2009-01-01, rj r...@panix.com wrote: When I edit a message, the edited version of it appears as a separate, new message in mutt's index, but without a Lines: header. So I pipe it through procmail where I have this in my procmailrc: # # Generate a Lines: header (needed for maildir mailbox # format) using procmail's scoring mechanism. Only # message-body lines are counted (not the headers): :0 Bfhw * -1^0 * 1^1 ^.*$ |formail -ILines: $= # This recipe adds a custom Lines: header, and it appears as well to retain the unignore headers that are defined as such in my .muttrc. But it strips out all of the other headers that were in the original, not-piped-through-procmail versions of the message (whether edited or non-edited). Can this recipe be modified to keep all the original headers intact while continuing to generate the custom Lines: header? I think you just need to unset the 'weed' variable before piping, then set it again afterwards. Alternatively, you could perform the formail filtering from within your editor rather than from mutt. Regards, Gary
Keeping all headers on edited messages piped thru procmail?
When I edit a message, the edited version of it appears as a separate, new message in mutt's index, but without a Lines: header. So I pipe it through procmail where I have this in my procmailrc: # # Generate a Lines: header (needed for maildir mailbox # format) using procmail's scoring mechanism. Only # message-body lines are counted (not the headers): :0 Bfhw * -1^0 * 1^1 ^.*$ |formail -ILines: $= # This recipe adds a custom Lines: header, and it appears as well to retain the unignore headers that are defined as such in my .muttrc. But it strips out all of the other headers that were in the original, not-piped-through-procmail versions of the message (whether edited or non-edited). Can this recipe be modified to keep all the original headers intact while continuing to generate the custom Lines: header? pgpqXFr8dTf2q.pgp Description: PGP signature
Re: Mutt problem, probably with procmail
On Sat, Sep 13, 2008 at 11:26:29PM +1000, Erik Christiansen wrote: # Avoid logging clashes. Separate log records. MAILDIR=/home/erik/mail # Thanks to Bart Schaefer Ruud H.G. van Tol: LOGFILE=$MAILDIR/tmp_log.$$ # - Each process uses a temporary log. FINAL_LOG=$MAILDIR/log# - Append here, via TRAP, at process exit: TRAP='procmail -p DEFAULT=$FINAL_LOG /dev/null $LOGFILE rm -f $LOGFILE' Off-topic, but an easier way to log everything to one file which leaves your TRAP variable free for other purposes is to use a global lockfile so only 1 procmail can run at a time: # Global lockfile LOCKFILE=$PMDIR/globallock Theoretically this could impact performance but I can't imagine anyone receiving enough mail to make this an actual problem on any modern machine. Vincent van Leeuwen Media Design - http://www.mediadesign.nl/
Re: Mutt problem, probably with procmail
On Sat, 13 Sep 2008, Aleksandar D. Balalovski wrote: hello, I've been using Mutt for half a year now, everything was fine. Yesterday I changed some of the recipes in procmailrc and since than fetchmail/procmail won't put the mail in the preferred mailbox. It puts it in /var/spool/mail/myusername. This is my ~/.muttrc: http://pastebin.com/m4ff673db This is my ~/.fetchmailrc: http://pastebin.com/m3da88750 This is my ~/.procmailrc: http://pastebin.com/d474e0144 If I type 'mail' I get the mails but that is not what I want, I want to use mutt to browse messages and reply and stuff... thanks I may be completely off track here (I am using mbox - you seem to be using maildir) but when this particular thing happened to me, it was the fault of postfix. There is a maximum mailbox size setting somewhere in /etc/postfix/main.cf. I have this mailbox_size_limit = 10240 I had changed it to this number from the original value (5120). It drove me nuts because my mailbox size went over 100mb at exactly the same time I had upgraded (or was it changed) my distro. :( ymmv, hth, Sharukh. -- Dr. Sharukh K R Pavri. Mutter Homoeopath, Linuxer. Is there another word for synonym?
Mutt problem, probably with procmail
hello, I've been using Mutt for half a year now, everything was fine. Yesterday I changed some of the recipes in procmailrc and since than fetchmail/procmail won't put the mail in the preferred mailbox. It puts it in /var/spool/mail/myusername. This is my ~/.muttrc: http://pastebin.com/m4ff673db This is my ~/.fetchmailrc: http://pastebin.com/m3da88750 This is my ~/.procmailrc: http://pastebin.com/d474e0144 If I type 'mail' I get the mails but that is not what I want, I want to use mutt to browse messages and reply and stuff... thanks
Re: Mutt problem, probably with procmail
On Sat, Sep 13, 2008 at 02:53:08PM +0200, Aleksandar D. Balalovski wrote: hello, I've been using Mutt for half a year now, everything was fine. Yesterday I changed some of the recipes in procmailrc and since than fetchmail/procmail won't put the mail in the preferred mailbox. It puts it in /var/spool/mail/myusername. This is my ~/.muttrc: http://pastebin.com/m4ff673db This is my ~/.fetchmailrc: http://pastebin.com/m3da88750 This is my ~/.procmailrc: http://pastebin.com/d474e0144 If I type 'mail' I get the mails but that is not what I want, I want to use mutt to browse messages and reply and stuff... thanks Why aren't you typing 'mutt' instead of 'mail'?
Re: Mutt problem, probably with procmail
* Aleksandar D. Balalovski [EMAIL PROTECTED] [09-13-08 08:55]: hello, I've been using Mutt for half a year now, everything was fine. Yesterday I changed some of the recipes in procmailrc and since than fetchmail/procmail won't put the mail in the preferred mailbox. It puts it in /var/spool/mail/myusername. This is my ~/.muttrc: http://pastebin.com/m4ff673db This is my ~/.fetchmailrc: http://pastebin.com/m3da88750 This is my ~/.procmailrc: http://pastebin.com/d474e0144 If I type 'mail' I get the mails but that is not what I want, I want to use mutt to browse messages and reply and stuff... Well, your procmail recipe will not work as the matches begin at the start of the recipe, ie: ^TO and your recipe will not match a normal To: Header. and will not deliver to Maildir type mailboxes, needs trailing /. :0: * ^TO_.*lugola-info-center $MAILDIR/lugola/ and you can use the log files to determine problems in procmail but you need to set the verbosity, ie: VERBOSE=on :0: * ^TO_.*lugola-info-center $MAILDIR/lugola/ VERBOSE=off this should place *any* msg to lugola-info-center@anywhere.anyplace in your ~/.Mail/lugola/ directory. DEFAULT setting, $HOME/.Mail/mbox, would put your lugola mail in ~/.Mail/mbox/lugola if anything *would* match your recipe. AND it does not appear that you have told mutt to look for new mail in the lugola directory set mailboxes=lugola you have multiple settings for spoolfile, set spoolfile=+INBOX set spoolfile = ~/.Mail I suggest you spend some time with the fine manual delivered with mutt and at http://mutt.org and for procmail, Nancy McGough's page: http://www.ii.com/internet/robots/procmail/qs/ note: there may be other problems with your configuration as I did not really analyze it very closely. -- Patrick Shanahan Plainfield, Indiana, USAHOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://counter.li.org
Re: Mutt problem, probably with procmail
On Sat, Sep 13, 2008 at 02:53:08PM +0200, Aleksandar D. Balalovski wrote:
hello, I've been using Mutt for half a year now, everything was fine.
Yesterday I changed some of the recipes in procmailrc and since than
fetchmail/procmail won't put the mail in the preferred mailbox. It
puts it in /var/spool/mail/myusername.
To see what procmail is doing, just log its actions, grab a coffee, and
sit down to some reading. I have it permanently enabled, just in case:
# Avoid logging clashes. Separate log records.
MAILDIR=/home/erik/mail # Thanks to Bart Schaefer Ruud H.G. van Tol:
LOGFILE=$MAILDIR/tmp_log.$$ # - Each process uses a temporary log.
FINAL_LOG=$MAILDIR/log# - Append here, via TRAP, at process exit:
TRAP='procmail -p DEFAULT=$FINAL_LOG /dev/null $LOGFILE rm -f $LOGFILE'
If implicated in your recipes, it may be useful to also log some
specifics, such as:
:0 # Unconditionally extract Message-id:
{ MSG_ID=`formail -xMessage-id:` }
LOG=$MSG_ID
:0
{ TO=`formail -xTo:` }
LOG=$TO
If logging is left enabled, it's good to delete or rotate the log file every
few months, when it grows over a few tens of megabytes.
I'll let somone else advise on the mutt side of things. (Mine isn't
involved in mail delivery, and I can't see why it should be, at least
when procmail is in use.)
Erik
--
When one person suffers from a delusion, it is called insanity.
When many people suffer from a delusion, it is called Religion.
-- Robert M. Pirsig in Zen and the Art of Motorcycle Maintenance
Re: Mutt problem, probably with procmail
On Sat, Sep 13, 2008 at 07:15:42AM -0600, Michael wrote: On Sat, Sep 13, 2008 at 02:53:08PM +0200, Aleksandar D. Balalovski wrote: hello, I've been using Mutt for half a year now, everything was fine. Yesterday I changed some of the recipes in procmailrc and since than fetchmail/procmail won't put the mail in the preferred mailbox. It puts it in /var/spool/mail/myusername. This is my ~/.muttrc: http://pastebin.com/m4ff673db This is my ~/.fetchmailrc: http://pastebin.com/m3da88750 This is my ~/.procmailrc: http://pastebin.com/d474e0144 If I type 'mail' I get the mails but that is not what I want, I want to use mutt to browse messages and reply and stuff... thanks Why aren't you typing 'mutt' instead of 'mail'? My bad. I misunderstood you last statement and what you meant. Sigh Most sorry.
Re: Mutt problem, probably with procmail
++ 13/09/08 09:20 -0400 - Patrick Shanahan: Well, your procmail recipe will not work as the matches begin at the start of the recipe, ie: ^TO and your recipe will not match a normal To: Header. and will not deliver to Maildir type mailboxes, needs trailing /. :0: * ^TO_.*lugola-info-center $MAILDIR/lugola/ If this would be the recipe you settle with, you should remove the second colon on the first line. The second colon tells procmail to lock the mailbox it wants to write to. This is required for mbox mailboxes, but for maildir mailboxes it is useless (as you never have two processes writing to the same file). -- Rejo Zenger . [EMAIL PROTECTED] . 0x75FC50F3 . https://rejo.zenger.nl GPG encrypted e-mail prefered. signature.asc Description: Digital signature
Re: Mutt problem, probably with procmail
* Rejo Zenger [EMAIL PROTECTED] [09-13-08 15:15]: ++ 13/09/08 09:20 -0400 - Patrick Shanahan: Well, your procmail recipe will not work as the matches begin at the start of the recipe, ie: ^TO and your recipe will not match a normal To: Header. and will not deliver to Maildir type mailboxes, needs trailing /. :0: * ^TO_.*lugola-info-center $MAILDIR/lugola/ If this would be the recipe you settle with, you should remove the second colon on the first line. The second colon tells procmail to lock the mailbox it wants to write to. This is required for mbox mailboxes, but for maildir mailboxes it is useless (as you never have two processes writing to the same file). Yes, that is correct. I didn't change the recipe to Maildir format until reading his .muttrc and should have removed the unnecessary lock. -- Patrick Shanahan Plainfield, Indiana, USAHOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://counter.li.org
