e-mail to PM

[Romeos Tune]

It sure seems like I saw it some time ago but........

Is there a hack around that will allow private message text to be sent to e-mail in the pm notification e-mail?

[Tralala]

Edit the 'pmreceived' phrase... add something like this:

----------- Private Message Content ---------------
$message
-------------------------------------------------------

[jimp]

Tralala,

That did not work for me, but you pointed me in the right direction. My pmreceived phrase now looks like (and works, vB 3.5.x):

Dear $touserinfo[username],

You have received a new private message at $vboptions[bbtitle] from $fromusername. Please click here to log in and read it:
$vboptions[bburl]/private.php

All the best,
$vboptions[bbtitle]

_______________
Subject: {$this->pmtext[title]}

{$this->pmtext[message]}

[Tralala]

Good to hear it's working for you. Hmm, not sure why yours had to be different. When I tried inserting $message it also worked just fine. (Others too.)


I ended up removing it though for two reasons... (1) it breaks down the concept of "read receipts," and (2) it also removes an incentive for folks to visit the forum more regularly.

In 3.0 a hack like this made a lot of sense because simply logging in (ie: from the road, on smartphone) to read a PM would reset all the new/unread post markers on the forum for that user, which is annoying. Now that 3.5 has the new database system instead to keep track of what posts are actually new and remain unread, this hack became less important. Folks can still log in quickly, read their PM's, read receipts are still accurate, and not lose their place on the forum.

Still, If there were a way to limit this to certain usergroups I'd be all over it. Mods and admins would appreciate it, I know that...



P.S. You can also customize the email subject text phrase if you like. The title of the PM may be too long to include, but how about the username of the sender:
"New Private Message at $vboptions[bbtitle] from $fromusername"

[jimp]

I think mine was different due to changes across vB 3.0 -> 3.5. (Someone in the thread you linked to said it did not work for vB 3.5.)

[S@NL - BlackBik]

Thanks Jimp, I was just looking for this