I was pessimistic; it seems that a BitBounce employee might read this message.

So, BitBounce, if you’re reading this:

1. Please drop aphiso...@gmail.com from your service before they do more harm 
to your reputation — there are thousands of subscribers to this mailing list — 
and until they unsubscribe from all their mailing lists.

2. Please make a donation of $2000 to the Django Software Foundation ($1000 if 
you’re cheap) to offset the trouble you’ve caused up to this point: 
https://www.djangoproject.com/fundraising/.You’re the ones who started 
suggesting money was an appropriate compensation for unsolicited email after 
all :-) and you sent quite a lot to us :-(

Looking forwards to a prompt resolution,


> Le 6 janv. 2019 à 10:35, Aymeric Augustin 
> <aymeric.augus...@polytechnique.org> a écrit :
> [[ I'm adding BitBounce support to this discussion, even though I expect I'll 
> just get one more of their spam — "we'll ignore the spam problem we cause to 
> you until you pay money to us". ]]
>>> On 2 Jan 2019, at 01:39, Daniele Procida <dani...@vurt.org> wrote:
>>>> On Wed, Jan 2, 2019, Daniele Procida <dani...@vurt.org> wrote:
>>>> On Tue, Jan 1, 2019, Daniele Procida <dani...@vurt.org> wrote:
>>>> If it continues to be an issue I will disable their receipt of email
>>>> temporarily. I assume I'll get the auto-replies myself to this message.
>>> One user's email receipt disabled so far; the user has been informed.
>> ... and the other bounces from an email address that isn't even subscribed 
>> to the list!
>> That is extremely annoying.
> It's aggravating.
> Here's one possible solution:
> - we export the individual email addresses of django-developers subscribers — 
> assuming Google Groups allows that
> - we write a script that sends an email to each of them with a unique sender 
> or subject — as far as I can tell these are the only parts of the original 
> email that make it into BitBounce's spam
> - when we get the BitBounce spam, we can map the sender or subject to the 
> original email address, then we unsubscribe it
> We can make tests by writing to aphiso...@gmail.com — the address indirectly 
> subscribed to django-developers that we're trying to remove.
> It seems that BitBounce's spam takes a while to arrive. Yesterday I emailed 
> the list at 23:24 and got the BitBounce spam at 00:00 (CET). Perhaps it's a 
> hourly cron, perhaps just a slow queue.
> Best regards,
> -- 
> Aymeric.

You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to