Sorry, fixed are also both failing subroutine calls in rebuild spamdb!
Thomas
Thomas Eckardt/eck
19.10.2009 01:03
Bitte antworten an
ASSP development mailing list
An
ASSP development mailing list
Kopie
Thema
[Assp-test] fixes in 2.0.1_RC0.5.00
Hi all,
fixed in 2.0.1_RC0.5.00:
-
Hi all,
fixed in 2.0.1_RC0.5.00:
- wrong maillog output for message score reasons
changed:
- If a server replies with 421 or 45x in (or to) the DATA part of the
client, assp stores the messages as OK, if no check was failed.
Now, in this case, assp will log [MessageOK] because the messages w
>COMMENT: remove whole second TR
No, this does not work with lower screen resolution.
Thomas
K Post
18.10.2009 14:48
Bitte antworten an
ASSP development mailing list
An
ASSP development mailing list
Kopie
Thema
[Assp-test] Working Code Change Suggestion: admin interface - maillogtail
d
>[spam found] (URIBLcache: fail, p06.com listed in
clean the URIBLcache.
Thomas
K Post
18.10.2009 22:03
Bitte antworten an
ASSP development mailing list
An
ASSP development mailing list
Kopie
Thema
[Assp-test] Message rejected by black.uribl.com even though it's not a
URIBL provider i
I think I found why the scoring logging isn't working consistently. It's
not that it always shows the first reason - it's that some reasons don't set
$this->{messagereason} in their subs and the pbAdd function uses that
variable with a higher priority than the reason parameter of pbAdd.
Not knowi
>However, it doesn't seem to work if the search string is blank.
MaillogTailBytes (tail bytes) is used if no search string is defined -
this is so for years !?
Thomas
K Post
18.10.2009 15:16
Bitte antworten an
ASSP development mailing list
An
ASSP development mailing list
Kopie
Thema
You are right :-) Thanks for your feedback.
-Original Message-
From: K Post [mailto:nntp.p...@gmail.com]
Sent: Sonntag, 18. Oktober 2009 22:36
To: ASSP development mailing list
Subject: Re: [Assp-test] Working Code Change Suggestion: admin interface -
maillogtail display header for .32/.
I suggest making it blink and have a "LOOK HERE DUMMY" graphic right next to
it. That'll help me find it. 3 years! Nuts. At least I'm not the only
one.
On Sun, Oct 18, 2009 at 4:40 PM, Fritz Borgstedt wrote:
>
> >I guess it just needs to be a little more prominent
>
> Surely you are joking.
ASSP development mailing list
schreibt:
>I wonder how long it's been there
more than 3 years
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this y
>I guess it just needs to be a little more prominent
Surely you are joking.
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart you
ASSP development mailing list
schreibt:
>I would also love to see this feature (shortcut at the bottom to jump
>back to the top).
"Go to Top" is right on the bottom.
--
Come build with us! The BlackBerry(R) Developer
Wow. scratch that last request. Look at the botton. "Go To Top' is right
there! I guess it just needs to be a little more prominent if both of us
missed it.
I wonder how long it's been there, and how much time i've wasted scrolling
all these years...
On Sun, Oct 18, 2009 at 4:25 PM, Marco Rauc
Scoring logging is not working correctly. It appears that as the scoring is
logged in the maillog, the first reason for a score is listed for each
line. Take this for example:
## helo had an ip in it, so we gave it a score of 5
Oct-18-09 16:23:45 msg97425-14632 123.194.130.146 <
eubanksjeliseoat
I would also love to see this feature (shortcut at the bottom to jump back to
the top).
best regards
Marco
-Original Message-
From: K Post [mailto:nntp.p...@gmail.com]
Sent: Sonntag, 18. Oktober 2009 22:10
To: ASSP development mailing list
Subject: Re: [Assp-test] Working Code Change S
I have a single line in my noLogRE file which is:
allowAdminConnectionsFrom
yet these lines are still being logged. Thoughts?
On Thu, Oct 15, 2009 at 9:38 AM, Fritz Borgstedt wrote:
> ASSP development mailing list
> schreibt:
> > I'll post the code
> >if you'd like, just let me know.
>
>
> J
and at the bottom of the log screen, why not put a link to a #top anchor
(needs to be set) so that when we go to the log screen and are brought to
the bottom that we don't have to scroll to the top manually to the top for
searching or other review.
On Sun, Oct 18, 2009 at 9:45 AM, K Post wrote:
I agree with this, this was the statement I was making when I was
pointing out the bug. It is not a bug to reject bare lf, but you must
send perm failure, or you waste resources of the sender.
--
Scott * If you contact me off list replace talklists@ with scott@ *
On Oct 18, 2009, at 3:33 AM,
On Oct 18, 2009, at 3:16 AM, Jean-Pierre van Melis wrote:
>> First, suggestion, turn off the bug in qmail, it is not the place
>> for it, if you want it, look to make a filter in ASSP that does this.
>
> I think you have to get back to the basics...
>
> First of all qmail's behavior is NOT a bug
I just had a legitimate email from Macy's blocked due to failing a URIBL
test. I know the defaults are multi.surbl.org|black.uribl.com but I found
that black.uribl.com is a little to strict for my taste.
(that's the reason I asked for the weighted list of URIBL providers like we
have for the dnsb
ASSP development mailing list
schreibt:
>Although I could download the mentioned 1.6 I was unable to download
>ASSP 2.0.1 RC 0.4.32
4.32 does not contain the modification for reporting "451".
Sorry, but versions before assp.pl 1.6.0 (0.1.20) are buggy and should
not be used.
-
whoops. in the attachment, I didn't change size=2 for the tailbytes field.
it's correct in the sample code of the first post, just not the attachment.
Also, I confirmed the note2 div placement. Just remove the tr and /tr and
put the div just below the note1 dive, before the table. looks much
bet
Also,
the lines:
$h2
are invalid html. There's a tr with no td. I think the div is supposed to
be BEFORE the table to display as the incorrect html code is being rendered
with the note below.
Select files only, if you want to search for mail-files.
In this case hi
Not critical.
I love the idea of being able to search a variable number of log files that
was introduced with .32. However, it doesn't seem to work if the search
string is blank.
If you search for something (search field not blank), it's fine, but if I
search for nothing and only show files and
The LogDateMMDD setting introduced in the latest 1.6.0 builds
formats the date wrongly: it writes, say, 0009.10.18 to the log, whereas
it should obviously be 2009.10.18.
--
Come build with us! The BlackBerry(R) Develop
As I previously posted, the .32 release's introduction of my requested
adjustable maillogtailbytes field isn't optimally formatted. I see tha this
hasn't been corrected in .33 in cvs, so here's my suggested code.
Lines that I changed are not indended and preceeded by a COMMENT line, so
you can qu
In this case 623. instead of showing:
Oct-17-09 21:54:32 HELO Blacklist: 2 in new mail , 623 now in list
it should show
Oct-17-09 21:54:32 HELO Blacklist: 2 in new mail, 623 now in list
Just one space after the word "mail" that should be removed. For both
spamdb and helo blacklist.
Whatever, no
I was actually testing something else and now I see this in my log:
Oct-18-09 13:04:13 63845-11809 [Worker_1] [MissingMX] 65.55.111.155
to: x...@xx.com MX mx1.hotmail.com has wrong IP <>
Oct-18-09 13:04:13 63845-11809 [Worker_1] [MissingMX] 65.55.111.155
to: x...@xx.com [scoring] MX missing: m
Already downloaded it using:
wget -O assp.pl
http://assp.cvs.sourceforge.net/viewvc/*checkout*/assp/assp2/assp.pl
cheers
-Oorspronkelijk bericht-
Van: Jean-Pierre van Melis [mailto:j...@mirmana.com]
Verzonden: zondag 18 oktober 2009 12:46
Aan: 'ASSP development mailing list'
Onderwerp:
I'm using 2.x on my own system and would like to test it.
Although I could download the mentioned 1.6 I was unable to download ASSP 2.0.1
RC 0.4.32 assp.pl
http://www.magicvillage.de/~Fritz_Borgstedt/assp/S05F324B2?WasRead=1
-Oorspronkelijk bericht-
Van: Jean-Pierre van Melis [mailto:j...
I assume, (don't know yet), it's only the logging request that has been granted.
Qmail should refuse the message permanently not temporarily, but refusal itself
is ok. Repairing as you suggested is explicitly mentioned as bad behavior.
JP
-Oorspronkelijk bericht-
Van: Scott Haneda [mail
> First, suggestion, turn off the bug in qmail, it is not the place for it, if
> you want it, look to make a filter in ASSP that does this.
I think you have to get back to the basics...
First of all qmail's behavior is NOT a bug. That message is not according to
specs. Even repairing the messag
31 matches
Mail list logo
