Hello all, when using macros to define a group of email addresses, is there a delimiter required to string them together?? Or do I need to enclose them in quotes?...as in:
$ALERTGROUP=kevin at domain.com bob at domain.com joe at domain.com
or
$ALERTGROUP="kevin at domain.com bob at domain.com joe at domain.com"
or maybe
$ALERTGROUP=%kevin at domain.com|bob at domain.com|joe at domain.com (pipe delimited)
Which would be correct?...if any
Thanks
Kevin
Note: The information contained in this email and in any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. The recipient should check this email and any attachments for the presence of viruses. Sender accepts no liability for any damages caused by any virus transmitted by this email. If you have received this email in error, please notify us immediately by replying to the message and delete the email from your computer. This e-mail is and any response to it will be unencrypted and, therefore, potentially unsecure. Thank you. NOVA Information Systems, Inc.
On Wed, Mar 30, 2005 at 05:33:45PM -0500, Kevin.Hanrahan at novainfo.com wrote:
Hello all, when using macros to define a group of email addresses, is there a delimiter required to string them together?? Or do I need to enclose them in quotes?...as in:
None of that is needed. This one
$ALERTGROUP=kevin at domain.com bob at domain.com joe at domain.com
will work, assuming you use it like
HOST=*
MAIL $ALERTGROUP COLOR=redComma-delimited also works for some people, but that depends on your "mail" program. Why? Because a definition like this
$ALERTGROUP=kevin at domain.com,bob at domain.com,joe at domain.com
ends up being passed as a command-line parameter to the $MAIL program. So if your mail-program understands a list of recipients separated by commas, it is actually more efficient because Hobbit only needs to run the mail program once with the comma-separated list of recipients.
Regards, Henrik
Comma-delimited also works for some people, but that depends on your "mail" program. Why? Because a definition like this
$ALERTGROUP=kevin at domain.com,bob at domain.com,joe at domain.com
ends up being passed as a command-line parameter to the $MAIL program. So if your mail-program understands a list of recipients separated by commas, it is actually more efficient because Hobbit only needs to run the mail program once with the comma-separated list of recipients.
Does hobbit understand that the comma delimited are actually individual email addresses for the purpose of deciding who to page? ie, say you had another rule which said don't page bob at domain.com, would it know to remove bob at domain.com from the rule?
I'm assuming it doesn't, as otherwise, I assume it would know they are individual addresses and pass them individually to mail....
Regards, Adam
--
Adam Goryachev Website Managers Ph: +61 2 8304 0000 adam at websitemanagers.com.au Fax: +61 2 9345 4396 www.websitemanagers.com.au
On Thu, Mar 31, 2005 at 01:25:34PM +1000, Adam Goryachev wrote:
Comma-delimited also works for some people, but that depends on your "mail" program. Why? Because a definition like this
$ALERTGROUP=kevin at domain.com,bob at domain.com,joe at domain.com
ends up being passed as a command-line parameter to the $MAIL program. So if your mail-program understands a list of recipients separated by commas, it is actually more efficient because Hobbit only needs to run the mail program once with the comma-separated list of recipients.
Does hobbit understand that the comma delimited are actually individual email addresses for the purpose of deciding who to page? ie, say you had another rule which said don't page bob at domain.com, would it know to remove bob at domain.com from the rule?
No, Hobbit doesn't do any parsing of the recipient addresses - they are blindly passed on to the mail- or script-program.
Regards, Henrik
On Thu, Mar 31, 2005 at 05:08:36AM, Henrik Stoerner wrote:
On Wed, Mar 30, 2005 at 05:33:45PM -0500, Kevin.Hanrahan at novainfo.com wrote:
[...] None of that is needed. This one
$ALERTGROUP=kevin at domain.com bob at domain.com joe at domain.com
will work, assuming you use it like
HOST=* MAIL $ALERTGROUP COLOR=redComma-delimited also works for some people, but that depends on your "mail" program. Why? Because a definition like this
$ALERTGROUP=kevin at domain.com,bob at domain.com,joe at domain.com
The only reason I like to use space separated instead of comma separated is such, space separated email addresses only shows itself in the To: header and _not_ all the email addresses.
There could be two reasons why I like to have not all emails in the same To: header.
- If anyone one wants to reply they won't reply to all. Some MUA are makes it easier to do that possible mistake.
- I would not want my oncall email address to be visible to other groups who requested to get email alerts as well.
My two cents.
-- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu "..there are two kinds of people: those who work and those who take the credit...try to be in the first group;...less competition there." - Indira Gandhi
participants (4)
-
henrik＠hswn.dk
-
iqbala-hobbit＠qwestip.net
-
Kevin.Hanrahan＠novainfo.com
-
mailinglists＠websitemanagers.com.au