>perhaps just mod the mbox2dbmail script a little.
>get it to connect to the database as well and then do the update at that
>point in time.
>BTW I made a wrapper for mbox2dbmail such that its moderatly easy to get
>it to process a bunch of users simultaniously
>Its somewhere in the archives.
I reviewed mbox2dbmail, the point is, it actually uses dbmail-deliver
program,
so the message is actually delivered via "normal" LDA (local-delivery-agent)
way.
Probably the option to dbmail-deliver to pass to dbmail a
fixed UIDL value for currently processed message,
would be solution too. The best solution would be previous-pop3server
independent, I mean that implementing internal support for tens of
"other pop3" UIDL algorithms will be rather short-way and
perspectiveless solution. But a way to update or force an UIDL for migrated
message, according to previous UIDL, whatever it was, would be ideal.
--
View this message in context:
http://www.nabble.com/additional-migration-issues-tp23115174p23124638.html
Sent from the dbmail dev mailing list archive at Nabble.com.
_______________________________________________
Dbmail-dev mailing list
[email protected]
http://mailman-new.icns.fastxs.net/cgi-bin/mailman/listinfo/dbmail-dev
