I test the new UIDL support in YAM for some time now and
as result i have 9 .uidl_... files in the YAM directory.
It seems all files contain the uidl's for the latest
loaded mails. I have only one account configured which
should not delete the E-Mails on the Server.
So here my request:
YAM should only write the .uidl_ files if 'Delete mail on server'
is *not* enabled. I see no reason why YAM should write the .uidl_
file when this option is enabled.
Such .uidl_ file(s) produce a lot unnecessarily overhead.
If YAM is getting mails next time then it load the .uidl_ files
for every account and check the content which must fail because
the mail(s) are already deleted on the server.
So here YAM loads 9 files but really necessary is only one.
A check for such file before getting mails is ok because
the configuration may have been changed and the user now want
to Delete the mails on the server.
If the .uidl_ file is finally empty (contain only the header)
then YAM should delete the .uidl_ file too.
Summary: YAM sould only remember uidl's for mails which are
really still on any server.
Additional a improved import function for the old .uidl file
would be nice too. Before YAM 2.7 is going into the wild
we should think about a way to get rid of the old .uidl file.
Otherwise YAM 2.7 and all later versions would still check for
the old .uidl file. Now we have the chance to change that.
A possible way is maybe at the first start of YAM 2.7 to
check the configuration and copy the old .uidl file into
all new .uidl_... files which has 'Delete mail on server'
not enabled and delete the old uidl. file afterwards.
Next time YAM is getting mails from this account(s) it
should delete not valid entries from the new .uidl_
file anyway and if it's ends in an empty file delete
the file. (see above)