(no subject)

Carlo Gibertini ( (no email) )
Tue, 9 Dec 1997 10:35:13 -0200

SMTP mailers can not be password checked before send mail...

Or can?

Carlo

----------
> De: Mitch Wagers <mwagers@ocsnet.net>
> Para: 'ntisp@emerald.iea.com'
> Assunto: RE:
> Data: Sexta-feira, 5 de Dezembro de 1997 22:57
>
> um, why even do that, it is way to complicated. Why have ANYONE use your

> mail server for ANYTHING besides YOUR mail. Relaying is out of the
> question, period, that's my thoughts. And Post.Office can be set to
verify
> email accounts on outgoing messages. In other words, if the user sending

> mail doesn't have a valid email account AND password on the server, the
> mail is denied.
>
> ----------
> From: Danny Sinang
> Sent: Saturday, December 06, 1997 12:47 AM
> To: ntisp@emerald.iea.com
> Subject: Re:
>
> I use NTMAIL and it has a feature that restricts the number of recepients
> an email could have ( RCPT clause limit per message ). I set it to a
small
> number ( 55 ). I could set it lower and further discourage the SPAMMER
from
> using me as a staging point since they have to send and send again.
>
> It's not your perfect solution, but it does some good.
>
> Hope Post.Office has that feature.
>
> Btw, NTMAIL has JUCE. People claim it stopped 99% of all the SPAMMING
going
> thru their servers.
>
> - Danny Sinang
>
> ----------
> > From: John D. Kerr <john.kerr@peel.com>
> > To: NTISP@emerald.iea.com
> > Subject:
> > Date: Saturday, December 06, 1997 8:35 AM
> >
> > Email Relaying Restriction
> >
> > Over the past few days, our systems have been used as a relay host for
> > subscribers of other services (in the most recent case - CompuServe) to
> > forward out hundreds of Spam messages. This action has put a tremendous
> > load on the servers, and generated hundreds of failed attempt message
to
> > the administrator (me!).
> >
> > We are running the latest release of Post.Office (v3.1.2) and it offers
> > features to block/eliminate this type of activity (at least they claim
> this
> > in their adverts). I have reviewed the options available, and there are
> > many - but I have not quite figured out the best solution for our
setup.
> >
> > What I think is the best solution, which I think would solve my problem
> is
> > as follows:
> > - Allow mail from ANY outside domains to flow freely into domains
hosted
> on
> > our mail server. This would mean blocking any mail not for local
domains.
> > - Allow mail from ANY IP addresses on my local domain to flow out
freely.
> >
> > This sounds like a simple solution to me, but I cannot figure out how
(or
> > even if this is possible) to do with Post.Office. Has anyone any
> experience
> > in this type of configuration with Post.Office?
> >
> > My second question, also around Post.Office, is whether I can have all
> > messages which go to the Mail Administrator (error messages) go into a
> NUL
> > device?? I really don't want to have to look at all the error messages
on
> > the Mail Administrator account daily, nor do I want to be forced to
clear
> > out message from the "Deferred Mail", "Handle Error Messages" system
> > administrator option.
> >
> > Any advice on these situations would be appreciated.
> >
> > John
> > john.kerr@peel.com
> >
> > ----------------------------------------------------------
> > NTISP Mailing List listserver@emerald.iea.com
>
> ----------------------------------------------------------
> NTISP Mailing List listserver@emerald.iea.com
>
>
>
> ----------------------------------------------------------
> NTISP Mailing List listserver@emerald.iea.com
>