From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ip15.shellworld.net ([64.49.204.174] helo=server2.shellworld.net ident=root) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1GoofV-0002Q7-00 for ; Mon, 27 Nov 2006 17:09:41 -0500 Received: from ip15.shellworld.net (jdashiel@ip15.shellworld.net [64.49.204.174]) by server2.shellworld.net (8.13.1/8.12.8) with ESMTP id kARM9eMv071587 for ; Mon, 27 Nov 2006 22:09:41 GMT (envelope-from jdashiel@shellworld.net) Date: Mon, 27 Nov 2006 17:09:40 -0500 (EST) From: Jude DaShiell To: speakup@braille.uwo.ca Subject: re: smtp problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.9 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2006 22:09:42 -0000 Error 554: which now happens tells me someone's internet provider switched to authenticated smtp message handling. Looks like openssl or sasl is going to be needed to send with that provider in the future. If there is any way possible to avoid sendmail I'd continue to do so. First, sendmail is the oldest and softest hacker exploit target on the internet after all Microsoft products. Second, how anybody gets authentication working in sendmail is something best left for those that were sending email about 2,000 years ago. Not easy at all and may involve a kernel rebuild.