'NoneType' object has no attribute 'group'

[dylancopeland]

Upon upgrading to 6.5.5 RC2, I'm still getting the following error when syncing mail:

ERROR: Exceptions occurred during the run! ERROR: While attempting to sync account 'Personal' 'NoneType' object has no attribute 'group'

The mail seems to be syncing fine though as I getting my mail. If there's any more output I can provide to further diagnose this, please let me know.

[controesempio]

I'm having the same issue, bot with version 6.5.4 and version 6.5.6-rc2. This only happens to me with a specific host, but I hadn't any luck by looking at the output given by "-d imap". Like dylancpeland, I'm willing to provide further output if you tell us what to look for.

[konvpalto]

Do you have "maxage" setting for the account you're trying to sync?

[konvpalto]

I had created a patch that will allow OI to output the full traceback at the end of the run,
http://codelabs.ru/patches/offlineimap/2013-always-show-full-tracebacks-at-the-end-of-the-run.diff
could you, please, try it?

Thanks!

[konvpalto]

@eschulte: #51 was moved here.

[eschulte]

Thanks for this patch! With the debugging output I was able to find that the error was actually thrown by my remotepasseval function. I'd love if this extra debugging information was available either by default or with a -v flag to offlineimap.

[konvpalto]

You're welcome ;) And yes, I think that the tracebacks will stay with us forever and will be shown at the end of the run in the default case: it makes much more easy to get meaningful reports from people and allow them to fix things by themselves. And, since some errors could be not that easily reproducible, thus command-line flag won't help to get tracebacks, I am for leaving tracebacks on and, may be, having some ways to shut them off, if needed.

I have some strange diagnostics from the OfflineIMAP with this patch applied in some corner cases; will polish the modification and commit to the master repository.

[konvpalto]

Tracebacks were added as f2c8583, weird issue with strange diagnostics turned to be programming error, fixed by 69765a3.

1ef5066 catches two potential sources for the original issue, though I wasn't been able to confirm that yet.

@ controesempio, @dylancopeland: could you, please, check out latest "next" branch and try to reproduce this problem again?