Return-Path: Received: from rwcrmhc13.comcast.net ([204.127.198.39] verified) by mail.stalker.com (CommuniGate Pro SMTP 4.2) with ESMTP id 30117611 for SIMS@mail.stalker.com; Thu, 26 Aug 2004 13:50:00 -0700 Received-SPF: none receiver=mail.stalker.com; client-ip=204.127.198.39; envelope-from=kevo@gatorgraphics.com Received: from server.digital-cohesion.com ([24.1.255.40]) by comcast.net (rwcrmhc13) with ESMTP id <2004082620494701500pd1tce>; Thu, 26 Aug 2004 20:49:47 +0000 Received: from localhost (localhost [127.0.0.1]) by server.digital-cohesion.com (Postfix) with ESMTP id 8393422F921 for ; Thu, 26 Aug 2004 20:49:46 +0000 (GMT) Received: from server.digital-cohesion.com ([127.0.0.1]) by localhost (server.digital-cohesion.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12071-10 for ; Thu, 26 Aug 2004 15:49:33 -0500 (CDT) Received: from [192.168.0.2] (192-168-0-2.digital-cohesion.com [192.168.0.2]) by server.digital-cohesion.com (Postfix) with ESMTP id 8B1F322F8EB for ; Thu, 26 Aug 2004 15:49:33 -0500 (CDT) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <6F037542-F7A1-11D8-85D2-000393B29272@gatorgraphics.com> Content-Transfer-Encoding: 7bit From: Kevin Windham Subject: Re: "we do not relay" problems Date: Thu, 26 Aug 2004 15:49:33 -0500 To: "SIMS Discussions" X-Mailer: Apple Mail (2.619) X-Virus-Scanned: by amavisd-new at digital-cohesion.com On Aug 26, 2004, at 3:25 PM, Chris Jensen wrote: > that's the same as checking "the server requires secure > authentication"? > > On Aug 26, 2004, at 4:17 PM, Christopher Bort wrote: > >> On 8/26/04 at 13:12, Chris Jensen wrote: >> >>> i've got a client that gets a lot of "we do not relay" problems, >>> despite setting up their outlook to log in to send messages and >>> recieve >>> messages before they send. i can't isolate their network because >>> they >>> are mobile. what else can i do to make sure they are able to send >>> their mail? >> >> Can they do SMTP AUTH? It's a better solution than POP-before-SMTP if >> the >> client supports it. No. Secure authentication normally uses ssl or some other protocol that SIMS doesn't support. Just use plain authentication and it should work, or try APOP which I believe you can enable in SIMS. Sorry if I'm wrong on that it's been a while since I used SIMS. HTH, Kevin