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

email.errors.HeaderParseError: header value appears to contain an embedded header #84

Open
craigmaloney opened this issue Feb 3, 2016 · 1 comment

Comments

@craigmaloney
Copy link

Getting the following error on this feed:

http://sarahcandersen.com/rss

Traceback (most recent call last):
File "bin/r2e", line 5, in
rss2email.main.run()
File "/home/craig/.virtualenvs/rss2email3/lib/python3.4/site-packages/rss2email/main.py", line 163, in run
args.func(feeds=feeds, args=args)
File "/home/craig/.virtualenvs/rss2email3/lib/python3.4/site-packages/rss2email/command.py", line 62, in run
feed.run(send=args.send)
File "/home/craig/.virtualenvs/rss2email3/lib/python3.4/site-packages/rss2email/feed.py", line 842, in run
for (guid, id_, sender, message) in self._process(parsed):
File "/home/craig/.virtualenvs/rss2email3/lib/python3.4/site-packages/rss2email/feed.py", line 357, in _process
processed = self._process_entry(parsed=parsed, entry=entry)
File "/home/craig/.virtualenvs/rss2email3/lib/python3.4/site-packages/rss2email/feed.py", line 502, in _process_entry
section=self.section)
File "/home/craig/.virtualenvs/rss2email3/lib/python3.4/site-packages/rss2email/email.py", line 119, in get_message
sender_name = str(_Header(sender_name, sender_encoding).encode())
File "/usr/lib/python3.4/email/header.py", line 393, in encode
"an embedded header: {!r}".format(value))
email.errors.HeaderParseError: header value appears to contain an embedded header: "Sarah's\nScribbles: "

@Ekleog
Copy link

Ekleog commented Sep 11, 2020

Hello,

This repository has been deprecated for a few years now, and has been replaced by https://github.com/rss2email/rss2email .

If this issue is still relevant to you, and not fixed with v3.12.2, could you please reopen the issue there?

Cheers,
Leo

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

No branches or pull requests

2 participants