Hm. I still need to get the picture of your set-up. Can you draw a scheme of your mailflow? (like this: http://sourceforge.net/apps/mediawiki/assp/index.php?title=File:121108_193515_0.png )
Áldás Szürkemedve 2010/2/26 Donald Brooks <dbro...@fertichem.ca> > relayHost:=208.79.240.5:587 > > relayPort:=587 > > allowRelayCon:=127.0.0.1|192.168.0. > > > > Don > > > > > > -----Original Message----- > From: Greybear [mailto:smo...@smokey.hu] > Sent: February-26-10 1:53 PM > To: For Users of ASSP > Subject: Re: [Assp-user] authentication to smarthost? > > > > Please double-check your configuration. > > What's RELAYHOST is set to? What's RELAYPORT is set to? > > > > > > Regards > > Greybear > > > > 2010/2/24 Donald Brooks <dbro...@fertichem.ca> > > > > > Still no joy. > > > > > > > > > > > > When I set my exchange connector to my ISP smarthost, mail goes out > > > fine. When I pass to ASSP, it does not. > > > > > > And yet if I telnet to the relayport in ASSP, I get the correct > response > > > back from the relayhost (ISP mail server). > > > > > > > > > > > > Feb-24-10 12:31:06 Connected: 192.168.0.205:17112 -> 192.168.0.205:587 > > > -> xxx.xxx.240.5:587; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:06 <> STARTTLS skipped in reply, problematic IP: > > > 127.0.0.1; > > > > > > Feb-24-10 12:31:07 127.0.0.1 <> SSL negotiation with MTA failed - > > > problem with MTA's SSL configuration?; > > > > > > > > > > > > Don Brooks > > > > > > dbro...@fertichem.ca > > > > > > P > > > > > > Pensons vert avant d'imprimer ce message! > > > > > > Please think green before printing this message! > > > > > > > > > > > > -----Original Message----- > > > From: Greybear [mailto:smo...@smokey.hu] > > > Sent: February-23-10 12:21 AM > > > To: For Users of ASSP > > > Subject: Re: [Assp-user] authentication to smarthost? > > > > > > > > > > > > Configure your ASSP as follows: > > > > > > > > > > > > At TLS options "do TLS" > > > > > > Configure relayhost on ASSP (no need to specify authentication - no > > > place > > > > > > for that either) > > > > > > Set up a relayport > > > > > > On exchange configure the smarthost to the ASSP's relayport and set up > > > > > > authentication with the credentials of your smarthost > > > > > > > > > > > > This is how it works for me. > > > > > > > > > > > > Regards > > > > > > Greybear > > > > > > > > > > > > 2010/2/19 Donald Brooks <dbro...@fertichem.ca> > > > > > > > > > > > > > I run an exchange server with ASSP, and pump my mail out through my > > > > > > > ISP's mail server configured as a smarthost in ASSP, in order > maintain > > > a > > > > > > > whitelist. Until recently, this has worked very well. Recently > > > however, > > > > > > > my ISP is being blacklisted due to someone having found an open > relay > > > in > > > > > > > their config and sending spam, which has prevented many of our > > > messages > > > > > > > from getting to their destinations. > > > > > > > > > > > > > > I've got a secondary MX service that also allows me to send mail, > but > > > > > > > they require TLS SMTP authentication for outbound messages. Right > now > > > > > > > exchange is sending out directly to them, bypassing ASSP, and > > > therefore > > > > > > > not whitelisting any addresses that we send to. > > > > > > > > > > > > > > I don't see it anywhere, so I figured I would ask... can ASSP > support > > > > > > > TLS SMTP authentication for a smarthost? > > > > > > > > > > > > > > Don > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > ------ > > > > > > > Download Intel® Parallel Studio Eval > > > > > > > Try the new software tools for yourself. Speed compiling, find bugs > > > > > > > proactively, and fine-tune applications for parallel performance. > > > > > > > See why Intel Parallel Studio got high marks during beta. > > > > > > > http://p.sf.net/sfu/intel-sw-dev > > > > > > > _______________________________________________ > > > > > > > Assp-user mailing list > > > > > > > Assp-user@lists.sourceforge.net > > > > > > > https://lists.sourceforge.net/lists/listinfo/assp-user > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > ------ > > > > > > Download Intel® Parallel Studio Eval > > > > > > Try the new software tools for yourself. Speed compiling, find bugs > > > > > > proactively, and fine-tune applications for parallel performance. > > > > > > See why Intel Parallel Studio got high marks during beta. > > > > > > http://p.sf.net/sfu/intel-sw-dev > > > > > > _______________________________________________ > > > > > > Assp-user mailing list > > > > > > Assp-user@lists.sourceforge.net > > > > > > https://lists.sourceforge.net/lists/listinfo/assp-user > > > > > > > > > > ------------------------------------------------------------------------ > ------ > > > Download Intel® Parallel Studio Eval > > > Try the new software tools for yourself. Speed compiling, find bugs > > > proactively, and fine-tune applications for parallel performance. > > > See why Intel Parallel Studio got high marks during beta. > > > http://p.sf.net/sfu/intel-sw-dev > > > _______________________________________________ > > > Assp-user mailing list > > > Assp-user@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/assp-user > > > > > ------------------------------------------------------------------------ > ------ > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Assp-user mailing list > > Assp-user@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/assp-user > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Assp-user mailing list > Assp-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-user > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
