On 29 Oct 2015, at 2:21pm, Adam Devita wrote:
> Question: Is it possible for the admin to easily backup the list,
> bisect it, and test for spam?
> That technique should identify the offending address in
> log2(N-Users-Subscribed) attempts.
You don't even need to mess with the genuine list
Assuming the A*spammer is a basic algo subscribed to the list, and
sending to any sender in a reasonably short time after posting;
Question: Is it possible for the admin to easily backup the list,
bisect it, and test for spam?
That technique should identify the offending address in
On Wed, Oct 28, 2015 at 6:52 PM, General Discussion of SQLite Database <
sqlite-users at mailinglists.sqlite.org> wrote:
> Effective immediately, the sender email address for mailing list posts
> will be elided. All replies must go back to the mailing list itself.
>
Please reconsider. Not
I think I received about four, which I removed in a couple of seconds.
Obviously it is a problem, but I don't think it calls for a change that
makes it impossible to see the sender of each message. I always open
messages from the SqLite developers sort of by default, for instance,
which I can
On 2015-10-28 10:34 PM, SQLite mailing list wrote:
> On 10/28/15, SQLite mailing list
> wrote:
>> This is ridiculous. I know how to handle spam. I can do nothing
>> about not knowing who sent these emails.
>>
> One thing you could do is add a signature line, to tell the rest of us
> who you
Yeah. Let's not admit defeat to a lone a**hole. My spam filter is bored
anyway -- let's give it something to do.
Eric
Sent from my iPhone
> On Oct 28, 2015, at 19:12, SQLite mailing list mailinglists.sqlite.org> wrote:
>
> I agree. This cure is worse than the disease.
>
> At least for
This really is awful and unworkable. There a re a few options
1. maintain things as they are now - and everyone has to add a
signature line and we need to open every message to see who has sent
it. There are some posters I make a point of reading and just seeing
their name in a mail header makes
On Wed, Oct 28, 2015 at 9:08 PM, SQLite
wrote:
>
> On 28 Oct 2015, at 7:36pm, General Discussion of SQLite Database
> wrote:
>
>> Has anybody received email from Alexa since the policy change? I have
>> not
>
> Nor me. I reliably got one for every post I made for about a week before the
On 28 Oct 2015, at 7:36pm, General Discussion of SQLite Database wrote:
> Has anybody received email from Alexa since the policy change? I have not
Nor me. I reliably got one for every post I made for about a week before the
change.
Simon.
Actually looking at this thread (in gmail) since the policy change is
a very retrograde step - all messages are displayed as from SQLite.
There are numerous scenarios where I want to see the name of the
sender (not necessarily the email address) so that I can pick and
choose which messages I
Is this over-reacting a bit. I have had one email from alexa (about
3/4 weeks ago). If it starts to become a real problem then do
something about it - until then I would think we all have more
important things to worry about.
Paul
www.sandersonforensics.com
skype: r3scue193
twitter:
On 28.10.2015 18:52, General Discussion of SQLite Database wrote:
> Hence, we have token the radical approach of denying the sender email
> address to*everyone*.
Could you preserve the sender's name in the from header instead of
substituting the generic "General Discussion of SQLite Database"?
>
> Could you preserve the sender's name in the from header instead of
> substituting the generic "General Discussion of SQLite Database"?
>
> This would make it possible to automatically highlight messages by
> author, i.e. the SQLite dev team.
I second that request!
--
Bill Drago
Staff
On 28 Oct 2015, at 5:52pm, General Discussion of SQLite Database wrote:
> All replies must go back to the mailing list itself.
Erm ... just a warning from an experienced mailadmin. If you do this exactly
the way you described they can trigger an endless loop of spam just by
subscribing
> Has anybody received email from Alexa since the policy change? I have
> not
I have never received any ... presumably Alexa's MTA (s if more than one) is
blacklisted ...
On 10/28/15, SQLite mailing list
wrote:
>
> This is ridiculous. I know how to handle spam. I can do nothing
> about not knowing who sent these emails.
>
One thing you could do is add a signature line, to tell the rest of us
who you are :-)
--
D. Richard Hipp
drh at sqlite.org
I agree. This cure is worse than the disease.
At least for now (from the 2 I got) the Alexa sender address was constant and
can be blacklisted. Regardless of how Alexa got our email addresses, they have
them and can send spam like any spammer.
-- Darren Duncan
On 2015-10-28 2:50 PM, SQLite
On 10/28/15, General Discussion of SQLite Database
wrote:
> On 2015-10-28 10:52 AM, General Discussion of SQLite Database wrote:
>> The reason for this change is to combat the "Alexa" spam. For the
>> past few weeks, whenever anybody posts to the mailing list, that
>> person gets a reply from
On Wed, Oct 28, 2015 at 1:46 PM, SQLite <
sqlite-users at mailinglists.sqlite.org> wrote:
> Is this over-reacting a bit. I have had one email from alexa (about
> 3/4 weeks ago). If it starts to become a real problem then do
> something about it - until then I would think we all have more
>
Effective immediately, the sender email address for mailing list posts
will be elided. All replies must go back to the mailing list itself.
The reason for this change is to combat the "Alexa" spam. For the
past few weeks, whenever anybody posts to the mailing list, that
person gets a reply from
On Wed, Oct 28, 2015 at 1:32 PM, General Discussion of SQLite Database <
sqlite-users at mailinglists.sqlite.org> wrote:
> On 2015-10-28 10:52 AM, General Discussion of SQLite Database wrote:
>
>> The reason for this change is to combat the "Alexa" spam. For the
>> past few weeks, whenever
On Wed, Oct 28, 2015 at 11:22 AM, General Discussion of SQLite Database <
sqlite-users at mailinglists.sqlite.org> wrote:
> On 28.10.2015 18:52, General Discussion of SQLite Database wrote:
>
>> Hence, we have token the radical approach of denying the sender email
>> address to*everyone*.
>>
>
>
On 2015-10-28 10:52 AM, General Discussion of SQLite Database wrote:
> The reason for this change is to combat the "Alexa" spam. For the
> past few weeks, whenever anybody posts to the mailing list, that
> person gets a reply from "Alexa"...
While that was often the case, I recall someone saying
On 2015-10-28 11:25 AM, General Discussion of SQLite Database wrote:
>>
>> Could you preserve the sender's name in the from header instead of
>> substituting the generic "General Discussion of SQLite Database"?
>>
>> This would make it possible to automatically highlight messages by
>> author,
24 matches
Mail list logo
