melib/nntp: accept invalid (non-ascii) address comment text #270
No reviewers
Labels
No Label
IMAP
JMAP
Maildir
Retired
User Experience
User Interface
bsd
bug
contacts
currently worked on
documentation
duplicate
easy
enhancement
help wanted
invalid
linux-gnu
macos
mbox
notmuch
question
security
wishlist
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: meli/meli#270
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "fix/269-invalid-ctext-loop"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
NNTP servers may return addresses that are not RFC 5322 compliant. An
address with a comment with non-ascii characters will make the parser loop indefinitely.
Fixes #269.
@epilys HI, I was able to pull this PR locally and cargo build,
the news.software.nntp etc does work now.
but the second issue is still there when I add more usenet groups I get the "Loading..." as I reported first.
some of the groups are:
It never loads any of the groups so can't tell which one is creating the bottleneck or if is just to many requests to the server etc...
Thanks
@r3k2 thanks for giving me a list to test with! Will get on it asap.
@epilys Thanks! I just finished patching this PR and testing, this seems to be working great, some groups take some time to finish but that is ok. PD: wondering how to do a mark all as read need to read the docs more. :)
Great, will merge in a few days because I'm away from home and I don't have access to my GPG key to sign the commits.
b603524bc3
to448e0635e0