[Perlwebmail-devel] Re: fyi, cvs update

[woodwardj@jaos.org]

>What are the consequences of removing the uidl?
>Does it have to do with the message number being incorrect if mail 
>arrives between two accesses to the mailbox?

Simultaneous arrivals aren't a problem, its just parallel deletes that could be an issue.  

It is not a great issue and would require specific timing, by closing the connection after
deletes, we minimize any issues (just as update/commit regularly helps with shared source
control).  

I think the other advantage people used where uidl's being unique offered unique links in your
browser. 

>Just want to know if the encoding of uidls I have sent as part of a 
>patch is causing problems with qpopper?
>It appears to work for me with qpopper (3.1.2).

Well we are getting to the point that we need to question if we have to escape/encode/decode
everything, or find a better way.  Simply the introduction of uidl support has caused my inbox
to get larger with people having issues.  It seems with different browsers, encodings, etc
there has not been a magic combination of encoding/escapes that solves it for everyone (the
qpopper crowd specifically). 


>The name is not appropriate for uidl but it is for general harnessing of URLs.
>     $line =~ s/[\n\r]+//g;      # stay friendly with base64 encoding
>     $line = encode_base64($line);
>     $line =~ s/\+/%2b/g;        # '+' is in the mime charset and '+' 
>gets converted ...
>     chomp($line);

Hmm... I will give that a try.

take care,
jason


Also, any thoughts on CGI::EncryptForm use ??