ElkArte Community

Elk Development => Bug Reports => Topic started by: Steeley on August 03, 2022, 05:00:34 pm

Title: EMail Replies to the EA forum
Post by: Steeley on August 03, 2022, 05:00:34 pm
In the topic "how to "Subscribe to boards and get the full text of the posts on that board"?", in addition to posting a reply directly to the thread,  https://www.elkarte.net/community/index.php?topic=6150.msg43946#msg43946 , I also sent in a (different) reply via email, to the same message as the board-posted reply..

As I start this topic some 45 minutes later it has not appeared, either gone off to bit heaven, or stuck in moderation.

" I shot an arrow into the air, where it's gone I know not where. "  Would someone like to take a look around and see if EA is actually working as intended?
Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 03, 2022, 11:01:53 pm
Of course, a few problems.

First was simply that the site uses Gmail / IMap, but was using the regular credentials.  Looks like the allow unsecure app access was removed at some point so instead had to change to an app password for allowing this site to access the email via IMap.  Of course that also required turning on f2a for the Gmail account and :yawning_face: you get the drift.

So once that was done it did pull in two emails :tada:

One from you that the system complained had no message body (I'm checking why, probably some filter) and one from @rjm which had no key in the message, so of course that is never going to post.
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 04, 2022, 06:50:19 am
Quote from: Spuds – Of course, a few problems.

First was simply that the site uses Gmail / IMap, but was using the regular credentials.  Looks like the allow unsecure app access was removed at some point so instead had to change to an app password for allowing this site to access the email via IMap.  Of course that also required turning on f2a for the Gmail account and :yawning_face: you get the drift.

So once that was done it did pull in two emails :tada:

One from you that the system complained had no message body (I'm checking why, probably some filter) and one from @rjm which had no key in the message, so of course that is never going to post.

I replied via email about 20 minutes ago and....  my guess is you're still unclogging that filter.. as that one didn't show up either..

Or maybe gmail detected my despise of it... ::)
Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 04, 2022, 03:12:58 pm
Think I have this traced down ... now I just need to be sure about the fix, I have something on my local but need to do some more testing.

The problem is caused by Pegasus Mail for Windows (4.80.1028)  presenting the message as Multipart/Related  and the way our parser deals with that.

QuoteThe multipart/related content type is used for compound documents (that is, messages in which the separate body parts are intended to work together to provide the full meaning of the message).

In this case there is only 1 part of that Multipart/Related, and its just a standard Multipart/Alternative.  Multipart/Alternative is also multiple sections but they contain the same message but encoded in different ways, like plain, html, base64, such that the client can present the best one.

Anyway since there is only one section in that Multipart/Related, the parser fails to pull it together so to speak.  Email is truly a dark and lonely place, probably filled with Cobol programmers !
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 04, 2022, 07:54:42 pm
Quote from: Spuds – Think I have this traced down ... now I just need to be sure about the fix, I have something on my local but need to do some more testing.

The problem is caused by Pegasus Mail for Windows (4.80.1028)  presenting the message as Multipart/Related  and the way our parser deals with that.

QuoteThe multipart/related content type is used for compound documents (that is, messages in which the separate body parts are intended to work together to provide the full meaning of the message).

In this case there is only 1 part of that Multipart/Related, and its just a standard Multipart/Alternative.  Multipart/Alternative is also multiple sections but they contain the same message but encoded in different ways, like plain, html, base64, such that the client can present the best one.

Anyway since there is only one section in that Multipart/Related, the parser fails to pull it together so to speak.  Email is truly a dark and lonely place, probably filled with Cobol programmers !


My guess is that the parser is looking for text after the Message Boundary before encountering the Alt-Boundary, and not seeing it, thinking the message is "empty"..

That is...


Content-type: Multipart/Related; boundary="Message-Boundary-13115"
X-PMFLAGS: 570949760 0 1 PRRPJEKN.CNM                      

--Message-Boundary-13115
Content-type: Multipart/Alternative; boundary="Alt-Boundary-9315.904040406"

Nothing here

--Alt-Boundary-9315.904040406 -(Start of Alt message 1)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

Text here

--Alt-Boundary-9315.904040406 - (end of Alt message 1, start of Alt message 2)
Content-type: text/html; charset=US-ASCII
Content-transfer-encoding: 7BIT
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 here

--Alt-Boundary-9315.904040406--(end of alt message 2)

--Message-Boundary-13115-- (End of message)


I think that's RFC1521 compliant, but I could be wrong, and/or my opinion is irrelevant.

I can turn off multipart formatting I suppose, it was good enough back in the 70's.  :D 

FWIW, it works fine with 1.16 on my own server.. (did I mention my distaste for gmail? Why yes, yes I did..)

::)
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 04, 2022, 07:56:05 pm
Well alrighty then, I'll reply to this post in email and see if it works now..

BTW, did I ever mention that I totally despise Google Mail? In fact, gmail address accounts are not permitted on my forum - I see it as the equivalent of having Google Inc. as a lurking member of the forum.

On a "public forum" it's not as big of a concern, I suppose.

OK, so I draw back the bow and yell "incomming"..

-Steeley

Did you exchange, a walk-on part in the war for a lead role in a cage? [~ Pink Floyd: "Wish You Were Here"]

--
Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 04, 2022, 08:09:54 pm
Should be working now, I ran the (2) failed emails again so they should post.

Yes the email is compliant AFAIK, it was just that our parser did not deal with it properly.

Normally when you get a Multipart/Related you will find at least two sections in that boundary.  The first is (normally) a typical Multipart/Alternative section with its own boundaries that include a plain text and html section.  Then, for example, there would be another part of the Multipart/Related such as an image that would used in the first part, and then another section, maybe with another image or whatever.

Anyway the parser was not dealing with only one section, so I put in a fix that should "just work" ... and I'm still looking to see if that was the best idea. 

TLDR :bug:
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 04, 2022, 08:35:59 pm
I see the earlier emailed reply successfully posted after your tweaks.

Just for the record, I have had bounces occur from some email servers if I just send a graphic without any text, which suggests that "not properly recognizing" that Multipart/Related; means combine the parts, not just "pick one" to use, is not uncommon. Tis indeed a dark art.
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 04, 2022, 10:46:35 pm
Well, I replied to this via email earlier - so far that one hasn't shown up.. (nor an even earlier reply to rjm's post.)

Thought I'd try it with multipart turned off, and discovered it was already deselected, so I turned it back on and will reply via email again and see if it works this time.

(looks like I might need a bigger quiver before this gets worked out..) .

-Steeley

Did you exchange, a walk-on part in the war for a lead role in a cage? [~ Pink Floyd: "Wish You Were Here"]

--
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 04, 2022, 11:01:10 pm
Quote from: Steeley – Well, I replied to this via email earlier - so far that one hasn't shown up.. (nor an even earlier reply to rjm's post.)

Thought I'd try it with multipart turned off, and discovered it was already deselected, so I turned it back on and will reply via email again and see if it works this time.

(looks like I might need a bigger quiver before this gets worked out..) .

-Steeley



Did you exchange, a walk-on part in the war for a lead role in a cage? [~ Pink Floyd: "Wish You Were Here"]

--

OK, that worked, yet another inbound to see if  I was responsible for the other two I referred to not posting..
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 05, 2022, 12:43:46 am
OK, Spuds, I've probably junked up your email queue with test emails from an unregistered EA account address, and duplicate email replies to the same post, none of which should post, and they didn't, of course. (Too many things going on simultooneously on my end).
 
The reason for the madness was to try to do an email reply with the multipart turned off and confirm it would still post. Once I solved my rectal/cranial inversion issues I set an email to a post I had never replied to with multipart off and...

Alas, that doesn't appear to post either.  However, I'm not sure what is sent in that situation is RFC compliant.

Here's the pertinent parts...

In-reply-to: <bc6514a0d15122eb072ce12f5c21b918-m43964@elkarte.net>
References: <6151@elkarte.net>, <bc6514a0d15122eb072ce12f5c21b918-m43964@elkarte.net>
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--


If this concerns you I'll work with you further, otherwise I'll just turn multipart back on and we can call it good since that appears to work now..

Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 05, 2022, 02:04:37 am
I'll pull those emails in and see what is happening ....

There are (5) pending in the queue, (2) are easy (email not in DB and expired key) which translates to the key is valid but was not sent to you, and you already used that key, they are like one time passwords, but the admin can override on a fail.

The other (3) I need to pull in as they fail with no message body, which is the parser error ... fun!
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 05, 2022, 02:14:45 am
Quote from: Spuds – I'll pull those emails in and see what is happening ....

There are (5) pending in the queue, (2) are easy (email not in DB and expired key) which translates to the key is valid but was not sent to you, and you already used that key, they are like one time passwords, but the admin can override on a fail.

The other (3) I need to pull in as they fail with no message body, which is the parser error ... fun!

At least two of those 5 are from a non-member addy (I have multiple "Identities" in Pegasus, and was switching back and forth multi-erroring), and at least two are email replies to previously email replied-to posts so those should fail anyway).

Only one (latest send date/time) should be a pure "empty" message body failure, from my EA account addy - and again, I'm not positive that's an RFC compliant format.
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 05, 2022, 02:49:14 am
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).
Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 05, 2022, 03:51:31 am
Took a quick look and its again a parser failure, kind of.

The empty messages, as far as the parser was concerned, were shown as Multipart/Related and in those boundaries are a single HTML message, not Multipart/Alternative, just a single HTML message. 

TBH I'm not sure that is compliant, I thought all emails must contain a text/plain section, but we are talking about email here LOL

Now I had put in a catch for messages missing a plain/text section but containing a text/html section.  The issue is that does not run when that is in the Multipart/Related area only when in the Multipart/Alternative section.    Not sure there is a quick work around for that with the current structure of the parser,  may have to refactor that area.
Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 05, 2022, 04:39:32 am
Well as I did a code :beers: :takeout_box: review, I did an experiment that looks to fix this issue (and the previous), and best of all it removes some code :D

Going way back,  improvements were added to properly (cough) work with Multipart/Related messages.  However some old conditions were left in place that had previously been used to, somewhat, work around/circumvent them. 

So when I come around in the AM I'll do a bit more testing, but right now it kind of looks good, at least with @Steeley email's
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 05, 2022, 06:05:36 am
Hopefully it opened up the acceptance criteria rather than narrowed it to Pegasus 4.80!

Little story: We had a bunch of old Sundstrand low-speed ARINC 429 data loggers that one of our engineers hacked so they would also work on the high-speed 429 buses. Worked great until a few years later when we built the first HF Data Link Radios,. We updated the HF's on a 28 day cycle with new HF Ground Stations as they came on line, and/or changed frequencies. Only they couldn't update in the aircraft, only on the bench for some reason. I found the reason.. the 429 bus had a programming error and was running at "Half-High-speed", in between low-speed and high speed. Our modified data-loggers didn't care, they worked with anything in between 10khz and 100khz. Those that were "compliant with the standards" (low-speed 12-14.5Khz, high speed 100Khz +/- 1%) however, wouldn't work when the bus is running at 50Khz.

I guess as long as the parser will work with  anything coming at it (good bad or ugly), it's all good (and low maintenance to boot). 

Can you shoot the code changes to me that I can plug into the appropriate 1.1.6 php files?

(BTW I just discovered something else with 1.16 that I'll bounce off you a little later - probably via PM.)
Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 06, 2022, 12:22:24 am
Quote from: Steeley – Hopefully it opened up the acceptance criteria rather than narrowed it to Pegasus 4.80!
It should have! ... Found a couple of other bugs but getting "out there" in terms of what the PBE function would expect to get in a reply.   The parser handles a lot of different cases but not all (by design)  TBH I wrote most of that 10 years ago so its showing its patina ;)
Quote from: Steeley – Can you shoot the code changes to me that I can plug into the appropriate 1.1.6 php files?
Yup ... I'll get this all in 1.1.9 and the specific files (I think there are two) should be drop in replacements.

And as a test I released (3) of your reply's back (the ones that the parser used to fail)
Title: Re: EMail Replies to the EA forum
Post by: ahrasis on August 06, 2022, 03:25:08 am
I like.
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 06, 2022, 06:03:11 am
Well alrighty then.  I went up on the board and deleted those three emails to "clean things up".

I'll be looking for the fixes, and hopefully Google doesn't decide in the meantime to implement some new "security/spam/pfishing" Gmail format protocol and try to drive it to the rest of the known universe.

If this posts, you'll know to check your PM for that "other issue" I mentioned.

-Steeley 


Did you exchange, a walk-on part in the war for a lead role in a cage?

[~ Pink Floyd: "Wish You Were Here"]

--
Title: Re: EMail Replies to the EA forum
Post by: rjm on August 06, 2022, 08:38:39 am
Would be an interesting opportunity. In fact, it is easier for me to swap my test forum from 1.1.8 to 1.1.9 instead of swapping to the 2.0 code base. In the latter case, a missing database table is complained about.
However, until now git fetch origin does not result in updates...
Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 06, 2022, 09:56:48 pm
I've been working on, somewhat sporadically, the 1.1.x => 2.0 update script to take care of any DB changes and updates.  Without that it will not "like" a 1.1.x db.

I've been doing more work on the parser and found some more edge cases that I fixed, all were mainly all around malformed email,  headers or body text but there were some ways to deal with those with out to much drama.  All the testing was on 2.0,  so up next it to test those changes on 1.1.x and make sure they work as expected there.

Once that is done, I'll post the updates for folks to test out.
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 07, 2022, 10:33:20 am
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?
Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 07, 2022, 04:04:34 pm
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!
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 07, 2022, 06:05:48 pm
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  
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 07, 2022, 08:39:21 pm
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.
Title: Re: EMail Replies to the EA forum
Post by: tino on August 07, 2022, 10:22:17 pm
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.
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 08, 2022, 05:25:28 am
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..)
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 09, 2022, 07:53:37 am
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"..  :(
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 12, 2022, 05:29:06 pm
Quote from: Spuds –
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!

@Spuds - reply to this so I get an email notification, and I'll throw another email reply at you with yet different formatting to stress-test the parser.. Pegasus has an "Attachment Information" switch that, if enabled, will give you this..

Code: [Select]

X-mailer: Pegasus Mail for Windows (4.80.1028)
X-PMFLAGS: 570949760 0 1 PIMHW5EA.CNM                      


--Message-Boundary-24840
Content-type: Multipart/Alternative; boundary="Alt-Boundary-9241.139177750"

--Alt-Boundary-9241.139177750
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

this is a test with an attachment

--Alt-Boundary-9241.139177750
Content-type: text/html; charset=US-ASCII
Content-transfer-encoding: 7BIT
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="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>

<snipped html>

</body>
</html>

--Alt-Boundary-9241.139177750--

--Message-Boundary-24840
Content-type: text/plain; charset=US-ASCII
Content-disposition: inline
Content-description: Attachment information.

The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.

   ---- File information -----------
     File:  butts.jpg
     Date:  22 Feb 2009, 9:32
     Size:  33794 bytes.
     Type:  JPEG-image

--Message-Boundary-24840
Content-type: Image/JPEG; name="butts.jpg"
Content-disposition: attachment; filename="butts.jpg"
Content-transfer-encoding: BASE64

/9j/4AAQSkZJRgABAQEBLAEsAAD/2wBDAA0JCgsKCA0LCgsODg0PEyAVExISEyccHhcgLikx


<snip>


If I recall correctly, two years ago the parser would interpret it as two separate attachments 

and the second part is stored as raw (unencoded) alphanumeric, which of course gives an
"unrecognized format" response.

In your reply to this, if you ask me nicely to not to blow up the parser, I won't do an email reply to it with an attachment and "Attachment Information" enabled ..  :)

Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 13, 2022, 03:55:06 am
I'm going to give this a test :boom:

Pretty sure it will do exactly what it did a couple of years ago, although I did fix a couple of attachment issues in the last update.  Attachments can be overly complex, or quite simple.  I know I purposely do not process cid: ones, those are inline, and doing ILA attachments via email was just more than I was willing to undertake LOL ...

Now if someone wants to give it a roll, 2.0 is better equipped to swap those cid: markers with the real thing and an ILA attach bbc.  Most of those that I've seen in real use are simply smileys/emoji and the parser will just use the alt tag if supplied.
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 13, 2022, 07:15:12 am
The following section of this message contains a file attachment prepared for transmission using the Internet MIME message format. If you are using Pegasus Mail, or any other MIME-compliant system, you should be able to save it or view it from within your mailer. If you cannot, please ask your system administrator for assistance.
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 13, 2022, 07:20:47 am
And this is the message I sent.. that posted above [Reply #31]


OK, well here goes - nothing fancy, just some text with RTF and an attachment, with attachment info enable.. no BBC, inline images or smilies..
(In case you wanted to know what buttts.jpg was... it's not what you think.)
-Steeley
----------------------------------------
Did you exchange, a walk-on part in the war for a lead role in a cage?
[~ Pink Floyd: "Wish You Were Here"]
--------------------------------------

On 13 Aug 2022 at 1:55, Spuds via ElkArte Community wrote:

 
 
 I'm going to give this a test
Pretty sure it will do exactly what it did a couple of years ago, although I did fix a couple of attachment issues in the last update.  Attachments can be overly complex, or quite simple.  I know I purposely do not process cid: ones, those are inline, and doing ILA attachments via email was just more than I was willing to undertake LOL ...
 Now if someone wants to give it a roll, 2.0 is better equipped to swap those cid: markers with the real thing and an ILA attach bbc.  Most of those that I've seen in real use are simply smileys/emoji and the parser will just use the alt tag if supplied.
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 13, 2022, 07:45:20 am
And here is the message formatting for that email...

Code: [Select]

Content-type: Multipart/Mixed; boundary=Message-Boundary-25951
Subject: Re: [ElkArte Community] EMail Replies to the EA forum
Reply-to: noreply@redacted.gon
Message-ID: <62F737F9.4907.B69DE98@noreply@redacted.gon>
Priority: normal
In-reply-to: <dae94d667b1a336ca3759ec01d87143b-m44006@elkarte.net>
References: <6151@elkarte.net>, <dae94d667b1a336ca3759ec01d87143b-m44006@elkarte.net>
X-mailer: Pegasus Mail for Windows (4.80.1028)
X-PMFLAGS: 570949760 0 1 PTQ5H8VY.CNM                      


--Message-Boundary-25951
Content-type: Multipart/Related; boundary="Message-Boundary-26598"

--Message-Boundary-26598
Content-type: Multipart/Alternative; boundary="Alt-Boundary-12114.191487640"

--Alt-Boundary-12114.191487640
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: Quoted-printable
Content-description: Mail message body

OK, well here goes - nothing fancy, just some text with RTF and an attachm=
ent, with
attachment info enable.. no BBC, inline images or smilies..

(In case you wanted to know what buttts.jpg was... it's not what you think=
.)

-Steeley
----------------------------------------
Did you exchange, a walk-on part in the war for a lead role in a cage?
[~ Pink Floyd: "Wish You Were Here"]
--------------------------------------

On 13 Aug 2022 at 1:55, Spuds via ElkArte Community wrote:

   
    I'm going to give this a test
   
    Pretty sure it will do exactly what it did a couple of years ago, alth=
ough I did fix a
    couple of attachment issues in the last update. Attachments can be ove=
rly
    complex, or quite simple. I know I purposely do not process cid: ones,=
 those are
    inline, and doing ILA attachments via email was just more than I was w=
illing to
    undertake LOL ...
   
    Now if someone wants to give it a roll, 2.0 is better equipped to swap=
 those cid:
    markers with the real thing and an ILA attach bbc. Most of those that =
I've seen in
    real use are simply smileys/emoji and the parser will just use the alt=
 tag if
    supplied.
   
   
   
   


Posting Information:
Spuds replied to the topic 'EMail Replies to the EA forum ' on the 'Bug Re=
ports'
Board.
You can reply to this email and have it posted as a topic reply.

ElkArte Community Links:

<*> To visit ElkArte Community on the web, go to:
https://www.elkarte.net/community

<*> You can see this message by using this link:
https://www.elkarte.net/community/index.php?topic=3D6151.msg44006#msg44006

<*> You can go to your first unread message by using this link:
https://www.elkarte.net/community/index.php?topic=3D6151.new;topicseen#new

<*> Unsubscribe to this Board by using this link:
https://www.elkarte.net/community/index.php?action=3Dnotify;sa=3Dunsubscri=
be;token=3D1
192_KwTmnLfnybdrBzecNuLH1ecUIcaRdXnwLqP84txxxxxxxxxxxG7gK_board_
2_xxxxxxxxxxxxx

Regards, The ElkArte Community



                         ElkArte Community
                      Dont like these emails?
                                 
             [dae94d667b1a336ca3759ec01d87143b-xxxxxxx]
                                 




--Alt-Boundary-12114.191487640
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>
<div align=3D"left" style=3D"min-height: 11pt; "><font face=3D"Arial" size=
=3D"2"><span dir=3D"ltr" style=3D"font-size:10.0pt; ">OK, well here goes -=
 nothing fancy, just</span><span dir=3D"ltr" style=3D"font-size:10.0pt; ">=
<b> some text with RTF and</b></span><span dir=3D"ltr" style=3D"font-size:=
10.0pt; "> an attachment, with
attachment info enable.. no BBC, inline images or smilies..</span></font><=
/div>
<div align=3D"left" style=3D"min-height: 11pt; "></div>
<div align=3D"left" style=3D"min-height: 11pt; "><font face=3D"Arial" size=
=3D"2"><span dir=3D"ltr" style=3D"font-size:10.0pt; ">(In case you wanted =
to know what buttts.jpg was... it's not what you think.)</span></font></di=
v>
<div align=3D"left" style=3D"min-height: 11pt; "></div>
<div align=3D"left" style=3D"min-height: 11pt; "><font face=3D"Arial" size=
=3D"2"><span dir=3D"ltr" style=3D"font-size:10.0pt; ">-Steeley</span></fon=
t></div>
<div align=3D"left" style=3D"min-height: 11pt; "><font face=3D"Arial" colo=
r=3D"#00007f" size=3D"2"><span dir=3D"ltr" style=3D"font-size:10.0pt; ">--=
--------------------------------------</span></font></div>
<div align=3D"left" style=3D"min-height: 11pt; "><font face=3D"Arial" size=
=3D"2"><span dir=3D"ltr" style=3D"font-size:10.0pt; ">Did you exchange, a =
walk-on part in the war for a lead role in a cage?</span></font></div>
<div align=3D"left" style=3D"min-height: 11pt; "><font face=3D"Arial" size=
=3D"2"><span dir=3D"ltr" style=3D"font-size:10.0pt; ">[~ Pink Floyd: &quot=
;Wish You Were Here&quot;]</span></font></div>
<div align=3D"left" style=3D"min-height: 11pt; "><font face=3D"Arial" colo=
r=3D"#00007f" size=3D"2"><span dir=3D"ltr" style=3D"font-size:10.0pt; ">--=
------------------------------------</span></font></div>
<div align=3D"left" style=3D"min-height: 11pt; "></div>
<div align=3D"left" style=3D"min-height: 11pt; "></div>
<div align=3D"left" style=3D"min-height: 11pt; "><font face=3D"Arial" size=
=3D"2"><span dir=3D"ltr" style=3D"font-size:10.0pt; ">--------------------=
--------------------</span></font></div>
<div align=3D"left" style=3D"min-height: 11pt; "><font face=3D"Arial" size=
=3D"2"><span dir=3D"ltr" style=3D"font-size:10.0pt; "><i>Did you exchange,=
 a walk-on part in the war for a lead role in a cage? </i></span></font></=
div>
<div align=3D"left" style=3D"min-height: 9pt; "><font face=3D"Arial" size=3D=
"1"><span dir=3D"ltr" style=3D"font-size:8.0pt; ">[~ Pink Floyd: &quot;Wis=
h You Were Here&quot;]</span></font></div>
<div align=3D"left" style=3D"min-height: 11pt; "></div>
<div align=3D"left" style=3D"min-height: 11pt; "><font face=3D"Arial" size=
=3D"2"><span dir=3D"ltr" style=3D"font-size:10.0pt; ">--------------------=
------------------</span></font></div>
<div align=3D"left" style=3D"min-height: 11pt; "></div>
<div align=3D"left" style=3D"min-height: 11pt; "><hr width=3D"100%" align=3D=
"left"/></div>
<div align=3D"left" style=3D"min-height: 11pt; "><font face=3D"Arial" size=
=3D"2"><span dir=3D"ltr" style=3D"font-size:10.0pt; ">On 13 Aug 2022 at 1:=
55, Spuds via ElkArte Community wrote:</span></font></div>
<div align=3D"left" style=3D"min-height: 11pt; "></div>
<div style=3D"margin-left: 0mm;">
<table width=3D"572" cellpadding=3D"0" cellspacing=3D"0" style=3D"border-c=
ollapse: collapse; border: none; ">
    <tr>
    <td align=3D"left" valign=3D"top" width=3D"564" bgcolor=3D"#f6f6f6" st=
yle=3D"padding-left: 4px; padding-right: 4px; border: solid #010101 0px;">
    <div align=3D"left" style=3D"margin-left:4mm; margin-right:0mm; text-i=
ndent:0mm; margin-top:0.00mm; margin-bottom:0.00mm;padding-top:0.00mm; pad=
ding-bottom:0.00mm; min-height: 12pt; ">&nbsp;</div>
    <table width=3D"564" cellpadding=3D"0" cellspacing=3D"0" style=3D"bord=
er-collapse: collapse; border: none; ">
        <tr>
        <td colspan=3D"2" align=3D"left" valign=3D"top" width=3D"556" bgco=
lor=3D"#ffffff" style=3D"padding-left: 10px; padding-right: 10px; padding-=
top: 10px; padding-bottom: 10px; border: solid #010101 0px;">
        <div align=3D"left" style=3D"margin-left:4mm; margin-right:0mm; te=
xt-indent:0mm; margin-top:0.00mm; margin-bottom:0.00mm;padding-top:0.00mm;=
 padding-bottom:0.00mm; min-height: 12pt; ">&nbsp;</div>
        <table width=3D"556" cellpadding=3D"0" cellspacing=3D"0" style=3D"=
border-collapse: collapse; border: none; ">
            <tr>
            <td align=3D"left" valign=3D"top" width=3D"548" bgcolor=3D"#ff=
ffff" style=3D"padding-left: 4px; padding-right: 4px; border: solid #01010=
1 0px;">
            <div align=3D"left" style=3D"margin-left:4mm; margin-right:0mm=
; text-indent:0mm; margin-top:0.00mm; margin-bottom:0.00mm;padding-top:0.0=
0mm; padding-bottom:0.00mm; min-height: 12pt; "><font face=3D"sans-serif">=
<span dir=3D"ltr" style=3D"font-size:11.0pt; background:#ffffff; "><br />I=
'm going to give this a test</span></font><font face=3D"Wingdings"><span d=
ir=3D"ltr" style=3D"font-size:11.0pt; background:#ffffff; "></span=
></font><font face=3D"sans-serif"><span dir=3D"ltr" style=3D"font-size:11.=
0pt; background:#ffffff; "><br /><br />Pretty sure it will do exactly what=
 it did a couple of years ago, although I did fix a
            couple of attachment issues in the last update.  Attachme=
nts can be overly
            complex, or quite simple.  I know I purposely do not proc=
ess cid: ones, those are
            inline, and doing ILA attachments via email was just more than=
 I was willing to
            undertake LOL ...<br /><br />Now if someone wants to give it a=
 roll, 2.0 is better equipped to swap those cid:
            markers with the real thing and an ILA attach bbc.  Most =
of those that I've seen in
            real use are simply smileys/emoji and the parser will just use=
 the alt tag if
            supplied.<br /><br /><br /><br /> </span></font></div>
            <div align=3D"left" style=3D"margin-left:0mm; margin-right:0mm=
; text-indent:0mm; margin-top:3.96mm; margin-bottom:0.00mm;padding-top:0.0=
0mm; padding-bottom:0.00mm; min-height: 12pt; "><hr size=3D"1pt" width=3D"=
576" align=3D"center"/><font face=3D"sans-serif"><span dir=3D"ltr" style=3D=
"font-size:11.0pt; background:#ffffff; "><br />Posting Information:<br />S=
puds replied to the topic 'EMail Replies to the EA forum ' on the 'Bug Rep=
orts'
            Board.<br />You can reply to this email and have it posted as =
a topic reply.<br /><br />ElkArte Community Links:<br /><br />&lt;*&gt; To=
 visit ElkArte Community on the web, go to:<br /></span></font><a href=3D"=
https://www.elkarte.net/community"><font face=3D"sans-serif" color=3D"#000=
0ff"><span dir=3D"ltr" style=3D"font-size:11.0pt; background:#ffffff; "><u=
>https://www.elkarte.net/community</u></span></font></a><font face=3D"sans=
-serif"><span dir=3D"ltr" style=3D"font-size:11.0pt; background:#ffffff; "=
><br /><br /></span></font><font face=3D"sans-serif"><span dir=3D"ltr" sty=
le=3D"font-size:11.0pt; background:#ffffff; ">&lt;*&gt; You can see this m=
essage by using this link:<br /></span></font><a href=3D"https://www.elkar=
te.net/community/index.php?topic=3D6151.msg44006#msg44006"><font face=3D"s=
ans-serif" color=3D"#0000ff"><span dir=3D"ltr" style=3D"font-size:11.0pt; =
background:#ffffff; "><u>https://www.elkarte.net/community/index.php?topic=
=3D6151.msg44006#msg44006</u></span></font></a><font face=3D"sans-serif"><=
span dir=3D"ltr" style=3D"font-size:11.0pt; background:#ffffff; "><br /><b=
r /></span></font><font face=3D"sans-serif"><span dir=3D"ltr" style=3D"fon=
t-size:11.0pt; background:#ffffff; ">&lt;*&gt; You can go to your first un=
read message by using this link:<br /></span></font><a href=3D"https://www=
.elkarte.net/community/index.php?topic=3D6151.new;topicseen#new"><font fac=
e=3D"sans-serif" color=3D"#0000ff"><span dir=3D"ltr" style=3D"font-size:11=
.0pt; background:#ffffff; "><u>https://www.elkarte.net/community/index.php=
?topic=3D6151.new;topicseen#new</u></span></font></a><font face=3D"sans-se=
rif"><span dir=3D"ltr" style=3D"font-size:11.0pt; background:#ffffff; "><b=
r /><br /></span></font><font face=3D"sans-serif"><span dir=3D"ltr" style=3D=
"font-size:11.0pt; background:#ffffff; ">&lt;*&gt; Unsubscribe to this Boa=
rd by using this link:<br /></span></font><a href=3D"https://www.elkarte.n=
et/community/index.php?action=3Dnotify;sa=3Dunsubscribe;token=3D1192_KwTmn=
LfnybdrBzecNuLH1ecUIcaRdXnwLqP84tWKK0VsAMBrTG7gK_board_2_1660355706"><font=
 face=3D"sans-serif" color=3D"#0000ff"><span dir=3D"ltr" style=3D"font-siz=
e:11.0pt; background:#ffffff; "><u>https://www.elkarte.net/community/index=
.php?action=3Dnotify;sa=3Dunsubscribe;token=3D1192_KwTmnLfnybdrBzecNuLH1ec=
UIcaRdXnwLqP84tWKK0VsAMBrTG7gK_board_2_1660355706</u></span></font></a><fo=
nt face=3D"sans-serif"><span dir=3D"ltr" style=3D"font-size:11.0pt; backgr=
ound:#ffffff; "><br /><br /></span></font><font face=3D"sans-serif"><span =
dir=3D"ltr" style=3D"font-size:11.0pt; background:#ffffff; ">Regards, The =
ElkArte Community</span></font></div>
            </td></tr>
        </table>
        <div align=3D"left">&nbsp;</div>
        </td></tr>
    </table>
    <table width=3D"540" cellpadding=3D"0" cellspacing=3D"0" style=3D"bord=
er-collapse: collapse; border: none; ">
        <tr>
        <td colspan=3D"2" align=3D"center" valign=3D"top" width=3D"532" he=
ight=3D"25" bgcolor=3D"#f6f6f6" style=3D"padding-left: 4px; padding-right:=
 4px; border: solid #010101 0px;">
        <div align=3D"center" style=3D"min-height: 10pt; "><font face=3D"s=
ans-serif" color=3D"#999999" size=3D"1"><span dir=3D"ltr" style=3D"font-si=
ze:9.0pt; background:#f6f6f6; ">ElkArte Community</span></font><font face=3D=
"sans-serif" color=3D"#999999"><span dir=3D"ltr" style=3D"font-size:11.0pt=
; background:#f6f6f6; "><br />Dont like these emails? </span></font></div>
        </td></tr>
        <tr>
        <td colspan=3D"2" align=3D"center" valign=3D"top" width=3D"532" bg=
color=3D"#f6f6f6" style=3D"padding-left: 4px; padding-right: 4px; border: =
solid #010101 0px;">
        <div align=3D"center" style=3D"min-height: 10pt; "><font face=3D"s=
ans-serif" color=3D"#f6f6f6" size=3D"1"><span dir=3D"ltr" style=3D"font-si=
ze:9.0pt; background:#f6f6f6; ">[dae94d667b1a336ca3759ec01d87143b-m44006]<=
/span></font></div>
        </td></tr>
    </table>
    <div align=3D"left" style=3D"margin-left:0mm; margin-right:0mm; text-i=
ndent:0mm; margin-top:0.00mm; margin-bottom:0.00mm;padding-top:0.00mm; pad=
ding-bottom:0.00mm; ">&nbsp;</div>
    </td></tr>
</table>
</div>
<div align=3D"left" style=3D"margin-left:0mm; margin-right:0mm; text-inden=
t:0mm; margin-top:0.00mm; margin-bottom:0.00mm;padding-top:0.00mm; padding=
-bottom:0.00mm; min-height: 12pt; "></div>
</body>
</html>

--Alt-Boundary-12114.191487640--

--Message-Boundary-26598--

--Message-Boundary-25951
Content-type: text/plain; charset=US-ASCII
Content-disposition: inline
Content-description: Attachment information.

The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.

   ---- File information -----------
     File:  butts.jpg
     Date:  22 Feb 2009, 9:32
     Size:  33794 bytes.
     Type:  JPEG-image

--Message-Boundary-25951
Content-type: Image/JPEG; name="butts.jpg"
Content-disposition: attachment; filename="butts.jpg"
Content-transfer-encoding: BASE64

/9j/4AAQSkZJRgABAQEBLAEsAAD/2wBDAA0JCgsKCA0LCgsODg0PEyAVExISEyccHhcgLikx
<SNIP>

--Message-Boundary-25951--


Just something twisted for your testcase.mbox..  enjoy..
Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 14, 2022, 12:40:52 am
That is a bit complicated ... All those empty sections. 

The parser is actually finding all the "parts" but where things break down is due to the HTML section being fully in-lined (a baseline for ensuring all dino email clients can render the HTML)

For example <div align="left" style="min-height: 11pt; "><font face="Arial" size="2"><span dir="ltr" style="font-size:10.0pt;">-Steeley</span></font></div> is what it puts in there for a single word, that is just brutal.  And of course all of that is wrapped in a table structure as well.

When the class that generates the forum post from the email parser, see's that level, it prefers to use the plain text section, and that seems to only have the last section.  I have a fix for the multipart/mixed which should combine the sections (it does when they are in one area) but here they are across multiple boundaries, but its one of those not-so-sure moments.  I ran this email through a couple of other "no dependency" parsers the ones I tried also had problems.

So interesting case, not sure I'll address it, but do have something to test.

TLDR ... I hate you LOL
Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 14, 2022, 12:42:03 am
Also that butts guy has one of the worst jobs ever !  Hope that is not the scope site adjustment range.
Title: Re: EMail Replies to the EA forum
Post by: Steeley on August 14, 2022, 08:23:58 am
Quote from: Spuds – That is a bit complicated ... All those empty sections. 

The parser is actually finding all the "parts" but where things break down is due to the HTML section being fully in-lined (a baseline for ensuring all dino email clients can render the HTML)

For example <div align="left" style="min-height: 11pt; "><font face="Arial" size="2"><span dir="ltr" style="font-size:10.0pt;">-Steeley</span></font></div> is what it puts in there for a single word, that is just brutal.  And of course all of that is wrapped in a table structure as well.

When the class that generates the forum post from the email parser, see's that level, it prefers to use the plain text section, and that seems to only have the last section.  I have a fix for the multipart/mixed which should combine the sections (it does when they are in one area) but here they are across multiple boundaries, but its one of those not-so-sure moments.  I ran this email through a couple of other "no dependency" parsers the ones I tried also had problems.

So interesting case, not sure I'll address it, but do have something to test.

TLDR ... I hate you LOL

I figured you 'd like that.. And no, I had no expectation of you trying to handle that. 

Did I mention the old jeans I have - well, actually, the jeans themselves are long gone, all I have left to wear are the patches?  Yes, I think I did.
I've been using Pegasus since shortly after it was released 30 years ago, and I'm trying to remember when that "attachment Info" removal option was added to the multi-part option..  no idea why it was included in the first place since I've never found an email system it didn't bugger up when enabled. And alas, since they switched to their new community forum all the old stuff over the past 25 years or so is no longer available.
Probably code reuse from their Mercury Transport product..

(Link-10081)

.
.

BTW, if you haven't had the pleasure yet, read "The Unix Haters Handbook". 
"Two of the most famous products of Berkeley are LSD and Unix. I don't think that is a coincidence."
Anyway, it has some hilarious email development stories (and I particularly like Chapter 2 - which claims Unix is essentially a virus with a user-interface... and then pretty much proves it).

As for butts guy, I believe the red spotting dot on the target is to let the shooter know where the last round went and that he needs to elevate his sights. (and probably desperately hoping the shooter knows which way to adjust to raise the impact point).
And to think I used to complain if I got assigned 'mess duty'..
(And not just butts guy  - I'd also hate to be a shop owner or apartment dweller beyond the fence.. )

Anyway, I don't expect anything to handle that 'attachment info' thing - the fact it's apparently a default you have to turn off is almost as big of a puzzle..
Pegasus has a number of email-sending configuration options  that I've not bothered to developed a "Truth Table" for, but I suspect several combinations result in formats that don't fit anything. Dave is working on version 5.0, which I suspect is going to be a brand new pair of jeans..
 And Dave is not particularly enamored with OAUTH2  [ https://www.pmail.com/devnews.htm ]
 "needlessly complex and convoluted, has little or no real-world standardization, and is at best dismally documented."
Other than that, it's hoped to be the Future Of Email[TM].

IOW, if you thought email was a dark art, remember it's always darkest before it goes pitch black. It's "gonna get better"..
Title: Re: EMail Replies to the EA forum
Post by: Spuds on August 14, 2022, 08:50:55 pm
Quote from: Steeley – BTW, if you haven't had the pleasure yet, read "The Unix Haters Handbook".
I'm going to have to find that, sounds like a fun read.

QuoteAnd Dave is not particularly enamored with OAUTH2
Interesting take on all of that.  Many of todays specs seem to make, or have to make, to many compromises to cover all the needs thrown at them.  Not that all of those needs are legit, but they end up being very complicated and somewhat open to interpretation, and of course are filled with must vs should lingo, can be quite maddening.

Quote from: Steeley – I'd also hate to be a shop owner or apartment dweller beyond the fence
LOL

I did put a "fix" on the site for that specific email, so now it should at least show the first text instead of the last.  The text line that it did show originally, the disclaimer, probably will not show, only because of the original post clipping that the system attempts,  it should get clipped and tossed (because its after the quoted section in the reply)
Title: Re: EMail Replies to the EA forum
Post by: Steeley on October 13, 2022, 02:21:52 am
Quote from: Steeley –
Anyway, I don't expect anything to handle that 'attachment info' thing - the fact it's apparently a default you have to turn off is almost as big of a puzzle..
Pegasus has a number of email-sending configuration options  that I've not bothered to developed a "Truth Table" for, but I suspect several combinations result in formats that don't fit anything. Dave is working on version 5.0, which I suspect is going to be a brand new pair of jeans..
 And Dave is not particularly enamored with OAUTH2  [ https://www.pmail.com/devnews.htm ]
 "needlessly complex and convoluted, has little or no real-world standardization, and is at best dismally documented."
Other than that, it's hoped to be the Future Of Email[TM].

IOW, if you thought email was a dark art, remember it's always darkest before it goes pitch black. It's "gonna get better"..


Just for amusement, here's the latest from Dave re Google and OATHE2...

Update, August 2022  After a difficult and mostly pretty horrible two-month process, Google have now approved Pegasus Mail to use OAUTH2 for accessing GMail.

BUT (you knew there was going to be a "but", didn't you)... In the time we have been waiting for the approval to complete, they have changed their own rules (by deciding that they will no longer accept the redirect method we were previously successfully using), and as a result, our OAUTH2 module no longer works.

The solution involves — and I'm not joking here — writing our own web server, and starting it up to receive the token from Google when you authorize Pegasus Mail to access your account. Fortunately, I have written web servers before, so this process is not as serious a problem as it might have been, but the simple fact that I should need to do it at all indicates just how ridiculous this whole 'OAUTH2 migration' has become.

I am now well into the process of completing a small web server I can include in Pegasus Mail to accommodate Google. It should require no configuration or setup, and Pegasus Mail users should not even know it's there, doing its work in the background. I hope to have the amended module in testing around the middle of August, and if all goes well, should have Pegasus Mail v4.81 with full GMail OAUTH2 support ready a short time after that.



I predict that eventually Dave will spin off a non-google-complaint product branch that will work with everyone else..  🤡