pop3 net_socket problem

Mitch Planck wrote:
> I've been using maia for a couple years now (I think
that long) and I've
> always used imap as my auth type and never had a
problem. I've got a
> client now who would like to use pop3 to validate
against their mail
> server.
>  
> Here is the error I get:
> [Fri Jul 28 16:18:46 2006] [error] [client
198.111.178.99] maia:
> 2006-07-28 16:18:46 (EDT) - Notice - fwrite(): send of
6 bytes failed
> with errno=32 Broken pipe at
/usr/local/share/pear/Net/Socket.php line
> [326]\n, referer: http
://gauntlet.ias.net/morley/login.php?lang=en
> This is a FreeBSD 5.1 server with php4.4.2,
apache2.0.58, the latest
> ports of everything, maia 1.00RC6 (old I know but I
don't want to
> upgrade right now although this may force my hand).

The "broken pipe" most likely just means that
your POP server refused
the connection, or that there's no POP server running at
the host and
port you specified.  Double-check your config.php settings
with respect
to the POP3 host and port, and try telnetting to that port
manually to
verify that you can indeed connect and authenticate against
that server.
 There may be firewalling issues or other access controls
blocking the
connection from taking place at all.

If that turns out not to be the case, then you may want to
look at the
PEAR modules you're using.  You're using some pretty old
code,
there--RC6 was issued more than  a year and a half ago, and
much has
changed since then.  I'm not just talking about changes
within Maia--the
modules that Maia relies on have evolved over the years,
too, some of
them incompatibly so.

In the older RC5, POP3 and IMAP were both handled under the
hood by the
University of Washington's IMAP library, so switching from
IMAP to POP3
or vice-versa was no big deal.  As of RC6 (which was never
"official",
just a vague post-RC5 repository checkout point) we had
switched to
using PEAR::Net_POP3 and PEAR::Net_IMAP, which are
separately maintained
modules.  Both of these rely on PEAR::Net_Socket, but there
may be
version-related interactions getting in the way.

The next thing I'd try is to upgrade Net_POP3 and
Net_Socket to their
latest versions, on the theory that those should be most
likely to work
together.  On the other hand, if Net_Socket has been
actively maintained
but Net_POP3 has been neglected for a year or more, you may
need to back
down to an older version of Net_Socket in order to find one
that works
with Net_POP3.  For reference, I'm using POP3 here, with
Net_POP3 1.3.6
and Net_Socket 1.0.6 without problems.

If all else fails, then an upgrade of the whole Maia package
and its new
prerequisites wouldn't be an altogether bad idea, if only
for the
insights that the newer configtests could offer you.


> One thing I noticed was that when running the
configtest.php it detects
> everything until I run pear upgrade-all and then it
thinks that
> Net_SMTP, Log, & Auth_SASL are not installed.
Before running it had
> slightly older versions of those and other modules from
the ports tree.

Nothing surprising there; the PEAR package format changed
over the past
year, so newer versions of PEAR modules are described in
ways that your
old RC6-era configtest can't read.  That doesn't mean Maia
can't /use/
those modules, it just means the configtest report isn't
accurate for
those items.

-- 
Robert LeBlanc <rjlrenaissoft.com>
Renaissoft, Inc.
Maia Mailguard <http://www.maiamail
guard.com/>

_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

> -----Original Message-----
> From: Robert LeBlanc [mailto:rjlrenaissoft.com] 
> Sent: Sunday, July 30, 2006 4:04 PM
> To: Mitch Planck
> Cc: maia-usersrenaissoft.com
> Subject: Re: [Maia-users] pop3 net_socket problem
> 
> Mitch Planck wrote:
> > I've been using maia for a couple years now (I
think that long) and 
> > I've always used imap as my auth type and never
had a problem. I've 
> > got a client now who would like to use pop3 to
validate 
> against their 
> > mail server.
> >  
> > Here is the error I get:
> > [Fri Jul 28 16:18:46 2006] [error] [client
198.111.178.99] maia:
> > 2006-07-28 16:18:46 (EDT) - Notice - fwrite():
send of 6 
> bytes failed 
> > with errno=32 Broken pipe at 
> /usr/local/share/pear/Net/Socket.php line 
> > [326]\n, referer: http
://gauntlet.ias.net/morley/login.php?lang=en
> > This is a FreeBSD 5.1 server with php4.4.2,
apache2.0.58, 
> the latest 
> > ports of everything, maia 1.00RC6 (old I know but
I don't want to 
> > upgrade right now although this may force my
hand).
> 
> The "broken pipe" most likely just means
that your POP server 
> refused the connection, or that there's no POP server
running 
> at the host and port you specified.  Double-check your 
> config.php settings with respect to the POP3 host and
port, 
> and try telnetting to that port manually to verify that
you 
> can indeed connect and authenticate against that
server.
>  There may be firewalling issues or other access
controls 
> blocking the connection from taking place at all.
> 
> If that turns out not to be the case, then you may want
to 
> look at the PEAR modules you're using.  You're using
some 
> pretty old code,
> there--RC6 was issued more than  a year and a half ago,
and 
> much has changed since then.  I'm not just talking
about 
> changes within Maia--the modules that Maia relies on
have 
> evolved over the years, too, some of them incompatibly
so.
> 
> In the older RC5, POP3 and IMAP were both handled under
the 
> hood by the University of Washington's IMAP library,
so 
> switching from IMAP to POP3 or vice-versa was no big
deal.  
> As of RC6 (which was never "official", just
a vague post-RC5 
> repository checkout point) we had switched to using 
> PEAR::Net_POP3 and PEAR::Net_IMAP, which are separately

> maintained modules.  Both of these rely on
PEAR::Net_Socket, 
> but there may be version-related interactions getting
in the way.
> 
> The next thing I'd try is to upgrade Net_POP3 and
Net_Socket 
> to their latest versions, on the theory that those
should be 
> most likely to work together.  On the other hand, if 
> Net_Socket has been actively maintained but Net_POP3
has been 
> neglected for a year or more, you may need to back down
to an 
> older version of Net_Socket in order to find one that
works 
> with Net_POP3.  For reference, I'm using POP3 here,
with 
> Net_POP3 1.3.6 and Net_Socket 1.0.6 without problems.
> 
> If all else fails, then an upgrade of the whole Maia
package 
> and its new prerequisites wouldn't be an altogether
bad idea, 
> if only for the insights that the newer configtests
could offer you.

This is what I wound up doing. I did the latest trunk
version and had no
problems with the database upgrade, just a few module
install and path
issues which weren't to hard to clear up.

After getting it all running again I tried pop3 against my
server and it
worked fine, then against my client's server and got the
same exact error
message. I then tried another outside pop3 server (comcast)
and it worked
fine. So it looks like my client's server (LotusNotes)
doesn't like working
with Pear-Net_POP3.

After banging my head on the wall for a while I found an old
program called
perdition, which is a pop3 (and other) proxy. With this
program's very lame
documentation it took me several hours to configure it but
it works without
having two separate config.php files as well. I'm using a
setup where it
looks at the email address used to login, if it's from my
client's domain it
uses their pop3 server, if not, my pop3 server. I'm
guessing that the pop3
implementation works better with LotusNotes than the pear
version.

Best regards,
Mitch Planck
Ias.net

_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users