Well, even --silent won't make the commonname mismatch disappear.
OTOH I don't feel like disabling warnings for SSL setups that at least theoretically enable man-in-the-middle attacks - the user isn't supposed to feel safe when in fact he isn't. If the upstream server supports APOP, CRAM-MD5 or similar authentication schemes, just not using SSL might be the easiest way to get rid of the messages. Is that an option? Kind regards, -- Matthias Andree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
