From: Matthias A. <mat...@gm...> - 2020-07-16 10:30:46
|
Am 16.07.20 um 10:50 schrieb Bjoern Voigt: > Matthias Andree wrote: >> Password buffers in 6.4.X are allocated dynamically, and there may be >> undocumented limitations on your mail service provider's (MSP's) end. 30 >> certainly does not seem too long to me, but might be for your MSP. > I still see a static maximum password length in the head branch of > Fetchmail: > > #define PASSWORDLEN 256 /* max password length */ > (source https://sourceforge.net/p/fetchmail/git/ci/legacy_64/tree/fetchmail.h#l117) Yes, I figured my assessment yesterday was reaching too short; while it is true that the password storage itself is allocated dynamically, some of the ways of how the passwords are acquired are not. I've marked an issue for that in Gitlab with milestone 7.0 so it's not forgotten. => https://gitlab.com/fetchmail/fetchmail/-/issues/17 I am not sure if that's fixable for 6.5.x though. |