When sending an email to the internet, MIME headers are not correct.
For example, sending a small image, the MIME headers for the attachment are like those:
Content-Type: attachment; name="Blue hills.jpg"
Content-Disposition: attachment; filename="Blue hills.jpg"
Content-Transfer-Encoding: base64
They should be:
Content-type: image/jpeg; name="Blue hills.jpg"
Content-disposition: attachment; filename="Blue hills.jpg"
Content-transfer-encoding: base64
Note the line "Content-Type:"
Some mail clients (if not all) cannot handle this and cannot open the attachment. See:
http://winlink.userecho.com/topic/103334-rms-express-attachnments-do-not-open-in-thunderbird/
This is specially important to those trying to update their blog with some images.
Some more notes:
- Sending from WL2K to WL2K works OK
- Sending from the internet to WL2K works OK
- The problem shows with RMSE and Airmail and Paclink
- The headers are OK in the outgoing message within Airmail
- The headers are NOT OK in the outgoing message within RMSE
- The headers were OK before being sent to Paclink
Thanks for the good work.
Please feel free to contact me for more info.
Service d'assistance aux clients par UserEcho
When traveling in remote locations we love using Winlink to update our blog. Adding the ability to enrich our post with pictures will enhance our communication beyond words. Correcting Content-Type: will make this possible. Thank you to the hundreds of volunteers that make the system work. 73 KI6AQG
Maybe not quite relevant, but cosysop a year ago did not succeed sending "bluehills.jpg" by RMS Express and PK232 pactor 1, but it worked if doing with AirMail and PK232 pactor 1.
We did not find a good explanation. Download worked. Why?
73 Finn/LA7UM
How is this attachement name issue going?
Picture uploads from a sailor this winter needed being done manually from someone at home after this person first got the winlink mail from the boat.
73. Finn/LA7UM