Re: [Assp-user] Fake 250 with LDAP

2007-01-10 Thread Fritz Borgstedt

 want to do this because daily I get hundreds (or more)
non-deliverable
emails delivered from servers all across the internet to email
addresses
here that don't exist. 

As everybody does. That was the reason  to have the flat_list and /or
ldap.
I do not get it, why you cannot use it as we all do.



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user


[Assp-user] Fake 250 with LDAP

2007-01-09 Thread Greg Wright
Can anyone advise what the repercussions may be from enabling the Fake
250  error in Validate Local's options?

 

I would like to enable LDAP Validation, but I am concerned it will block
legitimate email that was misaddressed.  And also it may make it harder
to troubleshoot.

 

Also, does the LDAP function integrate into PB - I see a score for
Invalid Recipient, but Im not sure if there is a relationship.

 

Ideally, I would want to ldap block undeliverables that come to an
address that doesn't exist. I get a lot, but be more flexible with how I
handled misaddressed legitimate content. I also don't want to encourage
harvesting.

 

 

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user


Re: [Assp-user] Fake 250 with LDAP

2007-01-09 Thread Micheal Espinola Jr (mobile)
Think about. If you enable the fake, no misadressed adresses will ever be 
reported back to the sender.

--
ME2   (mobile)

-Original Message-
From: Greg Wright [EMAIL PROTECTED]
Date: Tuesday, Jan 9, 2007 8:33 pm
Subject: [Assp-user] Fake 250 with LDAP

This is a multi-part message in MIME format.

--_


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user


Re: [Assp-user] Fake 250 with LDAP

2007-01-09 Thread Greg Wright
Yeah, which was why I asked if it was able to work in with the PB. I
don't want to be so heavy handed if I can avoid it.

Im also interested in IF i do decide to be heavy handed, does the faked
250 error result in any unusual conditions? I would like to learn from
the list's experiences, rather than from my own.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Micheal
Espinola Jr (mobile)
Sent: Wednesday, 10 January 2007 12:48 PM
To: assp-user@lists.sourceforge.net
Subject: Re: [Assp-user] Fake 250 with LDAP

Think about. If you enable the fake, no misadressed adresses will ever
be reported back to the sender.

--
ME2   (mobile)

-Original Message-
From: Greg Wright [EMAIL PROTECTED]
Date: Tuesday, Jan 9, 2007 8:33 pm
Subject: [Assp-user] Fake 250 with LDAP

This is a multi-part message in MIME format.

--_



-
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDE
V
___
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user


Re: [Assp-user] Fake 250 with LDAP

2007-01-09 Thread Micheal Espinola Jr
Greg Wright wrote:
 Yeah, which was why I asked if it was able to work in with the PB. I
 don't want to be so heavy handed if I can avoid it.
   

Why do you want to do this?  First, you are violating RFCs governing how
MTA behave.  Second, you are potentially making debugging valid email
problems difficult.  The only reason I can see doing this is if you are
operating a spam-trap.  I'd say that if you need to ask about doing this
- then you shouldn't do it - honestly.  You should only do it if you
have a specific need.  This isn't going to help deter spam.  Its going
to increase it - because the spammers will think they have found valid
addresses on your server.

 Im also interested in IF i do decide to be heavy handed, does the faked
 250 error result in any unusual conditions? I would like to learn from
 the list's experiences, rather than from my own.

See above.



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user


Re: [Assp-user] Fake 250 with LDAP

2007-01-09 Thread Greg Wright
Hi Michael,

First up, thank you for considering my question, i've been a member for
a long time, and the group is lucky to have your assistance.

I want to do this because daily I get hundreds (or more) non-deliverable
emails delivered from servers all across the internet to email addresses
here that don't exist. The kind of thing that happens when your domain
is used by the spammers as the From: address. So my ASSP, Virus Gateway
and Mail-server are (almost) constantly processing messages that are a
waste of processing time. 

It would be good to be able to score a penalty of 45 if the message is
To: an invalid local address, and score another 5 if the message matches
an RE that identifies a typical postmaster non-delivery message (either
the From: address or body content). The two combined scores would push
the sending IP into the PB.

Normal bounce replies would come back to us with a valid To: address, so
I am pretty sure this wouldn't break 'normal' operation.

Does that make sense?

Thanks again,
Greg

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Micheal
Espinola Jr
Sent: Wednesday, 10 January 2007 2:16 PM
To: Questions and Answers for users of ASSP Anti-Spam SMTP Proxy
Subject: Re: [Assp-user] Fake 250 with LDAP

Greg Wright wrote:
 Yeah, which was why I asked if it was able to work in with the PB. I 
 don't want to be so heavy handed if I can avoid it.
   

Why do you want to do this?  First, you are violating RFCs governing how
MTA behave.  Second, you are potentially making debugging valid email
problems difficult.  The only reason I can see doing this is if you are
operating a spam-trap.  I'd say that if you need to ask about doing this
- then you shouldn't do it - honestly.  You should only do it if you
have a specific need.  This isn't going to help deter spam.  Its going
to increase it - because the spammers will think they have found valid
addresses on your server.

 Im also interested in IF i do decide to be heavy handed, does the 
 faked 250 error result in any unusual conditions? I would like to 
 learn from the list's experiences, rather than from my own.

See above.




-
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDE
V
___
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user


Re: [Assp-user] Fake 250 with LDAP

2007-01-09 Thread Micheal Espinola Jr
Greg Wright wrote:
 I want to do this because daily I get hundreds (or more) non-deliverable
 emails delivered from servers all across the internet to email addresses
 here that don't exist. The kind of thing that happens when your domain
 is used by the spammers as the From: address. So my ASSP, Virus Gateway
 and Mail-server are (almost) constantly processing messages that are a
 waste of processing time. 
   

In that case you want to use the options in Validate Local Addresses. 
But I don't see how faking any responses to appear like a positive SMTP
session completed is going to be any benefit for what you are looking to
accomplish.  You can create a static list (which some people use scripts
to automatically export to from their MTA), or LDAP.

 It would be good to be able to score a penalty of 45 if the message is
 To: an invalid local address, and score another 5 if the message matches
 an RE that identifies a typical postmaster non-delivery message (either
 the From: address or body content). The two combined scores would push
 the sending IP into the PB.
   

What is good for you, is good for you.  Not everyone gets the same spam,
the amounts, or even the types.  I have modified all my PB settings to
be individually applicable to what each site I am running ASSP at gets
as spam - and how forgiving I need to be at each site.  I would stick
with the defaults until you have everything else running properly and
now want to finalize your config by penalizing IP addresses.  The
defaults are a bit forgiving, which is a good thing.  Once you are more
intimately familiar with what you want to accomplish, then you can tweak
away by making thing cost more.

 Normal bounce replies would come back to us with a valid To: address, so
 I am pretty sure this wouldn't break 'normal' operation.
   

Sure.  And you can use the bombRe to match against common spoofed bounce
replies so you can prevent them from ever getting to real recipients (in
case real addresses ever end up being used).

 Does that make sense?

I think so.  Based on what you said in your last email, the Validate
Local Addresses options should be your priority to prevent invalid
address mail from ever hitting your MTA  Worry about the PB later.  Its
your final step to make your ASSP installation more efficient by
blocking connections early from repeatedly bad behaving IPs.

HTH



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user