0 votes
by (170 points)

Hy, we cannot process some messages that are coded in a particular way: no Content-Type specified and apparently uuencoded attachments.
Loading the message with Rebex.Mail.MailMessage, it doesn't see attachments and inserts everything else in the message into the BodyText.
We have no control over source messages, so we can only parse them, but we can't in this situation.

Rebex.Mail for .NET v. 7.0.8755

Below is a piece of one message:

...
other headers
...
Message-ID: opec21023.20240205172112.126351.237.2.54@pec.aruba.it
X-Riferimento-Message-ID: !&!AAAAAAAAAAAYAAAAAAAAAKeb/F9WO2pOlxhx4gR9w9PCgAAAEAAAAGiEk/24b9VCgR0gv9YfI1gBAAAAAA==@pec.it

Here is the body text

begin 666 Prova trasmissione allegato via Pec.pdf
M)5!$1BTQ+C4)>+CS],,2 P(&]B:@H\/" (" @+U1Y<&4@+T-A=&%L;V<
...
other file content
...

:7IE(#D/CX<W1A<G1X<F5F"C(V.#@)25%3T8
`
end

begin 666 Prova trasmissione allegato via Pec.docx
M4$L#!!0!@(````(0#=_)4W9@$" %```3@"6T-O;G1E;G1?5'EP97-=
...
other file content
...
4!08`````"P+,$"``!P) ``````
`
end

Applies to: Rebex Secure Mail

1 Answer

0 votes
by (143k points)
selected by
 
Best answer

It looks like our UUdecoder does not properly parse UUencoded file names with whitespace characters. UUencode has been rarely used for a long time, so this issue went unnoticed for years until now. We will fix it for the next release! If you would like to get a hotfix in advance, please let us know.

by (170 points)
Depending on the time needed, we can try to resist the customer's assaults! :)
What is the expected timeframe for the next release?
Thanks
by (143k points)
The next release will b published in a week or two. I'll send you a link to a hotfix on Friday to ensure it works as expected :-)
by (143k points)
I just sent a link to the hotfix to your e-mail address. Please give it a try.
by (170 points)
The patch works correctly!
Have a nice weekend, thank you
ago by (143k points)
We have just published Rebex Secure Mail v7.0.8816 that resolves this issue:
https://www.rebex.net/secure-mail.net/history.aspx#7.0.8816
...