Skip to main content ↑ ↓
Recent Posts
1
Bug Reports / Re: EMail Replies to the EA forum
Last post by Steeley -
Quote from: tino – multipart should mean that there is both a html and text version or that an additional attachment is sent along with the text.

That was both Spuds and my assumption also... but Pegasus for one won't include plain text in "some" versions of multipart, if you have "rich text" (which is their plain text/html switch) selected. Other aspects of multipart, it will include both.  No idea what, if any of it, is RFC compliant.  But if it works, well, I haven't heard the FBI is investigating RFC standards violations ... yet anyway.

Sometimes I wonder if there is email traffic out their being sent around so intentionally "malformed" they get rejected by every standards-compliant or semi-compliant parser except the clandestine servers they're intended for, so hardly anyone knows about them. An Email "Dark Web" so to speak.  Nah, I'm sure that's just "crazy talk"..  :(
2
Bug Reports / Quote Fail -v1.1.6
Last post by Steeley -
This is to document a "fix" to a quoting problem I discovered on my board.

The issue was trying  to quote an emailed reply to a posted message  - and the posted reply contained an  "&" character that was not escaped (should be "&") and goofed up the xml...

The quote function would stall forever with a "LOADING" banner..

Spuds chased it down.. and the fix is to locate the Xml.template.php file in the theme folder and locate
Code: [Select]

function template_quotefast()
{
	global $context;

	echo '<', '?xml version="1.0" encoding="UTF-8"?', '>
<elk>
	<quote>', cleanXml($context['quote']['xml']), '</quote>
</elk>';
}


..and replace the "quote" line with:

Code: [Select]

        <quote><![CDATA[', cleanXml($context['quote']['xml']), ']]></quote>


That should take care of any  "non-escaped" characters that are posted to your forum from emails that cause subsequent quoting of that post to fail

I suspect Spuds will fold this into later releases..
3
Bug Reports / Re: EMail Replies to the EA forum
Last post by Steeley -
Quote from: Steeley – If it's any consolation, Spuds, if I turn off multipart in Pegasus, it doesn't post in my forum either..  (but it seems to recognize that I tried emailing a reply to the same message that failed earlier and thusly won't post a "properly formatted" reply attempt that follows).

I decided to dig into this a bit further, and dug out the emails in the cache that failed to post  on my server..

(In my best Maxwell Smart voice: ) Would you believe.....

...the reason it didn't post in my forum is because I don't use the same "identity" to log into it, as I use to log in here. So I was merrily switching "identities" in Pegasus as I sent emails to each forum, and "got out of sync". You got at least two emails from an unregistered email account and I got one.
The failure to post had nothing to do with the email format on 1.1.6 at all..  just a slipped nut on my keyboard.  :P

Pegasus and IER, and the parser on 1.1.6 are (and were) fine.

(Note- @Spuds - that should have nothing to do with the quoting thing I PM'd you about, however..)
4
Bug Reports / Re: EMail Replies to the EA forum
Last post by tino -
multipart should mean that there is both a html and text version or that an additional attachment is sent along with the text.

However mail clients don’t tend to follow this and ignore the rfc. I tend to strictly adhere to the RFC and just drop anything outside of that, which can cause issues with some clients. However surprisingly gmail, outlook and the other larger ones tend to conform pretty much.
5
Bug Reports / Re: EMail Replies to the EA forum
Last post by Steeley -
And just a note - the multipart enabled formatting did not change with the IER version update as the multipart disabled format did.

To be honest, I don't know why that multipart enable/disable switch even exists - my guess it's to allow compatibility with various mail-servers, at least during network "standards transitions", but I can't imagine that 95% of their userbase (and that includes me) would understand the need to "customize" their outbound mail for various server implementations, never mind knowing to switch multipart on/off depending on who they're sending to.  Pegasus also has a switch for adding "Attachment information" to multipart messages which I had to disable sometime back - I don't recall the problem it created now, but so far it appears that not having it enabled causes no grief anywhere. Indeed, programming for email is a dark and lonely place to grope around in.
6
Bug Reports / Re: EMail Replies to the EA forum
Last post by Steeley -
Maybe Michael was hoping nobody noticed. Why plead guilty before you've been charged? My post in the community at least amounts to someone saying "I see what you did there.." (For the record, I installed the previous version less than a month ago, and I have no idea what version the malformation began in. And I have little curiosity to start loading earlier versions to find out).

We did both question the RFC compliance of that earlier version of "non-multipart", but at least for me the malformation wasn't as clear until I saw the 'corrected' version.  In hindsight "Content-transfer-encoding: Quoted-printable" and multipart still being  presented with it "off" should have been a clue, but I've not spent much time looking at email headers before, and, perhaps more pertinent, I'm probably getting too old for this stuff.

More and more I can see the progression from "I know what's wrong" to  "Something's not right but I don't know why". and I'm looking forward to the day when I get to "Something's wrong? I didn't notice." Then there will be people to feed and take care of me and I can just watch TV..  ;D  
7
Bug Reports / Re: EMail Replies to the EA forum
Last post by Spuds -
That is nice and simple:smiley:Interesting they make no mention of it in the changelog.

I've added that latest example to my testcase.mbox just so I have it.  Been trying to build a nice set of tests that stress the parser and then check its output  -> forum post.  Overall this has been a good exercise in finding a few odd bugs!
8
Bug Reports / Re: EMail Replies to the EA forum
Last post by Steeley -
Well hells bells...  I went to post a question on the Pegasus Community board about the email formatting with multipart turned off, when I noticed the IERenderer part was updated this past week.

(IERenderer is the Pegasus Mail HTML renderer)

So I downloaded and installed it, and guess what...

NOW emails post to v. 1.1.6 just fine, either way..(multipart on or off...)

And instead of this with multipart deselected (copied from an earlier post):

X-mailer: Pegasus Mail for Windows (4.80.1028)
Content-type: Multipart/Related; boundary="Message-Boundary-12625"
X-PMFLAGS: 570949760 0 1 P68TF1SD.CNM                     

--Message-Boundary-12625
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: Quoted-printable
Content-description: Mail message body

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
          "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html  xmlns=3D"http://www.w3.org/1999/xhtml" xml:lang=3D"en" lang=3D"en">=
<head>
<title></title>
<meta http-equiv=3D"content-type" content=3D"text/html;charset=3Dutf-8"/>
<meta http-equiv=3D"Content-Style-Type" content=3D"text/css"/>
</head>
<body>

{snip}

</body>
</html>

--Message-Boundary-12625--

Instead, now I get this:

Priority: normal
X-mailer: Pegasus Mail for Windows (4.80.1028)
Content-type: text/html; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-PMFLAGS: 34079360 0 1 P6A14D28.CNM                       

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
          "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html  xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title></title>
<meta http-equiv="content-type" content="text/html;charset=utf-8"/>
<meta http-equiv="Content-Style-Type" content="text/css"/>
</head>
<body>

{snip}

</body>
</html>

No boundary markers at all,  just "html"  (settings have "rich text" enabled).

Now THAT looks sane, and it posts just fine using the existing parser in 1.1.6.

It appears the previous version(s) of IR hosed it all up. Pegasus itself hasn't been changed

(Of course, there's no mention of this in the latest version IR release notes, natch..)

In the course of posting that in the Pegasus community, I also asked if there shouldn't be at least SOME plain text in there somewhere?
9
Support / Re: \
Last post by rjm -
Quote from: Spuds – You should be able to make outbound adjustments with edits to the Maillist.Templates  to make it what you need.
Well, the templates section mentions the "template selection list". Hence, I'd believe that the template name is entered elsewhere, where it would be in effect for a specific outbound email class (in this case a "reply-by-email").
According to the header title of the templates section ("Custom bounce email templates"), templates seem only to be related to e.g. error bounce messages.

When I compare to filters resp. parser, a template name is merely optional. They are just simply active on all inbound emails.

Further to templates:
It's the recipient of a reply-by-email (trough notification active) who determines whether or not the posting appears in the email body - via a setting in the account preferences. Despite that, the template (on the admin settings) can indeed determine whether the posting appears e.g. on top of the email? When I inspect the list of template content shortcodes, I would expect a shortcode for "posting content" (to insert on a desired place in the text box "Notification Subject"
10
Support / Re: "Missing Key" error on reply-email
Last post by Spuds -
You should be able to make outbound adjustments with edits to the Maillist.Templates  to make it what you need.

For the inbound email, that is where the Filters and Parsers come in to play.  The idea is to make what gets posted look like a post and not an email.

Filters run first, and you can do simple find and replace.

Parsers run after Filters and there you can define regex code with the goal of finding either the start of a signature or the start of a quoted message and cut the message at that point.  Of course that only works if they post above the original in the reply.

I have been working on about 6 generic parser regex codes that seem to handle a majority of cases.  I'll post those if interested.