NEW: mail/rss2email3

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

NEW: mail/rss2email3

Kaashif Hymabaccus-2
Hello ports@

This is a port of the new version of rss2email, 3.9. Since it makes a
number of breaking changes from the version of rss2email we have now,
I'm making this an entirely new port.

This is heavily based on the port Thomas Levine submitted a while ago,
most of the credit goes to him.

Note: I install the script as r2e3 (not r2e) so as to avoid conflict
with rss2email-2.7. There were some ideas floating around about how to
rename ports or scripts to avoid confusion, but I think the best thing
to do is to avoid breaking people's scripts altogether and treat this
as a new, unrelated program. It almost is, since we have different
authors, a different version of Python and a different config file
format.

Comments? I think this is a fairly inoffensive and non-disruptive way
of handling this potential conflict.

--
Kaashif Hymabaccus
GPG: 3E810B04

rss2email3.tgz (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Stuart Henderson
On 2017/12/09 19:40, Kaashif Hymabaccus wrote:

> Hello ports@
>
> This is a port of the new version of rss2email, 3.9. Since it makes a
> number of breaking changes from the version of rss2email we have now,
> I'm making this an entirely new port.
>
> This is heavily based on the port Thomas Levine submitted a while ago,
> most of the credit goes to him.
>
> Note: I install the script as r2e3 (not r2e) so as to avoid conflict
> with rss2email-2.7. There were some ideas floating around about how to
> rename ports or scripts to avoid confusion, but I think the best thing
> to do is to avoid breaking people's scripts altogether and treat this
> as a new, unrelated program. It almost is, since we have different
> authors, a different version of Python and a different config file
> format.
>
> Comments? I think this is a fairly inoffensive and non-disruptive way
> of handling this potential conflict.
>
> --
> Kaashif Hymabaccus
> GPG: 3E810B04

I think that's the right way to handle it. Couple of comments,

MODPY_EGG_VERSION =     3.9

- please move this up in the block with DISTNAME

        ${INSTALL_DATA_DIR} ${PREFIX}/share/doc/${DISTNAME}

- usually we don't use the full version number in such directories,
${PREFIX}/share/doc/rss2email3 would probably be the most appropriate

(pkg/MESSAGE)

- please convert to a pkg-readme

Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Kaashif Hymabaccus-2
On Sat, Dec 09, 2017 at 10:32:26PM +0000, Stuart Henderson wrote:

>
> MODPY_EGG_VERSION =     3.9
>
> - please move this up in the block with DISTNAME
>
>         ${INSTALL_DATA_DIR} ${PREFIX}/share/doc/${DISTNAME}
>
> - usually we don't use the full version number in such directories,
> ${PREFIX}/share/doc/rss2email3 would probably be the most appropriate
>
> (pkg/MESSAGE)
>
> - please convert to a pkg-readme
Incorporated these suggestions. Tarball attached.

Also I moved everything around so it's in the same order as the
infrastructure Makefile template.

--
Kaashif Hymabaccus
GPG: 3E810B04

rss2email3.tgz (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Kaashif Hymabaccus-2
Ping with a new tarball. The distinfo in the previous one is wrong.

--
Kaashif Hymabaccus
GPG: 3E810B04

rss2email3.tgz (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Kaashif Hymabaccus-2
On Tue, Jan 16, 2018 at 12:14:10AM +0000, Kaashif Hymabaccus wrote:
> Ping with a new tarball. The distinfo in the previous one is wrong.
>
> --
> Kaashif Hymabaccus
> GPG: 3E810B04

Anyone interested in this? Tarball attached.

--
Kaashif Hymabaccus
GPG: 3E810B04

rss2email3.tgz (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Solène Rapenne-2

Kaashif Hymabaccus writes:

> On Tue, Jan 16, 2018 at 12:14:10AM +0000, Kaashif Hymabaccus wrote:
>> Ping with a new tarball. The distinfo in the previous one is wrong.
>>
>> --
>> Kaashif Hymabaccus
>> GPG: 3E810B04
>
> Anyone interested in this? Tarball attached.

make test fails for me

Traceback (most recent call last):
  File "test/test.py", line 15, in <module>
    import rss2email.feed as _rss2email_feed
  File "/home/ports/pobj/rss2email3-3.9/rss2email-3.9/rss2email/feed.py", line 49, in <module>
    import feedparser as _feedparser
ModuleNotFoundError: No module named 'feedparser'

a TEST_DEPENDS is needed here


A few changes are needed in pkg/PLIST too

- remove share/doc/rss2email3/README, because the README from pkg/README
  will be automatically put there-> share/doc/pkg-readmes/${FULLPKGNAME}
- ${MODPY_COMMENT} should be used for directories containing ${MODPY_PYCACHE}

--- pkg/PLIST.orig Mon Apr 30 17:44:04 2018
+++ pkg/PLIST Mon Apr 30 17:44:27 2018
@@ -3,7 +3,7 @@
 lib/python${MODPY_VERSION}/site-packages/rss2email/
 lib/python${MODPY_VERSION}/site-packages/rss2email-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info
 lib/python${MODPY_VERSION}/site-packages/rss2email/__init__.py
-lib/python${MODPY_VERSION}/site-packages/rss2email/${MODPY_PYCACHE}/
+${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/rss2email/${MODPY_PYCACHE}/
 lib/python${MODPY_VERSION}/site-packages/rss2email/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
 lib/python${MODPY_VERSION}/site-packages/rss2email/${MODPY_PYCACHE}command.${MODPY_PYC_MAGIC_TAG}pyc
 lib/python${MODPY_VERSION}/site-packages/rss2email/${MODPY_PYCACHE}config.${MODPY_PYC_MAGIC_TAG}pyc
@@ -33,5 +33,3 @@
 lib/python${MODPY_VERSION}/site-packages/rss2email/version.py
 @man man/man1/r2e3.1
 share/doc/pkg-readmes/${FULLPKGNAME}
-share/doc/rss2email3/
-share/doc/rss2email3/README

Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Kaashif Hymabaccus-2
On Mon, Apr 30, 2018 at 05:51:31PM +0200, Solene Rapenne wrote:
>
> a TEST_DEPENDS is needed here
>
>
> A few changes are needed in pkg/PLIST too
>
> - remove share/doc/rss2email3/README, because the README from pkg/README
>   will be automatically put there-> share/doc/pkg-readmes/${FULLPKGNAME}
> - ${MODPY_COMMENT} should be used for directories containing ${MODPY_PYCACHE}

Made these changes. Tarball attached.

--
Kaashif Hymabaccus
GPG: 3E810B04

rss2email3.tgz (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Jeremie Courreges-Anglas-2
On Sun, May 06 2018, Kaashif Hymabaccus <[hidden email]> wrote:

> On Mon, Apr 30, 2018 at 05:51:31PM +0200, Solene Rapenne wrote:
>>
>> a TEST_DEPENDS is needed here
>>
>>
>> A few changes are needed in pkg/PLIST too
>>
>> - remove share/doc/rss2email3/README, because the README from pkg/README
>>   will be automatically put there-> share/doc/pkg-readmes/${FULLPKGNAME}
>> - ${MODPY_COMMENT} should be used for directories containing ${MODPY_PYCACHE}
>
> Made these changes. Tarball attached.

The port looks good to me, the transition path makes sense I guess...

Two questions:

1. This proposal embeds "3" in the port directory name and the PKGNAME,
  what is supposed to happen with rss2email-4.0? A new mail/rss2email4
  port? :)

2. Right now it's not clear to me who is upstream,
  https://github.com/wking/rss2email or https://github.com/rss2email/rss2email ?

  https://github.com/wking/rss2email is mentioned as upstream in the 3.9
  release (2014) hosted on pypi.  https://github.com/rss2email/rss2email
  is mentioned as a possible new upstream in
  https://github.com/wking/rss2email/issues/105
  PR opened 9 days ago: https://github.com/rss2email/rss2email/issues/18
  All I know is that rss2email/rss2email has two more commits than
  wking/rss2email and transferred some PRs from it.

  I guess it would be nice to sort this out, especially a new release
  seems warranted, see for example the unreleased fix
  https://github.com/wking/rss2email/commit/354543d53e1b2716a416d23614b323d5c96aeee3
  https://github.com/rss2email/rss2email/commit/354543d53e1b2716a416d23614b323d5c96aeee3

Thoughts?

--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE

Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Stuart Henderson
On 2018/05/09 08:34, Jeremie Courreges-Anglas wrote:

> On Sun, May 06 2018, Kaashif Hymabaccus <[hidden email]> wrote:
> > On Mon, Apr 30, 2018 at 05:51:31PM +0200, Solene Rapenne wrote:
> >>
> >> a TEST_DEPENDS is needed here
> >>
> >>
> >> A few changes are needed in pkg/PLIST too
> >>
> >> - remove share/doc/rss2email3/README, because the README from pkg/README
> >>   will be automatically put there-> share/doc/pkg-readmes/${FULLPKGNAME}
> >> - ${MODPY_COMMENT} should be used for directories containing ${MODPY_PYCACHE}

That's not really needed here, it's python3+ only.

> >
> > Made these changes. Tarball attached.
>
> The port looks good to me, the transition path makes sense I guess...
>
> Two questions:
>
> 1. This proposal embeds "3" in the port directory name and the PKGNAME,
>   what is supposed to happen with rss2email-4.0? A new mail/rss2email4
>   port? :)

Has anyone figured out the process needed to move from aaronsw (RIP)'s
rss2email code that we have in ports now to this version? There was a
comment earlier that having the two in tree together made this easier
but no indication how. It would seem sensible to just have a one-time
bump to move across and avoid complexity.

> 2. Right now it's not clear to me who is upstream,
>   https://github.com/wking/rss2email or https://github.com/rss2email/rss2email ?
>
>   https://github.com/wking/rss2email is mentioned as upstream in the 3.9
>   release (2014) hosted on pypi.  https://github.com/rss2email/rss2email
>   is mentioned as a possible new upstream in
>   https://github.com/wking/rss2email/issues/105
>   PR opened 9 days ago: https://github.com/rss2email/rss2email/issues/18
>   All I know is that rss2email/rss2email has two more commits than
>   wking/rss2email and transferred some PRs from it.
>
>   I guess it would be nice to sort this out, especially a new release
>   seems warranted, see for example the unreleased fix
>   https://github.com/wking/rss2email/commit/354543d53e1b2716a416d23614b323d5c96aeee3
>   https://github.com/rss2email/rss2email/commit/354543d53e1b2716a416d23614b323d5c96aeee3
>
> Thoughts?

There's more activity on the dev branch of rss2email/rss2email, though
it's still not very lively. I'd probably go with whatever's on pypi plus
patches for now but consider switching if the more-active upstream feels
sufficiently confident to make a non-dev release.. But probably worth
monitoring those recently opened issues for a bit first?

Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Jeremie Courreges-Anglas-2
On Wed, May 09 2018, Stuart Henderson <[hidden email]> wrote:

> On 2018/05/09 08:34, Jeremie Courreges-Anglas wrote:
>> On Sun, May 06 2018, Kaashif Hymabaccus <[hidden email]> wrote:
>> > On Mon, Apr 30, 2018 at 05:51:31PM +0200, Solene Rapenne wrote:
>> >>
>> >> a TEST_DEPENDS is needed here
>> >>
>> >>
>> >> A few changes are needed in pkg/PLIST too
>> >>
>> >> - remove share/doc/rss2email3/README, because the README from pkg/README
>> >>   will be automatically put there-> share/doc/pkg-readmes/${FULLPKGNAME}
>> >> - ${MODPY_COMMENT} should be used for directories containing ${MODPY_PYCACHE}
>
> That's not really needed here, it's python3+ only.
>
>> >
>> > Made these changes. Tarball attached.
>>
>> The port looks good to me, the transition path makes sense I guess...
>>
>> Two questions:
>>
>> 1. This proposal embeds "3" in the port directory name and the PKGNAME,
>>   what is supposed to happen with rss2email-4.0? A new mail/rss2email4
>>   port? :)
>
> Has anyone figured out the process needed to move from aaronsw (RIP)'s
> rss2email code that we have in ports now to this version? There was a
> comment earlier that having the two in tree together made this easier
> but no indication how. It would seem sensible to just have a one-time
> bump to move across and avoid complexity.

I would prefer this approach too.  I thought you were an rss2email user.
Did you try the instructions in pkg/README?

>> 2. Right now it's not clear to me who is upstream,
>>   https://github.com/wking/rss2email or https://github.com/rss2email/rss2email ?
>>
>>   https://github.com/wking/rss2email is mentioned as upstream in the 3.9
>>   release (2014) hosted on pypi.  https://github.com/rss2email/rss2email
>>   is mentioned as a possible new upstream in
>>   https://github.com/wking/rss2email/issues/105
>>   PR opened 9 days ago: https://github.com/rss2email/rss2email/issues/18
>>   All I know is that rss2email/rss2email has two more commits than
>>   wking/rss2email and transferred some PRs from it.
>>
>>   I guess it would be nice to sort this out, especially a new release
>>   seems warranted, see for example the unreleased fix
>>   https://github.com/wking/rss2email/commit/354543d53e1b2716a416d23614b323d5c96aeee3
>>   https://github.com/rss2email/rss2email/commit/354543d53e1b2716a416d23614b323d5c96aeee3

There's also
https://github.com/rss2email/rss2email/commit/375404478410e12fd497d4f11bf7c7050e4eb907
which I find "funny".  Probably not many users rely on SSL/TLS.

>> Thoughts?
>
> There's more activity on the dev branch of rss2email/rss2email, though
> it's still not very lively. I'd probably go with whatever's on pypi plus
> patches for now but consider switching if the more-active upstream feels
> sufficiently confident to make a non-dev release.. But probably worth
> monitoring those recently opened issues for a bit first?

Probably. *shrug* :)

--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE

Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Stuart Henderson
On 2018/05/11 13:54, Jeremie Courreges-Anglas wrote:

> On Wed, May 09 2018, Stuart Henderson <[hidden email]> wrote:
> > On 2018/05/09 08:34, Jeremie Courreges-Anglas wrote:
> >> On Sun, May 06 2018, Kaashif Hymabaccus <[hidden email]> wrote:
> >> > On Mon, Apr 30, 2018 at 05:51:31PM +0200, Solene Rapenne wrote:
> >> >>
> >> >> a TEST_DEPENDS is needed here
> >> >>
> >> >>
> >> >> A few changes are needed in pkg/PLIST too
> >> >>
> >> >> - remove share/doc/rss2email3/README, because the README from pkg/README
> >> >>   will be automatically put there-> share/doc/pkg-readmes/${FULLPKGNAME}
> >> >> - ${MODPY_COMMENT} should be used for directories containing ${MODPY_PYCACHE}
> >
> > That's not really needed here, it's python3+ only.
> >
> >> >
> >> > Made these changes. Tarball attached.
> >>
> >> The port looks good to me, the transition path makes sense I guess...
> >>
> >> Two questions:
> >>
> >> 1. This proposal embeds "3" in the port directory name and the PKGNAME,
> >>   what is supposed to happen with rss2email-4.0? A new mail/rss2email4
> >>   port? :)
> >
> > Has anyone figured out the process needed to move from aaronsw (RIP)'s
> > rss2email code that we have in ports now to this version? There was a
> > comment earlier that having the two in tree together made this easier
> > but no indication how. It would seem sensible to just have a one-time
> > bump to move across and avoid complexity.
>
> I would prefer this approach too.  I thought you were an rss2email user.
> Did you try the instructions in pkg/README?

Aargh I missed that :)

So with a replacement, README is too late, but we can add to current.html
and upgrade notes. Something like this should work..

- Make a note of the default email address (r2e list | grep ^default)
- Export the list of feeds (r2e opmlexport > r2e.opml)
- Send any updates to feeds with the old version (r2e run)
- Update the package
- Create a new database (r2e new)
- Set the default email (r2e email "[hidden email]")
- Import the list of feeds (r2e opmlimport < r2e.opml)
- Ignore old updates (r2e run --no-send), or if you don't mind duplicates
and want to be sure you didn't miss any, re-send everything (r2e run).

Then I hit a runtime problem though...

$ r2e run
sax parsing error: <unknown>:104:121: undefined entity: feed-1 (http://www.undeadly.org/cgi?action=rss -> [hidden email])
Traceback (most recent call last):
  File "/usr/local/bin/r2e", line 5, in <module>
    rss2email.main.run()
  File "/usr/local/lib/python3.6/site-packages/rss2email/main.py", line 163, in run
    args.func(feeds=feeds, args=args)
  File "/usr/local/lib/python3.6/site-packages/rss2email/command.py", line 62, in run
    feed.run(send=args.send)
  File "/usr/local/lib/python3.6/site-packages/rss2email/feed.py", line 838, in run
    for (guid, id_, sender, message) in self._process(parsed):
  File "/usr/local/lib/python3.6/site-packages/rss2email/feed.py", line 357, in _process
    processed = self._process_entry(parsed=parsed, entry=entry)
  File "/usr/local/lib/python3.6/site-packages/rss2email/feed.py", line 470, in _process_entry
    for k,v in extra_headers.items():  # remove empty tags, etc.
RuntimeError: OrderedDict mutated during iteration

> There's also
> https://github.com/rss2email/rss2email/commit/375404478410e12fd497d4f11bf7c7050e4eb907
> which I find "funny".  Probably not many users rely on SSL/TLS.

Probably not for smtp..

Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Jeremie Courreges-Anglas-2
On Fri, May 11 2018, Stuart Henderson <[hidden email]> wrote:

> On 2018/05/11 13:54, Jeremie Courreges-Anglas wrote:
>> On Wed, May 09 2018, Stuart Henderson <[hidden email]> wrote:
>> > On 2018/05/09 08:34, Jeremie Courreges-Anglas wrote:
>> >> On Sun, May 06 2018, Kaashif Hymabaccus <[hidden email]> wrote:
>> >> > On Mon, Apr 30, 2018 at 05:51:31PM +0200, Solene Rapenne wrote:
>> >> >>
>> >> >> a TEST_DEPENDS is needed here
>> >> >>
>> >> >>
>> >> >> A few changes are needed in pkg/PLIST too
>> >> >>
>> >> >> - remove share/doc/rss2email3/README, because the README from pkg/README
>> >> >>   will be automatically put there-> share/doc/pkg-readmes/${FULLPKGNAME}
>> >> >> - ${MODPY_COMMENT} should be used for directories containing ${MODPY_PYCACHE}
>> >
>> > That's not really needed here, it's python3+ only.
>> >
>> >> >
>> >> > Made these changes. Tarball attached.
>> >>
>> >> The port looks good to me, the transition path makes sense I guess...
>> >>
>> >> Two questions:
>> >>
>> >> 1. This proposal embeds "3" in the port directory name and the PKGNAME,
>> >>   what is supposed to happen with rss2email-4.0? A new mail/rss2email4
>> >>   port? :)
>> >
>> > Has anyone figured out the process needed to move from aaronsw (RIP)'s
>> > rss2email code that we have in ports now to this version? There was a
>> > comment earlier that having the two in tree together made this easier
>> > but no indication how. It would seem sensible to just have a one-time
>> > bump to move across and avoid complexity.
>>
>> I would prefer this approach too.  I thought you were an rss2email user.
>> Did you try the instructions in pkg/README?
>
> Aargh I missed that :)
>
> So with a replacement, README is too late, but we can add to current.html
> and upgrade notes. Something like this should work..
>
> - Make a note of the default email address (r2e list | grep ^default)
> - Export the list of feeds (r2e opmlexport > r2e.opml)
> - Send any updates to feeds with the old version (r2e run)
> - Update the package
> - Create a new database (r2e new)
> - Set the default email (r2e email "[hidden email]")
> - Import the list of feeds (r2e opmlimport < r2e.opml)
> - Ignore old updates (r2e run --no-send), or if you don't mind duplicates
> and want to be sure you didn't miss any, re-send everything (r2e run).
>
> Then I hit a runtime problem though...
>
> $ r2e run
> sax parsing error: <unknown>:104:121: undefined entity: feed-1 (http://www.undeadly.org/cgi?action=rss -> [hidden email])
> Traceback (most recent call last):
>   File "/usr/local/bin/r2e", line 5, in <module>
>     rss2email.main.run()
>   File "/usr/local/lib/python3.6/site-packages/rss2email/main.py", line 163, in run
>     args.func(feeds=feeds, args=args)
>   File "/usr/local/lib/python3.6/site-packages/rss2email/command.py", line 62, in run
>     feed.run(send=args.send)
>   File "/usr/local/lib/python3.6/site-packages/rss2email/feed.py", line 838, in run
>     for (guid, id_, sender, message) in self._process(parsed):
>   File "/usr/local/lib/python3.6/site-packages/rss2email/feed.py", line 357, in _process
>     processed = self._process_entry(parsed=parsed, entry=entry)
>   File "/usr/local/lib/python3.6/site-packages/rss2email/feed.py", line 470, in _process_entry
>     for k,v in extra_headers.items():  # remove empty tags, etc.
> RuntimeError: OrderedDict mutated during iteration
Patch from upstream attached to work around this.



This is at least the second unreleased fix I noticed for newer python3+
versions.  This begs the question as to how this newer version is better
than what we already have in ports...

I get a warning using undeadly but no fatal crash:

  russell /usr/ports/mystuff/mail/rss2email3$ r2e3 run
  sax parsing error: <unknown>:104:121: undefined entity: undeadly (http://www.undeadly.org/cgi?action=rss -> [hidden email])

I received the mail below:
--8<--
From: "OpenBSD Journal: <author>" <[hidden email]>
Subject:
To: [hidden email]
Date: Fri, 11 May 2018 16:11:23 -0000 (11 minutes, 35 seconds ago)
User-Agent: rss2email/3.9 (https://github.com/wking/rss2email)



URL: None
-->8--

then mails for the p2k18 reports from landry@, naddy@, stsp@ and eric@
followed.  I get the same warnings, and the same mostly empty mail in
subsequent runs.

>> There's also
>> https://github.com/rss2email/rss2email/commit/375404478410e12fd497d4f11bf7c7050e4eb907
>> which I find "funny".  Probably not many users rely on SSL/TLS.
>
> Probably not for smtp..

Yep.

--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE

patch-rss2email_feed_py (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Stuart Henderson
On 2018/05/11 18:43, Jeremie Courreges-Anglas wrote:
> This is at least the second unreleased fix I noticed for newer python3+
> versions.  This begs the question as to how this newer version is better
> than what we already have in ports...

Very good point. I've had zero problems with 2.70..

Reply | Threaded
Open this post in threaded view
|

Re: NEW: mail/rss2email3

Daniel Jakots-3
In reply to this post by Jeremie Courreges-Anglas-2
On Fri, 11 May 2018 18:43:01 +0200, Jeremie Courreges-Anglas
<[hidden email]> wrote:

> I get a warning using undeadly but no fatal crash:
>
>   russell /usr/ports/mystuff/mail/rss2email3$ r2e3 run
>   sax parsing error: <unknown>:104:121: undefined entity: undeadly
> (http://www.undeadly.org/cgi?action=rss -> [hidden email])
>
> I received the mail below:
> --8<--
> From: "OpenBSD Journal: <author>" <[hidden email]>
> Subject:
> To: [hidden email]
> Date: Fri, 11 May 2018 16:11:23 -0000 (11 minutes, 35 seconds ago)
> User-Agent: rss2email/3.9 (https://github.com/wking/rss2email)
>
>
>
> URL: None
> -->8--  

That's because undeadly rss is broken.
https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fundeadly.org%2Fcgi%3Faction%3Drss
says "This feed does not validate." and tt-rss says "LibXML error 26 at
line 104 (column 129): Entity 'ecirc' not defined"
(It's not the first time)

I'm not saying rss2email3 couldn't handle it in a better way though.