Well put. Rfc is guideline. System admins interpret those guidelines for their own policy. Could be good, or bad, or neither.
Some rfc are common sense. The admin decides what they want to do. Certainly allowing a bare LF to congest a system is bad policy. It won't magically dissapear, so immediately reject it. This removes the burden from all systems. I think my bottom line was ASSP should make no effort to patch around a buggy qmail. Fix qmail, email thread done :) -- Scott Iphone says hello. On Oct 19, 2009, at 5:58 AM, Alex Frunza <ad...@ascomex.ro> wrote: > Mysoginistic some? > > Fine, I'll play along. Will you check say 50 of your regular senders' > ips at rfc-ignorant.org and tell me how many come up breaking a RFC > requirement? Whole ISP's are listed there for instance for having bad > whois, non-working abuse etc. etc. If you start playing by those rules > you'll end up an anti-spam kook blocking half the world... > > "ASSP is all about invalidating mail because of incompliance of RFC" > - where does ASSP claim that aim? link please > > Finally, can you please give a proper RFC quote saying what mail > servers are required to accept or reject? AFAIK the receiving system > has the right to decide for themselves what to accept or block, i.e. > I can block your e-mail just because I don't like your name, or I > can accept e-mail forging helo's if that's my wish and I wouldn't be > breaking any RFC's. The senders might, but that's not my business. > > > > > On 10/19/2009 3:38 PM, Jean-Pierre van Melis wrote: >> ASSP is all about invalidating mail because of incompliance of RFC >> and even >> goes further than this. It's just because this specific >> incompliance is not >> realistic it should just be discarded. >> non-RFC-compliance is indeed a valid reason to invalidate a message.. >> >> Reversing this logic into "An RFC-compliance should result in >> validating a >> message" is IMHO female logic.. >> >> JP >> --- >> --- >> --- >> --------------------------------------------------------------------- >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart >> your >> developing skills, take BlackBerry mobile applications to market >> and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> Assp-test mailing list >> Assp-test@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/assp-test >> >> >> > > > --- > --- > --- > --------------------------------------------------------------------- > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Assp-test mailing list > Assp-test@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-test ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
