[Request] longer (and selectable?) "eaten" log len

[rdigqd]

Hopefully (as it nears one year under discussion) the
"[Request] Option to disable (xxxx: ..." ,thread will
reach the wrap-up and IMPLEMENTATION stage. <G>

Whilst awaiting that day, though, I wanted to throw
another notion into the pot:
--> allowing an "eaten" log longer than three entries

Using SG as a white-list filter mechanism is very,
very useful!! But, more often than not, I don't
get all the 'good guys' added to my "trusted sender"
list before they msgs (at least the first few) get eaten.

If the e-mail id feeding into an SG account is very,
very busy (used in a discussion group, for instance),
the msg volume quickly surpasses the current limit of
3 items logged, and I don't even see notice of the
items missed cuz there fall off the list.

I realize there might be some storage issues (although
far less than in the case of providing a "limbo bucket" to
actually store the non-whitelisted msgs) but having the
option for a log of _at_least_ 10-15 entires sure would
be nice.

Comments??

j.

[josh]

We tried a bunch of different implementations of the eaten message log, and pretty much all of them brought the server down (with far fewer users than we have today) -- except for the current one.

I've added the feature to move the subject tagline to an X-Spamgourmet header, but it's currently not accessible from the web page -- if you want me to activate it for you, post your sg username or shoot me an email.

[rdigqd]

Bummer w.r.t. getting an "eaten" log with more entires

[PITA that increasing the bucket count for holding
"eaten" msg uid/subject info has such a
performance 'hit' on SG]

Wunnerful news w.r.t. the 'X-' header versus subject-line
modification issue!!

Per your kind offer (gosh its been a little while since
I dove into 'beta' work <G>) .... plz enable the 'X-'
capability for my "sejhre-ieee" uid

If it turns out to be a gem of a feature, I may well get
back to you with some of my other ids!

BTW: which implementation approach was taken
-- 'X-' OR subject-line for all of 'trusted'
_and_ 'msg x of y';
-- user ability to specify 'trusted' and/or 'x of y';
-- ???
(or will I just have to find out when I try it <G>)?

j.

[josh]

done -- it's all-or-nothing -- everything goes in one X-Spamgourmet line or in the header. Didn't want to get too ambitious out of the gate because I didn't have enough time to test much complexity.

[rdigqd]

Thanx, josh

Tested it out -- works as advertised!!

PLZ figger out the methodology soon to select for
"headers" or "subject line" for 'trusted' and 'x of y'
individually.

My preference is X-SG headers for 'trusted' and
modified-subject-line for 'x of y'.
That way, msgs from 'trusted' folks are not munged,
and I have a heads-up for 'x of y' ids to refresh the
count , or let it hit zero, as seems appropriate.

FWIW: I could live with the 'x of y' approach being
X-SG headers with, _in_addition_ modified-subject-line
arbitrarily enforced when 'x' is 2 or 1. Ya don't really
need to get that fancy unless you like a challenge and/or
other folks realllllly want it that way.

j.