While I can't give you the technical reason for this happening, I can
share what I beleive as well as know happens.
I think that the popper flags something within the mail file so that it
knows you checked the message without removing it from the server, and
while popper one read messages 1 - 10 the new popper has not.
Now if popper 2 checks mail, it sees lets say messages 1 - 15 ( 5 new
ones since popper 1 read it), it flags those messages, and then the next
time it already knows about 1-15.
So the good news is once everyone has taken 1 pass at the old messages
not removed from the server, they will not run into that problem again.
This has happened to me even when we went from one version of ipop3d to
another.
Hope that helps, and again it will only happen once to those who left
mail on the server after reading it.
Jack
Randall Gellens wrote:
> At 12:48 PM -0400 7/10/01, Dat B. Tran wrote:
>
> > Hi,
> > Does anyone know why the email clients download emails it
> > already have after i switched from ipop3d server to Qpopper with
> > SSL? How do i prevent this? Is there a work around for this
> > problem? Thanks!
>
> Most likely this is because there are no 'X-UIDL:' headers in the
> spool, or the ones there don't look right to Qpopper. I'm not
> familiar with ipop3d, so I can't give any specific advice, but if you
> can determine the UIDs it uses, you may be able to have a script of
> some sort that adds 'X-UIDL:' headers.
--
___________________________________________________________
Jack Sasportas
Innovative Internet Solutions
Phone 305.665.2500
Fax 305.665.2551
www.innovativeinternet.com
www.web56.net
