On Wed, December 27, 2006 16:44, Richard Frovarp wrote:
>> into your MUA. SMTP AUTH just adds some crypto to it - users just
>> check a different box when they set up their clients.
> Good point. Are the users force to authenticate a second time when they
> want to read mail?
who says thay care
Miles Fidelman wrote:
Mike,
I'm not sure why "It is not considered acceptable to force the users
to authenticate a second time when they want to send email" - we all
do that all do that all the time anyway. Pretty much all MTAs ask
clients for a username and password as part of the connectio
Mike,
I'm not sure why "It is not considered acceptable to force the users to
authenticate a second time when they want to send email" - we all do
that all do that all the time anyway. Pretty much all MTAs ask clients
for a username and password as part of the connection cycle - it's just
us
Thanks, mu comments embedded below.
mike
On 12/27/06, Michael Scheidell <[EMAIL PROTECTED]> wrote:
you will need to so lots of custom code.
Not so much
First, you will need a database of abusesive users (why not just suspend
their account. PERIOD, they violate your TOS, they violate the
SA catches and classifies spam. It does not configure, secure or synchronize
your MTA with any external source.
esto, this is the wrong mailing list for such a question.
The first thing you want to do is try and find an MTA that can achieve the
goals you set. Sendmail probably can, but will ne
Michael Scheidell
Cc: users@spamassassin.apache.org
Subject: Re: mapping dynamic IPs to specific accounts
Sort of. Our problem is not identifying the sending of spam
(well that is not our only problem) but recognizing a user as a past
spammer and denying them a
dynamic IPs to specific accounts
Thanks Miles, but I am not sure that this is what I am looking
for. My client's users will already have authenticated to access the
data network, but all that remains to identify them is the IP address
that they were assigned for that se
Sort of. Our problem is not identifying the sending of spam (well that is
not our only problem) but recognizing a user as a past spammer and denying
them access to our smtp servers. The only ID we have for those users is the
IP that was assigned to them by the data network. Since this is dynamic w
Thanks Miles, but I am not sure that this is what I am looking for. My
client's users will already have authenticated to access the data network,
but all that remains to identify them is the IP address that they were
assigned for that session. The data network guys have added code to update a
DNS
You aren't looking to use Authenticating, TLS, POP before Auth, or that
like to stop RELAYING, what you want to do is to catch accounts that are
SPAMMING (on purpose or infected?)
Something like a postfix policy server might help.
-Original Message-
From: Mike Kenny [ma
Mike Kenny wrote:
A client of mine provides an email service to a number of mobile
users. This leave my client open to abuse as addresses are assigned
dynamically and blocking specific users is difficult. We have set up
an internal, private DNS which we update with the authentication
details o
11 matches
Mail list logo
