efa-project.org

Hi

When viewing an email in the message viewer under MIME Type: text/plain it displays the text 'Part 11 not found' and 'Part 12 not found' under MIME Type: text/html instead of the body of the message.

This is happening with all messages received pre/post upgrade

Sounds like the MIME parser isn't working properly here. Do you have any messages that display properly, or is it affecting all of them in your setup?

Hi

It seems to be every email, a quick check of those sent since the upgrade and random ones checked in the historical qurantine folder.

I have two installations of EFA, one for sending and one for receiving, this is the sending gateway. I've yet to upgrade the receiving.

Thanks

Do you have a raw (i.e. quarantine file) sample you could safely forward?

If so , let me know. I would like to run it through some tests.

Or, you can just email to this address: shawniverson@summitgrid.org

I have a 3.0.1.9 installation running there

Found issue and prepared a fix.

***Removed post, see most recent fix below****

Thanks, applied fix and it's now working

Hi

After further investigation, it seems some are not displaying correctly, they are now showing 'Error: unable to validate input'

Thanks

Ok, at least we are making progress. Let me run some more tests...

dgrover wrote: 26 Mar 2017 16:08 Hi

After further investigation, it seems some are not displaying correctly, they are now showing 'Error: unable to validate input'

Thanks

Can you confirm line #115 in viewpart.php?

Hi

Line 115 is correct

Ok, let's do this...

Change line #116 as follows:
View the message and post the value that you see.

I'm seeing the same behaviour on my install

Need someone to try my post above and report back the value they have.

Ive done it on mine now. Where will i see that value?

If you place this instead on line 116 in viewpart.php
And view a message that is still having trouble, should show you the value.

Got you. It's corrected itself for now at least since doing original changes and rebooting. Random!

Also having this issue across 3 recently upgraded servers.
Is there a way to automate this fix, or does it require manual intervention?

Also receiving a lot of "Error: unable to validate security token" problems after upgrade.

The security token issue just logout clear your cache and log back in and it should behave

solarthread wrote: 29 Mar 2017 07:32 The security token issue just logout clear your cache and log back in and it should behave

Except it still happens after a cache & cookie clear. This is not a definitive fix for us.

Hi All,
I'm now also getting "Part 11 not found" and "Part 12 not found" issues on some emails now (as well as any quarantined emails older than 10 days not showing in the GUI).
I have had look at line #115 in viewpart.php and mine is different. My line #116 reads, Sorry to sound so ignorant here, but should I alter this / apply the fix or not, given i don't have the same starting point (and my code is different ) as the above topic, but the same symptom?
As always. Any help is greatly appreciated.

Actually after having a better look at the fix suggested by Shawn above on Git, my line numbers are much different. My case 'float': doesn't start until #4340, so I'm assumming there's other issues at play here. I am curious though as to why my code is different on the same version (3.0.1.9)

My float line also starts later, but the fix worked ok

shawniverson wrote: 27 Mar 2017 17:26 If you place this instead on line 116 in viewpart.php

Code: Select all

 die(__('dievalidate99') . ' Value:' . $part);

And view a message that is still having trouble, should show you the value.

Its happened again on another of my servers - just copied what its showing

Error: unable to validate inputValue:1.1.1

Error: unable to validate inputValue:1.1.2

Fix can be found here:

https://github.com/mailwatch/1.2.0/pull/714/files

Plan to roll out this and other fixes hopefully this weekend.