Expected default Spam delivery behavior?

Help! (Home for newbies)
22

That “may” mark the email as spam, that how it reads to me. Its add a header line X-Spam-Status: Yes

Check the mail headers for that line.

Steve

23

Yes I believe that is correct.

Main problem here is that the email is not being delivered to the .spam folder.

24

In your screenshot here:

The line that you have checked, mine says: " ~/Maildir/.Junk/ " which is odd, as another virtual server I have on the system reads same as your screenshot.

25

Ok now thats weird, I just checked it again, and now they both say " ~/Maildir/.Junk/ "

WTH?

See this thread:

26

Yes, because its may not be getting marked as spam, check a email you know is spam, and see if that line is there.
like this line
X-Spam-Status: Yes, score=14.9 required=5.0 tests=DKIMWL_BL,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,MPART_ALT_DIFF,RCVD_IN_PSBL,
RCVD_IN_SBL_CSS,RDNS_NONE,SPF_HELO_NONE,SPF_PASS,URIBL_ABUSE_SURBL,
URIBL_BLOCKED,URIBL_DBL_SPAM autolearn=no autolearn_force=no version=3.4.0

27

This is from a known spam I just received:
(I only changed my server name)

Message-Id: BCFD3667.42300@gmail.com
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on vps1.myserver.com
X-Spam-Flag: YES
X-Spam-Level: ********************
X-Spam-Status: Yes, score=20.2 required=5.0 tests=DKIM_ADSP_CUSTOM_MED,
FORGED_GMAIL_RCVD,FREEMAIL_FROM,HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,
HTML_SINGLET_MANY,MIME_QP_LONG_LINE,NML_ADSP_CUSTOM_MED,
NORDNS_LOW_CONTRAST,PDS_HP_HELO_NORDNS,RCVD_IN_BL_SPAMCOP_NET,
RCVD_IN_MSPIKE_BL,RCVD_IN_MSPIKE_ZBI,RCVD_IN_SBL_CSS,RCVD_IN_XBL,
RDNS_NONE,SPF_HELO_SOFTFAIL,SPF_SOFTFAIL,SPOOFED_FREEMAIL,
SPOOFED_FREEMAIL_NO_RDNS,SPOOF_GMAIL_MID,T_SCC_BODY_TEXT_LINE,
URIBL_ABUSE_SURBL,URIBL_BLOCKED,URIBL_DBL_SPAM,URIBL_SBL
autolearn=spam autolearn_force=no version=3.4.4

28

so that’s good anyway, try adding this and saving, see if it works

image
image737×286 18.8 KB

29

Oh I think I got it working


Both my virtualmin Server Configuration > Spam and Virus Delivery > Destination for Spam both now say:
Write to standard spam Maildir ~/Maildir/.Junk/

Previously it had:
Write to mail file under home directory: ~/Maildir/.spam/

I checked the “Write to standard spam Maildir ~/Maildir/.Junk/” line, and now the server has created a Junk folder in each mailbox and the Spam email tests are going to that folder. The spams emails would not go to the .spam folder when it said .spam previously. No idea why.

I haven’t received any real spam messages in the last hour so I cannot say it is working for sure, but this is a good sign. Well sort of, because I usually would have seen a real spam or two in the last hour. But can’t say for sure
 so I will let it sit for a bit and see what happens.

Thanks for your help tonight, its much appreciated! Fingers crossed this is good to go


30

Great, I thought ~ would not be used as it means home. Your writing to home anyway.

Steve

1 Like
31

Just got a real world spam email and it went to the .junk folder!! Looks like its working, fingers crossed.

Thanks so much for your help, I really appreciate it!

1 Like
32

In case you move on to testing whitelisting, let me warn you that it is not absolute. The SpamAssassin whitelisting rule just subtracts a preset amount from the spam score, so a high-scoring message can still be flagged as spam even when the address it comes from is whitelisted. This is desirable because the address could still be spoofed. But you might need to adjust the score for the whitelist rule.

In particular, if you test with GTUBE, be aware that SpamAssassin has a special rule just for GTUBE that scores it at +1000.

33

Thank you for the heads up


34

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.