As you're using Outlook, you may need to look into setting up the list to allow the top line(s) of the message body to be treated by SmartList as headers for purposes of commands...

There's a bigger issue with Outlook, which is that Outlook defaults to wrapping after 80 characters, and smartlist won't see the remainder of the approved: or x-command: header if it's wrapped. We would commonly exceed 80 characters with a subscribe request, whereupon Outlook would wrap the last "word" which is the whole email address. You'll then get a "X-Diagnostic: Missing argument for subscribe" header in the returned mail to the maintainer's box. Further, the corporate/workgroup (CW) configuration of Outlook does not allow configuration of the number of characters to wrap at. The simple solution for us was to use Outlook Express which is already there on the machines and allows configuration of a 132 character wrap limit. I guess the application to this problem is that if your maintainer's email address or the password is extrordinarily long, you won't be able to send approvals from Outlook.

approved: moderatorsEmail@service.net_password

As far as I know, there should be a space, not an underscore, between the moderator's email address and the password. Anyone have a different view? Merrick Munday