@Milyn_Dsilva_CC the “No testing function found for this credential” message is actually a known cosmetic issue with the IMAP credential type, not an actual credential failure. n8n’s IMAP credential never had a test function defined (theres a long-standing github issue on it — #4955), so the test button shows that error regardless of whether ur creds are valid. confusing UX.
the real test is to save the credential anyway, hook it up to the IMAP Trigger node, and run the workflow. if the credentials are actually bad u’ll get a different and specific error at execution time like “Invalid login” or “AUTHENTICATIONFAILED” — that one tells u the real problem.
if it does fail at runtime with auth errors after saving, the most common cause for gmail specifically is the app password format. has to be exactly 16 chars with no spaces (paste it as one block, not the spaced display version google shows in the UI), and the google account needs 2FA enabled or app passwords arent even an option. also double check the host and port: imap.gmail.com:993 with SSL/TLS on.
what email provider are u connecting to? gmail, outlook, custom mail server? that changes the specific app password / oauth path.
None of the smtp / imap creds are working , i tried with new app passwords yet it does not work, there is an issues from n8n end, idk what are you talking baout
Please revert to the previous version. Does it work now?
Also provide more context as stated by @achamm
What is your type of n8n setup? npm? docker? n8n version?
i dont know which was the previous version as i updated after 2-3 months, il give a try tho
i use n8n via docker , self hosted on prem - version (Version 2.21.7) i downgraded to old version still facing same issue
what version did u upgrade from and to? if u went anywhere on 2.20.x → 2.21.4 or 2.21.5 thats exactly the broken cluster confirmed in 296188.
@Milyn_Dsilva_CC please share your json.