Re: Procmailrc question

[Paul E Condon]

Your two emails were a help, but opened up some new questions:
Executing install-mh in an xterm failed because install-mh was not
found.  I used find /usr -name 'install-mh' and found *two*
versions. One was in /usr/bin/mh . I take this to be the modern
equivalent of the old /usr/local/nmh/bin. So it appears that install-mh
does something else than installing nmh software somewhere in /usr.
Seeing the swap of mh and bin and the dropping of local, I looked for
the modern analog of /usr/local/nmh/lib at /usr/lib/mh and it is there.
But I foolishly ran install-mh, before looking for its man page. I think
I should not have run it, at least not until I have made more progress
on reviving my old setup. 

I have been looking at mh as a possible alternative to my, more
'mainstream', but non-functioning, email system. And I think I will
look at it seriously, but not until later. I can't see trying to
bring up two different email systems concurrently. Both trying to 
deliver the same email arriving via fetchmail and both looking to 
feed my outgoing emails to exim4, or maybe one to exim4 and the other
to something else. 

I think I would still like to learn what the Debianly correct PATH 
definition is from someone who has a fetchmail/exim4/procmail/mutt
system running in wheezy, and can simply open up his/her .procmailrc
and copy that line into an email. In this there is too much verbiage
about how I can do whatever I want, and not enough explanation of
what is a known solution to a common problem. But even in how-tos 
that say they are specifically for Debian there are instructions
for setup a .forward file to run procmail and I know that is not
part of the Debian way.


On 20110417_175932, Jude DaShiell wrote:
> In debian dpkg-reconfigure nmh may do what install-nmh does for non-debian 
> systems.  I read up on nmh from the nmh website.On Sun, 17 Apr 2011, Paul 
> E Condon wrote:
> 
> > I once had my email working nicely, but over the last few years
> > the setup has decayed. I am now running wheezy with fetchmail to
> > get email from my ISP, exim4 to send outgoing email to my ISP, and
> > do other things locally, and procmail running in my $home. I have
> > no interest in setting up system-wide (i.e. several users) mail
> > delivery since I am the only user of email here. I have been keeping
> > the same .procmailrc file from well before the transition from
> > exim3 to exim4, making ad hoc kludge changes only when absolutely
> > forced to, and largely without a clue as to what I was doing.
> > 
> > I once had spamassassin working, but for a long while it has not
> > been working. Certainly there has been no evidence of it working
> > since I installed xfce under wheezy. Today I noticed in my
> > .procmailrc the following line, which is left over from long ago:
> > 
> > PATH=/usr/local/nmh/lib:/usr/local/nmh/bin:/usr/bin:/usr/local/bin
> > 
> > This line is there for the benefit of the scripting that inplements
> > the recipes that follow. But this is wrong for my wheezy!!! In
> > particular, everything in /usr was put there by installing wheezy with
> > a squeeze business-card CD followed by debian package installs using
> > aptitude pointing to ftp.us.debian.org/debian/. Aptitude says that the
> > package nmh is installed. But there is no directory /usr/local/nmh/ on
> > the computer. Sometime in the past the organization of Debian /usr
> > transitioned from having that directory to not have it. It's been long
> > enough that it may have gone thru several transitions while I was
> > confused and inattentive (because of poor access to emails, perhaps)
> > 
> > Anyway, I think I need a PATH statement that is appropriate for
> > Debian wheezy before I can do any meaningful debugging. 
> > 
> > Can someone who is running a single user Wheezy system using single
> > user .procmailrc and spamassassin (or spamc/spamd) please post a copy
> > of the PATH statement is a working setup? 
> > 
> > As an added goody, please tell me where you got the information.
> > Did it get installed automagically by a Debian package? Or what?
> > 
> > TIA
> > 
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/alpine.bsf.2.00.1104171758250.15...@freire1.furyyjbeyq.arg
> 

-- 
Paul E Condon   
pecon...@mesanetworks.net


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110418021418.gb24...@big.lan.gnu

Re: Procmailrc question

[Rob Owens]

On Sun, Apr 17, 2011 at 03:38:21PM -0600, Paul E Condon wrote:
> I once had my email working nicely, but over the last few years
> the setup has decayed. I am now running wheezy with fetchmail to
> get email from my ISP, exim4 to send outgoing email to my ISP, and
> do other things locally, and procmail running in my $home. I have
> no interest in setting up system-wide (i.e. several users) mail
> delivery since I am the only user of email here. I have been keeping
> the same .procmailrc file from well before the transition from
> exim3 to exim4, making ad hoc kludge changes only when absolutely
> forced to, and largely without a clue as to what I was doing.
> 
> I once had spamassassin working, but for a long while it has not
> been working. Certainly there has been no evidence of it working
> since I installed xfce under wheezy. Today I noticed in my
> .procmailrc the following line, which is left over from long ago:
> 
> PATH=/usr/local/nmh/lib:/usr/local/nmh/bin:/usr/bin:/usr/local/bin
> 
> This line is there for the benefit of the scripting that inplements
> the recipes that follow. But this is wrong for my wheezy!!! In
> particular, everything in /usr was put there by installing wheezy with
> a squeeze business-card CD followed by debian package installs using
> aptitude pointing to ftp.us.debian.org/debian/. Aptitude says that the
> package nmh is installed. But there is no directory /usr/local/nmh/ on
> the computer. Sometime in the past the organization of Debian /usr
> transitioned from having that directory to not have it. It's been long
> enough that it may have gone thru several transitions while I was
> confused and inattentive (because of poor access to emails, perhaps)
> 
> Anyway, I think I need a PATH statement that is appropriate for
> Debian wheezy before I can do any meaningful debugging. 
> 
> Can someone who is running a single user Wheezy system using single
> user .procmailrc and spamassassin (or spamc/spamd) please post a copy
> of the PATH statement is a working setup? 
> 
This is my PATH statement, which worked under Lenny and still works in
Squeeze.  I haven't tried Wheezy.  I'm using mbox for my mail format.
"mbox" is also my default message location.

Heck, I'll include most of my .procmailrc for you:

PATH=/usr/local/bin:/usr/bin:/bin
HOME=/home/rob
MAILDIR=$HOME/Mail
DEFAULT=$MAILDIR/mbox
LOGFILE=$MAILDIR/.procmaillog

### Trust EZhoster and PTD.net to do accurate spam filtering:
:0:
* ^Subject:.*SPAM
/dev/null

### bogofilter spam filtering:
:0fw
| /usr/bin/bogofilter -uep
#
:0:
* ^X-Bogosity: Spam, tests=bogofilter
spam

# some mailing lists:

:0:
* ^todebian-u...@lists.debian.org
debian-user

:0:
* ^From.*.posts.freecycle.org
freecycle

-Rob


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110417224627.ga16...@aurora.owens.net

Re: Procmailrc question

[Jude DaShiell]

In debian dpkg-reconfigure nmh may do what install-nmh does for non-debian 
systems.  I read up on nmh from the nmh website.On Sun, 17 Apr 2011, Paul 
E Condon wrote:

> I once had my email working nicely, but over the last few years
> the setup has decayed. I am now running wheezy with fetchmail to
> get email from my ISP, exim4 to send outgoing email to my ISP, and
> do other things locally, and procmail running in my $home. I have
> no interest in setting up system-wide (i.e. several users) mail
> delivery since I am the only user of email here. I have been keeping
> the same .procmailrc file from well before the transition from
> exim3 to exim4, making ad hoc kludge changes only when absolutely
> forced to, and largely without a clue as to what I was doing.
> 
> I once had spamassassin working, but for a long while it has not
> been working. Certainly there has been no evidence of it working
> since I installed xfce under wheezy. Today I noticed in my
> .procmailrc the following line, which is left over from long ago:
> 
> PATH=/usr/local/nmh/lib:/usr/local/nmh/bin:/usr/bin:/usr/local/bin
> 
> This line is there for the benefit of the scripting that inplements
> the recipes that follow. But this is wrong for my wheezy!!! In
> particular, everything in /usr was put there by installing wheezy with
> a squeeze business-card CD followed by debian package installs using
> aptitude pointing to ftp.us.debian.org/debian/. Aptitude says that the
> package nmh is installed. But there is no directory /usr/local/nmh/ on
> the computer. Sometime in the past the organization of Debian /usr
> transitioned from having that directory to not have it. It's been long
> enough that it may have gone thru several transitions while I was
> confused and inattentive (because of poor access to emails, perhaps)
> 
> Anyway, I think I need a PATH statement that is appropriate for
> Debian wheezy before I can do any meaningful debugging. 
> 
> Can someone who is running a single user Wheezy system using single
> user .procmailrc and spamassassin (or spamc/spamd) please post a copy
> of the PATH statement is a working setup? 
> 
> As an added goody, please tell me where you got the information.
> Did it get installed automagically by a Debian package? Or what?
> 
> TIA
> 



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.bsf.2.00.1104171758250.15...@freire1.furyyjbeyq.arg

Re: Procmailrc question

[Jude DaShiell]

If you runn install-nmh, then nmh will make the directories it needs and 
perhaps start working.  I use nmh and like it better than mbox because 
when malware hits a message that message with offending garbage can be 
sacrificed without the loss of your entire collection of messages.

Hope this helps.On Sun, 17 Apr 2011, Paul E Condon wrote:

> I once had my email working nicely, but over the last few years
> the setup has decayed. I am now running wheezy with fetchmail to
> get email from my ISP, exim4 to send outgoing email to my ISP, and
> do other things locally, and procmail running in my $home. I have
> no interest in setting up system-wide (i.e. several users) mail
> delivery since I am the only user of email here. I have been keeping
> the same .procmailrc file from well before the transition from
> exim3 to exim4, making ad hoc kludge changes only when absolutely
> forced to, and largely without a clue as to what I was doing.
> 
> I once had spamassassin working, but for a long while it has not
> been working. Certainly there has been no evidence of it working
> since I installed xfce under wheezy. Today I noticed in my
> .procmailrc the following line, which is left over from long ago:
> 
> PATH=/usr/local/nmh/lib:/usr/local/nmh/bin:/usr/bin:/usr/local/bin
> 
> This line is there for the benefit of the scripting that inplements
> the recipes that follow. But this is wrong for my wheezy!!! In
> particular, everything in /usr was put there by installing wheezy with
> a squeeze business-card CD followed by debian package installs using
> aptitude pointing to ftp.us.debian.org/debian/. Aptitude says that the
> package nmh is installed. But there is no directory /usr/local/nmh/ on
> the computer. Sometime in the past the organization of Debian /usr
> transitioned from having that directory to not have it. It's been long
> enough that it may have gone thru several transitions while I was
> confused and inattentive (because of poor access to emails, perhaps)
> 
> Anyway, I think I need a PATH statement that is appropriate for
> Debian wheezy before I can do any meaningful debugging. 
> 
> Can someone who is running a single user Wheezy system using single
> user .procmailrc and spamassassin (or spamc/spamd) please post a copy
> of the PATH statement is a working setup? 
> 
> As an added goody, please tell me where you got the information.
> Did it get installed automagically by a Debian package? Or what?
> 
> TIA
> 



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.bsf.2.00.1104171755130.15...@freire1.furyyjbeyq.arg

Re: .procmailrc

[kmark]

On Sun, 5 Oct 2003 [EMAIL PROTECTED] wrote:

> How do I make procmail sort out the debian user list?
> I've tried:
>
> #Debian user
> :0
> * ^To:[EMAIL PROTECTED]
> debian
>
> But it doesn't work.

Hi Anjun,
this procmailrc contains a few helpful options. A logfile, a default
mailbox and a backup copy of every message before it goes to any rules
that you add
---
PATH=/usr/local/bin:/usr/bin:/bin
MAILDIR=$HOME/mail  #put all sorted mail here
DEFAULT=$HOME/mbox   #default mail box
LOGFILE=$MAILDIR/from   #log file
# backup copy of all mail
:0 c
$MAILDIR/backup
# rule for debian-user list
:0
* ^To:[EMAIL PROTECTED]
$MAILDIR/daily/debian-user
# add other rules here
--
-Kev


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: .procmailrc

[Oliver Fuchs]

On Sun, 05 Oct 2003, [EMAIL PROTECTED] wrote:

> How do I make procmail sort out the debian user list?
> I've tried:
> 
> #Debian user
> :0
> * ^To:[EMAIL PROTECTED]
> debian
> 
> But it doesn't work.

Hi,
I use for example:

:0:
* [EMAIL PROTECTED]
debian

:0:
* [EMAIL PROTECTED]
debian-news

:0:
* ^TO_(debian-security-announce|debian-security)@lists\.debian\.org
debian-security

If you are using the digest-form:

  :0:
  * ^Subject:.*debian.*Digest
  | formail +1 -ds >>debian

Oliver
-- 
... don't touch the bang bang fruit


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: .procmailrc

[Michael West]

On Sun, Oct 05, 2003 at 08:14:46PM +0200, [EMAIL PROTECTED] wrote:
> How do I make procmail sort out the debian user list?
> I've tried:
> 
> #Debian user
> :0
> * ^To:[EMAIL PROTECTED]
> debian
> 
> But it doesn't work.
> 

I use 

:0:
* X-Mailing-List: <\/[EMAIL PROTECTED]
`echo $MATCH | sed -e 's/[\/]/_/g'`

To match all mails with X-Mailing-List headers in one go.


-- 
"In the land of the blind, the one-eyed man is caned."


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: .procmailrc

[Christian Borchmann]

so mach ich das:


.procmailrc [B---] 37 L:[ 12+21  33/ 60] *(580 / 947b)= .  10 0x0A

# Debian Mailinglisten sortieren

:0
* ^X-Mailing-List: <[EMAIL PROTECTED]>
Maildir/.Mailinglisten.debian-user-german/new

alles noch sehr rudimentär, denn ich hab das mit procmail auch erst heute
nachmittag kapiert ;-)


schau dir mal den header der mail an:


X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/303787
X-Loop: [EMAIL PROTECTED]
List-Id: 
List-Post: 
List-Help: 
List-Subscribe:

List-Unsubscribe:

List-Archive: 
Precedence: list

gute nacht

-- 
mit freundlichen Grüßen

Christian "SPITFIRE" Borchmann

URL: http://www.borchi.de

Weekend Warrior´s Clan

URL: http://www.ww-clan.com
IRC: irc.de.quakenet.org #ww-clan

Jagdgeschwader 2 "Richthofen"

URL: http://www.jg2.de
IRC: irc.sturmovik.de #jg2

Gut gekotzt ist halb gefrühstückt...
(old german wisdom)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: .procmailrc

[Hans Gubitz]

:0:
* ^TOdebian-user
/home/NN/Mail/debian

On Sun, Oct 05, 2003 at 08:14:46PM +0200, [EMAIL PROTECTED] wrote:
> How do I make procmail sort out the debian user list?
> I've tried:
> 
> #Debian user
> :0
> * ^To:[EMAIL PROTECTED]
> debian
> 
> But it doesn't work.
> 
> -- 
> Kjetil Ørbekk <[EMAIL PROTECTED]>
> 

-- 
Hans Gubitz <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: .procmailrc

[Shane Hickey]

> How do I make procmail sort out the debian user list?

This is what I do, and it works like a charm:

:0:
* [EMAIL PROTECTED]
DEBIAN-USER/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: .procmailrc

[Matthias Hentges]

Am Son, 2003-10-05 um 20.14 schrieb [EMAIL PROTECTED]:
> How do I make procmail sort out the debian user list?
> I've tried:
> 
> #Debian user
> :0
> * ^To:[EMAIL PROTECTED]
> debian
> 
> But it doesn't work.

Try this:

:0 H
* ^X-Mailing-List.*debian-user.*
debian

Works For Me (TM).

-- 

Matthias Hentges 
Cologne / Germany

[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4   -> No files, no URL's

My OS: Debian Woody. Geek by Nature, Linux by Choice


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

Re: .procmailrc

[Philippe Marzouk]

On Sun, Oct 05, 2003 at 08:14:46PM +0200, [EMAIL PROTECTED] wrote:
> How do I make procmail sort out the debian user list?
> I've tried:
> 
> #Debian user
> :0
> * ^To:[EMAIL PROTECTED]
> debian
> 
> But it doesn't work.
> 

I use :

:0
* ^X-Mailing-List: <[EMAIL PROTECTED]>
.debian-user/


If you want to stick to the To header then, you'd better use that :

* [EMAIL PROTECTED]


HTH,
Philippe


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: .procmailrc

[Denis Dzyubenko]

On Sun, 5 Oct 2003 20:14:46 +0200,
 ??(a) wrote to Debian User List:

a> How do I make procmail sort out the debian user list?
a> I've tried:

a> #Debian user
a> :0
a> * ^To:[EMAIL PROTECTED]
a> debian

a> But it doesn't work.

this should work fine, check procmail log (LOGFILE variable, for more
info see procmailrc(5)).

But, for sorting debian lists it is better to use X-Mailing-List
header.

-- 
Denis.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Procmailrc to play sound async when message arrives

[tb . nospam]

On Tue, Sep 23, 2003 at 09:53:36AM +0100, Carlos Sousa wrote:
> On Tue, 23 Sep 2003 01:16:51 -0700 [EMAIL PROTECTED] wrote:
> > On Tue, Sep 23, 2003 at 09:06:49AM +0100, Carlos Sousa wrote:
> > > On Mon, 22 Sep 2003 19:45:42 -0700 [EMAIL PROTECTED] wrote:
> > > > 
> > > > if I fork bplay several times, it doesn't "mix" the sounds: they 
> > > > still play out synchronously, even though the caller isn't blocked.
> > > > 
> > > > Is there a sound utility that will play a WAV file in an "overlapped 
> > > > way" -- so that I can get my "rapid fire clicking effect".  I know alsa 
> > > > can do this: I play XMMS and Festival and MPlayer all simultaneously.  
> > > > How can I do that from the command line with a WAV?
> > > 
> > > The command 'play' (sox) does exactly that on my system.
> > 
> > play seems to block until sound is fully played for me; identically to 
> > bplay.  Specifically:
> > 
> > play file.wav &
> > play file.wav &
> > play file.wav &
> > 
> > Control returns immediately; but files play sequentially not 
> > simultaneously.
> 
> Not here. Perhaps it's an issue with the sound daemon running on your
> system, then. I'm running artsd.
> 

A-HA!  That's what I needed.  artsplay/artsd did the trick.

Thx.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Procmailrc to play sound async when message arrives

[Carlos Sousa]

On Tue, 23 Sep 2003 01:16:51 -0700 [EMAIL PROTECTED] wrote:
> On Tue, Sep 23, 2003 at 09:06:49AM +0100, Carlos Sousa wrote:
> > On Mon, 22 Sep 2003 19:45:42 -0700 [EMAIL PROTECTED] wrote:
> > > 
> > > if I fork bplay several times, it doesn't "mix" the sounds: they 
> > > still play out synchronously, even though the caller isn't blocked.
> > > 
> > > Is there a sound utility that will play a WAV file in an "overlapped 
> > > way" -- so that I can get my "rapid fire clicking effect".  I know alsa 
> > > can do this: I play XMMS and Festival and MPlayer all simultaneously.  
> > > How can I do that from the command line with a WAV?
> > 
> > The command 'play' (sox) does exactly that on my system.
> 
> play seems to block until sound is fully played for me; identically to 
> bplay.  Specifically:
> 
> play file.wav &
> play file.wav &
> play file.wav &
> 
> Control returns immediately; but files play sequentially not 
> simultaneously.

Not here. Perhaps it's an issue with the sound daemon running on your
system, then. I'm running artsd.

-- 
Carlos Sousa
http://vbc.dyndns.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Procmailrc to play sound async when message arrives

[tb . nospam]

On Tue, Sep 23, 2003 at 09:06:49AM +0100, Carlos Sousa wrote:
> On Mon, 22 Sep 2003 19:45:42 -0700 [EMAIL PROTECTED] wrote:
> > 
> > if I fork bplay several times, it doesn't "mix" the sounds: they 
> > still play out synchronously, even though the caller isn't blocked.
> > 
> > Is there a sound utility that will play a WAV file in an "overlapped 
> > way" -- so that I can get my "rapid fire clicking effect".  I know alsa 
> > can do this: I play XMMS and Festival and MPlayer all simultaneously.  
> > How can I do that from the command line with a WAV?
> 
> The command 'play' (sox) does exactly that on my system.
> 
> -- 
> Carlos Sousa
> http://vbc.dyndns.org/
> 

play seems to block until sound is fully played for me; identically to 
bplay.  Specifically:

play file.wav &
play file.wav &
play file.wav &

Control returns immediately; but files play sequentially not 
simultaneously.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Procmailrc to play sound async when message arrives

[Carlos Sousa]

On Mon, 22 Sep 2003 19:45:42 -0700 [EMAIL PROTECTED] wrote:
> 
> if I fork bplay several times, it doesn't "mix" the sounds: they 
> still play out synchronously, even though the caller isn't blocked.
> 
> Is there a sound utility that will play a WAV file in an "overlapped 
> way" -- so that I can get my "rapid fire clicking effect".  I know alsa 
> can do this: I play XMMS and Festival and MPlayer all simultaneously.  
> How can I do that from the command line with a WAV?

The command 'play' (sox) does exactly that on my system.

-- 
Carlos Sousa
http://vbc.dyndns.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Procmailrc to play sound async when message arrives

[tb . nospam]

On Tue, Sep 23, 2003 at 02:22:28AM -0400, [EMAIL PROTECTED] wrote:
> 
> 
> On Mon, 22 Sep 2003 [EMAIL PROTECTED] wrote:
> 
> >
> > so unless anybody has a better already written sound buffer mixer to
> > recommend, consider this matter closed.
> >
> > Thanks for your attention.
> > -T
> >
> I had a sugguestion. have a lock file. so, if your script is about to play
> a new sound, it check to see if a sound is being played. It will then not
> play/queue up a new sound. So, one long tone will play.
> Does this make sense?
> -Kev

Thanks.  Lockfile was the answer.  I was able to do it in bash.

Pseudocode:
[Make a .RAW copy of the .WAV.  Get lock.  First time, record name of 
.WAV.  Or else, record name of .RAW.  Invoke 2nd script async.  Release 
lock.  
2nd script: Sleep 2 seconds.  Get lock.  Cat files to bplay async.  
Clear list of files.  Release lock.]

It ends up making a rapid-fire series of clicks, once per mail.

I have another question: Can Procmail fire a single script when it's 
done processing *ALL* mails?  I could simplify things if that's 
possible.

Whew!
-Tom


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Procmailrc to play sound async when message arrives

[Robert Vollmert]

> if I fork bplay several times, it doesn't "mix" the sounds: they 
> still play out synchronously, even though the caller isn't blocked.

I've experienced this with OSS emulation on ALSA. Perhaps playing the
sound with 'aplay' instead helps? If not, consider configuring the
'dmix' plug-in for ALSA.

Cheers
Robert


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Procmailrc to play sound async when message arrives

[kmark]

On Mon, 22 Sep 2003 [EMAIL PROTECTED] wrote:

>
> so unless anybody has a better already written sound buffer mixer to
> recommend, consider this matter closed.
>
> Thanks for your attention.
> -T
>
I had a sugguestion. have a lock file. so, if your script is about to play
a new sound, it check to see if a sound is being played. It will then not
play/queue up a new sound. So, one long tone will play.
Does this make sense?
-Kev


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Procmailrc to play sound async when message arrives

[tb . nospam]

On Mon, Sep 22, 2003 at 07:45:42PM -0700, [EMAIL PROTECTED] wrote:
> On Mon, Sep 22, 2003 at 10:15:40PM -0400, Andrew Perrin wrote:
> > There's probably an easier way than this, but you could use perl to fork()
> > the bplay processes, so they don't block.
> > 
> 
> Okay, I realized I could just call a bash script that ends in & to play 
> the sounds async to procmail, that's half the question.
> 
> Now my question is narrower and doesn't involve procmail:
> 
> if I fork bplay several times, it doesn't "mix" the sounds: they 
> still play out synchronously, even though the caller isn't blocked.
> 
> Is there a sound utility that will play a WAV file in an "overlapped 
> way" -- so that I can get my "rapid fire clicking effect".  I know alsa 
> can do this: I play XMMS and Festival and MPlayer all simultaneously.  
> How can I do that from the command line with a WAV?

Ignore me: I've figured it out.  It's going to require bplay reading a 
named pipe, and a custom C program feeding headerless data to the pipe 
for each instance, and me learning how do to this on Unix (I know how to 
do Overlapped I/O and I/O Completion ports on Windows)...

so unless anybody has a better already written sound buffer mixer to 
recommend, consider this matter closed.

Thanks for your attention.
-T


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Procmailrc to play sound async when message arrives

[tb . nospam]

On Mon, Sep 22, 2003 at 10:15:40PM -0400, Andrew Perrin wrote:
> There's probably an easier way than this, but you could use perl to fork()
> the bplay processes, so they don't block.
> 

Okay, I realized I could just call a bash script that ends in & to play 
the sounds async to procmail, that's half the question.

Now my question is narrower and doesn't involve procmail:

if I fork bplay several times, it doesn't "mix" the sounds: they 
still play out synchronously, even though the caller isn't blocked.

Is there a sound utility that will play a WAV file in an "overlapped 
way" -- so that I can get my "rapid fire clicking effect".  I know alsa 
can do this: I play XMMS and Festival and MPlayer all simultaneously.  
How can I do that from the command line with a WAV?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Procmailrc to play sound async when message arrives

[Andrew Perrin]

There's probably an easier way than this, but you could use perl to fork()
the bplay processes, so they don't block.

--
Andrew J Perrin - http://www.unc.edu/~aperrin
Assistant Professor of Sociology, U of North Carolina, Chapel Hill
[EMAIL PROTECTED] * andrew_perrin (at) unc.edu


On Mon, 22 Sep 2003 [EMAIL PROTECTED] wrote:

> I'm a procmail newb.  I've written a recipie to play a WAV when a
> message arrives.  It works, it sounds nice, but it's synchronous:
>
> :0 c
> * ^X-Mailing-List:.*lists.debian.org*
> | /usr/bin/bplay /x/x/click_x.wav
>
> Since this WAV takes ~1 sec to play, procmail blocks 1 sec per message.
> It ends up taking a long time with a bunch of messages.
>
> Is there any way I can make the clicks "overlap" with multiple messages
> (cl-cl-cl-cl-click vs click.pause.click.pause.click.pause.click) and the
> whole process to run asynchronously to procmail?
>
> Thanks
> -Tom
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: procmailrc question

[kmark]

On Mon, 15 Sep 2003, Colin Watson wrote:

> If you don't create a directory called $HOME/mail/debian-user, then
> procmail will automatically save mail to an mbox by that name. If
> there's a directory there, it'll default to a maildir (erm, as in the
> mailbox format, as distinct from $MAILDIR).
B-I-N-G-O! I made $HOME/mail/, thus maildir. so I did:
cat msg.* > new_mbox
I seem to have overlooked that little detail.
-Kevin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: procmailrc question

[Kenneth Dombrowski]

On 03-09-15 03:10 -0400, [EMAIL PROTECTED] wrote:
> Hi DU,
> I'm new to procmail and I wondered if you can point me in the right
> direction.
> this is my .procmailrc
> --
> PATH=/usr/local/bin:/usr/bin:/bin
> MAILDIR=$HOME/mail  #you'd better make sure it exists
> DEFAULT=$HOME/mbox   #completely optional
> LOGFILE=$MAILDIR/from   #recommended
> :0 c
> $MAILDIR/backup
> :0
> * ^To: [EMAIL PROTECTED]
> $MAILDIR/nylxs-announce
> :0
> * ^To: [EMAIL PROTECTED]
> $MAILDIR/debian-user
> -
> my debian-user mail is being saved as individual message. How do I tell it
> to save it to a mailbox? like $HOME/mail/debian-user or
> $HOME/mail/debian-user/mbox.

Hi Kevin,

I'm using the Courier-style Maildirs with something like this:


DEFAULT=$HOME/Maildir/
# to invoke programs from .procmailrc, you may need
SHELL=/bin/sh
# directory for storing procmail config + logs
# (note procmail does not expand "~", you must use "$HOME")
PMDIR=$HOME/Procmail
# -
# Once MAILDIR is set, procmail will cd to it
# and all relative paths will be relative to $MAILDIR
# -
MAILDIR=$HOME/Maildir
### sort spamassassin-flagged msgs
:0
* ^X-Spam-Flag: YES
.spam-caught/
# messages that fall through all your procmail recipes are 
# delivered to your default INBOX
:0
* ^TO_debian-(user|isp|apache)
.IN-debian/
:0
* ^TO_nylug-talk
.IN-nylug-talk/


hth,
Kenneth


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: procmailrc question

[Colin Watson]

On Mon, Sep 15, 2003 at 03:10:43AM -0400, [EMAIL PROTECTED] wrote:
> I'm new to procmail and I wondered if you can point me in the right
> direction.
> this is my .procmailrc
> --
> PATH=/usr/local/bin:/usr/bin:/bin
> MAILDIR=$HOME/mail  #you'd better make sure it exists
> DEFAULT=$HOME/mbox   #completely optional
> LOGFILE=$MAILDIR/from   #recommended
> :0 c
> $MAILDIR/backup
> :0
> * ^To: [EMAIL PROTECTED]
> $MAILDIR/nylxs-announce
> :0
> * ^To: [EMAIL PROTECTED]
> $MAILDIR/debian-user
> -
> my debian-user mail is being saved as individual message. How do I tell it
> to save it to a mailbox? like $HOME/mail/debian-user or
> $HOME/mail/debian-user/mbox.

If you don't create a directory called $HOME/mail/debian-user, then
procmail will automatically save mail to an mbox by that name. If
there's a directory there, it'll default to a maildir (erm, as in the
mailbox format, as distinct from $MAILDIR).

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: .procmailrc/.muttrc conflict ?

[Tyler Creelan]

Adam asked:

> You'll notice that .procmail uses Maildir to define a mailbox, yet when
> I uncomment the Maildir lines in the .muttrc, I get the error message
> that "Maildir is not a mailbox".

MAILDIR is a *variable* under procmail, not an actual directory. It
makes no sense to reference a directory called "Maildir" in your
.muttrc. 

TFC


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: .procmailrc multiple actions

[Sven Burgener]

On Fri, Feb 02, 2001 at 07:02:01PM +0100, Marc A. Donges wrote:
> On Friday, February 02, 2001 at 18:41:16 (+0100), Sven Burgener wrote:
> > --8<--
> > :0
> > * ^From: Mail Delivery Subsystem
> > | (formail -I "To: [EMAIL PROTECTED]") |\
> >   (formail -I "CC: [EMAIL PROTECTED], [EMAIL PROTECTED]") | $SENDMAIL -t
> > 
> > :0
> > ! [EMAIL PROTECTED]
> > --8<--
> 
> The first recipy is a delivering one. This means that if the first
> pattern matches, the mail won't get to the second.

True, but ...

> If you want to have both actions taken, you must specify the "c" flag
> on the first one (":0c" instead of ":0").

... that wasn't my question.

It is not my intention to apply both the formail'ing and the '!'
forwarding to one particular email.

> Furthermore, your first recipy will almost certainly create
> mail-loops: If [EMAIL PROTECTED] cannot be delivered to, the mail will
> be bounced to the account that did the above procmail-filtering, in
> turn being forwarded to [EMAIL PROTECTED] You should therefore specify
> "-f '<>'" on the sendmail-command-line to create a
> zero-return-address.

Thanks for the info about this issue. I'll take that into account.

> Why do you want those headers to appear in the message?

I merely want the mail to appear to be destined to "[EMAIL PROTECTED]"
instead of the user on the system that has the above .procmailrc file
and that receives this email in the first place.

Additionally, I want to add a CC: to the message on-the-fly, overwriting
an existing one, if there.

I must apologise, the above code *does* work. My test scenario / test
setup was misleading me.  /me blushes

Thank you for your time and insight, though.

Sven
-- 
"{sum += $2} END {print sum}", said Tom awkwardly.

Re: .procmailrc multiple actions

[Marc A. Donges]

On Friday, February 02, 2001 at 18:41:16 (+0100), Sven Burgener wrote:
> --8<--
> :0
> * ^From: Mail Delivery Subsystem
> | (formail -I "To: [EMAIL PROTECTED]") |\
>   (formail -I "CC: [EMAIL PROTECTED], [EMAIL PROTECTED]") | $SENDMAIL -t
> 
> :0
> ! [EMAIL PROTECTED]
> --8<--

The first recipy is a delivering one. This means that if the first
pattern matches, the mail won't get to the second.

If you want to have both actions taken, you must specify the "c" flag on
the first one (":0c" instead of ":0").

Furthermore, your first recipy will almost certainly create mail-loops:
If [EMAIL PROTECTED] cannot be delivered to, the mail will be bounced to
the account that did the above procmail-filtering, in turn being
forwarded to [EMAIL PROTECTED] You should therefore specify "-f '<>'" on
the sendmail-command-line to create a zero-return-address.

Another problem exists in the recipy. Strange things, that you will not
understand at first glance will happen, if the rewritten Mail contains
any Resent-(To|Cc|Bcc):-Headers. They take precedence over the
(To|Cc):-headers you are inserting.

Why do you want those headers to appear in the message?

Marc

-- 
  _ _  Marc A. Donges+49 791 51804
  'v'   <[EMAIL PROTECTED]>
 /   \   PGP-Key(DSA): 1024D/1C9ECFF2
  W W
 Fingerprint: 58B9 07A6 CBB1 7016 EB1D  7D35 EEBE 67DC 1C9E CFF2

Re: Procmailrc ?

[David Kanter]

I happened to see this in the www.procmail.org mailing list archives
yesterday. Sorry I don't know the answer off the top of my head, but it's
there.

On Sat, Mar 18, 2000 at 04:17:56PM -0600, Lance Hoffmeyer wrote:
> I keep getting a "Suspecious rc file /home/lance/.procmailrc" "Coundn't 
> read rc file" when I fetchmail -m 'procmail' and get mail from my ISP.
---end quoted text---

-- 
David Kanter
FreeBSD 3.4
[EMAIL PROTECTED]

Re: procmailrc file suspicious?

[Mark Brown]

On Fri, Jul 02, 1999 at 06:38:40PM -0500, Lance Hoffmeyer wrote:

> Now when I use fetchmail and it tries to read my .procmailrc it tells me it 
> is a suspicious file and won't read it.  
> Anyone know what is going on here?  My rights are set to read/write for 
> everyone.  My user is the owner and group.

Could you be more specific?  How is procmail being invoked?  If you mean
.fetchmailrc, you should have it set og-rwx.  Try a similar thing for
.procmailrc, ane make sure it's a regular file and not (for example) a
symlink.  The exact error messages would be helpful.  

> Any suggestions?  Also, any suggestions on how to remove that '~' 
> subdirectory without destroying my home directory again?

Specify a more complete path to it, such as

   rm -rf ./~

from the parent directory.

-- 
Mark Brown  mailto:[EMAIL PROTECTED]   (Trying to avoid grumpiness)
http://www.tardis.ed.ac.uk/~broonie/
EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/


pgpVBXISinXNp.pgp
Description: PGP signature

Re: procmailrc file suspicious?

[Steve Lamb]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, 2 Jul 1999 18:38:40 -0500, Lance Hoffmeyer wrote:

>it is in a directory called data (i.e. /data/~).  

rmdir \~I think

- -- 
 Steve C. Lamb | I'm your priest, I'm your shrink, I'm your
 ICQ: 5107343  | main connection to the switchboard of souls.
- ---+-

-BEGIN PGP SIGNATURE-
Version: PGPsdk version 1.0 (C) 1997 Pretty Good Privacy, Inc

iQA/AwUBN31U73pf7K2LbpnFEQIZVACg5HwDtYUV5JFAIvfn+OCBLv5DWOwAn2FH
QU10OxhuQgMe4ls2qsm5dY7a
=VcGk
-END PGP SIGNATURE-

Re: procmailrc help

[ioannis]

 Attached to this letter you will find a procmailrc file. Adjust
 the MAILDIR variable and are set. 




> Here's what I want to do:
> 1) mail addressed to me goes into the inbox (even from mailing lists)
> 2) mailing lists are separated (already working)
> 3) remaining messages go into a junk folder


-- 
Ioannis Tambouras 
[EMAIL PROTECTED], West Palm Beach, Florida
Signed pgp-key on key server. 

#VERBOSE=on
HOME=/home/paul
PATH=$HOME/bin:/usr/bin:/bin:/usr/local/bin:.
MAILDIR=/home/paul/mail
DEFAULT=$MAILDIR/junk
LOGFILE=$MAILDIR/log
LOCKFILE=$HOME/Mail/.lockmail


:0
*(^To:|^Cc:)[EMAIL PROTECTED]
inbox


:0
*(Cc:|From:|To:).*debian-bugs*
bug

:0
*(Cc:|From:|To:).*debian.*changes*
changes

:0
*(Cc:|From:|To:).*debian-user
user

:0
*(Cc:|From:|To:).*debian-announce
announce

:0
*(Cc:|From:|To:).*debian-changes
changes

Re: procmailrc help

[Jim Pick]

The Filtering Mail FAQ explains how to set up both procmail and mailagent.

http://www.ii.com/internet/faqs/launchers/mail/filtering-faq/

Cheers,

 - Jim



pgpzXLTTlL8Zs.pgp
Description: PGP signature

Re: procmailrc help

[Branden Robinson]

On Sat, 13 Sep 1997, Paul Miller wrote:

> Here's what I want to do:
> 
> 1) mail addressed to me goes into the inbox (even from mailing lists)
> 2) mailing lists are separated (already working)
> 3) remaining messages go into a junk folder
> 
> any ideas?

Sure.  This is what I do, except for the junk part, which I've been meaning
to add for a while and just did.  I notice most spam has bogus or useless
To: lines, so that makes filtering that nasty stuff all the easier.

Here's an abbreviated version of my .procmailrc:

--- SNIP ---
PATH=$HOME/bin:/usr/local/bin:/usr/bin:/bin
MAILDIR=$HOME/mail # you'd better make sure it exists
# DEFAULT=$MAILDIR/default # completely optional
LOGFILE=$MAILDIR/logfile   # recommended

# Use the Sender: (or Resent-Sender:) line if it exists, b/c that way we
# don't have to worry about messages cc'ed to me personally when I also
# belong to the list

:0:
* ^Sender: JS Bach and other Early and Baroque Music List <[EMAIL PROTECTED]>.*
bach-list

:0:
* ^Resent-Sender: debian-announce-request.*
debian-announce

:0:
* ^Resent-Sender: debian-changes-request.*
debian-changes

:0:
* ^Resent-Sender: debian-devel-request.*
debian-devel

:0:
* ^Resent-Sender: debian-user-request.*
debian-user

# NASANews only comes from one address, so this is easy
:0:
* ^From: [EMAIL PROTECTED]
nasanews

:0:
* !^To: .*branden.*
junk
--- SNIP ---

Explanation: since I use the recommended .forward:

"|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #branden"

Anything not processed by the .procmailrc stays in the inbox.  This is what
we want.  All the mailing list stuff is sorted out -- if you want for
some reason to collapse all your mailing lists into one box, I think you
can just pile all those asterisk lines into one recipe and dump them to
"mailing-list" or something.

Note the last line.  I'm liberal with the "To:" field because I get mail
forwarded to the home box from all kinds of places.  The ! in front of it
just says "not".

There you go.

--
G. Branden Robinson |   "I came, I saw, she conquered."  The
Purdue University   |   original Latin seems to have been
[EMAIL PROTECTED]  |   garbled.
http://www.ecn.purdue.edu/~branden/ |   -- Robert Heinlein


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? 
e-mail to [EMAIL PROTECTED] .

Re: procmailrc help

[Marcus Brinkmann]

On Sun, Sep 14, 1997 at 01:02:38AM -0400, [EMAIL PROTECTED] wrote:
> 
>  Attached to this letter you will find a procmailrc file. Adjust
>  the MAILDIR variable and are set. 

[snip]
> :0
> *(Cc:|From:|To:).*debian-bugs*
> bug

But if you want put all mail *from* the list to  the folder, perhaps the
X-Mailing-List header is the preferred way...

:0:
* ^X-Mailing-List: *
debian.bugs

On the other hand, there is certainly more than one way to do it.

Marcus

-- 
"Rhubarb is no Egyptian god."
Marcus Brinkmann
[EMAIL PROTECTED]
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? 
e-mail to [EMAIL PROTECTED] .