KCLUG

5 participants
3248 discussions

RE: Bash Question
by djgoku 14 Oct '04

14 Oct '04

On Thu, 14 Oct 2004 15:04:15 -0500, Ben Kelley <blk6224(a)gmail.com> wrote: > $? is the exit code of the previous command # attempt to remount the RW mount point as RW; else abort $MOUNT -o remount,rw $MOUNT_DEVICE $SNAPSHOT_RW ; if (( $? )); then { $ECHO "snapshot: could not remount $SNAPSHOT_RW readwrite"; exit; } fi; So in this example if failed it would echo "snapshot: ...", or else go to next set of code. Correct? Thanks, -- dj_goku -www.djgoku.com- -www.tektronic.org-

2 2

RE: Re: Help configuring fetchmail
by Brian Densmore 14 Oct '04

14 Oct '04

I am by no means a procmail or exim guru. But from what I've read Jeremy's configuration will not work on pre exim 4.x. Brian > -----Original Message----- > From: linux(a)bizniche.com > >[snip] > > So I tried setting it up like you mention. The only thing I don't > understand is the driver=accept part. I get an error related to this > when I log in as another user and run 'mail -s "testing" mdg'. The > error is: > -------- > avast:/home/mdg# mail -s "testing" mdg > Cc: > Null message body; hope that's ok > 2004-10-14 10:33:52 Exim configuration error > router procmail: cannot find router driver "accept" in line 405 > Can't send mail: sendmail process failed with error code 1 > avast:/home/mdg# > --------- > > I wondered if you have anything in your .conf about the accept...maybe > another section that defines it? I tried to make sure that there were > no transport or router conflicts. > > My .procmailrc file looks like yours, with obvious > changes...homedir and > maildir changes. The rest is the same. > > My exim.conf looks like this: http://mdg.homelinux.org/exim.conf > > Also...I'm not using exim4, and thought this might be a difference. > > Any ideas? > > Matt > _______________________________________________ > Kclug mailing list > Kclug(a)kclug.org > http://kclug.org/mailman/listinfo/kclug >

2 1

Re: Re: Help configuring fetchmail
by linux＠bizniche.com 14 Oct '04

14 Oct '04

> Oops.. I meant router, not transport. You need an entry in transport and > router, but order _does_ matter in the router section, and not in the > transport. Therefore, the procmail router should be listed before the > maildir or in your case "local_delivery". > > Basically, exim will go down the router list and say "do I match this > router condition?" It will get to procmail and say "Do I have > /usr/bin/procmail and ~/.procmailrc for the user?" If those two > conditions exist, then it delivers the mail to procmail > > > Is this the trasport that you mentioned? What does a procmail setup > > look like? > > For procmail, you will need to have the procmail router and transport. > The procmail_pipe is the transport. It basically tells exim what to do > with the email should the procmail router match. > > > Here is my procmail router > > ********* > procmail: > debug_print = "R: procmail for $local_part@$domain" > driver = accept > domains = +local_domains > check_local_user > transport = procmail_pipe > require_files = ${local_part}:${home}/.procmailrc:+/usr/bin/procmail > no_verify > no_expn > ********* > > The transport line says, if this matches, then call the procmail_pipe > transport to know where to deliver the email. This particular router > verifies that the intended recipient is infact a local user, and then > checks the required_files for a .procmailrc and /usr/bin/procmail file. > If those are present, then it calls the procmail_pipe transport. Mine > looks like this: > > ************** > procmail_pipe: > debug_print = "T: procmail_pipe for $local_part@$domain" > driver = pipe > path = "/bin:/usr/bin:/usr/local/bin" > command = "/usr/bin/procmail" > return_path_add > delivery_date_add > envelope_to_add > ************** > > The command line will pipe (see the driver line) the full email to that > command. Procmail will then figure out who it goes to and read the > .procmailrc file to figure out how to deliver it. A simple procmailrc > file for maildirs would look something like this: > > ************** > HOME=/home/jeremy > PMDIR=$HOME/.procmail > LOGFILE=$PMDIR/log > MAILDIR=$HOME/mail/ > LOCKFILE=$PMDIR/.lockmail > VERBOSE=no > > # catch all for inbox > :0 > $MAILDIR > *************** Jeremy: So I tried setting it up like you mention. The only thing I don't understand is the driver=accept part. I get an error related to this when I log in as another user and run 'mail -s "testing" mdg'. The error is: -------- avast:/home/mdg# mail -s "testing" mdg Cc: Null message body; hope that's ok 2004-10-14 10:33:52 Exim configuration error router procmail: cannot find router driver "accept" in line 405 Can't send mail: sendmail process failed with error code 1 avast:/home/mdg# --------- I wondered if you have anything in your .conf about the accept...maybe another section that defines it? I tried to make sure that there were no transport or router conflicts. My .procmailrc file looks like yours, with obvious changes...homedir and maildir changes. The rest is the same. My exim.conf looks like this: http://mdg.homelinux.org/exim.conf Also...I'm not using exim4, and thought this might be a difference. Any ideas? Matt

1 0

RE: Shared teleconferencing in Linux
by Brian Densmore 14 Oct '04

14 Oct '04

Getting to meetings is rather tough for me these days. Dropping off and picking up my daughter from daycare, she might get a bit cranky staying out that late, and when she gets cranky everyone hears about it. She's really still only got one word for complaining... WAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHHHHHHHHHHHHHH!!!!! Not sure, I'm ready to subject the list to that yet, but if there is a consensus on the list to see the demo, I'll provide the other half, it would have to be a desktop though because I haven't been able to get the sound working on the laptop (ok I haven't tried every combination). > -----Original Message----- > From: Brian Kelsay > > > If GnomeMeeting is on Knoppix, then I have it on my laptop, > otherwise I could apt-get it real quick. I know my usb > webcam and sound works. I'd have to bring some external > speakers though, because the built-in ones suck. I might > even have a headset w/ mic around somewhere that I've never > used. If you bring the other half, then we'll do it. >

3 3

RE: Shared teleconferencing in Linux
by Brian Kelsay 14 Oct '04

14 Oct '04

I understand. Luckily the crying at my house is at a dull roar mostly. The youngest is 4 now. So if you don't want to bring her that's cool. If you have a Yamaha OPL3-Sax chipset, then good luck, you'll need it. If I recall, you have an older laptop that may have one of those. An old Toshiba, right? Somebody else want to volunteer to bring the other half of the required hardware? Laptop or desktop, webcam that works under Linux, network and sound already working under Linux. I'll have a 10/100/wireless switch and always have a few extra Cat5 cables. I have a newer USB webcam, but haven't gotten it to work yet. Brian Kelsay >>> "Brian Densmore" <> 10/14/04 09:11AM >>> Getting to meetings is rather tough for me these days. Dropping off and picking up my daughter from daycare, she might get a bit cranky staying out that late, and when she gets cranky everyone hears about it. She's really still only got one word for complaining... WAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHHHHHHHHHHHHHH!!!!! Not sure, I'm ready to subject the list to that yet, but if there is a consensus on the list to see the demo, I'll provide the other half, it would have to be a desktop though because I haven't been able to get the sound working on the laptop (ok I haven't tried every combination).

1 0

RE: Shared teleconferencing in Linux
by Brian Kelsay 14 Oct '04

14 Oct '04

If GnomeMeeting is on Knoppix, then I have it on my laptop, otherwise I could apt-get it real quick. I know my usb webcam and sound works. I'd have to bring some external speakers though, because the built-in ones suck. I might even have a headset w/ mic around somewhere that I've never used. If you bring the other half, then we'll do it. Brian Kelsay >>> "Brian Densmore" <> 10/14/04 08:51AM >>> You know doing a gnomemeeting with a pair of linked PCs would be a great demo day event. Maybe even a gnomemeeting meets netmeeting.

1 0

Just saw these quotes/links on Mozilla.org
by Brian Kelsay 14 Oct '04

14 Oct '04

Why Use Firefox? "Beware of spyware. If you can, use the Firefox browser." - USA Today http://www.usatoday.com/tech/news/computersecurity/2004-09-08-zombieinfect_… "Better than Internet Explorer by leaps and bounds." - FORBES http://www.forbes.com/2004/09/29/cx_ah_0929tentech.html?partner=tentech_new… Brian Kelsay

1 0

RE: Shared teleconferencing in Linux
by Brian Densmore 14 Oct '04

14 Oct '04

You know doing a gnomemeeting with a pair of linked PCs would be a great demo day event. Maybe even a gnomemeeting meets netmeeting.

1 0

Re: Shared teleconferencing in Linux
by Brian Kelsay 14 Oct '04

14 Oct '04

>From GnomeMeeting.org FAQ: 2.7. Does it support the T.120 protocol? No, T.120 support is not implemented in GnomeMeeting yet. We prefer to focus on videoconferencing features and protocols than to add support for T.120. Moreover, most T.120 features like desktop sharing, or file transfers can be easily achieved using other dedicated tools. That sounds like the whiteboard feature. If you want to remote control the other person's desktop, use rdesktop or vnc. With one of those you could open an editor and type stuff for them to see. GnomeMeeting does support text chat. Brian Kelsay >>> Leo Mauler <webgiant(a)yahoo.com> 10/14/04 05:54AM >>> --- Brian Kelsay <Brian.Kelsay(a)kcc.usda.gov> wrote: > Gnomemeeting is one option. It is supposed to > connect to Net Meeting. I don't know if you get > the shared whiteboard. > > Brian Kelsay Well, if it connects to NetMeeting, then chances are there's some sort of shared chalkboard-like structure. > >>> Leo Mauler <webgiant(a)yahoo.com> 10/12/04 07:13AM > >>> > What I'm wanting here is the ability to type chat, > draw on a shared whiteboard, share photos, and > possibly audio teleconferencing. I'm not looking > for > video teleconferencing but it would be interesting > as > an option. > > I was adjusting Components for a friend with > Windows98 > and saw "NetMeeting". It sounded interesting but > I'd > like to be able to do that with Linux instead, and > presumably things have improved a bit since 1998.

1 0

Re: Re: Re: Re: Help configuring fetchmail
by linux＠bizniche.com 13 Oct '04

13 Oct '04

Jeremy Turner <jeremy(a)linuxwebguy.com> wrote on 10/13/2004, 08:37:16 PM: > On Wed, October 13, 2004 1:26 pm, linux(a)bizniche.com said: > > That sounds exactly like what I want to do. I guess I get confused > > because I often see procmail and exim mentioned in the same > > context...leading me to believe they do the same thing. > > > > So, all I need to add is procmail. Currently, I guess exim sends the > > mail to my Maildir...and now I need to tell it to send to procmail > > instead. I'll read up on procmail and see how it might fit in. > > If you're using Debian, you can 'apt-get install procmail' then create > yourself a ~/.procmailrc file. exim in woody and in sarge is setup to > check for procmail _before_ delivering to maildir, unless you set it up > differently. Basically, if the procmail transport is listed before the > maildir transport, you're okay. I am using debian, but while trying to get it working, I did change the exim conf to use maildir. The related section looks like this: local_delivery: driver = appendfile group = mail mode = 0660 mode_fail_narrower = false envelope_to_add = true return_path_add = true directory=${home}/Maildir maildir_format = true prefix="" Is this the trasport that you mentioned? What does a procmail setup look like? I also see this procmail section in the conf file, but I'm not sure if it's doing anything. procmail_pipe: driver = pipe command = "/usr/bin/procmail" return_path_add delivery_date_add envelope_to_add # check_string = "From " # escape_string = ">From " suffix = "" > Now what should go in your .procmailrc? I used to list all of my mailing > lists by hand, then I found this script: > > http://www.dotfiles.com/files/12/215_.procmailrc > > This procmailrc will attempt to dynamically check for certain headers in > the email and then deliver them into that folder. It works great 99% of > the time. The only problem is that one mailing list uses the email > address of "talk@...." so that mailing list gets put under the 'talk' > folder. KCLUG, however gets put under the 'kclug' folder. > > The drawback is that if SpamAssassin (or your spam solution) doesn't catch > an email and the spam email has a header that _looks like_ it's from a > mailing list, then it creates a new folder to put the mail in. I have a > couple of folders that were created in this way. > > But like I said, 99% good. So, you're using it to filter mail into folders, and the mail is all coming from the same email account, correct? I have fetchmail checking a few different pop3 accounts, and so I could probably filter by the to: address or something, and place them in different folders, as you say. Either way, fetchmail will dump it all into one place and then procmail can filter it. Right? Matt

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

KCLUG