Skip to main content
Topic: Parsing Unwanted Text in Replies (Read 211 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Parsing Unwanted Text in Replies

EMails sent to users have the following text embedded by default..

<*> To visit Forum on the web, go to:

<*> You can see this message by using this link:

<*> You can go to your first unread message by using this link:

<*> Unsubscribe to this by using this link:;board=40.0

I've attempted to remove it on incoming reply emails, using the parser [Main->Maillist Center-> Parser], but apparently I'm not holding my tongue right. More accurately, I'm not sure what code / format I should be putting in the parser.  Nothing I've tried so far gives me any joy, nor have I found the parser-formatting addressed on the boards here. or in the documentation (did I miss it?).

So, I'll add one more bread crumb..

Also, I'm not sure if I can strip the message ID that follows the above text from the reply text [bba7f55025693216e8ad6ec5f6yaddayaddayadda] with impunity also, or if that will goof stuff up.. If I can strip it without impact, that's ideal..

At the moment I've added signature text instructing members to delete that before replying, but that's not particularly effective, so deleting it automagically on receipt is the more elegant solution.

Can someone edumicate me, please?

// Deep inside every dilemma lies a solution that involves explosives //

Re: Parsing Unwanted Text in Replies

Reply #1
I'd recommend using filters for that, the parsers are to try and "cut" the original message form the reply and all of the above is long after where it should have cut.  Then again you may want the reply so really your choice.  

As an example of a filter, which without testing could also work as a parser, is the following regex

Code: [Select]
~\<\*\>\s+To visit .*? on the web, go to:.*\[url\]http:\/\/www.*?.com\/\[\/url\]~si
with a replacement of nothing would remove that one line (filter) and if used as a parser it *should* cut the message at that point as well.   Give that a try.
Be safe, Be kind, Happy Programing

Re: Parsing Unwanted Text in Replies

Reply #2
Thanks for the reply, and the suggestion Spuds .. I learned a little bit more about regex

Actually, the text on my board (and this forum also, so I passed this to the admins), comes through starting with... 
Posting Information: 
yadda yadda

So, "standard" search string in the parser = "Posting Information: "

Finally figured out why nothing I tried worked...

No.. there is not a space after the colon in the reply email text.....  [fap]
// Deep inside every dilemma lies a solution that involves explosives //