[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Notice: in file [ROOT]/includes/session.php on line 2208: Array to string conversion
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4688: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4690: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4691: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4692: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
Poco Forums • View topic - Check email against DNSBLs (DNS blacklists)

Check email against DNSBLs (DNS blacklists)

Scripting questions and ideas

Moderators: Eric, Tomas, robin, Michael

Waiting for a spam

Postby muncher1 » Mon Dec 20, 2004 8:54 am

Added ver 1.16 and now running debug it pops up a little window that says: "The DNSBL script should only be run on incoming messages or manually only." I'll miss the debug run since if everything clears the debug then the only messages is a #timeout error at the close.

In the setup script the timeout was left blank. I'll wait for a spam email now and see what happens.

By the way so far its hitting 100%. I've got 12,272 junk words and 3,645 good words so everything should be tuned up by now.

Thx,
Chris
muncher1
Poco Tourist
 
Posts: 27
Joined: Sun Dec 19, 2004 2:23 pm

Getting the "must run message" when Poco starts up

Postby muncher1 » Mon Dec 20, 2004 9:07 am

Mat,

When starting Poco for the first time after completely exiting the program when it goes to check mail the popup message about running the DNSBL runs which is the same message stated in the previous post. If I tell Poco to check mail again it doesn't pop up.

If I change the tinmeout from having nothing to any number when restarting Poco the message about running the script reappears.

Chris
muncher1
Poco Tourist
 
Posts: 27
Joined: Sun Dec 19, 2004 2:23 pm

Postby Hogyt » Mon Dec 20, 2004 9:12 am

My mistake, i said that timeout wouldn't work but it still works in the script, it just isn't passed to nslook.exe so you still need to set a value for it (i use 4). What could happen is that nslook.exe keeps on running in the background and you end up with 100's of nslook processes running but more likely nslook has some built-in timeout value.

So, set the timeout to some value (eg. 4) and i'll add an error message if it isn't set and explain better what is going on in the first post.
Mat
Hogyt
Poco Enthusiast
 
Posts: 241
Joined: Thu Jul 29, 2004 11:22 am
Location: England

Re: Getting the "must run message" when Poco start

Postby Hogyt » Mon Dec 20, 2004 9:14 am

muncher1 wrote:If I change the tinmeout from having nothing to any number when restarting Poco the message about running the script reappears.

So timeout is set, and you restart PocoMail then is it an automatic mail check or a manual check that gives the error? Is the script set to run as an incoming filter?
Mat
Hogyt
Poco Enthusiast
 
Posts: 241
Joined: Thu Jul 29, 2004 11:22 am
Location: England

Set to run as incoming filter, Yes!

Postby muncher1 » Mon Dec 20, 2004 9:20 am

Yes it is set to run as an incoming filter. Changed the timeout to 4 and still the pop up message appears when program is restarted. I do have Poco set to automatically check mail on startup. The pop up message is coming up before Poco has a chance to get the mail, if any.

Took the auto check mail on startup off and when Poco restarts the message is still popping up even though mail isn't being checked.

Chris
muncher1
Poco Tourist
 
Posts: 27
Joined: Sun Dec 19, 2004 2:23 pm

Postby Hogyt » Mon Dec 20, 2004 9:43 am

Can you try v1.17? I don't think it's fixed but it should say #PocoScriptMode = some number in that popup and if you say the number it may help track it down. Thanks!
Mat
Hogyt
Poco Enthusiast
 
Posts: 241
Joined: Thu Jul 29, 2004 11:22 am
Location: England

V 1.17 response

Postby muncher1 » Mon Dec 20, 2004 9:51 am

Comes up with:

#PocoScriptMode = 20

---------

Chris
muncher1
Poco Tourist
 
Posts: 27
Joined: Sun Dec 19, 2004 2:23 pm

Postby Hogyt » Mon Dec 20, 2004 9:58 am

Do you have an OnStartup event that is running the script? If so, remove that and the message shouldn't appear.
Mat
Hogyt
Poco Enthusiast
 
Posts: 241
Joined: Thu Jul 29, 2004 11:22 am
Location: England

That was it..........Events had checked DNSBL in Startup.

Postby muncher1 » Mon Dec 20, 2004 10:26 am

Went through al the settings and under "tools", "events", "startup" was checked "run Script: DNSBL"

Unchecked the box, restarted Poco and it DIDN'T show up. I feel so stupid.

Now to figure out how to send the junkmail to an invisible junk mailbox that I can toggle on and off visually.

Thx for all the help. Got something accomplished today.

Chris
muncher1
Poco Tourist
 
Posts: 27
Joined: Sun Dec 19, 2004 2:23 pm

Postby Hogyt » Mon Dec 20, 2004 10:42 am

It's no problem, thank you for finding bugs in it. There is one more update to come in the next few minutes then i'll be happy with it.

Thanks again!
Mat
Hogyt
Poco Enthusiast
 
Posts: 241
Joined: Thu Jul 29, 2004 11:22 am
Location: England

Postby Hogyt » Mon Dec 20, 2004 10:57 am

Updated to v1.18. Temporary files (which are created when the script runs to store the results of the DNSBL tests) are cleaned when the script is run as well as when it finishes. I've slightly changed how the timeout works so if you get lots of timeouts increase the value in the "Setup Script" screen.

There have been quite a few changes today to get it to work with Win 95, 98 and ME so if anyone notices a problem please post! :D
Mat
Hogyt
Poco Enthusiast
 
Posts: 241
Joined: Thu Jul 29, 2004 11:22 am
Location: England

Thanks Mat!

Postby muncher1 » Mon Dec 20, 2004 11:01 am

Mat,

Thx for spending so much time on this today. You did make it possible to run on a lot of other systems besides XP. That in itself is a pretty good accomplishment for one day.

I've added ver 1.18 and had no problems.

So far the filtering is showing 100% success with 11 emails blocked.

Chris
muncher1
Poco Tourist
 
Posts: 27
Joined: Sun Dec 19, 2004 2:23 pm

Postby Hogyt » Tue Dec 21, 2004 3:18 am

I'm glad its working well for you!

Updated to v1.19. This is the last planned update (unless any bugs are found). See the first post for the updated script.

Two changes, the first is that the version number of the script is added to the X-Poco-Spam-DNSBL header (for debugging).

The second change requires a bit of explaining. When the script runs it calls nslookup (or nslook) and then it waits around for it to create some short files in the temp folder that holds the DNSBL result (these temp files are cleared up by the script). If the script timed out there was a small (probably didn't happen in practice) chance that nslookup/nslook finished during a subsequent email check and overwrote the result for that email check with a previous result. Now a random number is added to the temporary filename so that a previous result cannot interfere with the current result.

Ok so you probably didn't want to know that but anyway thats the change ;-)

Over the last couple of updates the timeout option has been fiddled around with. It should now approximately give a time in seconds after which the script will give up waiting for nslookup to finish (it's not exactly in seconds but thats a rough guide). 1 is probably too small a value, so 2 or above is recommended (i use 4 but it depends on your connection).

Thanks to everyone that has helped with the development of the script and keep on posting bugs! :lol:
Mat
Hogyt
Poco Enthusiast
 
Posts: 241
Joined: Thu Jul 29, 2004 11:22 am
Location: England

v1.19 tested

Postby muncher1 » Tue Dec 21, 2004 5:24 am

Mat,

Tested v1.19 and it worked fine. The debug was nice to use. I set the timeout at 25 and it worked fine.

Chris
muncher1
Poco Tourist
 
Posts: 27
Joined: Sun Dec 19, 2004 2:23 pm

Postby mrQQ » Thu Oct 13, 2005 7:16 am

hey,

does anyone know why this script detected 127.0.0.1 for these headers?

Code: Select all
Received: from localhost (localhost [127.0.0.1])
        by mx.kis.lt (postfix) with ESMTP id D437F20F0A9
        for <XXX>; Thu, 13 Oct 2005 22:08:55 +0300 (EEST)
Received: from mx.kis.lt ([127.0.0.1])
        by localhost (mx [127.0.0.1]) (amavisd-new, port 10024) with LMTP
        id 21411-01-89 for <XXX>;
        Thu, 13 Oct 2005 22:08:54 +0300 (EEST)
Received: from watcher.cs.microlink.lt (watcher.cs.microlink.lt [213.197.128.84])
        by mx.kis.lt (postfix) with SMTP id 6DFBC20E6D7
        for <XXX>; Thu, 13 Oct 2005 22:08:53 +0300 (EEST)
Received: (qmail 9382 invoked from network); 13 Oct 2005 19:08:48 -0000
Received: from axis.tdd.lt (213.197.128.94)
  by watcher.cs.microlink.lt with SMTP; 13 Oct 2005 19:08:48 -0000
Received: from whycertainly.net ([222.65.63.179])
        by axis.tdd.lt (8.12.8p1/8.11.6) with SMTP id j9DJ8W7l090166;
        Thu, 13 Oct 2005 22:08:44 +0300 (EEST)
        (envelope-from strawveri(at)whycertainly.net)
Posted-Date: Thu, 13 Oct 2005 22:08:32 +0300 (EEST)


shouldnt it take the very last Received: header, cause that's the first sender?

~ masked email address ... Eric ~
mrQQ
Frequent Visitor
 
Posts: 66
Joined: Wed Feb 09, 2005 6:03 am

PreviousNext

Return to PocoScript Help and How-To

Who is online

Users browsing this forum: No registered users and 1 guest

cron