hi!B<:?z 7AMS02K!fC=: E ^ w   @ QZ     (previously authorized)Authorization OK on %s@%s Authorization failure on %s@%s%s Bad certificate: Subject Alternative Name contains NUL, aborting! Bad certificate: Subject CommonName contains NUL, aborting! Cannot find absolute path for fetchmail's home directory. Issuer Organization: %s Subject CommonName: %s The attempt to get authorization failed. Since we have already succeeded in getting authorization for this connection, this is probably another failure mode (such as busy server) that fetchmail cannot distinguish because the server didn't send a useful error message.The attempt to get authorization failed. This probably means your password is invalid, but some servers have other failure modes that fetchmail cannot distinguish from this because they don't send useful error messages on login failure. The fetchmail daemon will continue running and attempt to connect at each cycle. No future notifications will be sent until service is restored.Unknown Organization Warning: Issuer Organization Name too long (possibly truncated). Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!) client/server synchronizationProject-Id-Version: fetchmail 6.3.5 Report-Msgid-Bugs-To: fetchmail-devel@lists.sourceforge.net PO-Revision-Date: 2022-04-09 10:24+0000 Last-Translator: Anthony Harrington Language-Team: English (British) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Plural-Forms: nplurals=2; plural=n != 1; X-Launchpad-Export-Date: 2024-09-02 19:09+0000 X-Generator: Launchpad (build 1b1ed1ad2dbfc71ee62b5c5491c975135a771bf0) X-Bugs: Report translation errors to the Language-Team address. Language: en_GB (previously authorised)Authorisation OK on %s@%s Authorisation failure on %s@%s%s Bad certificate: Subject Alternative Name contains NULL, aborting! Bad certificate: Subject Common Name contains NUL, aborting! Cannot find absolute path for Fetchmail's home directory. Issuer Organisation: %s Subject Common Name: %s The attempt to get authorisation failed. Since we have already succeeded in getting authorization for this connection, this is probably another failure mode (such as busy server) that fetchmail cannot distinguish because the server didn't send a useful error message.The attempt to get authorisation failed. This probably means your password is invalid, but some servers have other failure modes that fetchmail cannot distinguish from this because they don't send useful error messages on login failure. The fetchmail daemon will continue running and attempt to connect at each cycle. No future notifications will be sent until service is restored.Unknown Organisation Warning: Issuer Organsation Name too long (possibly truncated). Warning: the connection is insecure, continuing anyway. (Better use --sslcertck) client/server synchronisation