![]() Send your files to whichever reader you’ll be using. Note that your free mobile Kindle app and your Kindle device emails are different. Once everything is set, you can now head to your email and attach your desired document and send it to your Send to Kindle email address. Just make sure that you type the word “ convert” on the subject line when sending a PDF file to your Send to Kindle email address. Related: What’s the Best E-Reader App for Windows 10?Īs an added perk, Amazon converts PDF files to the Kindle format and allows you to make use of functionalities like annotations, Whispersync, and changing font sizes. Other than the Kindle formats, here are the different supported file types that you can email to your dedicated Send to Kindle email address: As long as your file is one of the specific formats supported by the Send to Kindle by email option, you should be able to open it on your device. My understanding of the "interactive shell" is that it's waiting for you to type the message body, but accepts commands starting with a special character (~), which makes it a command interpreter too.Step 3: Check if Your File Format Is Supportedĭon’t worry if the file you mean to send is not in the formats primarily supported by Kindle. If that’s not needed, the non-interactive use can be forced by redirecting /dev/null to the standard input, e.g.: The GNU mailutils documentation on MIME implies that this should work as you expected to, for instance it states:Īll the examples above will enter the usual interactive shell, allowing you to compose the body of the message. ![]() UPDATE: From the headers you included, it looks like your mailer is using MIME, but as you noticed yourself, it's not sending the file as an attachment (which would have been marked with Content-Disposition: attachment), but as the main body of the email (ignoring the body you supplied.) While MIME looks like this: Content-Type: application/pdfĬontent-Disposition: attachment filename=myebook.pdf Uuencode looks something like this: begin 644 myebook.pdf You should be able to tell whether it looks like uuencode or MIME. Add your Kindle email address to the recipient field and leave the subject. One way to confirm this is to send mail with attachments to yourself using both mail and mutt and look at the raw email body. Send a Document to Your Kindle Email Address Open up your regular email client and create a new draft email. (Also, perhaps the man page might have details about using uuencode format for attachments or MIME support or lack thereof. It's hard to tell how your mail command will behave (from your question) since there are many implementations of mail shipped by different Linux distributions (many of which do not even support attachments at all.) If you give more details about your Linux distribution, package which owns the mail binary and perhaps some reference from man mail, we can try to confirm that. Uuencode is an outdated email format and has been largely superceded by MIME, so I wouldn't be surprised that the handler for would not be able to recognize uuencode format, only MIME. I'm fairly sure what is happening here is that your mail program is sending its attachments using uuencode format, while mutt sends them in MIME format. a, -append=HEADER: VALUE append given header to the message being sent Upon closer inspection I noticed that the one from mail is missing the text "See attachment".Īccording to the man page on the server I'm using -A correctly: -A, -attach=FILE Received: by 2002:a2e:9c0f:0:0:0:0:0 with SMTP id s15-v6csp1355528lji Ĭontent-Type: multipart/mixed boundary="5mCyUwZo2JvN/JJP"Ĭontent-Type: text/plain charset=us-asciiĬontent-Disposition: attachment filename="20181024T0942.mobi" The headers from mutt (Please let me know if I stripped out too much): Delivered-To: Question: Why does it work with mutt but not with mail? How would I troubleshoot such an issue? I already checked the postfix logs ( /var/log/mail.log) but couldn't see any differences between the two methods above. I'm using postfix to forward the emails to a hosted smtp server. Interestingly it works fine (as in the ebook appears on my kindle) if I use mutt like this: echo "See attachment" | mutt -s subject -a $EMAIL_FILE - $EMAIL_TO The email appeared correctly with attachment in my personal inbox. I tested this command by sending it to my personal email address instead of the one. I'm using the following command to send the email with attachment: echo "See attachment" | mail -s subject -aFrom:"$EMAIL_FROM" -A $EMAIL_FILE -r $EMAIL_FROM $EMAIL_TO Your email to Kindle(s) did not include any attachments. Problem: If I configure the server to send to my email address (as described here: ) I get back an email telling me: Background: I'm trying to set up a server to regularly pull RSS feeds, package them up in a mobi-ebook and send them to my kindle.
0 Comments
Leave a Reply. |