On Sat, 27 May 2006 11:54:46 -0700, "Alex Teslik" <alex@xxxxxxxxxxxxxx>
said:
> On Sun, 28 May 2006 00:48:52 +0800, Max Waterman wrote
> > I'm still not getting anywhere with this. If I send a message from
> > another account, it seems to work fine, so now I'm trying to figure out
> > what the difference is in the messages. The body is identical, so it
> > must be something in the header. I tried to duplicate the message I'm
> > sending, but it hasn't made much difference.
> >
> > One message I keep seeing is :
> >
> > "WARNING: Message 1148537537.53 disappeared from POP3 server ..."
> >
> > Can anyone tell me what this means and how to fix it?
>
> inconsistent UIDL handling?
Well, it keeps reporting the same UIDL for the message (though I don't
know how to check internally); but that might be something to do with
it. I was concentrating on the differences between the messages (the one
that works and the one which fails), which seemed to be only in the
header - some 'X-' lines (mostly spam related), and, of course,
'delivered-to' lines, were different, but I couldn't 'set' those in my
sent message.
Clearly, the simple external API of Mail::Box hides enormous internal
complexity making it difficult to debug. It's clear to me that it's a
Mail::Transport::POP3 bug, but I can't prove it or fix it, so I have to
move on. I've altered the design to send the message some other way (not
email).
In any case, like the OP, this latest version seems to give many more
'uninitialised value' warnings than the one I was using before.
Also, I just noticed this seeming self-contradictory message(s) :
"
WARNING: Use moveMessage() or copyMessage() to move between open
folders.
You cannot add a message which is already part of a folder to a new
one. Please use moveTo or copyTo.
"
It seems like there are many ways to do things, but some ways don't work
:(
Another message I keep getting is :
"
ERROR: Server at mail1.nthcode.com:110 does not seem to be talking POP3.
"
which happens when I try to open a connection to the server. I've
concluded that this is because my previous connection was to recent,
since if I wait a while, it works fine. On one server I've tried, it
alternates between success/failure. Perhaps the server is giving a
relevant message, but Mail::Transport::POP3 doesn't understand it - if
so, it might be nice for the error message to reflect what the server is
saying.
Anyway, thanks to all of you who tried to help me :)
I don't suppose this is the end of it though :(
Max.
>
> Alex
|
