.forward for Postfix

[pll at lanminds.com]

>>>>> On Thu, 15 Aug 2002, "Rodent" == Rodent of Unusual Size wrote:

  Rodent> One of my packages (an email autoresponder; any of you who
  Rodent> have sent me private mail have seen it ;-) is designed to be
  Rodent> set up as a piped recipient in a .qmail or .forward file.

>>>>> On Thu, 15 Aug 2002, "Marc" == Marc Evans wrote:

  Marc> If your postfix service is setup to use it, the .forward
  Marc> should work just like sendmail's. By default I do believe that
  Marc> .forward is enabled.

Additionally, if you use procmail, you could do away with the 
.forward concept all together, and have the autoresponder invoked 
only to respond to mail which gets 'sorted' into a specific folder.

I do this with vacation all the time:

	# Vacation response for Inbox Messages.
	:0 H
	*
	{
	  :0 Hc
	  *
	  |rcvstore +INBOX
	
	  :0H
	  * 
	  |/usr/bin/vacation -t3d pll
	}

First everything goes to my INBOX, but the 'c' flag tells procmail to 
continue processing the current message, which causes it to be 
matched by the subsequent rule which invokes vacation.

In case it's not obvious, this is a "catch-all" rule.  IOW, it's the 
last rule in my .procmailrc, so if some other rule didn't already 
grab the message, it eventually gets matched by this rule.

I can turn this on/off at will by simply commenting this section out 
and uncommenting the one which says:

	# Catch-all - anything that makes it this far goes to INBOX
	:0 H
	*
	|rcvstore +INBOX

Don't know if that's helpful at all.  FWIW, I use procmail with 
postfix, and have no .forward :)
-- 

Seeya,
Paul
--
	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.

	 If you're not having fun, you're not doing it right!