[Psi-Jack -//- Decker]
þ Synchronet þ Decker's Heaven -//- bbs.deckersheaven.com[Psi-Jack -//- Decker]
Found a bug in Synchronet 3.16a where if you attach a file to an
attachment, it sends it oddly.
For example. I sent myself an email with file attachment, and in
Thunderbird and KMail, I literally see this in the message viewer:
This is a multi-part message in MIME format.
--tSDQQe2ItIxEy0Y9c9brq25S2sLIL1WEUjfs
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Just... testing?
Re: Bug in Mail Attachments
By: Psi-Jack to All on Thu Sep 18 2014 06:05 pm
Found a bug in Synchronet 3.16a where if you attach a file to an
attachment, it sends it oddly.
For example. I sent myself an email with file attachment, and in
Thunderbird and KMail, I literally see this in the message viewer:
This is a multi-part message in MIME format.
If you're expecting the Synchronet mail server to decode MIME body text (in messages received via SMTP), it has never done that and it was never intended to.
I agree that it would be *nice* if when viewing MIME-encoded messages
over Telnet/SSH/RLogin, that only the text/plain part was decoded and displayed to the user, but that is a significant enhancement, not a bug-fix.
þ Synchronet þ Decker's Heaven -//- bbs.deckersheaven.com[Psi-Jack -//- Decker]
No, I'd just expect it to format OUTBOUND email properly. This was email sent to an external email address, like gmail, my own mail server, etc, and not actually formatted properly from the start. Not a decoding issue, but
an ENCODING issue on Synchronet's part. Though Decoding would be nice too, for obvious reasons that it is in fact... A mail server, but even still,
Re: Bug in Mail Attachments
By: Digital Man to Psi-Jack on Thu Sep 18 2014 03:55 pm
Re: Bug in Mail Attachments
By: Psi-Jack to All on Thu Sep 18 2014 06:05 pm
Found a bug in Synchronet 3.16a where if you attach a file to an
attachment, it sends it oddly.
For example. I sent myself an email with file attachment, and in
Thunderbird and KMail, I literally see this in the message viewer:
This is a multi-part message in MIME format.
If you're expecting the Synchronet mail server to decode MIME body
text (in messages received via SMTP), it has never done that and it
was never intended to.
No, I'd just expect it to format OUTBOUND email properly. This was email sent to an external email address, like gmail, my own mail server, etc, and not actually formatted properly from the start. Not a decoding issue, but
an ENCODING issue on Synchronet's part.
i sent from bbses.info's email server to my gmail address. i attached a
.png file.
with my email client poppeeper and with gmail's web interface, the emails showed up as normal and the file attachment was okay.
Re: Bug in Mail Attachments
By: Psi-Jack to Digital Man on Fri Sep 19 2014 10:03 am
Re: Bug in Mail Attachments
By: Digital Man to Psi-Jack on Thu Sep 18 2014 03:55 pm
Re: Bug in Mail Attachments
By: Psi-Jack to All on Thu Sep 18 2014 06:05 pm
Found a bug in Synchronet 3.16a where if you attach a file to an
attachment, it sends it oddly.
For example. I sent myself an email with file attachment, and in
Thunderbird and KMail, I literally see this in the message viewer:
This is a multi-part message in MIME format.
If you're expecting the Synchronet mail server to decode MIME body
text (in messages received via SMTP), it has never done that and
it was never intended to.
No, I'd just expect it to format OUTBOUND email properly. This was
email sent to an external email address, like gmail, my own mail
server, etc, and not actually formatted properly from the start. Not a
decoding issue, but an ENCODING issue on Synchronet's part.
Gotcha. Well there is a little MIME-encoding support in the Synchronet mail server for messages that were not originally MIME encoded. How did actually create and send the original email with attachment?
þ Synchronet þ Decker's Heaven -//- bbs.deckersheaven.com[Psi-Jack -//- Decker]
By: Psi-Jack to Digital Man on Fri Sep 19 2014 10:03 am
No, I'd just expect it to format OUTBOUND email properly. This was
email sent to an external email address, like gmail, my own mail
server, etc, and not actually formatted properly from the start. Not
a decoding issue, but an ENCODING issue on Synchronet's part. Though Decoding would be nice too, for obvious reasons that it is in
fact... A mail server, but even still,
i sent from bbses.info's email server to my gmail address. i
attached a .png file.
with my email client poppeeper and with gmail's web interface, the
emails showed up as normal and the file attachment was okay.
i sent from bbses.info's email server to my gmail address. i
attached a .png file.
with my email client poppeeper and with gmail's web interface, the
emails showed up as normal and the file attachment was okay.
okay so on irc he told me he was using the send file to netmail
function on the bbs. and it does send the way he mentioned.
On Fri, 19 Sep 2014, Mro wrote to Psi-Jack:
By: Psi-Jack to Digital Man on Fri Sep 19 2014 10:03 am
confirmed... looks fine over here when i just tested from max's sync to one of my email addresses... i attached a text file which was base64 encoded as an octet-stream...
the only thing i initially saw in the raw email was the "client" section of the "Originator-Info:" header... my test was done when telnetted into sync... "client" says "<no name>" which is true i guess but would be
nicer to maybe say "synchronet" or "sbbs" or similar since that was the ""client"" used to generate the email ;)
[Psi-Jack -//- Decker]
[Psi-Jack -//- Decker's Heaven]
[Psi-Jack -//- Decker]
(document icon) dhtest.txt[Psi-Jack -//- Decker's Heaven]
þ Synchronet þ Decker's Heaven -//- bbs.deckersheaven.com[Psi-Jack -//- Decker]
confirmed... looks fine over here when i just tested from max's sync to one of my email addresses... i attached a text file which was base64 encoded as an octet-stream...
Re: Bug in Mail Attachments
By: mark lewis to Mro on Sat Sep 20 2014 14:01:51
confirmed... looks fine over here when i just tested from max's sync
to one of my email addresses... i attached a text file which was
base64 encoded as an octet-stream...
actually, i've gotta back off on this confirmation... i had viewed the
confirmed... looks fine over here when i just tested from
max's sync to one of my email addresses... i attached a text
file which was base64 encoded as an octet-stream...
actually, i've gotta back off on this confirmation... i had viewed
the
are you replying to mark lewis,
cause on my bbs it says you are replying to me,
but i didnt create that msg.
also i am missing the msg from mark lewis.
I agree that it would be *nice* if when viewing MIME-encoded
messages over Telnet/SSH/RLogin, that only the text/plain part was
decoded and displayed to the user, but that is a significant
enhancement, not a bug-fix.
Yes, that would be a definite enhancement wish in the future too. Displaying only the plain/text only portion of a multipart mime message.
Re: Bug in Mail Attachments
By: Psi-Jack to Digital Man on Fri Sep 19 2014 10:03 am
I agree that it would be *nice* if when viewing MIME-encoded
messages over Telnet/SSH/RLogin, that only the text/plain part was
decoded and displayed to the user, but that is a significant
enhancement, not a bug-fix.
Yes, that would be a definite enhancement wish in the future too. Displaying only the plain/text only portion of a multipart mime message.
This is a feature I would love to see, as well.
I see on the Synchronet wiki page for the mail server, there is an entry
for "external mail processor." I don't know what that is, exactly, but in theory could I write a JS module which would strip non-plain-text from an email and only display the content of the text/plain portion?
I see on the Synchronet wiki page for the mail server, there is an entry for "external mail processor." I don't know what that is, exactly, but in theory could I write a JS module which would strip non-plain-text from an email and only display the content of the text/plain portion?
I see on the Synchronet wiki page for the mail server, there is an entry for "external mail processor." I don't know what that is, exactly, but
in theory could I write a JS module which would strip non-plain-text
from an email and only display the content of the text/plain portion?
An external mail processor could be written to convert a MIME-encoded email to plain text, but then you'd stop being able to receive file attachments, HTML-encoded emails, etc., so I doubt that's a solution.
On 12-23-14 22:41, Kirkman wrote to Digital Man <=-
I see on the Synchronet wiki page for the mail server, there is an entry for "external mail processor." I don't know what that is, exactly, but
in theory could I write a JS module which would strip non-plain-text
from an email and only display the content of the text/plain portion?
An external mail processor could be written to convert a MIME-encoded email to plain text, but then you'd stop being able to receive file attachments, HTML-encoded emails, etc., so I doubt that's a solution.
That is, in fact, what I wanted to do. I don't really use my BBS for personal or work email. It's mostly for the kids, and for me to
experiment with. My daughter has started receiving email from folks,
but if they send HTML, it's almost unreadable through the telnet interface.
I don't think I'm up to the challenge of writing a JS MIME processing module (though I did find one written in Node,js).
But after some work this evening, I cobbled together a Python script
which strips out everything except the "text/plain" content part. It
seems to be working well.
If anyone else is interested, I tossed it onto GitHub:
https://github.com/Kirkman/Mail-to-Plain-Text
This is something I was really interested to work with the listserver. I performed the installation as you perscribed on your site (had to get python). Installed Python but didn't reboot the server yet, I made all the changes as per your instructions and nothing. Still seeing the MIME. I'll not be rebooting the server till the weekend so no worries about it not working till I do that. My question is, if it does start working after the reboot, can this be implimented into the listserver function.
On 12-24-14 13:48, Kirkman wrote to Bill McGarrity <=-
This is something I was really interested to work with the listserver. I performed the installation as you perscribed on your site (had to get python). Installed Python but didn't reboot the server yet, I made all the changes as per your instructions and nothing. Still seeing the MIME. I'll not be rebooting the server till the weekend so no worries about it not working till I do that. My question is, if it does start working after the reboot, can this be implimented into the listserver function.
Are you on Windows or Linux? If you just installed Python, you may need
to check if the Python directory has been added to your PATH.
Also, make sure the .py script is executable and owned by the same user your BBS runs as.
As far as the list server, I would guess so.
But after some work this evening, I cobbled together a Python script which strips out everything except the "text/plain" content part. It seems to be working well.
If anyone else is interested, I tossed it onto GitHub:
https://github.com/Kirkman/Mail-to-Plain-Text
þ Synchronet þ Decker's Heaven -//- bbs.deckersheaven.com[Psi-Jack -//- Decker]
That's pretty good stuff, Kirkman. Granted, I myself use both POP and Telnet to access my mail, but I also get some occasional scenarios where I somehow actually get junk mail that's all html or just plain junk mail, so.. I'm considering my options, including pondering the idea of integrating dspamd into my Synchronet setup to see if I can. Having a start towards that goal may prove useful though.
But given that state of BBSing, I think very few users would actually want such a thing, so it's probably not going to happen.
Psi-Jack wrote to Kirkman <=-
That's pretty good stuff, Kirkman. Granted, I myself use both POP and Telnet to access my mail, but I also get some occasional scenarios
where I somehow actually get junk mail that's all html or just plain
junk mail, so..
Psi-Jack wrote to Kirkman <=-
That's pretty good stuff, Kirkman. Granted, I myself use both POP
and Telnet to access my mail, but I also get some occasional
scenarios where I somehow actually get junk mail that's all html or
just plain junk mail, so..
I wish someone would port procmail over to javascript -- I used to use a script called "procmail sanitizer" when I ran my own email server and loved it for streamlining my email and de-html ing it.
[Psi-Jack -//- Decker]
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 333 |
Nodes: | 10 (0 / 10) |
Uptime: | 146:08:30 |
Calls: | 581 |
Messages: | 237921 |