Lorna,
If you're simply trying to migrate single mbox type mailboxes, you could just as easily try the good-old formail route: cat /var/mail/user | formail -ds /usr/local/sbin/dbmail-smtp -u user -m Inbox Formail is very robust and fast, and even if there's some really goofy message in that mailbox, formail will probably recover and simply skip that message. mailbox2dbmail is especially suited for quickly migrating trees of mailboxes. For single mailbox migration you don't need it. Still, it should ideally be useful even in your case, so this really does indicate a bug in mailbox2dbmail. Just not an urgent one. The whole import route as such leaves plenty of room for serious improvement. But then even a modicum of a functional export route is total vaporware at the moment. If you do find out what tripping mailbox2dbmail, please do share by filing a bug. If I can replicate your problem it will be fixed. Lorna Sanchez M. wrote: > Hello! > > A friend and I are using dbmail, and we have to migrate HUGE inboxes, > around 1GB each. We used the mailbox2dbmail with success to migrate > other accouts below 600M but for accounts above or so, we have the > "Error parsing mail" error. > The curious thing is that we get that error around the 10,000 or > 11,000 line (each one of us is migrating a different HUGE inbox). > > Is there a problem with insertions in mysql? Does mysql has a limit? > I'm not convinced that my inbox file has a problem. > > This is the line I'm using: > ./mailbox2dbmail -u user -t mbox -m /var/mail/user -b Inbox -p > /usr/local/sbin/dbmail-smtp > > Thanks a lot for the help! > > Lorna. > _______________________________________________ > Dbmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- ________________________________________________________________ Paul Stevens mailto:[EMAIL PROTECTED] NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] The Netherlands________________________________http://www.nfg.nl
