hi,
while there haven't been much issues in the last month/years, I now get some spam per day in trans-fr-owner.
Is there something you can do?
<img alt="2017-04-07-spam.PNG" src="/fedora-infrastructure/issue/raw/files/d20a01842691f434db30594029b63be2605134d4b062871a5869da569cb8148c-2017-04-07-spam.PNG" />
thanks for your help
I was going to suggest that you set the list to reject posts from non-members as that usually gets rid of most of these kinds of things, but I see you already have it set to reject them.
@abompard can you take a look? Could there be some issue with the reject for non subscribers on this list?
Metadata Update from @kevin: - Issue tagged with: lists
trans-fr-owner isn't the list address, it's an alias to the list owners, and I don't know if this goes through spam filtering. There's no members-only filtering since it's not the actual list posting address, but I'll check the spam filtering.
trans-fr-owner
I don't receive spam anymore, have do done something?
I take the opportunity to discuss few related question:
It's up to you if you want to confirm/validate subscriptions. Most lists don't bother and just let anyone who wants to subscribe do so.
I'll leave the rest of those questions for @abompard
Hmm, you shouldn't receive two emails when you validate a subscription. That may be a bug.
As far as links are concerned, it's a known missing feature. Mailman3 is now completely independent from the web interface, but there isn't enough integration between the two at the moment to let Mailman know at which URL the web UI lives, so it can't include a link in the emails.
ok, where are we here? Is there anything further to do, or can we close this out now?
I think we can close it. There is a minor issue that makes us receive two emails, but I don't know if @abompard wish to keep this bug open or wish to create a new one, nor if it is confirmed by other users.
I'd prefer another ticket for this duplicate emails issue, thanks.
done: https://pagure.io/fedora-infrastructure/issue/6000
Metadata Update from @jibecfed: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.