WordPress › Support » Post via email

William
Member
Posted 5 years ago #

Hi all.
Has anyone resolved the error message in wp-mail.php, which should poll a POP3 server to download an entry? It goes like this:
Ooops POP3: premature NOOP OK, NOT an RFC 1939 Compliant server
My hosters, Gradwell.com, were suprised of the problem (they too use WP, but haven't yet needed to use the Post By Email feature). I'm running RC1. Any ideas or suggestions welcome!
Thanks
Will

mriannnnnn
Member
Posted 5 years ago #

I am also seeing this error. What can we do to resolve this issue and can some one explain why it is happening.

mriannnnnn
Member
Posted 5 years ago #

I hate to push this but... :-P
Is it an issue with my server or WP? Is there anything that I can do to adjust the code to accommodate what my server can do?

carthik
Member
Posted 5 years ago #

Try changing the username from example@example.com to just example
if you see what I mean.
For me, it works on one mailserver, and on the other, it gives me the error described here.
I think when a script tries to access the mailserver and the mailserver doesn't like it/something's wrong, this error is generated, but I am not absolutely sure

mriannnnnn
Member
Posted 5 years ago #

yeah I get what you mean but the host that I am using does not use the same domain name for the smtp server as for my site so my domain has to be in the username.
*wipes brow* darn run on sentences. heh

William
Member
Posted 5 years ago #

Has anyone received a solid response from WP regarding this?
Will

mriannnnnn
Member
Posted 5 years ago #

Well I have not gotten an email and none other then us have responded to this question.

matt
Troublemaker
Posted 5 years ago #

I haven't been able to recreate this problem. I suspect it's something funky with the server. Do you have another POP3 account you could try it on?

mriannnnnn
Member
Posted 5 years ago #

no I do not have another POP3 server to use.
I'm just not familiar enough with the mail functions of PHP to give feedback on this intelligently. What kind of response is PHP expecting. Could you point me in the right direction? I'll try to figure it out myself. I'll talk to my hosting service. Though all the email that are sent from WP work.
*shrug*

digory
Member
Posted 5 years ago #

To fix, edit wp-includes/class-pop3.php, and change this line:
if($this->RFC1939) {
to this:
if(!$this->RFC1939) {
(add exclamation point).

Anonymous
Unregistered
Posted 5 years ago #

so, i've done this, and I'm still getting the same POP3 error.
any other ideas or solutions ?

Anonymous
Unregistered
Posted 4 years ago #

Just for the record..
I had "Ooops POP3: premature NOOP OK, NOT an RFC 1939"
and the resolution from digory fixed my problem.

anujkp
Member
Posted 4 years ago #

I had the same problem -- "Ooops POP3: premature NOOP OK, NOT an RFC 1939" --

and the solution from Digory fixed the problem.

grinder
Member
Posted 4 years ago #

Digory's modification worked for me also.

rjeffries
Member
Posted 4 years ago #

My ISP recently did a fresh install of WP 1.5 for me.
He ran into this darned "post by email" bug, just liek we did
back when he first installed Wordpress maybe a year or 18 months ago. When will this fix be rolled into production code? It looks liek there is one missing exclamation point?

irishangel
Member
Posted 4 years ago #

I got this same error, and tried digory's solution to no avail.... I'm wondering... can I set up a pop 3 acct on my isp with name of the
"postaccount"? it would be much easier to post via email.... a feature I was truly looking forward to utilitizing..
My ISP doesn't host my blog however..

crimespree
Member
Posted 4 years ago #

I posted another question before I found this post, Digory's fix worked for me too... (on v. 1.5)

bepike
Member
Posted 4 years ago #

Digory...YOU ROCK! ahhh the power of the bang...this fix worked for me also.

chenks
Member
Posted 4 years ago #

fixed my problem too

wilf888
Member
Posted 4 years ago #

And it fixed my problem too! Thanks a lot!!!

JakobHede
Member
Posted 4 years ago #

Digory's modification didn't solve my problem, I was still getting the error-message:

Ooops POP3: premature NOOP OK, NOT an RFC 1939

But the modification was inspirational in actually solving the problem.

The short solution:
My fix; edit wp-includes/class-pop3.php, and change these lines:

107 $this->BANNER = $this->parse_banner($reply); 108 $this->RFC1939 = $this->noop();

To

107 $this->BANNER = $this->parse_banner($reply); 108 return true; 109 $this->RFC1939 = $this->noop();

(Insert line 108: return true;)

Now, I'm no certified web-geek, and I don't know php, but here's what I think:
I had to google on "noop rfc 1939" to try to understand what was happening.
You say noop to the mail-server, to verify that it conforms to rfc 1939, by verifying that it responds coherently to the noop request. The code in wp-includes/class-pop3.php apparently assumes that the proper answer is always +OK, and discards the server if it ever replies otherwise. But the problem here stems from the fact that the conflicting noop request is sent in the particular authorization state, where the proper answer apparently is -ERR, as opposed to sending the request in the transaction state, where the proper answer is +OK.
Actually from reading the rfc 1939, it would appear that you should actually never send noop during the authorization state, so that is what my modification achieves: It cuts out a strictness test against the mailserver, that apparently isn't strict itself.
I also developed another - much longer - modification, that modified the code to still carry out the test, but actually expect the right answer : -ERR.
But since that modification is so much more complex, and achieved the same as the simple solution, and I don't know for certain which solution is actually the most correct, and I don't know the particular motivation for performing this strictness test at this point in the mail-transaction, I only offer the simple solution here.

So one could argue that Digory's modification rectifies a banal syntax-error, while my modification hints at a more conceptual problem with the code. Maybe a problem that should be considered to be a bug worthy of a bug-entry, whereever that is... I'll go dig that up... maybe.

Cheers, Jakob.

JakobHede
Member
Posted 4 years ago #

Ahh, I just discovered corroboration in this thread: http://wordpress.org/support/topic/6371#post-38163
And in the two bug-tickets:
http://trac.wordpress.org/ticket/253
http://trac.wordpress.org/ticket/410

mbshafer
Member
Posted 4 years ago #

Jakob,

Thanks for the quick fix (line 108).
Would like to see your more extensive modification that you refer to if you would be so kind as to share it. I'm likewise no PHP guru (in the process of learning) and of course digging through code fixes is a great way to learn.

Cheers!
Mike Shafer

oasis-k
Member
Posted 3 years ago #