Hi,

Ok, making a little ground on this.

When I remove the Spamhalter Local IP network IP's, (and I also shut off my Antivirus with mail scanning) I'm now getting some headers in some emails.  But, only for SOME LOCAL emails being sent. 

Appears all outside emails received via MarcuryD are not given headers.  These are the one that should be getting checked.

They are all received from my ISP's catch-all pop3 account.

If Spamhalter has been told to "whitelist" entries for an IP or domain name of incoming mail, where is this entry and how do I clear it?

Thanks,

Mark

Hello,

Running Mercuy with spamhalter ver 4.5.

Installed over existing version.

Can access SPAMHALTER from Mercuy32 config menu.

Have Mercury installed on a server and run from another PC.  Mapped drive to Mercury as M:\. 

When installing spamhalter, it installed itself in a spamhalter folder inside the Mercury directory. (so //Mercury/Spamhalter)

Appears spamhalter will not run this way if the spamhalter.dll is not in the root Mercury directory.

So, I copied the .dll and INI files to the root of Mercury.  Basically, I have two versions of daemon.ini and spamhalter.ini and its all screwed up.

My spamhalter database exists in ..Mercury/spamhalter/spamhalter.  Don't ask me how it got there.

My spamhalter does not work.  I can edit all setting from Mercury Config-Spamhalter, however it does not add the X-spamhalter to all my incoming messages, so it is obviously not checking them.

However, if I send an email to the yesspam mailbox, the Mercury core says:   *Job killed by Daemon  Hummm...

So, my question is, during spamhalter install, is it supposed to install all the files in its own "Spamhalter" directory in the Mercury directory, or is it supposed to just put all its files DIRECTLY in the Mercury directory?

I could not even see spamhalter in the Merucry Configuration menu unless some of the config files were put in the root Mercury directory.

So, it got all messed up, and YEP I'm sure I'm partly to blame.  Where is everything supposed to be?

Thanks!

MP

Ok,

Re-installed spamhalter from the server.  Chose default directory c:\mercury.  Said YES to remove spamwall from daemon.ini. Said YES to replace spamhalter.ini file.

I see how it was supposed to install.  The installe put certain files in the root of Mercury and created a spamhalter folder. 

This folder hold the datbase stuff only.

Edited spamhalter.ini to fix paths.  Re-ran Mercury, turned on Spamhalter through Mercury config menu.

Messages received still do not contain X-SPAMWALL header lines.

What am I missing?

DAEMON.INI

 [global daemons]
SpamHalter=M:\spamhalter.dll;spamhalter (M is mapped drive to server from WS as /Mercury)
[Daemon_Config]
SpamHalter=M:\spamhalter.dll;spamhalter

SPAMHALTER.INI

[SpamHalter]
Queue=
Debug=1
BayDebug=0
CleanTime=20
StatRate=1
SpamAddr=yesspam
NoSpamAddr=nospam
HoneyPot=
LocalIP=127.0.0.1/8,192.168.0.0/16
DynamicHost=
Password=password
BlockTag=X-Blocked
VirusTag=attach removed
LogVirWall=0
subject=
tagname=X-SPAMWALL
WhitelistText=Whitelisted
BlockText=Blocked SPAM!
DebugText=Debug -
ProbText=probability -
SpamText=SPAM detected!
bayDataDir=M:\spamhalter\
logfile=M:\spamhalter\sh~Y~W.LOG
Enabled=1
SpamTrack=1
TrainAlways=1
IgnoreWhite=0
ImageParser=1

[bayDynamic]
bayForcedWrites=1
bayNoSpamBoost=3
bayClasifyMaxTokens=20
bayUnknownProb=40
baySpamProb=80
bayMaxCorrCnt=50
bayOldDays=30
bayExpire=180
bayWhiteOldDays=60
CustomHeaders=

[bayStatic]
bayMaxLength=8192
bayMinTokenLength=3
bayMaxTokenLength=25

Thanks,

MP 

Hi again,

What headers does spamhalter actually put in the mail it processes for whitelist or blacklist?

Thanks,

 MP  

All looks OK.

Did you restart Mercury after enabling Spamhalter?

[quote user="Mrpush"]

What headers does spamhalter actually put in the mail it processes for whitelist or blacklist?

[/quote]

 Sample Here:

[quote]

X-SPAMWALL: Passed through antiSPAM test by Spamhalter 4.5.0.408 on me.com (128)
X-SPAMWALL: probability - 0.0%
X-SPAMWALL: Whitelisted

[/quote]

Hi,

Ya know, I thought I did, but then was not sure, so I just did and those pesky X-SPAMWALL: headers are just NOT there. 

Any other ideas welcome....humm...

Thanks,

Mark 

> DAEMON.INI
>  [global daemons]
> SpamHalter=M:\spamhalter.dll;spamhalter (M is mapped drive to server from WS as /Mercury)
> [Daemon_Config]
> SpamHalter=M:\spamhalter.dll;spamhalter

Mercury running on the server?  If so Spamhalter needs to be mapped to the local drive, not as seen from a workstation.

In addition, what does the Mercury | System messages and the Spamhalter log show.

You ARE testing from an IP outside your Local IP range aren't you?

[quote]LocalIP=127.0.0.1/8,192.168.0.0/16[/quote]

Try removing your LAN range from here.

EDIT: Also, anything sent using SMTP AUTH does not get headers.

Thomas,

Yes, I have Mercury32 installed on a server, and I just run loader.exe from another workstation. 

On that WS I have mapped a drive M to //server1/Mercury directory.  So in Spamhalter INI's it is simply "M:/spamhalter" path.

In System messages, I get a bunch of "FILTER:ListScan rule references empty list", but I believe that is just a bad filter I have set up. 

SH log show some kind of processing for example:

 D 20100318 123029.202 MG00008C Mercury version >= 4.1
D 20100318 123029.218 MG00008C jobfile: \\Server1\MERCURY$\QUEUE\MG00008C.QDF
D 20100318 123029.233 MG00008C spamdir: \\Server2\OUTLOOKPST$\yesspam
D 20100318 123029.265 MG00008C nospamdir: \\Server2\OUTLOOKPST$\nospam
D 20100318 123047.890 MG00008E JF_NOFILTER
D 20100318 123047.984 MG00008D JF_NOFILTER
D 20100318 123757.510 MG00008F Mercury version >= 4.1
D 20100318 123757.510 MG00008F jobfile: \\Server1\MERCURY$\QUEUE\MG00008F.QDF
D 20100318 123757.542 MG00008F spamdir: \\Server2\OUTLOOKPST$\yesspam
D 20100318 123757.557 MG00008F nospamdir: \\Server2\OUTLOOKPST$\nospam
D 20100318 123757.573 MG00008F IP: 192.168.1.16
D 20100318 123757.589 MG00008F > Match ACL
  20100318 123757.604 MG00008F from: <mark@mydomain.com>
  20100318 123757.604 MG00008F  to: p****r@aol.com
D 20100318 123757.620 MG00008F > Local sender
D 20100318 123757.620 MG00008F > for Whitelist
_ 20100318 123757.698 MG00008F Done. (273)
D 20100318 124610.351 MG000091 Mercury version >= 4.1
D 20100318 124610.367 MG000091 jobfile: \\Server1\MERCURY$\QUEUE\MG000091.QDF
D 20100318 124610.382 MG000091 spamdir: \\Server2\OUTLOOKPST$\yesspam
D 20100318 124610.414 MG000091 nospamdir: \\server2\OUTLOOKPST$\nospam

The only difference I see here is the UNC path over the Mapped drive path in my INI's.

I have checked a bunch of emails from other domains coming in, and I see no X-spamwall headers in any of them.

Thanks,

Mark

Dilberts,

I removed the LAN IP range just to test.  No luck there.

 Humm, SMTP auth...you mean SMTP that requires passwords?

Thanks,

MP 

Thomas,

Sorry about that, I did a restart and checked the sys messages and I get this at startup:

Spamhalter 4.5.0.408 Started

mn_win 0.3.0 Started

So it seems ok all the way around but no headers in any incoming e-mails.

Thanks,

MP

Yes, I have Mercury32 installed on a server, and I just run

loader.exe from another workstation. 

On that WS I have mapped a drive M to //server1/Mercury directory. 

So in Spamhalter INI's it is simply "M:/spamhalter" path.

Really bad idea, you WILL lose mail if Mercury ever loses a connection to the mailboxes on the server.  You need to run Mercury off the local hard drive, including the scratch and queue directory so if you ever lose connection to the mail store on the server you will not lose mail.

D 20100318 123757.510 MG00008F jobfile: \\Server1\MERCURY$\QUEUE\MG00008F.QDF
D

20100318 123757.542 MG00008F spamdir: \\Server2\OUTLOOKPST$\yesspam
D

20100318 123757.557 MG00008F nospamdir: \\Server2\OUTLOOKPST$\nospam
D

20100318 123757.573 MG00008F IP: 192.168.1.16
D 20100318 123757.589

MG00008F > Match ACL
  20100318 123757.604 MG00008F from: <mark@mydomain.com>
 

20100318 123757.604 MG00008F  to: p****r@aol.com
D 20100318 123757.620

MG00008F > Local sender
D 20100318 123757.620 MG00008F > for

Whitelist

The headers are not added to this message since it's a local sender and you have setup Spamhalter to exclude/whitelist mail from this IP address.. You might want to post your shexclde.txt and shwhite.txt files for review. 

Spamhalter 4.5.0.408 Started

mn_win 0.3.0 Started

So it seems ok all the way around but no headers in any incoming

e-mails.

I expect that you have some IP address excluded from processing and if all mail comes in via that IP address it will never put any headers in the message.  It's always possible that that Windows mailbox daemon is causing some sort of problem but it does not with my test Mercury-Windows setup.

Thu, 13:52:25    DialogControl daemon loaded successfully
Thu, 13:52:26    Spamhalter 4.5.1.411 started
Thu, 13:52:26    ClamWall 1.4.0.96 started
Thu, 13:52:26    PopFileD (version 1.22.0): startup name: PopFileD param: -p111 -s50 -l -t
Thu, 13:52:26    RcptCheck daemon: Header X-Rcpt-To will be added
Thu, 13:52:26    RcptCheck daemon loaded successfully
Thu, 13:52:26    GrayWall 1.2.0.118 started
Thu, 13:52:26    mn_win 0.3.0 started
Thu, 13:52:26    Program started
 

Thomas,

I haven not intentionally excluded any IP's anywhere in the configs of Mercuy or Spamhalter.  Are you implying that the smaphalter DB has this exclusion in it? (where are you refering to excluding IP's)

I'm not sure where to go from here, I guess I'll try a completely new test install without Windows mailbox daemon etc and see what happens.

Thanks for the help, I'll let you know what I find.

Mark

I haven not intentionally excluded any IP's anywhere in the configs of

Mercuy or Spamhalter.  Are you implying that the smaphalter DB has this

exclusion in it? (where are you refering to excluding IP's)