Realised this morning that my routing plugin was storing recipient verification statistics in the transaction object and I had some snowshoe spammer creating new transactions for each recipient thereby sidestepping my invalid recipient throttling.
So I added the same stats to the connection object and used that instead when calculating the tarpit delay for each invalid recipient.
I do the same with karma (the connection gets slower, and slower, but I *do* believe, b/c I see the same thing
_smf_
I had one session earlier with 248 transactions!
ultimatt
IIRC. my limit plugin prevents that...
I'm less tolerant...
b/c I want them to reconnect, as their "currently spamming IP is probably blacklisted after chatting with karma for 65 seconds
_smf_
I'm not fussed about it - of the 5 recipients that were accepted, one wanted no filtering, so they got the message - the remaining 4 were used to train DSPAM that the message should be considered spam.
aajag.us was already listed in the DBL, so I would have rejected it anyway under normal circumstances.
lnb
ultimatt: hi, would you happen to know a fix when changing spam auto learn options where the error is: DB Error: [1406] Data too long for column 'preference' at row 1 (POST /?_task=settings&_action=plugin.sauserprefs.save) ? I have checked around and have not found one.
ultimatt
sauser is roundcube's spamassassin plugin
lnb
oyes
yes
ultimatt
so I'd start by looking in that plugins config and source
lnb
ok, so you have not run into this issue?
ultimatt
not yet, but I'm not using that plugin
lnb
i am looking in config.inc.php and don't know which value would cause the error. the setting change is simply a number. The default is 12 and I want 5. So how could going from 12 => 5 be too long?
_smf_
lnb: DB Error: data too long is a database schema error. e.g. the database field is specified as a VARCHAR(32) and you're trying to store > 32 characters in it.
So I doubt you'll be able to fix that with configuration changes.
You're going to have to find the plugin forum and ask there instead.
lnb
_smf_: i presume its storing the value in the value column. In that column there are email addresses. This is simply up to a 2 digit value