{"id":70,"date":"2011-08-29T08:49:02","date_gmt":"2011-08-29T13:49:02","guid":{"rendered":"http:\/\/microgecko.com\/binnacle\/?p=70"},"modified":"2011-09-26T17:37:05","modified_gmt":"2011-09-26T22:37:05","slug":"actualizar-post-de-wordpress-enviado-por-mail","status":"publish","type":"post","link":"https:\/\/microgecko.isi.com.mx\/?p=70","title":{"rendered":"Actualizar post de wordpress enviado por mail"},"content":{"rendered":"
\n

 <\/p>\n

http:\/\/=
\ncodex.wordpress.org\/Post_to_your_blog_using_email<\/p>\n

 <\/p>\n

WordPress =
\ncan be configured to use e-mail to post to a blog. To enable this =
\nfunctionality, you need to: <\/span><\/p>\n

Create a dedicated e-mail account to be =
\nused solely for posting to your blog, <\/span>Configure WordPress to access that =
\naccount, and <\/span>Configure WordPress to publish messages =
\nfrom the e-mail account <\/span><\/p>\n

You can blog by e-mail using most standard e-mail software =
\nprograms or a <\/span>Weblog Client<\/span> =
\n— a program specifically designed to send posts via email. =
\n<\/span><\/p>\n

Limitations: – Standard =
\ncharacters in the object – Plain text only <\/span><\/p>\n

Setting Up Post via E-mail<\/span><\/span><\/span>Step 1 – Create an e-mail =
\naccount<\/span><\/span><\/span>Log in to WordPress with the =
\nadministration login you use to administer your WordPress blog. =
\n<\/span>Go to Settings > Writing. Read the instructions under Post via =
\ne-mail<\/b> at the bottom of the page. At the end of these instructions, =
\nWordPress will suggest three random strings of numbers you may want to =
\nuse for the login name of the new e-mail account you’ll create. =
\n<\/span>Create a new e-mail account on your web =
\nhost’s mail server or a separate e-mail server, using one of the =
\nsuggested numeric strings (or your own secret word) for the username =
\n(also called a "login name"). A mail server receives e-mails =
\non your behalf and stores them for retrieval. Do not<\/b> use public, =
\nfree e-mail servers like Yahoo, Hotmail, etc., for this account. =
\n<\/span><\/p>\n

Note:<\/span><\/b> It is =
\nstrongly recommended that you use a "secret" address – that =
\nis, an e-mail account name that is very difficult to guess and known =
\nonly to you, such as those suggested by WordPress. Any e-mail sent to =
\nthis address will automatically be posted to your blog. Be aware, =
\nhowever, that some e-mail servers do not allow numbers-only e-mail =
\naccounts or accounts starting with a number. Please check with your web =
\nhost. <\/span><\/p>\n

Step 2 – Configure WordPress to =
\naccess your new account<\/span><\/span><\/span>When you are done creating the new =
\ne-mail account , return to the Writing Options panel and fill in the =
\nname of the mail server<\/b> and port number<\/b> your web hosting =
\nprovider uses. (If you don’t know these, refer to your web hosting =
\nprovider’s FAQ or manual pages. The port number is usually 110.) If your =
\nmail server requires an SSL (secure) connection, precede your mail =
\nserver address with <\/span>ssl:\/\/<\/span>, e.g. =
\n<\/span>ssl:\/\/pop.example.com<\/span>. <\/span>Next, enter the login name<\/i> and =
\npassword<\/i> for your new e-mail account =
\n.<\/span><\/p>\n

NOTE:<\/span><\/b> In the =
\nLogin Name field, use the full e-mail address (e.g., <\/span>user@example.com<\/span>).<\/span><\/p>\n

Choose the default category that will be =
\nassigned to posts submitted via e-mail. <\/span>Click Update Options<\/b> . <\/p>\n

NOTE:<\/span><\/b> If you are using the <\/span>Administration<\/span> > <\/span>Settings<\/span> > <\/span>Writing<\/span> > <\/span>Post via =
\ne-mail section<\/span> to specify the e-mail =
\naddress before<\/i> you’ve actually created the e-mail account, =
\nremember to use the same login and password when you create the account =
\nas you specified in the section.<\/span><\/p>\n

Step 3 – Publish Your E-mail =
\nPosts <\/span><\/span><\/span><\/p>\n

You’ve created the new e-mail account and configured your =
\nWordPress blog to accept e-mails from that account, but you still need =
\nto set up WordPress to publish those e-mail messages on your blog. Do =
\none of the following: <\/span><\/p>\n

Manual Browser Activation<\/span><\/span><\/span><\/p>\n

Go to the =
\nfollowing link <\/span>http:\/\/example.com\/ins=
\ntalldir\/wp-mail.php<\/span> immediately after =
\nyou send an e-mail to your new e-mail account. (Note:<\/b> You must do =
\nthis every time you send a new post.) <\/span><\/p>\n

Automated Browser Activation<\/span><\/span><\/span><\/p>\n

An alternative =
\nto manual browser activation is to add the following iframe code to the =
\nfooter of your blog: <\/span><\/p>\n

<iframe =
\nsrc=3D"<\/span>http:\/\/yourblogdomain\/wordpressinstalldir\/wp-mail.php<\/span>=
\n<\/span>" name=3D"mailiframe" =
\nwidth=3D"0" height=3D"0" frameborder=3D"0" =
\nscrolling=3D"no" =
\ntitle=3D""><\/iframe><\/span> =
\n<\/span><\/p>\n

Edit the above line of code =
\nso that it refers to the location of your wp-mail.php file. Add this =
\nline of code to the footer.php file in the directory for whatever theme =
\nyou are using (don’t include it within an HTML paragraph). =
\n<\/span><\/p>\n

You may have to refresh your =
\nblog to see the new post. New users may find this method the most =
\nhelpful. <\/span><\/p>\n

If you’re using or =
\nwould like to use the <\/span>Postie Plugin<\/span> for WordPress, =
\nuse the following iframe code, which will call Postie’s check mail =
\ncommands: <\/span><\/p>\n

<iframe =
\nsrc=3D"<\/span>http:\/\/yourblogdomain\/wordpressinstalldir\/wp-content\/plugins=
\n\/postie\/get_mail.php?Submit=3DRun+Postie<\/span>" name=3D"mailiframe" width=3D"0" =
\nheight=3D"0" frameborder=3D"0" =
\nscrolling=3D"no" title=3D""> <\/iframe> =
\n<\/span><\/p>\n

Add this code to your =
\nfooter, and the next time anyone goes to your blog, your new emails will =
\nbe automatically posted, so you need to do nothing but send them. You =
\nmay have to refresh the blog to see the changes. =
\n<\/span><\/p>\n

Action-based =
\n<\/span><\/span>functions.php<\/span> Activation <\/span><\/span><\/span><\/p>\n

An alternative =
\nto calling the <\/span>iframe<\/span> on =
\nevery page load (detailed above), or setting up a cron job (details =
\nbelow), you can add an action to your active theme’s <\/span>functions.php<\/span> file. This will check for mail every 15 minutes and does =
\nnot add any HTML to your theme. <\/span><\/p>\n

add_action(‘shutdown’, =
\n‘retrieve_post_via_mail’);<\/span>function retrieve_post_via_mail() =
\n{<\/span>        flush(); \/\/ =
\nDisplay the page before the mail fetching =
\nbegins<\/span>        =
\nif(get_transient(‘retrieve_post_via_mail’)) { =
\n<\/span>          =
\n     return; \/\/ The mail has been checked recently; =
\ndon’t check again<\/span>        } else { \/\/ The =
\nmail has not been checked in more than 15 =
\nminutes<\/span>          =
\n     $mail =3D =
\nwp_remote_get(get_bloginfo(‘wpurl’).’\/wp-mail.php’);<\/span>          =
\n     if(!is_wp_error($mail)) { \/\/ If retrieve =
\nsucceeded<\/span>          =
\n             =
\nset_transient(‘retrieve_post_via_mail’, 1, 60 * 15); \/\/ check again in =
\n15 minutes.<\/span>          =
\n     } else {<\/span>          =
\n             =
\nset_transient(‘retrieve_post_via_mail’, 1, 60 * 5); \/\/ check again in 5 =
\nminutes; we don’t want to overload the =
\nserver<\/span>          =
\n     }<\/span>        =
\n}<\/span>}<\/span><\/p>\n

This method =
\nis good for users who would like to avoid using cron jobs, which are =
\nconfigured on the server. Unlike cron jobs, this process will only run =
\nwhen pages on the blog are loaded. Cron jobs run independent of site =
\ntraffic.<\/em> <\/span><\/p>\n

WP-Cron Plugin Activation <\/span><\/span><\/span><\/p>\n

Download, =
\ninstall, and activate the <\/span>WP-Cron<\/span> Plugin. It will work =
\nin the background without user intervention to update your site about =
\nevery 15 minutes. <\/span><\/p>\n

NOTE: =
\nWP-CRON is no longer supported by the author<\/span><\/b> <\/span><\/p>\n

Cron Job Activation <\/span><\/span><\/span><\/p>\n

Set up a UNIX =
\ncron job to have your blog periodically view <\/span>http:\/\/example.com\/ins=
\ntalldir\/wp-mail.php<\/span> using a =
\ncommand-line HTTP agent like wget, curl or GET. The command to execute =
\nwill look like: <\/span><\/p>\n

wget -N http:\/\/example.com\/ins=
\ntalldir\/wp-mail.php <\/span><\/p>\n

If =
\nyou use a different program than <\/span>wget<\/span>, =
\nsubstitute that program and its arguments for <\/span>wget<\/span> in this line. <\/span><\/p>\n

Note:<\/span><\/b> Another possibility is =
\nto run "php \/full\/path\/to\/wp-mail.php" in a cronjob. This will =
\nrun the php-script using php, without the need for an extra program to =
\nrun. (You are more likely authorized to run php than wget.) =
\n<\/span><\/p>\n

For more information about =
\nsetting up a cron job, see: <\/span><\/p>\n

Intro=
\n To Cron Jobs Your hosting provider’s FAQ or manual =
\npages <\/span><\/p>\n

Note to =
\nWindows Users:<\/span><\/b> There are similar programs =
\nto cron available if your host runs Windows. For example, <\/span>VisualCron<\/span>, <\/span>Cron for =
\nWindows<\/span> and <\/span>pycron<\/span>. Consult these =
\nprojects’ documentation for further information. =
\n<\/span><\/p>\n

Procmail Activation <\/span><\/span><\/span><\/p>\n

If your server =
\nuses <\/span>procmail<\/span>, a simple =
\n<\/span>.procmailrc<\/span> in =
\nthe blogmailaccounts home directory will be sufficient: =
\n<\/span><\/p>\n

Shell=3D\/bin\/sh<\/span>MAILDIR=3D$HOME\/.maildir\/<\/span>DEFAULT=3D$MAILDIR<\/span>:0<\/span>{<\/span>:0Wc<\/span>.\/<\/span>:0<\/span>| wget -N =
\n<\/span>http:\/\/example.com\/installdir\/wp-mail.php<\/span><\/span>}<\/span><\/p>\n

This could =
\nbe more specific, such as capturing certain subject expressions. Check =
\n<\/span>procmail<\/span> for more =
\ninformation. <\/span><\/p>\n

.qmail Activation <\/span><\/span><\/span><\/p>\n

If your server =
\nuses qmail to process e-mail, you may be able to use it to call =
\nwp-mail.php whenever an e-mail message is delivered. To do this, first =
\ncreate a small shell script to call wp-mail.php. You could call the file =
\n<\/span>wp-mail<\/span>: =
\n<\/span><\/p>\n

#!\/bin\/sh<\/span>\/bin\/sh -c "sleep 5; \/path\/to\/php =
\n\/path\/to\/your\/blog\/wp-mail.php > \/dev\/null" =
\n&<\/span><\/p>\n

The <\/span>sleep<\/span> command causes a 5-second delay to allow qmail to finish =
\nprocessing the message before wp-mail.php is called. Note that the =
\nampersand on the end of the line is required. The above script should go =
\nin your root directory, and the execute bit should be set (chmod 700). =
\nFor debugging purposes, you could change <\/span>\/dev\/null<\/span> to a =
\nfilename to save the output generated by wp-mail.php. =
\n<\/span><\/p>\n

Then all you need to do =
\ncreate\/modify the appropriate .qmail file to call your shell script. Add =
\nthe following line to the .qmail file for your mailbox name: =
\n<\/span><\/p>\n

|\/path\/to\/your\/root\/directory\/wp-mail<\/span><\/p>\n

See your ISP’s documentation for use of .qmail =
\nfiles. Naming conventions may vary for different ISPs. =
\n<\/span><\/p>\n

Email Format<\/span><\/span><\/span><\/p>\n

WordPress will =
\nuse the Subject line of your email for the title of the post, and all =
\nbody of the email will be used as the content of the post, with =
\ncommon HTML tags stripped<\/i>. WordPress will file the post under =
\nwhichever category is selected for "Usual Category" in Step 1, =
\nand will use Site Admin as the poster. <\/span><\/p>\n

Posting by email does not support attachments and any =
\nattachments sent with the email will appear in their raw form in the =
\nblog post. <\/span><\/p>\n

Testing<\/span><\/span><\/span><\/p>\n

To test your =
\nconfiguration, simply send an e-mail to <\/span>yournewaccount@yourmaildomain<\/span> (or to <\/span>user@yourmaildomain<\/span> if you used the <\/span>.qmail<\/span> =
\nforwarding setup). <\/span>Then do the following: <\/p>\n

If you have no automated system set up, =
\nsimply view <\/span>http:\/\/example.com\/ins=
\ntalldir\/wp-mail.php<\/span> in your browser. =
\nThe script should tell you that it found an e-mail, and print details of =
\nthe post it made. Then view your blog again to see your email posted. =
\n<\/span>If you are using an iframe code in your =
\nfooter, refresh your browser to see the new post. =
\n<\/span>If you are using WP-Cron, simply wait =
\nfifteen or twenty minutes. <\/span>If you have a cron job running, wait =
\nuntil the next time it’s scheduled to run (or temporarily edit the cron =
\njob to make it run sooner). If you run tail <\/span>-f =
\n\/var\/log\/cron<\/span> in a terminal, you’ll be =
\nable to see the job create its log entry when it’s finished running. =
\nWhen that happens, just view the site in your web browser to see your =
\nemail posted. <\/span>Your email may be recorded with a post =
\nstatus of ‘Pending Review’ rather than ‘Published’. If the status is =
\n‘Pending Review’, then the post will be visible in the Dashboard but =
\nwill not be visible in the Blog. By default, wp-mail.php will validate =
\nthe sending email address against the email addresses for authorized =
\nusers. If the email address is found, the post status will be =
\n‘Published’, otherwise the status will be ‘Pending Review’. =
\n<\/span>Troubleshooting<\/span><\/span><\/span><\/p>\n

If you receive =
\nthe following error messages, follow the procedures below. =
\n<\/span><\/p>\n

Error =
\nMessage:<\/span><\/b> <\/span><\/p>\n

Ooops POP3: premature NOOP OK, NOT an RFC 1939 Compliant =
\nserver<\/span><\/p>\n

For this error, open =
\n<\/span>wp-includes\/class-pop3.php<\/span> and change this line: <\/span><\/p>\n

if($this->RFC1939) {<\/span><\/p>\n

to this: <\/span><\/p>\n

if(!$this->RFC1939) {<\/span><\/p>\n

Note the exclamation point. =
\n<\/span><\/p>\n

Error =
\nMessage:<\/span><\/b> <\/span>There does not seem to be any new =
\nmail<\/span> <\/span><\/p>\n

This error is a bit of a misnomer – the test just checks to =
\nsee if anything was retrieved. <\/span><\/p>\n

If you’re feeling adventuresome, =
\nopen <\/span><\/p>\n

wp-mail.php<\/span><\/p>\n

and search for: =
\n<\/span><\/p>\n

$count =3D =
\n$pop3->login(get_settings(‘mailserver_login’), =
\nget_settings(‘mailserver_pass’));<\/span><\/p>\n

Change the lines following it to something like: =
\n<\/span><\/p>\n

  if (0 =3D=3D =
\n$count) :<\/span>    echo "There does not seem to be any =
\nnew mail. <br\/>\\n";<\/span>    echo "count =3D $count<br\/> =
\n\\n"; <\/span>    <\/span>echo "$pop3->ERROR =
\n\\n";    =
\nexit;  endif;<\/span><\/p>\n

You’ll =
\nthen be presented with a more informative message. =
\n<\/span><\/p>\n

The e-mail server may be =
\nrefusing connections that attempt to provide an unencrypted password – =
\nlike POP3. If your webserver and e-mail server are on the same physical =
\ncomputer, you can specify <\/span>localhost<\/span> or =
\n<\/span>127.0.0.1<\/span> as =
\nthe mail server. That traffic is assumed to be OK without encryption =
\nbecause it never traveled across the network. =
\n<\/span><\/p>\n

Extensions and Add-ons<\/span><\/span><\/span><\/p>\n

There are =
\nseveral add-ons and hacks that will extend the capabilities of posting =
\nby e-mail with WordPress. Some of these may involve changing the core =
\nfiles, so do it carefully and make backups<\/b>. =
\n<\/span><\/p>\n

Enhanced Functionality Hack<\/span><\/span><\/span><\/p>\n

One =
\nreplacement file for the original <\/span>wp-mail.php<\/span> =
\nfile has been created: <\/span><\/p>\n

Postie<\/span> supports posting to =
\ncategories, automatic removal of email signatures, POP3\/IMAL (+SSL) and =
\nmore. <\/span>Hack E-mail Format<\/span><\/span><\/span><\/p>\n

The following =
\nenhancements may be made to your <\/span>wp-mail.php<\/span> so =
\nyour e-mail will be translated into metadata for your post: =
\n<\/span><\/p>\n

Sender’s =
\ne-mail address <\/span><\/p>\n

The enhanced =
\n<\/span>wp-mail.php<\/span> =
\nlooks up the email address you send from in its user database. If there =
\nis a match with any user there, it files the post under that user. If =
\nthere is no match, it drops the e-mail and does not create a post in the =
\nblog. (Great for security and spam prevention.) It is set by the =
\nFrom<\/b> field. <\/span><\/p>\n

Subject line <\/span><\/p>\n

If =
\n<\/span>[n]<\/span> is present =
\nanywhere in the subject line of your email, the e-mail will be filed =
\nunder the category numbered n. Otherwise, it will be posted under =
\nwhichever category is selected for "Usual Category" in Step 1. =
\nExample: [1] This is a Test! would be posted as "This is a =
\nTest!", filed under General. <\/span><\/p>\n

Blog By Email From Yahoo! Mail, =
\nGmail and Hotmail<\/span><\/span><\/span><\/p>\n

By default, =
\nmost web-based email clients send messages in HTML formatting, which =
\nWordPress’s blog-by-email feature filters out. =
\n<\/span><\/p>\n

To get around this, you must =
\nselect "plain text" before sending. =
\n<\/span><\/p>\n

In Yahoo! Mail, the button =
\nfor switching to plain text is just to the right of the SUBJECT field. =
\nIn Gmail a similar button is located at the right end of the text =
\nformatting tool bar. Hotmail’s is found next to the SPELL CHECK button =
\nin the email action bar which is located above the email message.<\/span><\/span><\/p>\n

 <\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

  http:\/\/= codex.wordpress.org\/Post_to_your_blog_using_email   WordPress = can be configured to use e-mail to post to a blog. To enable this = functionality, you need to: Create a dedicated e-mail account to be = used solely for posting to your blog, Configure WordPress to access that = account, and Configure WordPress to publish messages = from […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"_links":{"self":[{"href":"https:\/\/microgecko.isi.com.mx\/index.php?rest_route=\/wp\/v2\/posts\/70"}],"collection":[{"href":"https:\/\/microgecko.isi.com.mx\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/microgecko.isi.com.mx\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/microgecko.isi.com.mx\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/microgecko.isi.com.mx\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=70"}],"version-history":[{"count":2,"href":"https:\/\/microgecko.isi.com.mx\/index.php?rest_route=\/wp\/v2\/posts\/70\/revisions"}],"predecessor-version":[{"id":125,"href":"https:\/\/microgecko.isi.com.mx\/index.php?rest_route=\/wp\/v2\/posts\/70\/revisions\/125"}],"wp:attachment":[{"href":"https:\/\/microgecko.isi.com.mx\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=70"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/microgecko.isi.com.mx\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=70"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/microgecko.isi.com.mx\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=70"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}