From jstk888@outlook.com Wed Jun 24 08:25:13 2026
From: jstk888@outlook.com
To: xymon@xymon.com
Subject: [Xymon] Trouble With Alert Format
Date: Wed, 04 May 2022 11:22:01 +0000
Message-ID: <PU4P216MB11492E50692C46634C8D81A2E2C39@PU4P216MB1149.KORP216.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3462297996513510568=="

--===============3462297996513510568==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello fellow xymoners,

I have recently setup monitoring of the existence of files in a particular di=
rectory, and this seems to be working well. When I setup an alert for a "red"=
 condition, I receive an email message with what appears to be some html tags=
 within it, eg:

        &red <a href=3D"/xymon-cgi/svcstatus.sh?CLIENT=3Dmyserver.com&amp;SEC=
TION=3Dfile:/path/to/myfile">/path/to/myfile</a>
        File is a  - should be file

I have tried setting the alert "FORMAT" to TEXT, PLAIN and SMS, but this does=
n't seem to have any effect. I have also tried sending the alert through the =
html_mail.pl extension scripts, and this doesn't seem to have any effect eith=
er. All I really want is a plain text message, which is easy to read. Does an=
yone know how I could clean this up?

Example Alert Config:
HOST=3Dmyserver.com
        MAIL alerts at someone.who.cares.com REPEAT=3D240m COLOR=3Dred FORMAT=
=3DTEXT

Regards,
Jonathan



--===============3462297996513510568==--


From alt36@cam.ac.uk Wed Jun 24 08:25:13 2026
From: alt36@cam.ac.uk
To: xymon@xymon.com
Subject: [Xymon] Trouble With Alert Format
Date: Wed, 04 May 2022 16:38:43 +0100
Message-ID: <f0428ee3-31b4-a9ef-fa48-d1389bc2227c@cam.ac.uk>
In-Reply-To: =?utf-8?q?=3CPU4P216MB11492E50692C46634C8D81A2E2C39=40PU4P216MB?=
 =?utf-8?q?1149=2EKORP216=2EPROD=2EOUTLOOK=2ECOM=3E?=
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2280298118822951946=="

--===============2280298118822951946==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On 04/05/2022 12:22, Jonathan Bishop wrote:
> Hello fellow xymoners,
>=20
> I have recently setup monitoring of the existence of files in a=20
> particular directory, and this seems to be working well. When I setup an=20
> alert for a "red" condition, I receive an email message with what=20
> appears to be some html tags within it, eg:
>=20
>  ? ? ? &red <a=20
> href=3D"/xymon-cgi/svcstatus.sh?CLIENT=3Dmyserver.com&amp;SECTION=3Dfile:/p=
ath/to/myfile">/path/to/myfile</a>
>  ? ? ? File is a? - should be file
>=20
> I have tried setting the alert "FORMAT" to TEXT, PLAIN and SMS, but this=20
> doesn't seem to have any effect. I have also tried sending the alert=20
> through the html_mail.pl extension scripts, and this doesn't seem to=20
> have any effect either. All I really want is a plain text message, which=20
> is easy to read. Does anyone know how I could clean this up?
>=20
> Example Alert Config:
> HOST=3Dmyserver.com
>  ? ? ? ? MAIL alerts at someone.who.cares.com REPEAT=3D240m COLOR=3Dred FOR=
MAT=3DTEXT

This may be a red herring, but I wonder if you could try changing the=20
order of the different parts of the config line to e.g.

HOST=3Dmyserver.com COLOR=3Dred MAIL alerts at someone.who.cares.com=20
FORMAT=3DTEXT REPEAT=3D240m

Quoting selectively from the stock comments at the top of my alerts.cfg=20
file ....

This file is made up from RULES and RECIPIENTS.
A RULE is a filter made from ... (etc etc)
A RECIPIENT can be a MAIL address, or a SCRIPT. Recipients can also have=20
rules associated with them...

..so for your rule, HOST and COLOR constitute the "RULE", MAIL is the=20
"RECIPIENT", and REPEAT and FORMAT then modify the "RECIPIENT". Your=20
rule mixes together tokens from the RULE and RECIPIENT parts, which=20
might lead to the config rule not being parsed properly.

(Or maybe this is nonsense and the order doesn't matter here; I suspect=20
it would take a careful reading of the source to see how the different=20
tokens in that config file get parsed)

Adam

--===============2280298118822951946==--


From kspringer@innovateteam.com Wed Jun 24 08:25:13 2026
From: kspringer@innovateteam.com
To: xymon@xymon.com
Subject: [Xymon] Trouble With Alert Format
Date: Wed, 04 May 2022 09:59:19 -0600
Message-ID: <388e8eac-435e-fbb0-967f-9dfa6d092724@innovateteam.com>
In-Reply-To: <f0428ee3-31b4-a9ef-fa48-d1389bc2227c@cam.ac.uk>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3298389686532685123=="

--===============3298389686532685123==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Here's some details of how I send email alerts. They're completely=20
customizable.? Hope it helps.
http://www.krisspringer.com/posts/xymon-email-alerts.php

I have since switched to Slack alerts instead of emails, but those are a=20
bit more complex. Let me know if you want instructions for that.

Kris Springer


On 5/4/22 09:38, Adam Thorn wrote:
> On 04/05/2022 12:22, Jonathan Bishop wrote:
>> Hello fellow xymoners,
>>
>> I have recently setup monitoring of the existence of files in a=20
>> particular directory, and this seems to be working well. When I setup=20
>> an alert for a "red" condition, I receive an email message with what=20
>> appears to be some html tags within it, eg:
>>
>> ?? ? ? &red <a=20
>> href=3D"/xymon-cgi/svcstatus.sh?CLIENT=3Dmyserver.com&amp;SECTION=3Dfile:/=
path/to/myfile">/path/to/myfile</a>
>> ?? ? ? File is a? - should be file
>>
>> I have tried setting the alert "FORMAT" to TEXT, PLAIN and SMS, but=20
>> this doesn't seem to have any effect. I have also tried sending the=20
>> alert through the html_mail.pl extension scripts, and this doesn't=20
>> seem to have any effect either. All I really want is a plain text=20
>> message, which is easy to read. Does anyone know how I could clean=20
>> this up?
>>
>> Example Alert Config:
>> HOST=3Dmyserver.com
>> ?? ? ? ? MAIL alerts at someone.who.cares.com REPEAT=3D240m COLOR=3Dred=20
>> FORMAT=3DTEXT
>
> This may be a red herring, but I wonder if you could try changing the=20
> order of the different parts of the config line to e.g.
>
> HOST=3Dmyserver.com COLOR=3Dred MAIL alerts at someone.who.cares.com=20
> FORMAT=3DTEXT REPEAT=3D240m
>
> Quoting selectively from the stock comments at the top of my=20
> alerts.cfg file ....
>
> This file is made up from RULES and RECIPIENTS.
> A RULE is a filter made from ... (etc etc)
> A RECIPIENT can be a MAIL address, or a SCRIPT. Recipients can also=20
> have rules associated with them...
>
> ..so for your rule, HOST and COLOR constitute the "RULE", MAIL is the=20
> "RECIPIENT", and REPEAT and FORMAT then modify the "RECIPIENT". Your=20
> rule mixes together tokens from the RULE and RECIPIENT parts, which=20
> might lead to the config rule not being parsed properly.
>
> (Or maybe this is nonsense and the order doesn't matter here; I=20
> suspect it would take a careful reading of the source to see how the=20
> different tokens in that config file get parsed)
>
> Adam
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon


--===============3298389686532685123==--


From josh@imaginenetworksllc.com Wed Jun 24 08:25:13 2026
From: josh@imaginenetworksllc.com
To: xymon@xymon.com
Subject: [Xymon] Trouble With Alert Format
Date: Wed, 04 May 2022 13:47:32 -0400
Message-ID:
 <CAN9qwJ8aPWJw3Tjb08jNGdPQKmcUwUw7URC8qgfcgk9cpLJ+pw@mail.gmail.com>
In-Reply-To: <388e8eac-435e-fbb0-967f-9dfa6d092724@innovateteam.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1297076808366748710=="

--===============1297076808366748710==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

Kris,

I would love to see Slack alerts if you wouldn't mind.

On Wed, May 4, 2022 at 12:54 PM Kris Springer <kspringer at innovateteam.com>
wrote:

> Here's some details of how I send email alerts. They're completely
> customizable.  Hope it helps.
> http://www.krisspringer.com/posts/xymon-email-alerts.php
>
> I have since switched to Slack alerts instead of emails, but those are a
> bit more complex. Let me know if you want instructions for that.
>
> Kris Springer
>
>
> On 5/4/22 09:38, Adam Thorn wrote:
> > On 04/05/2022 12:22, Jonathan Bishop wrote:
> >> Hello fellow xymoners,
> >>
> >> I have recently setup monitoring of the existence of files in a
> >> particular directory, and this seems to be working well. When I setup
> >> an alert for a "red" condition, I receive an email message with what
> >> appears to be some html tags within it, eg:
> >>
> >>        &red <a
> >> href="/xymon-cgi/svcstatus.sh?CLIENT=myserver.com
> &amp;SECTION=file:/path/to/myfile">/path/to/myfile</a>
> >>        File is a  - should be file
> >>
> >> I have tried setting the alert "FORMAT" to TEXT, PLAIN and SMS, but
> >> this doesn't seem to have any effect. I have also tried sending the
> >> alert through the html_mail.pl extension scripts, and this doesn't
> >> seem to have any effect either. All I really want is a plain text
> >> message, which is easy to read. Does anyone know how I could clean
> >> this up?
> >>
> >> Example Alert Config:
> >> HOST=myserver.com
> >>          MAIL alerts at someone.who.cares.com REPEAT=240m COLOR=red
> >> FORMAT=TEXT
> >
> > This may be a red herring, but I wonder if you could try changing the
> > order of the different parts of the config line to e.g.
> >
> > HOST=myserver.com COLOR=red MAIL alerts at someone.who.cares.com
> > FORMAT=TEXT REPEAT=240m
> >
> > Quoting selectively from the stock comments at the top of my
> > alerts.cfg file ....
> >
> > This file is made up from RULES and RECIPIENTS.
> > A RULE is a filter made from ... (etc etc)
> > A RECIPIENT can be a MAIL address, or a SCRIPT. Recipients can also
> > have rules associated with them...
> >
> > ..so for your rule, HOST and COLOR constitute the "RULE", MAIL is the
> > "RECIPIENT", and REPEAT and FORMAT then modify the "RECIPIENT". Your
> > rule mixes together tokens from the RULE and RECIPIENT parts, which
> > might lead to the config rule not being parsed properly.
> >
> > (Or maybe this is nonsense and the order doesn't matter here; I
> > suspect it would take a careful reading of the source to see how the
> > different tokens in that config file get parsed)
> >
> > Adam
> > _______________________________________________
> > Xymon mailing list
> > Xymon at xymon.com
> > http://lists.xymon.com/mailman/listinfo/xymon
>
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>

--===============1297076808366748710==--


From kspringer@innovateteam.com Wed Jun 24 08:25:13 2026
From: kspringer@innovateteam.com
To: xymon@xymon.com
Subject: [Xymon] Trouble With Alert Format
Date: Thu, 05 May 2022 07:36:45 -0600
Message-ID: <8f5722b3-9b8e-164e-1b33-d7a2555f3097@innovateteam.com>
In-Reply-To:
 <CAN9qwJ8aPWJw3Tjb08jNGdPQKmcUwUw7URC8qgfcgk9cpLJ+pw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6366117104580704820=="

--===============6366117104580704820==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Here's my Slack Alert instructions.
http://www.krisspringer.com/posts/xymon-slack-alerts.php

Kris Springer



On 5/4/22 11:47, Josh Luthman wrote:
> Kris,
>
> I would love to see Slack alerts if you wouldn't mind.
>
> On Wed, May 4, 2022 at 12:54 PM Kris Springer=20
> <kspringer at innovateteam.com> wrote:
>
>     Here's some details of how I send email alerts. They're completely
>     customizable.? Hope it helps.
>     http://www.krisspringer.com/posts/xymon-email-alerts.php
>
>     I have since switched to Slack alerts instead of emails, but those
>     are a
>     bit more complex. Let me know if you want instructions for that.
>
>     Kris Springer
>
>
>     On 5/4/22 09:38, Adam Thorn wrote:
>     > On 04/05/2022 12:22, Jonathan Bishop wrote:
>     >> Hello fellow xymoners,
>     >>
>     >> I have recently setup monitoring of the existence of files in a
>     >> particular directory, and this seems to be working well. When I
>     setup
>     >> an alert for a "red" condition, I receive an email message with
>     what
>     >> appears to be some html tags within it, eg:
>     >>
>     >> ?? ? ? &red <a
>     >> href=3D"/xymon-cgi/svcstatus.sh?CLIENT=3Dmyserver.com
>     <http://myserver.com>&amp;SECTION=3Dfile:/path/to/myfile">/path/to/myfi=
le</a>
>     >> ?? ? ? File is a? - should be file
>     >>
>     >> I have tried setting the alert "FORMAT" to TEXT, PLAIN and SMS,
>     but
>     >> this doesn't seem to have any effect. I have also tried sending
>     the
>     >> alert through the html_mail.pl <http://html_mail.pl> extension
>     scripts, and this doesn't
>     >> seem to have any effect either. All I really want is a plain text
>     >> message, which is easy to read. Does anyone know how I could clean
>     >> this up?
>     >>
>     >> Example Alert Config:
>     >> HOST=3Dmyserver.com <http://myserver.com>
>     >> ?? ? ? ? MAIL alerts at someone.who.cares.com REPEAT=3D240m COLOR=3D=
red
>     >> FORMAT=3DTEXT
>     >
>     > This may be a red herring, but I wonder if you could try
>     changing the
>     > order of the different parts of the config line to e.g.
>     >
>     > HOST=3Dmyserver.com <http://myserver.com> COLOR=3Dred MAIL
>     alerts at someone.who.cares.com
>     > FORMAT=3DTEXT REPEAT=3D240m
>     >
>     > Quoting selectively from the stock comments at the top of my
>     > alerts.cfg file ....
>     >
>     > This file is made up from RULES and RECIPIENTS.
>     > A RULE is a filter made from ... (etc etc)
>     > A RECIPIENT can be a MAIL address, or a SCRIPT. Recipients can also
>     > have rules associated with them...
>     >
>     > ..so for your rule, HOST and COLOR constitute the "RULE", MAIL
>     is the
>     > "RECIPIENT", and REPEAT and FORMAT then modify the "RECIPIENT".
>     Your
>     > rule mixes together tokens from the RULE and RECIPIENT parts, which
>     > might lead to the config rule not being parsed properly.
>     >
>     > (Or maybe this is nonsense and the order doesn't matter here; I
>     > suspect it would take a careful reading of the source to see how
>     the
>     > different tokens in that config file get parsed)
>     >
>     > Adam
>     > _______________________________________________
>     > Xymon mailing list
>     > Xymon at xymon.com
>     > http://lists.xymon.com/mailman/listinfo/xymon
>
>     _______________________________________________
>     Xymon mailing list
>     Xymon at xymon.com
>     http://lists.xymon.com/mailman/listinfo/xymon
>

--===============6366117104580704820==--


From josh@imaginenetworksllc.com Wed Jun 24 08:25:13 2026
From: josh@imaginenetworksllc.com
To: xymon@xymon.com
Subject: [Xymon] Trouble With Alert Format
Date: Thu, 05 May 2022 10:40:23 -0400
Message-ID:
 <CAN9qwJ-h0PpePjA_FGPPY1NtSNi5ohs=nXQyxNZccbUecBhAGw@mail.gmail.com>
In-Reply-To: <8f5722b3-9b8e-164e-1b33-d7a2555f3097@innovateteam.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7870196976279370411=="

--===============7870196976279370411==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Fantastic guide, thank you!

Just a little gotcha: when copy/paste the guide is offering line breaks
which causes issues.  The cat's text:alert line pastes with a line break
and that makes the post look like code instead of a pretty link/a href.
Your shell script should NOT have a line break after the pipe.

On Thu, May 5, 2022 at 9:36 AM Kris Springer <kspringer at innovateteam.com>
wrote:

> Here's my Slack Alert instructions.
> http://www.krisspringer.com/posts/xymon-slack-alerts.php
>
> Kris Springer
>
>
>
>
> On 5/4/22 11:47, Josh Luthman wrote:
>
> Kris,
>
> I would love to see Slack alerts if you wouldn't mind.
>
> On Wed, May 4, 2022 at 12:54 PM Kris Springer <kspringer at innovateteam.co=
m>
> wrote:
>
>> Here's some details of how I send email alerts. They're completely
>> customizable.  Hope it helps.
>> http://www.krisspringer.com/posts/xymon-email-alerts.php
>>
>> I have since switched to Slack alerts instead of emails, but those are a
>> bit more complex. Let me know if you want instructions for that.
>>
>> Kris Springer
>>
>>
>> On 5/4/22 09:38, Adam Thorn wrote:
>> > On 04/05/2022 12:22, Jonathan Bishop wrote:
>> >> Hello fellow xymoners,
>> >>
>> >> I have recently setup monitoring of the existence of files in a
>> >> particular directory, and this seems to be working well. When I setup
>> >> an alert for a "red" condition, I receive an email message with what
>> >> appears to be some html tags within it, eg:
>> >>
>> >>        &red <a
>> >> href=3D"/xymon-cgi/svcstatus.sh?CLIENT=3Dmyserver.com&amp;SECTION=3D
>> file:/path/to/myfile">/path/to/myfile</a>
>> >>        File is a  - should be file
>> >>
>> >> I have tried setting the alert "FORMAT" to TEXT, PLAIN and SMS, but
>> >> this doesn't seem to have any effect. I have also tried sending the
>> >> alert through the html_mail.pl extension scripts, and this doesn't
>> >> seem to have any effect either. All I really want is a plain text
>> >> message, which is easy to read. Does anyone know how I could clean
>> >> this up?
>> >>
>> >> Example Alert Config:
>> >> HOST=3Dmyserver.com
>> >>          MAIL alerts at someone.who.cares.com REPEAT=3D240m COLOR=3Dred
>> >> FORMAT=3DTEXT
>> >
>> > This may be a red herring, but I wonder if you could try changing the
>> > order of the different parts of the config line to e.g.
>> >
>> > HOST=3Dmyserver.com COLOR=3Dred MAIL alerts at someone.who.cares.com
>> > FORMAT=3DTEXT REPEAT=3D240m
>> >
>> > Quoting selectively from the stock comments at the top of my
>> > alerts.cfg file ....
>> >
>> > This file is made up from RULES and RECIPIENTS.
>> > A RULE is a filter made from ... (etc etc)
>> > A RECIPIENT can be a MAIL address, or a SCRIPT. Recipients can also
>> > have rules associated with them...
>> >
>> > ..so for your rule, HOST and COLOR constitute the "RULE", MAIL is the
>> > "RECIPIENT", and REPEAT and FORMAT then modify the "RECIPIENT". Your
>> > rule mixes together tokens from the RULE and RECIPIENT parts, which
>> > might lead to the config rule not being parsed properly.
>> >
>> > (Or maybe this is nonsense and the order doesn't matter here; I
>> > suspect it would take a careful reading of the source to see how the
>> > different tokens in that config file get parsed)
>> >
>> > Adam
>> > _______________________________________________
>> > Xymon mailing list
>> > Xymon at xymon.com
>> > http://lists.xymon.com/mailman/listinfo/xymon
>>
>> _______________________________________________
>> Xymon mailing list
>> Xymon at xymon.com
>> http://lists.xymon.com/mailman/listinfo/xymon
>>
>
>

--===============7870196976279370411==--


From kspringer@innovateteam.com Wed Jun 24 08:25:13 2026
From: kspringer@innovateteam.com
To: xymon@xymon.com
Subject: [Xymon] Trouble With Alert Format
Date: Thu, 05 May 2022 08:54:32 -0600
Message-ID: <7c6786e2-2df5-29f2-8a25-92d7417c3f00@innovateteam.com>
In-Reply-To:
 <CAN9qwJ-h0PpePjA_FGPPY1NtSNi5ohs=nXQyxNZccbUecBhAGw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5356606478202659851=="

--===============5356606478202659851==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Yes, I have had issues with line breaks and spaces when copy/pasting.?=20
Also quotation marks sometimes get screwed up when copying from how-to's=20
with certain fonts.? If things don't work when copy/pasting, always=20
check line breaks, spaces, and quotation marks.

Kris Springer


On 5/5/22 08:40, Josh Luthman wrote:
> Fantastic guide, thank you!
>
> Just a little gotcha: when copy/paste the guide is offering line=20
> breaks which causes issues.? The cat's text:alert line pastes with a=20
> line break and that makes the post look like code instead of a pretty=20
> link/a href.? Your shell script should NOT have a line break after the=20
> pipe.
>
> On Thu, May 5, 2022 at 9:36 AM Kris Springer=20
> <kspringer at innovateteam.com> wrote:
>
>     Here's my Slack Alert instructions.
>     http://www.krisspringer.com/posts/xymon-slack-alerts.php
>
>     Kris Springer
>
>
>
>     On 5/4/22 11:47, Josh Luthman wrote:
>>     Kris,
>>
>>     I would love to see Slack alerts if you wouldn't mind.
>>
>>     On Wed, May 4, 2022 at 12:54 PM Kris Springer
>>     <kspringer at innovateteam.com> wrote:
>>
>>         Here's some details of how I send email alerts. They're
>>         completely
>>         customizable.? Hope it helps.
>>         http://www.krisspringer.com/posts/xymon-email-alerts.php
>>
>>         I have since switched to Slack alerts instead of emails, but
>>         those are a
>>         bit more complex. Let me know if you want instructions for that.
>>
>>         Kris Springer
>>
>>
>>         On 5/4/22 09:38, Adam Thorn wrote:
>>         > On 04/05/2022 12:22, Jonathan Bishop wrote:
>>         >> Hello fellow xymoners,
>>         >>
>>         >> I have recently setup monitoring of the existence of files
>>         in a
>>         >> particular directory, and this seems to be working well.
>>         When I setup
>>         >> an alert for a "red" condition, I receive an email message
>>         with what
>>         >> appears to be some html tags within it, eg:
>>         >>
>>         >> ?? ? ? &red <a
>>         >> href=3D"/xymon-cgi/svcstatus.sh?CLIENT=3Dmyserver.com
>>         <http://myserver.com>&amp;SECTION=3Dfile:/path/to/myfile">/path/to=
/myfile</a>
>>         >> ?? ? ? File is a? - should be file
>>         >>
>>         >> I have tried setting the alert "FORMAT" to TEXT, PLAIN and
>>         SMS, but
>>         >> this doesn't seem to have any effect. I have also tried
>>         sending the
>>         >> alert through the html_mail.pl <http://html_mail.pl>
>>         extension scripts, and this doesn't
>>         >> seem to have any effect either. All I really want is a
>>         plain text
>>         >> message, which is easy to read. Does anyone know how I
>>         could clean
>>         >> this up?
>>         >>
>>         >> Example Alert Config:
>>         >> HOST=3Dmyserver.com <http://myserver.com>
>>         >> ?? ? ? ? MAIL alerts at someone.who.cares.com REPEAT=3D240m
>>         COLOR=3Dred
>>         >> FORMAT=3DTEXT
>>         >
>>         > This may be a red herring, but I wonder if you could try
>>         changing the
>>         > order of the different parts of the config line to e.g.
>>         >
>>         > HOST=3Dmyserver.com <http://myserver.com> COLOR=3Dred MAIL
>>         alerts at someone.who.cares.com
>>         > FORMAT=3DTEXT REPEAT=3D240m
>>         >
>>         > Quoting selectively from the stock comments at the top of my
>>         > alerts.cfg file ....
>>         >
>>         > This file is made up from RULES and RECIPIENTS.
>>         > A RULE is a filter made from ... (etc etc)
>>         > A RECIPIENT can be a MAIL address, or a SCRIPT. Recipients
>>         can also
>>         > have rules associated with them...
>>         >
>>         > ..so for your rule, HOST and COLOR constitute the "RULE",
>>         MAIL is the
>>         > "RECIPIENT", and REPEAT and FORMAT then modify the
>>         "RECIPIENT". Your
>>         > rule mixes together tokens from the RULE and RECIPIENT
>>         parts, which
>>         > might lead to the config rule not being parsed properly.
>>         >
>>         > (Or maybe this is nonsense and the order doesn't matter
>>         here; I
>>         > suspect it would take a careful reading of the source to
>>         see how the
>>         > different tokens in that config file get parsed)
>>         >
>>         > Adam
>>         > _______________________________________________
>>         > Xymon mailing list
>>         > Xymon at xymon.com
>>         > http://lists.xymon.com/mailman/listinfo/xymon
>>
>>         _______________________________________________
>>         Xymon mailing list
>>         Xymon at xymon.com
>>         http://lists.xymon.com/mailman/listinfo/xymon
>>
>

--===============5356606478202659851==--


From jstk888@outlook.com Wed Jun 24 08:25:13 2026
From: jstk888@outlook.com
To: xymon@xymon.com
Subject: [Xymon] Trouble With Alert Format
Date: Fri, 06 May 2022 03:02:55 +0000
Message-ID: <PU4P216MB1149B3680BFC2C2383715DF6E2C29@PU4P216MB1149.KORP216.PROD.OUTLOOK.COM>
In-Reply-To:
 <CAN9qwJ8aPWJw3Tjb08jNGdPQKmcUwUw7URC8qgfcgk9cpLJ+pw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0689374500726226830=="

--===============0689374500726226830==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello all,

Thank you for your responses. You have highlighted to me that firstly, I lack=
ed a proper understanding of how mime types and mime headers work in email, a=
nd secondly that the mail utility on RHEL 7 doesn't support changing mime typ=
es!

To work around the problem, I borrowed Kris's script and used sendmail to sen=
d the email instead. I then set manually the "Content-Type" header to "text/h=
tml". Below is an example of something that works for me on RHEL7.

Another question on xymon alerts... what is the significance of the ampersand=
 in "&red" in an alert message?

Regards,
Jonathan

#!/bin/sh

NOTICE=3D`echo "$BBALPHAMSG" | grep -c INFO`

if [ $RECOVERED -eq 1 ];
then
        echo -e "To: $RCPT\nSubject: $BBSVCNAME on $BBHOSTNAME is Recovered\n=
Content-Type: text/html\n
<html>
<b>HTML HERE</b>
</html>" | sendmail -f monitoring at whocares.com -t
elif [ $NOTICE -gt 0 ];
then
        echo -e "To: $RCPT\nSubject: $BBSVCNAME on $BBHOSTNAME - Notice\nCont=
ent-Type: text/html\n
<html>
<b>HTML HERE</b>
</html>
" | sendmail -f monitoring at whocares.com -t
else
        echo -e "To: $RCPT\nSubject: $BBSVCNAME on $BBHOSTNAME is $BBCOLORLEV=
EL\nContent-Type: text/html\n
<html>
<b>HTML HERE</b>
</html>
" | sendmail -f monitoring at whocares.com. -t
fi



________________________________
From: Xymon <xymon-bounces at xymon.com> on behalf of Josh Luthman <josh at i=
maginenetworksllc.com>
Sent: Thursday, 5 May 2022 5:47 AM
To: Kris Springer <kspringer at innovateteam.com>
Cc: xymon at xymon.com <xymon at xymon.com>
Subject: Re: [Xymon] Trouble With Alert Format

Kris,

I would love to see Slack alerts if you wouldn't mind.

On Wed, May 4, 2022 at 12:54 PM Kris Springer <kspringer at innovateteam.com<=
mailto:kspringer at innovateteam.com>> wrote:
Here's some details of how I send email alerts. They're completely
customizable.  Hope it helps.
http://www.krisspringer.com/posts/xymon-email-alerts.php

I have since switched to Slack alerts instead of emails, but those are a
bit more complex. Let me know if you want instructions for that.

Kris Springer


On 5/4/22 09:38, Adam Thorn wrote:
> On 04/05/2022 12:22, Jonathan Bishop wrote:
>> Hello fellow xymoners,
>>
>> I have recently setup monitoring of the existence of files in a
>> particular directory, and this seems to be working well. When I setup
>> an alert for a "red" condition, I receive an email message with what
>> appears to be some html tags within it, eg:
>>
>>        &red <a
>> href=3D"/xymon-cgi/svcstatus.sh?CLIENT=3Dmyserver.com<http://myserver.com>=
&amp;SECTION=3Dfile:/path/to/myfile">/path/to/myfile</a>
>>        File is a  - should be file
>>
>> I have tried setting the alert "FORMAT" to TEXT, PLAIN and SMS, but
>> this doesn't seem to have any effect. I have also tried sending the
>> alert through the html_mail.pl<http://html_mail.pl> extension scripts, and=
 this doesn't
>> seem to have any effect either. All I really want is a plain text
>> message, which is easy to read. Does anyone know how I could clean
>> this up?
>>
>> Example Alert Config:
>> HOST=3Dmyserver.com<http://myserver.com>
>>          MAIL alerts at someone.who.cares.com<mailto:alerts at someone.who=
.cares.com> REPEAT=3D240m COLOR=3Dred
>> FORMAT=3DTEXT
>
> This may be a red herring, but I wonder if you could try changing the
> order of the different parts of the config line to e.g.
>
> HOST=3Dmyserver.com<http://myserver.com> COLOR=3Dred MAIL alerts at someone=
.who.cares.com<mailto:alerts at someone.who.cares.com>
> FORMAT=3DTEXT REPEAT=3D240m
>
> Quoting selectively from the stock comments at the top of my
> alerts.cfg file ....
>
> This file is made up from RULES and RECIPIENTS.
> A RULE is a filter made from ... (etc etc)
> A RECIPIENT can be a MAIL address, or a SCRIPT. Recipients can also
> have rules associated with them...
>
> ..so for your rule, HOST and COLOR constitute the "RULE", MAIL is the
> "RECIPIENT", and REPEAT and FORMAT then modify the "RECIPIENT". Your
> rule mixes together tokens from the RULE and RECIPIENT parts, which
> might lead to the config rule not being parsed properly.
>
> (Or maybe this is nonsense and the order doesn't matter here; I
> suspect it would take a careful reading of the source to see how the
> different tokens in that config file get parsed)
>
> Adam
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com<mailto:Xymon at xymon.com>
> http://lists.xymon.com/mailman/listinfo/xymon

_______________________________________________
Xymon mailing list
Xymon at xymon.com<mailto:Xymon at xymon.com>
http://lists.xymon.com/mailman/listinfo/xymon

--===============0689374500726226830==--