RE: [jira] Commented: (JAMES-530) Add more spool manage commandsto RemoteManager

[Norman Maurer <nm...@byteaction.de>]

Sure .. It will be for all spooling commands. Anyway i whould prefer to
use "key" or to use a "regex". IMO both make no sense at the same time. 

If i have time to complete it i will post it to jira and we all can have
a look again. I think changing the syntax in not so hard if it works ;-)

bye
Norman
 
Am Dienstag, den 13.06.2006, 08:57 -0400 schrieb Noel J. Bergman:
> Without commenting (pro or con, because I haven't had time to think about
> it) on the syntax:
> 
>   REMOVESPOOL <spool> <key>='<regex>'
> 
> I will suggest that a LISTSPOOL or equivalent is vital, so that the admin
> can see what would be removed before actually doing it.  :-)
> 
> 	--- Noel
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
> 
> !EXCUBATOR:1,448eb66d43379520657772!

RE: [jira] Commented: (JAMES-530) Add more spool manage commandstoRemoteManager

["Noel J. Bergman" <no...@devtech.com>]

Norman Maurer wrote:

> > Noel J. Bergman:
> >   REMOVESPOOL <spool> <key>='<regex>'

> i whould prefer touse "key" or to use a "regex".
> IMO both make no sense at the same time.

As far as I can see, I didn't change your syntax.  You had subject=, and I
just generalized that as <key>, since it could be subject, sender,
remotehost, or other attribute, no?

For the message data, what would you think about putting the header in the
regex, so that it is expressed as something like:

  message="^Sender:.*@apache.org$"

rather than having to parse for headers explicitly, as in the earlier case?

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org