Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libemail-mime-perl: fails to handle boundary="0" #63

Closed
gregoa opened this issue Nov 17, 2019 · 2 comments · Fixed by #64
Closed

libemail-mime-perl: fails to handle boundary="0" #63

gregoa opened this issue Nov 17, 2019 · 2 comments · Fixed by #64

Comments

@gregoa
Copy link

gregoa commented Nov 17, 2019

We have the following bug reported to the Debian package of
Email-MIME, c.f. https://bugs.debian.org/944887

The bug report contains a patch.

It doesn't seem to be a bug in the packaging, so you may want to take
a look. Thanks!

------8<-----------8<-----------8<-----------8<-----------8<-----

Email::MIME fails to handle mail with a boundary value of "0",
since Perl treats 0 as false.  This is a common type of bug in
Perl code.

Reading RFC 2046, the BNF for allowed boundary characters
allows 1-70 characters, so a single "0" is acceptable:

     boundary := 0*69<bchars> bcharsnospace
     bchars := bcharsnospace / " "
     bcharsnospace := DIGIT / ALPHA / "'" / "(" / ")" /
                      "+" / "_" / "," / "-" / "." /
                      "/" / ":" / "=" / "?"

------8<-----------8<-----------8<-----------8<-----------8<-----

Thanks for considering,
gregor herrmann,
Debian Perl Group

@pali
Copy link
Contributor

pali commented Nov 17, 2019

Patch in that Debian bug tracker is not complete, there is missing proper check on another place. I took that patch, fixed that problem, changed coding style to what is used in Email::MIME and created a pull request: #64

CC: @devmchakan

@gregoa
Copy link
Author

gregoa commented Nov 17, 2019 via email

@rjbs rjbs closed this as completed in #64 May 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants