First, Don, sorry for the version query, it was in your post a day ago and I missed it..
And yea, as MikeS noted, an empty CNM file can do that, (which is why I suggested doing a delta compare on the raw envelope views of a good one and a bad one, since it is really hard to send a 0 byte file to Michael ... or anyone else for that matter).
Interestingly when checking the "Is a valid MIME message" which is orginally unchecked - the gibberish is replaced by valid readable text.
So the envelope has some key information or formatting that Pegasus (running on XP, but not Win10, if I deduce the significance of Brian's post correctly) can't parse, but that's not the only issue (and not the one - sender/subject - you posted up about).
I've got a couple XP boxes available and the same version of Pegasus, but armed with the additional information I can't see how I can use them to assist in figuring this out, so I'll step back.
But before I do, some questions I'd seek answers to:
- Is it only this particular sender?
- Is it only this particular recipient? (Can someone ask the sender to send a test message copying the recipient, and another user in the installation, and maybe an addy off the installation?)
- Is there info in the raw envelope that is different between the 'bad' vs. 'good' emails ?
- Is there enough information in the raw envelope view to identify the sending (or receiving!) server in the 'bad' vs. 'good' emails (the same, or different routing in the mail-server farm?)
- Is there a temporal connection (all used to be OK, then some bad sometimes, and now, some bad all the time?) - My own host's mailservers were "updated" a couple times last year, each time introducing problems that took quite awhile to discover - not all servers in the farm were updated at the same time, a crap-shoot which ones served messages to or from my domain - and many days to determine the cause. That kind of thing can happen on the sender's side too, and often the only way to tell is to rule out everything else as a possible cause...
Ultimately it all boils down to identifying "what's different"? My experience is that it could be anything (and probably is..)
Good luck, I'm going back to lurk..
First, Don, sorry for the version query, it was in your post a day ago and I missed it..
And yea, as MikeS noted, an empty CNM file can do that, (which is why I suggested doing a delta compare on the raw envelope views of a good one and a bad one, since it is really hard to send a 0 byte file to Michael ... or anyone else for that matter).
[quote="pid:56691, uid:28210"]Interestingly when checking the "Is a valid MIME message" which is orginally unchecked - the gibberish is replaced by valid readable text.[/quote]
So the envelope has some key information or formatting that Pegasus (running on XP, but not Win10, if I deduce the significance of Brian's post correctly) can't parse, but that's not the only issue (and not the one - sender/subject - you posted up about).
I've got a couple XP boxes available and the same version of Pegasus, but armed with the additional information I can't see how I can use them to assist in figuring this out, so I'll step back.
But before I do, some questions I'd seek answers to:
- Is it only this particular sender?
- Is it only this particular recipient? (Can someone ask the sender to send a test message copying the recipient, and another user in the installation, and maybe an addy off the installation?)
- Is there info in the raw envelope that is different between the 'bad' vs. 'good' emails ?
- Is there enough information in the raw envelope view to identify the sending (or receiving!) server in the 'bad' vs. 'good' emails (the same, or different routing in the mail-server farm?)
- Is there a temporal connection (all used to be OK, then some bad sometimes, and now, some bad all the time?) - My own host's mailservers were "updated" a couple times last year, each time introducing problems that took quite awhile to discover - not all servers in the farm were updated at the same time, a crap-shoot which ones served messages to or from my domain - and many days to determine the cause. That kind of thing can happen on the sender's side too, and often the only way to tell is to rule out everything else as a possible cause...
Ultimately it all boils down to identifying "what's different"? My experience is that it could be anything (and probably is..) (doh)
Good luck, I'm going back to lurk..
edited Jun 11 at 3:29 pm