Next to a hosting provider we are also an access-provider. One with a good reputation, I might say. We provide access to the Internet, period.
Every country and individual have different opinions about this subject, but this is mine/ours. The Internet is not what it was and neither is it what it will be. We monitor all our subnets and if something goes wrong we inform the client and if they can't solve it, we can block certain services on our core-switches. This is real-world and we're not fighting tornadoes here. Nothing is gained by a superiour attitude towards the clients that are paying your bills.. Our ADSL, SDSL, VDSL and fibre customers have static IP's and most of them have no problem sending their mails. Some of them are "given" a decent PTR-record. Maybe it's possible to enhance Sendmail with a scheme to do such a verification. It's the most logical place to do it. But that's not an argument. ASSP is already doing a lot of things that don't even have anything to do with fighting Spam (Charset conversion). JP -----Oorspronkelijk bericht----- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Charles Marcus Verzonden: maandag 16 juni 2008 16:55 Aan: ASSP development mailing list Onderwerp: Re: [Assp-test] Antwort: Re: Verifying recipients On 6/16/2008, JP van Melis ([EMAIL PROTECTED]) wrote: > I merely want to improve some setups of which I know they are flawed. > They exist, because we have DSL-clients who think they can maintain > their own mailserver. We don't want to deprive them the right to do > this. They do NOT have a 'right' to do this. If they want to run a mail server, they need to learn the basics, and engaging in backscatter is NOT acceptable. Most DLS-based (dynamic IP's) mail servers will have a huge problem sending and receiving mail from legitimate mail servers anyway, because they are by default on lots of black lists. For this reason alone, it is highly recommended to NOT run your own mail server from such a connection. > ASSP and Sendmail know for which domains they are relaying, but not > which user. It's a catch-all. The end-user's MTA is most likely > configured worse. Well, hopefully at least you are not engaging in backscatter... If I were you, rather than spend time fighting a tornado, I'd spend time fixing the actual problem... figure out a way to get ASSP a list of valid recipients, or, best case, learn how to configure sendmail to pass-thru the VRFY request to whatever server DOES know the list of valid recipients, and simply let ASSP use its own internal VRFY command. And simply make it a policy that any customer of yours who wants to host their own email server MUST use recipient validation. -- Best regards, Charles ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
