I just met this problem: when a Piwigo is attacked by comment spammers, the administrators receives many emails (see #1033) and the content of the comment is copied into the email. It's fine for "normal" comment, but it's a problem if it's a spam.
For example if the content of the spam comment is about "vi*gra". This keywords is forwarded in the email and receiving email hoster (let's say Yahoo or Hotmail) will quickly consider the sending server as a spam factory and block its IP address. Then no other email will get to the *@yahoo.com or *@hotmail.com users :-(
Fighting against spam on Piwigo is already very painful, we need to avoid forwarding the problem to email providers.
I just met this problem: when a Piwigo is attacked by comment spammers, the administrators receives many emails (see #1033) and the content of the comment is copied into the email. It's fine for "normal" comment, but it's a problem if it's a spam.
For example if the content of the spam comment is about "vi*gra". This keywords is forwarded in the email and receiving email hoster (let's say Yahoo or Hotmail) will quickly consider the sending server as a spam factory and block its IP address. Then no other email will get to the *@yahoo.com or *@hotmail.com users :-(
Fighting against spam on Piwigo is already very painful, we need to avoid forwarding the problem to email providers.
<!-- github-sync-id:456255461 -->
Hey,
Used piwigo a while ago now gonna setup another environment :-)
I'm also looking to get involved in open source development.
My suggestion to solve the above is...
Remove the comment content from the email this will then bypass host spam filters...
Then mayb set a rule based on the comment (name, timestamp) so if someone does spam it only sends one email to admin and also notifys them of potential spam.
I.e. if user has X comments within the last 2mins flag as spam ?
Like I say I'm new to coding/piwigo but need to start somewhere :-)
Hey,
Used piwigo a while ago now gonna setup another environment :-)
I'm also looking to get involved in open source development.
My suggestion to solve the above is...
Remove the comment content from the email this will then bypass host spam filters...
Then mayb set a rule based on the comment (name, timestamp) so if someone does spam it only sends one email to admin and also notifys them of potential spam.
I.e. if user has X comments within the last 2mins flag as spam ?
Like I say I'm new to coding/piwigo but need to start somewhere :-)
<!-- github-comment-id:503131558 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I just met this problem: when a Piwigo is attacked by comment spammers, the administrators receives many emails (see #1033) and the content of the comment is copied into the email. It's fine for "normal" comment, but it's a problem if it's a spam.
For example if the content of the spam comment is about "vi*gra". This keywords is forwarded in the email and receiving email hoster (let's say Yahoo or Hotmail) will quickly consider the sending server as a spam factory and block its IP address. Then no other email will get to the *@yahoo.com or *@hotmail.com users :-(
Fighting against spam on Piwigo is already very painful, we need to avoid forwarding the problem to email providers.
Hey,
Used piwigo a while ago now gonna setup another environment :-)
I'm also looking to get involved in open source development.
My suggestion to solve the above is...
Remove the comment content from the email this will then bypass host spam filters...
Then mayb set a rule based on the comment (name, timestamp) so if someone does spam it only sends one email to admin and also notifys them of potential spam.
I.e. if user has X comments within the last 2mins flag as spam ?
Like I say I'm new to coding/piwigo but need to start somewhere :-)