On Wed, 26 Sep 2001, James Stansfield wrote:
> > Oh, you _can_ set it up that way, but I would really discourage doing so.
> > It usually turns you into a spam site in less than a week. Tell your pop
> > users to use their own isp's smtp server for sending mail out. The only
> > exception I would consider would be if the remote user has a connection
> > with a static ip. You may be taling about pop-before-relay (we don't
> > include the patches for that), but since pop sends username and password
> > over clear text, it's insecure anyway.
>
> Yeah but more and more ISPs aren't allowing their SMTP to send email
> from accounts that aren't on their system. Roaming users require a single
> SMTP server for their hosted domain based email. Case in point: my office's
> mail server will only relay email based on our domain's email addresses. So
> in this case I couldn't send email out using their internet connection with
> my personal domain. Thus the need for an external SMTP server from my ISP
> (office)...
> What do you thinkg of Don's suggestion of popauth? It looks like a good
> idea to me.
Not familiar with it, but it sounds like a variation of pop-before-relay.
You might try setting up cipe tunnels (encrypts everything) and then
allowing relays from the "internal" cipe addresses. Then your pop
access would also be encrypted. But that would likely be a pain in the
butt.
--
Chris Kloiber, RHCE
Enterprise Support - Red Hat, Inc.
[root@earth root]# rm -rf /bin/laden
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
