[TriLUG] help with procmail/postfix

[Tanner Lovelace]

On Tue, 2003-07-29 at 23:33, Tom Woods wrote:
> Yes... mostly!  The TriLUG recipe seems to work fine.  I had trouble with
> the check for duplicates recipe, so I've #'d it out until I can try to
> figure out exactly what it's doing.  Below is my .procmailrc as it stands
> today (much of it directly "borrowed" from your file.)

Heh.  Take a look at the procmailex man page, which, iirc, is where
I got the duplicate message recipe.  But, glad to know it works.

> Also, the backup of 100 messages seems to actually backup 32 messages,
> each in their own file.  Is that right?

Yes, you're right. The comment is wrong.

> One more question...  In the mail class, someone mentioned that they use
> the trilug server as their backup mail server for their domain, I think. 
> Is that something that's allowed?  If so, what needs to be done to set it
> up?

Adding that as a benefit of membership has been discussed and iirc,
the only thing we were waiting on was we wanted to write up an
acceptable use policy.  Unfortunately, myself and the rest of the
SC sort of dropped the ball on that.  :-(  Perhaps we can solicit
suggestions for AUPs from the entire list? :-) 

> Thanks again for your help!  I'm starting to get hooked on this stuff.

It is pretty cool at times. :-)  (Specific comments on recipes below)

[...]
> #################################################################
> # Check for duplicate messages.
> #################################################################
> #:0 Wh: msgid.lock
> #| formail -D 8192 $HOME/logs/msgid.cache

I didn't notice the PATH statement at the top of your .procmailrc.
You may want to make sure that formail is in the default path, or
just add the PATH statement at the top of the file.  If you don't 
add it, I'm not sure what it defaults to, check the man pages.

> # Here's my trilug list recipe. :-)
> # Note that the List-Id line should be all on one line.
> :0 :
> * ^List-Id: Triangle Linux Users Group discussion list <trilug.trilug.org>
> * ^Subject.*\[TriLUG
> $MAILINGLISTDIR/TriLUG

Cool.  Note that on some of my new .procmailrc recipes (the one I showed
you was the oldest I have) I've started putting wildcards (.*) in the
List-Id line since it can change if mailman is updated.

[...]
> 
> # Catch spam :-)
> :0:
> * ^X-Spam-Status: Yes
> $MAILINGLISTDIR/Spam
> 
> :0:
> * ^X-Spam-Flag: YES
> $MAILINGLISTDIR/Spam

Now here you get into a somewhat personal area.  I personally prefer to
catch spam at the top of my .procmailrc so that mailing list spam never 
makes it to the mailing list folders.  Other people I know prefer to do
it the way you set it up where all mailing list mail, even spam, gets
put in the mailing list folder before the spam filtering happens.
Whichever way you do it, it really doesn't matter, but just be aware
that the .procmailrc file is parsed from top to bottom and that 
recipes at the top will take precedence over those at the bottom.

Overall, it looks good. :-)

Cheers,
Tanner
-- 
Tanner Lovelace | lovelace(at)wayfarer.org | http://wtl.wayfarer.org/
--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--
GPG Fingerprint = A66C 8660 924F 5F8C 71DA  BDD0 CE09 4F8E DE76 39D4
GPG Key can be found at http://wtl.wayfarer.org/lovelace.gpg.asc
--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--
<refrain>
1. Creativity and innovation always builds on the past.
2. The past always tries to control the creativity that builds upon it.
3. Free societies enable the future by limiting this power of the past.
4. Ours is less and less a free society.
</refrain>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://www.trilug.org/pipermail/trilug/attachments/20030730/b1205f41/attachment.pgp>