Page 1 of 1

popfetcher: weird behaviour

Posted: Sat Mar 25, 2006 11:07 am
by fneumeier
I've just installed the POPfetcher plugin - features are exactly what I need.

My problem now is as follows: I've configured the plugin type "external", only accepting postings from one specific restricted e-mail sender address.

When calling http://mydomain.com/s9y/index.php?/plugin/SECRET_WORD the e-mail is fetched from the POP3 account, resulting in this message:
Number of messages extracted from your mailbox: 1
All messages deleted from your mailbox

E-mail address UNAUTHORIZED_ADDRESS is not the same as configured restriction to RESTRICTED_ADDRESS@web.de. Ignoring mail.
--------------------------------------------------------------------------------
Date: Sat, 25 Mar 2006 10:48:34 +0100
From: UNAUTHORIZED_ADDRESS
Subject: another test, unauthorized.

Published new blog entry with id: 8
The message is showing up in the blog, while it shouldn't because it was not send from the restricted e-mail address.

Even more interesting is that the posting is showing up as "Entry is not yet published" in the admin interface (Entries - Edit Entries). Which by the way also happens when I send the e-mail from the authorized restricted e-mail address.

Any idea what the problem here is? Thanks very much fror your help.

Franz

Re: popfetcher: weird behaviour

Posted: Sun Mar 26, 2006 10:13 pm
by garvinhicking
Hi Franz!

Many thanks for telling us - what you've faced is an actual bug. It did tell you about an unauthorized address, but did not skip the mail.

I just patched that, simply by inserting a "continue" into this block of code:

Code: Select all

             if (!empty($onlyfrom) && trim($from) != trim($onlyfrom)) {
                   echo '<br />'.sprintf(MF_ERROR_ONLYFROM, $from, $onlyfrom);
                   continue;
               }
The second problem about publish/draft state is an issue of how you configured the popfetcher plugin. You should see an option whether to publish or not publish entries inside your configuration screen!? Also make sure you're using version 1.8 at least?

Best regards,
Garvin