Re: [cobalt-users] [QUBE2] Relay w/o Spam

[Mike Vanecek <nospam99@xxxxxxxxxxxx>]

On Fri, 31 Mar 2000 09:06:19 -0600, "Jeff Newman" <mjeffn@xxxxxxxx> wrote:

:>I think that you will be able to do it from the GUI by allowing mail
:>forwarding from the domain or network address that the user is at.  Since
:>they they are most likely PPP with DHCP that is all the granularity will
:>will be able to get.  That also means that anybody from that domain/network
:>would be able to use your server to forward mail as well.

Yes I already allow some specific ips, but I really do not want to open my
sendmail to a large domain of potential spammers or whatever. Just trying to
do my part to keep the relay hole as small as possible.  SMTP before POP is
the de facto solution. How can I implement that feature on a Qube2?

:>
:>You really should look into the watchguard firebox.  (I don't sell them, i
:>am just really impressed with the product)

I have got my firewall pretty clean on and off the net (based on exposure
versus cost). Does the watchguard firebox come with email and web services;
i.e., do I replace the Qube2 with it?

Thanks for the thought

:>
:>-----Original Message-----
:>From: cobalt-users-admin@xxxxxxxxxxxxxxx
:>[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Mike Vanecek
:>Sent: Thursday, March 30, 2000 11:31 PM
:>To: cobalt-users@xxxxxxxxxxxxxxx
:>Subject: [cobalt-users] [QUBE2] Relay w/o Spam
:>
:>
:>How does one set up the Qube2 SendMail to safely relay mail from an user
:>that
:>may be using a dynamic IP from a different domain? Since I only have a
:>couple
:>of users for which I would allow such relaying it would be nice if I could
:>test against something as easy as their From: address.
:>
:>I suspect it cannot be done that easily. Yet, reading the sendmail doco
:>leads
:>one to think it might be possible?
:>
:>>From the sendmail doco,
:>
:>"Keys can be a fully or partly qualified host or domain name ...  Keys can
:>also be a network address or subnetwork ...  Lastly, keys can be
:>user@xxxxxxxxxxx to reject mail from a specific user.
:>
:>For example, a database might contain:
:>
:>cyberpromo.com	REJECT
:>sendmail.org	RELAY
:>spam@xxxxxxxxx	550 Spammers shan't see sunlight here
:>
:>to reject all mail from any host in the cyberpromo.com domain, allow any
:>relaying to or from any host in the sendmail.org domain, and reject mail
:>from
:>spam@xxxxxxxxx with a specific message."
:>
:>If one can reject by address, could I use it to RELAY??  [It should not be
:>too big a spam whole since the from address that is allowed to relay will be
:>known only to me.]
:>
:>If so, is
:>
:>      makemap  hash  /etc/mail/access  <   /etc/mail/access
:>
:>the correct way to map access into access.db?  Am I going to make the Cobalt
:>system GUI management tool bonkers doing this? I really do not want to zap
:>the thing and then have to start over ... much too tired and old for much
:>more of that.
:>
:>If the above won't work, does a pop before smtp solution exist for the Qube2
:>and can it be installed by someone that is starting to feel quite braindead?
:>If so, can someone please direct me to where I can find information about
:>it?
:>
:>If these won't work, can any one please offer an idea that might? It is
:>amazing that the more I read and study this stuff, the less I know ...
:>
:>Thanks.
:>
:>Mike.
:>
:>
:>
:>
:>
:>_______________________________________________
:>cobalt-users mailing list
:>cobalt-users@xxxxxxxxxxxxxxx
:>To Subscribe or Unsubscribe, please go to:
:>http://list.cobalt.com/mailman/listinfo/cobalt-users
:>
:>
:>_______________________________________________
:>cobalt-users mailing list
:>cobalt-users@xxxxxxxxxxxxxxx
:>To Subscribe or Unsubscribe, please go to:
:>http://list.cobalt.com/mailman/listinfo/cobalt-users