Title: noop problem
Last modified: August 18, 2016

---

# noop problem

 *  [aleinside](https://wordpress.org/support/users/aleinside/)
 * (@aleinside)
 * [21 years, 10 months ago](https://wordpress.org/support/topic/noop-problem/)
 * hi guys, i’m an italian really happy user.
    i try to update my blog via mail,
   but if the mail server was different by the mail domain, i get an error “premature
   noop ok etc etc”. so i have commented this piece of code (for all three times
   in the file class-pop3.php) and now the wp-mail work right! /*$this->RFC1939 
   = $this->noop(); if($this->RFC1939) { $this->ERROR = _(“POP3: premature NOOP 
   OK, NOT an RFC 1939 Compliant server”); $this->quit(); return false; } else*/
   i don’t know if my method is right, but it works 😉 P.S. is there a function 
   that return, not print, the post, title, author? a sort of the_content(), the_author(),
   but with a return value? P.P.S. sorry for my bad english 😀

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Anonymous
 * [21 years, 10 months ago](https://wordpress.org/support/topic/noop-problem/#post-57289)
 * I commented out just the following part:
    ` if($this->RFC1939) { $this->ERROR
   = _("POP3: premature NOOP OK, NOT an RFC 1939 Compliant server"); $this->quit();
   return false; } else And it works fine, as that’s the part that makes it fail.
   Also, I only did this in the connect function, and have had no problems. Elsewhere,
   it just might not be a problem checking the noops, only when connecting. It’s
   odd that we tell it to noop though, then complain about it doing so.
 *  [Lorelle](https://wordpress.org/support/users/lorelle/)
 * (@lorelle)
 * [21 years, 5 months ago](https://wordpress.org/support/topic/noop-problem/#post-57570)
 * Can anyone tell me if the above “commented out” of the POP3 error actually works?
   I’m having the same problems as many others getting the email function to work
   as my server (ipowerweb) doesn’t seem to have an updated POP3 server. So if this
   works, then I’ll use it.
    Thanks, Lorelle
 *  [loneboat](https://wordpress.org/support/users/loneboat/)
 * (@loneboat)
 * [20 years, 11 months ago](https://wordpress.org/support/topic/noop-problem/#post-57603)
 * —I commented out just the following part:
    —if($this->RFC1939) { —$this->ERROR
   = _(“POP3: premature NOOP OK, NOT an RFC 1939 Compliant server”); —$this->quit();—
   return false; —} else
 * I used the above method, and it worked like a charm…
 *  [Lorelle](https://wordpress.org/support/users/lorelle/)
 * (@lorelle)
 * [20 years, 11 months ago](https://wordpress.org/support/topic/noop-problem/#post-57604)
 * Let’s see, I posted this in November of 2004 and now I’m getting an answer …and
   people complain that their questions never get answered. Gees. 😉
 * BTW, I never did get this to work, but I have to figure it out so it’s a good
   reminder, even seven months later.
 *  [nealp](https://wordpress.org/support/users/nealp/)
 * (@nealp)
 * [20 years, 7 months ago](https://wordpress.org/support/topic/noop-problem/#post-57617)
 * I experienced the exact same error on my HostExcellence.com installation and 
   the modification suggested above worked for me as well.
 *  [jakobhede](https://wordpress.org/support/users/jakobhede/)
 * (@jakobhede)
 * [20 years, 7 months ago](https://wordpress.org/support/topic/noop-problem/#post-57618)
 * The same solution of preventing the noop test during authorization also worked
   for me.
    IOW: Just skip from line 108 in the `connect` function. I wrote about
   it there: [http://wordpress.org/support/topic/5436](http://wordpress.org/support/topic/5436)
   It appears that this code is a needless obstacle to itself, and that it would
   better help people getting it to work, if it was changed to stop trying so hard
   to refuse the mailserver.
 *  [oasis-k](https://wordpress.org/support/users/oasis-k/)
 * (@oasis-k)
 * [20 years, 4 months ago](https://wordpress.org/support/topic/noop-problem/#post-57627)
 * Nope… commenting out didn’t work for me… has anyone tried these solutions and
   failed and then found another way. I’ve tried all 3 fixes so far and nothing 
   works

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘noop problem’ is closed to new replies.

 * 7 replies
 * 7 participants
 * Last reply from: [oasis-k](https://wordpress.org/support/users/oasis-k/)
 * Last activity: [20 years, 4 months ago](https://wordpress.org/support/topic/noop-problem/#post-57627)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics