🚀 go-pugleaf

Think I got it
MSGID_FROM_MTA_SHORT
is thrown as a result of there not being a "From" value (as in name).
Thanks


"Ted Tripp" <ttripp@rankexec.com> wrote in message
news:40e40f83$1@newsgroups.borland.com...
> Hi all,
>
> I wrote a notifier application (an event occurs and concerned parties are
> notified via email). I am using Indy 9.x IdSMTP and IdMessage to send an
> email (BCB5).  When testing emails sent to another of my email accounts,
it
> is blocked by Spam Assassin with the messages below.   This notifier
worked
> a couple weeks ago.  I know my Spam Assassin is set aggressively, however
5
> would seem to be the default given to me and so would assume many others
> would be set to 5 as well.  The same email, sent by Outlook, with the same
> config, does not get blocked. The real problem seems to be the  3.3
> MSGID_FROM_MTA_SHORT .  From what I have read, I cannot control the
> Msg-ID--any idea what in Indy would cause this to be trapped by Spam
> Assassin, but not trapped if sent by Outlook?
>
> Content analysis details: (6.0 points, 5.0 required)
> pts rule name description
> ---- ---------------------- ----------------------------------------------
--
> --
> 3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
> 2.5 RCVD_IN_DYNABLOCK RBL: Sent directly from dynamic IP address
> [216.160.57.51 listed in dnsbl.sorbs.net]
> 0.1 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS
> [216.160.57.51 listed in dnsbl.sorbs.net]
>
>