Curious why no IP is being listed

[kenknight]

Hi all,

I'm not exactly sure if this is a problem or not, but I've been getting probably 20 or more a day of these emails that have no subject, no body and the raw source is pretty scarce. The main thing I was curious about was the fact that there wasn't any IP source information in the headers. Here is the raw source;

Code: Select all

Return-Path: HairRestoration82s@tradeissue.info
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on
   server64.HelpConsulting.local
X-Spam-Level: ******
X-Spam-Status: Yes, score=6.7 required=6.3 tests=EMPTY_MESSAGE,MISSING_DATE,
   MISSING_HEADERS,MISSING_MID,MISSING_SUBJECT,NO_HEADERS_MESSAGE,NO_RECEIVED,
   NO_RELAYS,TVD_SPACE_RATIO shortcircuit=no autolearn=no version=3.2.3
X-Spam-Report:
   *  0.0 MISSING_MID Missing Message-Id: header
   *  0.0 MISSING_DATE Missing Date: header
   * -0.0 NO_RELAYS Informational: mes


What would be the best way to block these types of messages from coming through? I'd really like to block the physical socket but I need some source ip info in order to do that.

Thanks,
Ken

[MerlethePearl]

Set your spam settings...

I just had same problem and think I fixed it...

Set my spam mark as 1 delete at 4...

If your delete threshold is 20 - I think it is too high...
As it takes spam scores and adds them... Spam gets to 3 in a hurray... And 6 easily if 2nd spam score...

But rarely gets to 20 I think...

So 20 is way too high... Not sure why the default is that high... I didn't notice it right away...

[dzekas]

Set your spam settings...

I just had same problem and think I fixed it...

Set my spam mark as 1 delete at 4...

If your delete threshold is 20 - I think it is too high...
As it takes spam scores and adds them... Spam gets to 3 in a hurray... And 6 easily if 2nd spam score...

But rarely gets to 20 I think...

So 20 is way too high... Not sure why the default is that high... I didn't notice it right away...

If you have delete threshold at 4, you are losing emails without noticing it. False positives happen. That's why default delete threshold is that high and your scoring levels point at misconfigured spamassassin.

[Bill48105]

Yeah like dzekas said, be careful setting delete score too low.. You are much better off setting delete high enough false positive is nearly impossible then use rules to move messages to Spam folders based on score. Then the user can decide. I have highest score for delete then a lower yet high score for server rule that is pretty safe, then for users who want more filtering I create user rules with lower score threshold. Then I have daily script I run that deletes emails over 60 days old from each user's spam folder & emails them a report telling them how many messages are in their spam folder & to be sure & check it regularly. VOILA! Cleaner inboxes & safer spam handling with safety net.
Bill

[Conzi]

Then I have daily script I run that deletes emails over 60 days old from each user's spam folder & emails them a report telling them how many messages are in their spam folder & to be sure & check it regularly. VOILA! Cleaner inboxes & safer spam handling with safety net.
Bill

I Bill48105, excuse the intrusion, can you kindly post somewhere this script ?

[glenluo]

My delete score is 20,do not make it too slow,or good emails will be deleted !
I mainly use SPF checking,if SPF checking "fail",just delete,i set the score 20
others,most of settings are set to ''2" score.