We found some spam originating from the server that runs our VB 3.8.
On inspection, the spam was from a request to blog.php.
This is the snippet of interest:
if (!$vbulletin->options['enableemail'])
{
standard_error(fetch_error('emaildisabled'));
}
This says that there is to be some enableemail configuration that is to be respected by blog.php and if that email configuration is turned off, just print a message stating that the email feature has been disabled.
But, it doesn't work as such. We have emailing turned off in vb control panel and we confirmed that we could indeed send email via the blog software recreating the spam we originally detected.
This was the rewrite to fix placed above the snippet above.
standard_error(fetch_error('emaildisabled'));
Is this ignoring of enableemail configuration fixed in 4.* ? If not, can it be looked into?
Thanks,
Tom/Adam/Jim
On inspection, the spam was from a request to blog.php.
This is the snippet of interest:
if (!$vbulletin->options['enableemail'])
{
standard_error(fetch_error('emaildisabled'));
}
This says that there is to be some enableemail configuration that is to be respected by blog.php and if that email configuration is turned off, just print a message stating that the email feature has been disabled.
But, it doesn't work as such. We have emailing turned off in vb control panel and we confirmed that we could indeed send email via the blog software recreating the spam we originally detected.
This was the rewrite to fix placed above the snippet above.
standard_error(fetch_error('emaildisabled'));
Is this ignoring of enableemail configuration fixed in 4.* ? If not, can it be looked into?
Thanks,
Tom/Adam/Jim
Comment