feed: Rename 'processing error' -> 'feedparser warning'

A few folks have stumbled over this one, thinking that the error
message meant the feed wasn't parsed [1,2,3].  All we're actually
doing is passing along a feedparser warning, so adjust our prefix
accordingly and drop the level from ERROR to WARNING.  Hopefully this
makes it clearer that:

* We still process these feeds, despite the boxo exception.  If
  feedparser can parse the feed despite the exception, it will do so.
* We probably can't fix these issues in rss2email.  You need to fix
  them in the feed itself, or adjust feedparser to deal with the
  busted feed.

[1]: http://article.gmane.org/gmane.mail.rss2email/168
[2]: #37
[3]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760963

Reported-by: Arun Persaud <apersaud@lbl.gov>
Reported-by: Joey Hess <joeyh@debian.org>
Signed-off-by: W. Trevor King <wking@tremily.us>

Author: wking

CHANGELOG

@@ -1,3 +1,6 @@
+v3.10 (unreleased)
+    * Change 'processing error' to 'feedparser warning'.
+
 v3.9 (2014-09-01)
     * Catch and error out if a user adds a feed with a duplicate name.
     * Split sender into both sendmail's -F and -f.

rss2email/feed.py

@@ -426,7 +426,7 @@ def _check_for_errors(self, parsed):
         elif parsed.bozo or exc:
             if exc is None:
                 exc = "can't process"
-            _LOG.error('processing error: {}: {}'.format(exc, self))
+            _LOG.warning('feedparser warning: {}: {}'.format(exc, self))
             warned = True
 
         if (not warned and