Qmail
[Top] [All Lists]

Re: qmail srs patch

To: qmail@list.cr.yp.to
Subject: Re: qmail srs patch
From: Charles Cazabon <qmail@discworld.dyndns.org>
Date: Mon, 18 Dec 2006 10:16:23 -0600
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-qmail@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list qmail@list.cr.yp.to
In-reply-to: <4586BAFA.7030700@tpn.com.br>
Mail-followup-to: qmail@list.cr.yp.to
Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
References: <45868F17.4000400@tpn.com.br> <02f601c722b1$5183dae0$7e00a8c0@pawel> <4586BAFA.7030700@tpn.com.br>
User-agent: Mutt/1.5.11
Marcelo Coelho <marcelo@tpn.com.br> wrote:
> 
> Modify:
> | forward to@recipient.com
> 
> To:
> &to@recipient.com
> 
> I will also modify forward and condredirect to use SRS, the next version 
> (qmail-srs-0.3.patch) will work with "| forward" too.
> 
> Anyway, I beleive that forward using &to@recipient.com is better than 
> |forward to@recipient.com, because &to@recipient.com will be handled 
> directly by qmail-local, while |forward will require an external call.

For that specific case, yes.  But |forward is more flexible, in letting you do
things like env variable expansion:

  |forward "$LOCAL"@otherdomain.example.net
  
Charles
-- 
--------------------------------------------------------------------------
Charles Cazabon                               <qmail@discworld.dyndns.org>
Read http://pyropus.ca/personal/writings/12-steps-to-qmail-list-bliss.html
My services include qmail consulting.  See http://pyropus.ca/ for details.
--------------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>