vBMail v2.1.3 Patch Level 4

Bug Fixes:

• Sending a HTML email via WYSIWYG would not display the email correctly in the mail history

Fillip

Sorry, I don't know where you get the "Poor Man's Bounced Email Handler" from?

This product will check for bounced email from users and remove email features from their account, as well as preventing the mails you send via vBMail from being delivered to users who have reached the bounced mail threshold.


Fillip

Hello

Fine mod but... it's not possible to send a picture into the message ?

Merry Xmas, Fred

I've installed this plugin but every page of the plugin gives me this error:

Invalid action. Go back.

How to fix this?

Hi Fred,

I believe using the IMG BBCode will work :)

There's no attachment support at this time, though.

Hi there,

This is most commonly caused by an incorrect upload. Could you please double-check that you have dragged and dropped the contents of the "upload" folder to your forum's folder?


Fillip

I apologize to the vBulletin staff, but I'm at a loss what to do to get some support for their paid product.

What a poorly designed customer support system on their main site... I've tried to post this four times there under their "open ticket" function and it still wouldn't appear anywhere. I even tried a PM to Belazor and it wouldn't accept that... and yes, I was logged in, as would be obvious since it let me download updates to my paid products. It just keeps going back to their home page.

================================================== =====

I simply was trying to upgrade (since I have a lifetime license which I believe is the PRO version since that’s the paid version) from 1.20 installed to vBMail v2.1.3pl4.

I uploaded the new files as recommended..

I made the modification to class_mail.php as recommended..

==================
3. Open ./includes/class_mail.php and find:
$this->smtpSocket = fsockopen(($this->secure == 'ssl' ? 'ssl://' : 'tcp://') . $this->smtpHost, $this->smtpPort, $errno, $errstr, 30);

Add above:
static $hook_code = false;
if ($hook_code === false)
{
$hook_code = vBulletinHook::fetch_hook('dbtech_vbmail_smtp_exec _send');
}
if ($hook_code)
{
eval($hook_code);
}
=====================

This is all I did .. I never got as far as importing the product XML?

Immediately started getting this error which crashed the whole site and I couldn't even get into AdminCP any longer.

tech_vbmail_mailinglist', ); ?>xtracache); } } ?>
Parse error: syntax error, unexpected '}' in /usr/www/apache/htdocs/milsurps/dbtech/vbmail/hooks/global_start.php on line 65

I contacted my Unix support person, since I'm a neophyte with coding. He modified a vBulletin config file so he could get back into our AdminCP and he disabled vBmail plugin which is still showing v1.20 of vB. I then restored all if the old vBMail 1.20 upload files, but I'm afraid to re-enable this thing at all now. My Unix tech recommended I don't do anything else, as he said it might crash the site again.

What I don’t understand is that when I went to do the change in class_mail.php, which appears as an instruction for both v.120 and v2.1.3pl4. my class_mail.php version that existed under v1.20, DID NOT already have that change?

Yet, I was running 1.20 fine and sending newletters to our various advisory groups?

Regardless, I added the suggested code to my native class_mail.php under vBulletin 4.13PL8, so I could do your vBmail v2.1.3pl4 upgrade and that's when our site blew up. It was almost immediately when I made that change, so I’m not sure what that means?

So, I have no idea why 1.20 was working if that change was never made and now I can't use either version of our paid product.

Regardless, I do need to get either the old version or new version running again for our members, so what would you recommend I do?

Thanks for your help?

Regards,
Doug

Hi there,

I'm sorry for the difficulties you're having with our support ticket system. I have investigated our server logs, and the contents of your message was triggering a ModSecurity rule designed to prevent PHP Injection exploits. To read more about ModSecurity, if you're unfamiliar, you can click this link: https://www.modsecurity.org/

I have now disabled the offending rule, so you should experience no further problems posting support tickets @ our site :)

This looks like a corrupted / interrupted upload of the global_start file.

If you PM me with an FTP and AdminCP account over @ www.dragonbyte-tech.com (not here @ vB.org), I'll upgrade the mod for you :)


Fillip

An error message other than just returning to the home page would have been informative, saving all of us a lot of time .. ;)

I will PM you on your site the information ...

Thanks again to Vbulletin.org staff for permitting my post here .. :up:

Regards,
Doug

Unfortunately I don't believe I can control this, as we run cPanel/WHM and I can't find a location to change this.


Fillip

Mod security isn't designed this way. :( It purposely obfuscates failures, leaving impression that everything worked fine from hackers side.

You can't just like that change the way it works. And it really has strange set of rules by default. You need to work really hard on all rules to get it working without problems on site like DBTech's (they had need for many things in posts, like php code, html code, paths to directories (linux or more rarely windows)).

All in all, mod security is more of a hindrance than security. Of course, someone who took really long time maybe can found set of rules that would give additional security without blocking genuine people posting their problems.

But... this is not the place for detailed discussion about mod security.