If you want to set a cover for a specific Recipe, you need to add a cover_url attribute in its Recipe source code. It can be a local file (if it's a relative directory, it's relative to the KindleEar application directory) or a web image, for example:
cover_url = '/temp/mycover.jpg'
cover_url = 'application/images/mycover.jpg'
cover_url = 'https://www.google.com/mycover.jpg'
cover_url = False #no cover image
Additionally, if you want to customize the masthead, add a masthead_url attribute, which has the same format as cover_url.
KindleEar does not store passwords in plain text and cannot retrieve them. If login fails due to password verification, a "Forgot Password?" link is provided. Click on this link to reset your password using the email address registered when creating your account.
If your application is deployed on the Google Cloud Platform (GAE), the email address is: xxx@appid.appspotmail.com
(where xxx is any valid string, and appid is your application name).
If deployed using Docker Compose, the email address is: xxx@domain
, remember to open port 25 and set MX records correctly in the DNS server.
To use this function, you need to add whitelist first. If set to *
, it allows all emails. Otherwise, the format should be xx@xx.xx
or @xx.xx
.
This email will convert the received email body into e-book and push them to your registered email. If the email only contains links (one link per line), it will fetch the web content of the links and create an e-book before pushing.
If email's address is links@domain
or subject contains the identifier !links
, regardless of the email content, KindleEar will only extract the links from the email, then fetch the webpages and send them as e-books to your Kindle. This feature is best suited for sending serialized web content directly to Kindle for viewing.
If email's address is article@domain
or the identifier !article
is present in the subject, all links will be ignored, and the content will be directly converted into an e-book for delivery.
The default language of the e-book is same as of the custom RSS. If you need another language, you can add the identifier !lang=en
(replace en
with the language code you need) after the email subject.
By default, the e-book is pushed to the administrator's registered email. If you want to push it to another user's email, use the format: username__xxx@domain
. (Note the double underscore)
If you send the e-book download link to book@domain
, KindleEar will directly download the corresponding e-book and forward it to the registered email. (Note: there are restrictions on file extensions; you cannot send file extensions that may have security risks, such as exe, zip files are allowed, but zip files cannot contain files with potential security risks.)
The suffix list that GAE can send emails to see: Mail Python API Overview (book/file/download email addresses are reserved for downloading e-books).
Amazon no longer supports pushing mobi format. If you have mobi files (‘.mobi', ‘.prc', ‘.azw', ‘.azw3', ‘.pobi') that need to be sent to your Kindle, you can send them as an attachment via email to convert@domain
. KindleEar will convert them to epub and then send them to Amazon.
Note: Mobi files must not have DRM encryption; otherwise, the conversion will fail.
Sending to trigger@domain
triggers a manual delivery. If the email subject is empty or ‘all', it is equivalent to the "Deliver Now" button on the website. If specific books need to be pushed, write their names in the subject, separated by commas.
Emails sent to debug@domain
will directly fetch the links from the email and send HTML files directly to the administrator's email instead of the Kindle mailbox.
Some websites require registering an account and logging in to read and download articles. For such websites, you can add an attribute in the Recipe source code:
needs_subscription = True
Then, after subscribing, you can select "Website Login Information" from the corresponding Recipe's popup menu to enter your login account and password.
"Subscribe" is for combined delivery, which combines all Recipes and custom RSS feeds subscribed to with this option into one file for delivery. "Subscribe (Deliver Separately)" creates a separate file for this Recipe for delivery, which is more suitable for Recipes that generate large file or have special delivery times.
Each send mail service provider has limitations on the size of individual emails. For example, GAE restricts it to 31.5MB, while Mailjet currently allows 15MB only. If the attachment exceeds this limit, it will result in a failed push.
KindleEar has ported the "Ebook Translator" plugin from calibre, which can translate foreign language news while fetching, making it convenient to learn foreign languages and also have a wider range of news sources.
The feature translation is disabled by default and needs to be enabled for each Recipe individually, with each Recipe having different settings.
After subscribing to a recipe, click the floating button on the right and select the "Translator" button to enter settings page.
color:#123456;font-style:italic
.At the bottom of the "Feeds" page, you'll find several bookmarklet links, which offer some convenient functions.
To use them, simply drag and drop the links to your browser's bookmark bar.
Each user of KindleEar has their own unique Bookmarklet links, and the ones you see currently apply only to your logged-in account.
Subscribe with KindleEar: This function is for conveniently subscribing to RSS links. When you open the corresponding RSS link on your computer and click this Bookmarklet, the current URL and title will be filled into the text field under "Custom RSS" in KindleEar. It saves you a couple of copy-paste actions - perfect for lazy people.
KindleEar provides a feature to upload recipe files via the web page.
After Calibre updated the recipes, you can simply upload the recipe files you are interested in without the need to redeploy KindleEar.
However, if you wish to merge recipe files into the built-in library:
builtin_recipes.zip
and builtin_recipes.xml
.If you have more questions, you can submit an issue at https://github.com/cdhigh/KindleEar/issues and wait for a reply. Before submitting a question, it's recommended to search for previously submitted issues first. Maybe someone has already submitted a similar issue? If no one has submitted a similar issue, when you submit a new one, it's recommended to attach the Logs information of GAE backend or the platform you deployed to for problem location, which can also get you a faster reply.