Issue w/ read_emails()

[BotezanTechnologic]

SYSTEM: Command read_emails returned: Error: decode() argument 'encoding' must be str, not None

Auto-GPT is throwing this error when it attempts to read_emails() and fetch any of my recent mails for processing or replies.

I believe the Imap/smtp is configured properly as I was able to send an email out with auto-gpt, but I could be wrong.

Also attempted some work-arounds in the python code, but was unsuccessful after a few different attempts.

Using 2FA w/ app password setup.

[riensen]

Thanks for the bug report. Can you let me know, what parameters Auto-GPT is using when calling the read_email command? A screenshot also works.

[riensen]

@BotezanTechnologic in addition I extended the imap search parameter such that more complex imap searches can be handled. This might resolve the issue.

[runquik]

Also testing this. Send email works pretty well but I'm also getting the permissions errors when trying to read emails. Also getting a permission error when trying to attach a file:

[runquik]

Oh, here are a couple of shots from the read_emails command:

[BotezanTechnologic]

Thanks for looking into this @riensen ! Appreciate you already pushing a possible fix, my bad on not replying till now.

When testing this I was just using the same test setup as in the docs.

Will test with the updated imap params later today and let you know what happens. If it throws another error, I will provide screenshots.

[BotezanTechnologic]

Confirmed fixed & working on my end ✅

Thank you @riensen !

[riensen]

Oh, here are a couple of shots from the read_emails command:

Auto-GPT seems to try to pass additional parameters to the read emails function. There is nothing that can be done to fix this within the plug-in. Its a problem within Auto-GPT (GPT not following directions).

[riensen]

@BotezanTechnologic Thanks for confirming!

[runquik]

@BotezanTechnologic can you tell me what you did to fix? I'm using the latest imap config and still having the same error

[BotezanTechnologic]

@runquik just updated with the new changes that got pushed. I don't think you and I were experiencing the same error.