headers
qpopper-request | 1 Jul 2006 09:02
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
Randall Gellens | 9 Jul 2006 04:12

Re: Failure to POP mail

At 6:48 PM -0400 6/19/06, Gerard E. Seibert wrote:

>  OS: FreeBSD 6.1 Stable
>
>  I am not sure if this is a qpopper problem or not. I have several 
> accounts that I use 'fetchmail' to gather for me. One of these 
> accounts can grow quite large. All too frequently, when I attempt 
> to POP mail from this account from another computer on my network, 
> the action fails. This is the message I find in the 
> /var/log/messages file:
>
>  Jun 19 18:21:50 seibercom qpopper[2839]: I/O error flushing output 
> to client spamcop at boss [192.168.0.3]: Operation not permitted (1)

I think that generally means the client has disconnected, often 
because it timed out, and Qpopper never got a SIGHUP.  Are you 
running the latest Qpopper?  There were some bugs fixed that closed 
some situations in which Qpopper didn't get the signal.

>
>  'spamcop' is the name of the account and 'Boss' is one of the 
> computers on the network.
>
>  If I attempt to open the file with 'pico' I receive an error 
> message that the file has a long line.

You normally wouldn't expect a spool to have lines that long.  That 
does suggest some sort of corruption.

>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Randall Gellens | 9 Jul 2006 03:49

Re: max username length

At 10:20 AM +0100 6/2/06, Obantec Support wrote:

>  What is the maximum length of usernames qpopper 4.0.8 can handle?

Qpopper generally limits usernames to 64 bytes.

--

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly-selected tag: ---------------
    The highlight of the annual Computer Bowl occurred when Bill Gates,
who was a judge, posed the following question to the contestants:
    "What contest, held via Usenet, is dedicated to examples of weird,
obscure, bizarre, and really bad programming?"
    After a moment of silence, Jean-Louis Gassee (ex-honcho at Apple)
hit his buzzer and answered "Windows."
                                          --Recounted by Adam C. Engst
Permalink | Reply | 0 comments |
headers
Randall Gellens | 9 Jul 2006 03:56

Re: lock files 4.0.8 on FC3

At 8:39 AM +0100 6/4/06, Obantec Support wrote:

>  Can someone tell me what the lock files look like on qpopper
>  dovecot used .username.lock but i have yet to see any sign of qpopper
>  creating a lock file.
>
>  the tempfile .username.pop is working and chmod -rw-rw--.... and i see
>  username go to 0bytes while this is in progress but no sign of a lock file?
>
>  my LDA is procmail and i recall it looks for username.lock to hold of
>  writing to the mbox.

Qpopper creates a lock file which is the name of the spool file with 
".lock" appended.  But the spool is only locked while the contents 
are copied to or from the temp drop, so it may be hard to catch if 
you're watching for it.  You can enable Qpopper tracing to see it 
create and release the lock.

--

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly-selected tag: ---------------
There is always an easy solution to every human problem -- neat,
plausible, and wrong.                            --H.L. Mencken
Permalink | Reply | 0 comments |
headers
Randall Gellens | 9 Jul 2006 04:05

Re: moving .pop files to a new location on a live server

At 8:29 PM +0100 6/11/06, Obantec Support wrote:

>  Hi
>
>  I am having file lock problems. 1 customer has a soft quota of 50MB and hard
>  limit of 100MB and a 27MB mbox file.
>
>  a snip of the logs shows
>
>  Jun 11 12:00:46 proteus2 popper[6328]: martinco at 82.45.254.97
>  (82.45.254.97): -ERR POP timeout from myservers.name.here
>  Jun 11 19:27:25 proteus2 popper[4862]: (v4.0.8) Timeout (120 secs) during nw
>  read from martinco at 82.45.254.97 (82.45.254.97)
>  Jun 11 19:27:25 proteus2 popper[4862]: martinco at 82.45.254.97
>  (82.45.254.97): -ERR POP timeout from myservers.name.here
>  Jun 11 20:06:48 proteus2 popper[7819]: martinco at 82.45.254.97
>  (82.45.254.97): -ERR [IN-USE] /var/mail/.martinco.pop lock busy!  Is another
>  session active? (11)

Hi Mark,

I'm a bit confused.  The 20:06:48 session should have been fine, 
since the 19:27:25 session should have ended after the timeout.  Was 
the popper process for the user still active?  Also, what does the 
spool being locked have to do with quotas?

>  i need to resolve this by using a separate location for the .pop files with
>  no quotas.
>  i have the space on a second drive that is not using quotas.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
DebianTech | 18 Jul 2006 19:38
Picon

Deleting Email

I've always been bothered by this and I'm not sure if there is a way to 
fix it so..

When a mail user sets their email client to leave messages on the server 
but delete then when they are removed from their trash bin, the messages 
don't get removed. Using default settings that remove the messages when 
received works. Is there something i can do to make this work?
Permalink | Reply | 1 comment |
headers
Gerard | 18 Jul 2006 20:41
X-Face
Favicon

Qpopper continually fails to POP mail from large mbox

Using FreeBSD 6.1 STABLE

I am continuing to have a problem with qpopper getting mail from an mbox
once the file grows to any sizable capacity

This is an excerpt from the /var/log/messages file:

Jul 18 08:36:47 seibercom qpopper[894]: gerard at 192.168.0.3 (192.168.0.3): -ERR POP EOF or I/O Error
Jul 18 08:36:47 seibercom qpopper[894]: Stats: gerard 0 0 143 30288106 192.168.0.3 192.168.0.3
Jul 18 08:36:50 seibercom qpopper[894]: I/O error flushing output to client gerard at 192.168.0.3
[192.168.0.3]: Operation not permitted (1)

The recourse I have is to manually delete the contents of the mailbox. I
have the latest version of qpopper installed. I am unsure as to where I
could post this problem to other than here. I would like to post a bug
report, but I am not sure as to where to place it.

Perhaps someone could assist me.

Ciao!

--

-- 
Gerard Seibert
gerard <at> seibercom.net
Permalink | Reply | 1 comment |
headers
Daniel Senie | 18 Jul 2006 22:14

Re: Qpopper continually fails to POP mail from large mbox

At 02:41 PM 7/18/2006, Gerard wrote:
>Using FreeBSD 6.1 STABLE
>
>I am continuing to have a problem with qpopper getting mail from an mbox
>once the file grows to any sizable capacity
>
>This is an excerpt from the /var/log/messages file:
>
>Jul 18 08:36:47 seibercom qpopper[894]: gerard at 192.168.0.3 
>(192.168.0.3): -ERR POP EOF or I/O Error
>Jul 18 08:36:47 seibercom qpopper[894]: Stats: gerard 0 0 143 
>30288106 192.168.0.3 192.168.0.3
>Jul 18 08:36:50 seibercom qpopper[894]: I/O error flushing output to 
>client gerard at 192.168.0.3 [192.168.0.3]: Operation not permitted (1)

This message most commonly indicates the client gave up and went 
away. Perhaps your customer is giving up because you're trying to 
push 30MB of data to them?

>The recourse I have is to manually delete the contents of the mailbox. I
>have the latest version of qpopper installed. I am unsure as to where I
>could post this problem to other than here. I would like to post a bug
>report, but I am not sure as to where to place it.

This issue has been discussed at length. Generally the issue is not 
qpopper's fault. You haven't mentioned what version of qpopper you're 
running, though, it's also possible you're running an older version.
Permalink | Reply | 0 comments |
headers
Daniel Senie | 19 Jul 2006 00:36

Re: Qpopper continually fails to POP mail from large mbox

At 06:29 PM 7/18/2006, Gerard wrote:
>Daniel Senie <dts <at> senie.com>
>
> > At 02:41 PM 7/18/2006, Gerard wrote:
> > >Using FreeBSD 6.1 STABLE
> > >
> > >I am continuing to have a problem with qpopper getting mail from an mbox
> > >once the file grows to any sizable capacity
> > >
> > >This is an excerpt from the /var/log/messages file:
> > >
> > >Jul 18 08:36:47 seibercom qpopper[894]: gerard at 192.168.0.3
> > >(192.168.0.3): -ERR POP EOF or I/O Error
> > >Jul 18 08:36:47 seibercom qpopper[894]: Stats: gerard 0 0 143
> > >30288106 192.168.0.3 192.168.0.3
> > >Jul 18 08:36:50 seibercom qpopper[894]: I/O error flushing output to
> > >client gerard at 192.168.0.3 [192.168.0.3]: Operation not permitted (1)
> >
> > This message most commonly indicates the client gave up and went
> > away. Perhaps your customer is giving up because you're trying to
> > push 30MB of data to them?
> >
> >
> > >The recourse I have is to manually delete the contents of the mailbox. I
> > >have the latest version of qpopper installed. I am unsure as to where I
> > >could post this problem to other than here. I would like to post a bug
> > >report, but I am not sure as to where to place it.
> >
> > This issue has been discussed at length. Generally the issue is not
> > qpopper's fault. You haven't mentioned what version of qpopper you're
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gerard | 19 Jul 2006 00:29
X-Face
Favicon

Re: Qpopper continually fails to POP mail from large mbox

Daniel Senie <dts <at> senie.com>

> At 02:41 PM 7/18/2006, Gerard wrote:
> >Using FreeBSD 6.1 STABLE
> >
> >I am continuing to have a problem with qpopper getting mail from an mbox
> >once the file grows to any sizable capacity
> >
> >This is an excerpt from the /var/log/messages file:
> >
> >Jul 18 08:36:47 seibercom qpopper[894]: gerard at 192.168.0.3 
> >(192.168.0.3): -ERR POP EOF or I/O Error
> >Jul 18 08:36:47 seibercom qpopper[894]: Stats: gerard 0 0 143 
> >30288106 192.168.0.3 192.168.0.3
> >Jul 18 08:36:50 seibercom qpopper[894]: I/O error flushing output to 
> >client gerard at 192.168.0.3 [192.168.0.3]: Operation not permitted (1)
> 
> This message most commonly indicates the client gave up and went 
> away. Perhaps your customer is giving up because you're trying to 
> push 30MB of data to them?
> 
> 
> >The recourse I have is to manually delete the contents of the mailbox. I
> >have the latest version of qpopper installed. I am unsure as to where I
> >could post this problem to other than here. I would like to post a bug
> >report, but I am not sure as to where to place it.
> 
> This issue has been discussed at length. Generally the issue is not 
> qpopper's fault. You haven't mentioned what version of qpopper you're 
> running, though, it's also possible you're running an older version.
(Continue reading)

Permalink | Reply | 5 comments |

Gmane