headers
qpopper-request | 1 Apr 2005 10:01
Favicon

Qpopper Monthly Help File

         M O N T H L Y   Q P O P P E R   L I S T   H E L P

Addresses:
----------

Email addresses for this particular list server:

  List server:           qpopper-request <at> lists.pensive.org
  Everyone on the list:  qpopper <at> lists.pensive.org
  Human in charge:       listmaster <at> lists.pensive.org

Virtually,
The List Server Admin <listmaster <at> lists.pensive.org>
Permalink | Reply | 0 comments |
headers
Roy_Harrison | 1 Apr 2005 22:12

Mail Relay not allowed

This is stumping me. I have the machine/network I'm sending from in the 
/etc/mail/relay-domains..this has worked fine for generic sendmail and I 
swear it did on an earlier test of qpopper. Now I get the following back 
from my client when I try to send mail to an address outside of my domain 
(rlg.org).:

The following addresses had permanent fatal errors -----
<thinkgreen <at> threeparty.org>
    (reason: 550 Mail relay not allowed)

I can send email to another mail server in my network..like the one I'm 
sending this email from.

This seems to be a very basic RTFM type of issue but the FM ain't telling 
me anything about relaying.

Thanks Ahead of time

Roy
Permalink | Reply | 1 comment |
headers
Roy_Harrison | 1 Apr 2005 22:24

Re: Mail Relay not allowed

Duh Roy...this is Qpopper...not sendmail no wonder it doesn;t have 
anything about relaying.
I wish I had this conversation before I hit send :-)

Peace

Roy

Roy_Harrison <at> notes.rlg.org
04/01/2005 12:12 PM

        To:     Subscribers of Qpopper <qpopper <at> lists.pensive.org>
        cc: 
        Subject:        Mail Relay not allowed

This is stumping me. I have the machine/network I'm sending from in the
/etc/mail/relay-domains..this has worked fine for generic sendmail and I
swear it did on an earlier test of qpopper. Now I get the following back
from my client when I try to send mail to an address outside of my domain
(rlg.org).:

The following addresses had permanent fatal errors -----
<thinkgreen <at> threeparty.org>
(reason: 550 Mail relay not allowed)

I can send email to another mail server in my network..like the one I'm
sending this email from.

This seems to be a very basic RTFM type of issue but the FM ain't telling
me anything about relaying.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Phil Kemp | 18 Apr 2005 20:50

I/O EOF Help - I'm stuck...

I am using qpopper on a linux RH 7.1 system and had been having no problems 
with it up until a couple of weeks ago. 

I typically access the linux machine from a winXP box. Eudora worked fine, 
Outlook worked fine, telnet to port 110 worked fine. 

Now for some reason that I cannot determine, the pop session abnormally 
terminates at the point where the messages are being retrieved. Telnet 
sessions to port 110 show that the login process succeeds, the LIST command 
shows the messages. 

Once I issue the RETR command the connection drops. 

I have compiled in and turned on debug and have the log files. I hesitate to 
post them in case this is known issue. I have googled it and found spotty 
references but nothing definitive.. 

I should note that this behaviour is seen on two different net interfaces on 
the winxp box, with and without the firewall. I am running SP2, but the 
behaviour was also present on SP1. Disabling Symantec Virus does nothing 
either... 

I am completely stumped... 

BTW, Eudora happily sends email via SMTP and my web access is fine using 
browsers and other program.... 

Any help would be most appreciated.. 

Cheers
(Continue reading)

Permalink | Reply | 1 comment |
headers
Phil Kemp | 18 Apr 2005 21:42

Re: I/O EOF Help - I'm stuck...

On Mon, 18 Apr 2005 15:23:19 -0400 (EDT), Sylvain Robitaille wrote
> On Mon, 18 Apr 2005, Phil Kemp wrote:
> 
> > Now for some reason that I cannot determine, the pop session abnormally
> > terminates at the point where the messages are being retrieved. Telnet
> > sessions to port 110 show that the login process succeeds, the LIST
> > command shows the messages.
> >
> > Once I issue the RETR command the connection drops.
> 
> This is when issuing RETR during a telnet session to the POP server?

Yes..

> Does it happen regardless of the message you're asking to RETR, or only
> with one (or more) specific message(s)? 

Any message

> Are you able to verify that 
> the mail spool isn't corrupted somehow?

Yes the spool is fine. openmail, elm, mutt, and mail all read it fine.

> 
> I'll be interested in seeing what more you find about this.  I've 
> seen what I think is similar behaviour as you describe, but from 
> what I'm able to see it has always looked to me as though the 
> *client* is dropping the connection ...
(Continue reading)

Permalink | Reply | 6 comments |
headers
Sylvain Robitaille | 18 Apr 2005 21:23
Picon
Picon

Re: I/O EOF Help - I'm stuck...

On Mon, 18 Apr 2005, Phil Kemp wrote:

> Now for some reason that I cannot determine, the pop session abnormally
> terminates at the point where the messages are being retrieved. Telnet
> sessions to port 110 show that the login process succeeds, the LIST
> command shows the messages.
>
> Once I issue the RETR command the connection drops.

This is when issuing RETR during a telnet session to the POP server?
Does it happen regardless of the message you're asking to RETR, or only
with one (or more) specific message(s)?  Are you able to verify that the
mail spool isn't corrupted somehow?

I'll be interested in seeing what more you find about this.  I've seen
what I think is similar behaviour as you describe, but from what I'm
able to see it has always looked to me as though the *client* is
dropping the connection ...

--

-- 
----------------------------------------------------------------------
Sylvain Robitaille                              syl <at> alcor.concordia.ca

Systems analyst                                   Concordia University
Instructional & Information Technology        Montreal, Quebec, Canada
----------------------------------------------------------------------
Permalink | Reply | 0 comments |
headers
Sylvain Robitaille | 19 Apr 2005 19:03
Picon
Picon

Re: I/O EOF Help - I'm stuck...

On Mon, 18 Apr 2005, Phil Kemp wrote:

> See the attached file for the debug log output...

Well, it all looks "normal" to me until this line:

   Apr 18 10:45:02 nakiska popper[24011]: I/O error flushing output to
       client kemp at ...: Operation not permitted (1) [pop_send.c:689]

The relevant code of pop_send.c is:

    664 /*
    665  *  Flush the output that might be buffered to client
    666  */
    667 void
    668 pop_write_flush ( POP *p )
    669 {
    670     int rslt = 0;
    ...
    681         rslt = fflush ( p->output );
    ...
    684     if ( rslt == EOF ) {
    ...
    689             pop_log ( p, POP_NOTICE, HERE, ... );
    ...
    694         hangup = TRUE;
    695     } /* flush failed */
    ...
    700 }
(Continue reading)

Permalink | Reply | 0 comments |
headers
Randall Gellens | 20 Apr 2005 20:23

Re: I/O EOF Help - I'm stuck...

The log snippit starts with Qpopper cleaning up the connection.  It 
would be helpful to see what happened prior to that point, especially 
what it was that made Qpopper start cleaning up.  Was it a QUIT?  A 
client disconnect?  A HUP singal?
--

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly-selected tag: ---------------
It wasn't as easy to get programs right as we had thought.
                                           --Wilkes, 1949
Permalink | Reply | 4 comments |
headers
Phil Kemp | 20 Apr 2005 21:15

Re: I/O EOF Help - I'm stuck...

It was definitley not a QUIT..

I'm beginning to believe that it was a client disconnect. It's very hard to 
tell why.... on the client machine ALL POP3 clients fail. Eudora, Outlook 
2003, and a Telnet to port 110..

All net traffic is fine... ftp, http, CIFS.. They all work fine and at full 
bandwidth..

I'll look into the HUP on linux side...

More when I get more data..

thanks
PK

On Wed, 20 Apr 2005 11:23:20 -0700, Randall Gellens wrote
> The log snippit starts with Qpopper cleaning up the connection.  It 
> would be helpful to see what happened prior to that point, 
> especially what it was that made Qpopper start cleaning up.  Was it 
> a QUIT?  A client disconnect?  A HUP singal?
> -- 
> Randall Gellens
> Opinions are personal;    facts are suspect;    I speak for myself only
> -------------- Randomly-selected tag: ---------------
> It wasn't as easy to get programs right as we had thought.
>                                            --Wilkes, 1949

--
Phil Kemp
(Continue reading)

Permalink | Reply | 3 comments |
headers
Randall Gellens | 20 Apr 2005 23:26

Re: I/O EOF Help - I'm stuck...

At 12:15 PM -0700 4/20/05, Phil Kemp wrote:

>  It was definitley not a QUIT..
>
>  I'm beginning to believe that it was a client disconnect. It's very hard to
>  tell why.... on the client machine ALL POP3 clients fail. Eudora, Outlook
>  2003, and a Telnet to port 110..

Interesting that all clients fail.

I'd suggest a client-side trace or a TCP packet trace.  Or, a kernel 
trace on the server side (run Qpopper on a new port and run it via 
ktrace, truss, or the equivalent on your platform).

To enable client-side tracing in Eudora:

On Macs, drag the "esoteric settings" plug-in (which comes with 
Eudora) from the "Extra Plugins" folder to the "Eudora Stuff" folder. 
Quit and restart Eudora. Then in your Eudora settings go to 
"Logging". Check "all bytes transferred".

On Windows, move the "esoteric.epi" plug-in (which comes with Eudora) 
from the "extrastuff" folder to the same folder as the "eudora.exe" 
file. Quit and relaunch Eudora. Then in your Eudora settings go to 
"Logging". Check "all bytes sent" and "all bytes received".
Permalink | Reply | 1 comment |

Gmane