Weird error messages in my maillog

[Jason Williams]

Hello everyone.

I'm working on a setup where MS is going to be sitting on our Company DMZ,
acting as our mail gateway. I'm using FreeBSD, Sendmail and MS 4.28-5. I
have everything setup and started to do my initial testing.

Everything appears to be working correctly for the most part, but when I
watch the maillog, I see some interesting messages that are being generated
and im not sure why.
Here is a snip:

Mar 22 03:02:38 mailmg sendmail[8162]: i2MB1Jnx008135: SYSERR(root): header
syntax error, line "X-Acme Company-MailScanner-Information: Please contact
the ISP for more information"
Mar 22 03:02:38 mailmg sendmail[8162]: i2MB1Jnx008135: SYSERR(root): header
syntax error, line "X-Acme Company-MailScanner: Found to be clean"
Mar 22 03:02:38 mailmg sendmail[8162]: i2MB1Jnx008135: SYSERR(root): header
syntax error, line "X-Acme Company-MailScanner-SpamScore: s"
Mar 22 03:02:39 mailmg sendmail[8162]: i2MB1Jnx008135:
to=jwilliams at acme.com, ctladdr=<root at mailmg.acme.com> (0/0),
delay=00:01:20, xdelay=00:00:01, mailer=esmtp, pri=120677,
relay=www.acme.com. [xxx.xxx.xxx.xxx], dsn=2.0.0, stat=Sent (i2MB3Sl10893
Message accepted for delivery)
Mar 22 03:02:39 mailmg sendmail[8162]: i2MB1Kuj008142: SYSERR(root): header
syntax error, line "X-Acme Company-MailScanner-Information: Please contact
the ISP for more information"
Mar 22 03:02:39 mailmg sendmail[8162]: i2MB1Kuj008142: SYSERR(root): header
syntax error, line "X-Acme Company-MailScanner: Found to be clean"
Mar 22 03:02:39 mailmg sendmail[8162]: i2MB1Kuj008142: SYSERR(root): header
syntax error, line "X-Acme Company-MailScanner-SpamScore: s"
Mar 22 03:02:39 mailmg sendmail[8162]: i2MB1Kuj008142:
to=jwilliams at acme.com, ctladdr=<root at mailmg.acme.com> (0/0),
delay=00:01:19, xdelay=00:00:00, mailer=esmtp, pri=122395,
relay=www.acme.com. [xxx.xxx.xxx.xxx], dsn=2.0.0, stat=Sent (i2MB3Sl10895
Message accepted for delivery)

When I was tracing steps, it appears that these emails were 'root's emails
being forwarded to my email address.

I'm still going to be looking through logs and my configs to try and figure
out why this is being generated. In the meantime, I thought i'd see if
anyone else has seen this error before.

I appreciate it.

Jason