On Thursday 31 January 2008 22:47, Darrell D. Mobley wrote:
> > -----Original Message-----
> > From: Michael Stauber [mailto:bq (at mark) solarspeed.net]
> > Sent: Thursday, January 31, 2008 9:18 PM
> > To: coba-e (at mark) bluequartz.org
> > Subject: [coba-e:11860] Re: Relay Problems.
> >
> > Hi William,
> >
> > > So how would I relay e-mail through his domain name that I am hosting
> > > on my server without having to list his IP each time?
> > >
> > > Is there a "relay after POP" option in BlueQuartz?
> >
> > In the GUI interface see "Server Management" / "Network Services" /
> > "Email".
> >
> > That page has a "Basic" and an "Advanced" tab.
> >
> > In the "Advanced" tab you find a checkbox for "POP Authenticated
> > Relaying",
> > which is what you're asking for.
> >
> > But rather use "Enable SMTP Auth" (see the "Basic" tab). When "Enable
> > SMTP Auth" is checked, email is relayed if the user athenticates against
> > the SMTP
> > server with a valid username and password. All email clients support that
> > method and it works considerably better than "POP Authenticated
> > Relaying", which is just a dirty hack anyway.
> > --
> > With best regards,
> >
> > Michael Stauber
> >
> One point on the use of this: If you use RBL's and the user is on a dynamic
> block, there is a good chance the mail won't get through even using the
> recommendations Michael made. I am on Comcast, and because it is in the
> block of dynamically assigned IPs, some RBL's won't allow my mail through
> unless I list the Comcast IP in the relay for this IP settings.
>
Actually I believe the SMTP-AUTH (which uses the submit.cf configuration
from /etc/mail) bypasses this (rbl check) and will allow any _authenticated_
IP to send.
--
Larry Smith
SysAd ECSIS.NET
sysad (at mark) ecsis.net