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...   
   

I'm not saying you shouldn't be practical with these rules.     
  
   
 "ASSP is all about invalidating mail because of incompliance of 
RFC" - where does ASSP claim that aim? link please Why does it need to be 
explicitly stated? It's quite obvious 
to me, apparently not to you. Besides that..., it's not an aim, the RFC's 
are merely a means to differentiate. Spammers prefer to be anonymous and 
have to break RFC-rules to achieve that. Furthermore they are only 
interested in getting as much mail out. They are only putting for instance a 

message-id in because they are otherwise more likely refused.
 
 
> Finally, can you please give a proper RFC 
quote saying what mail servers are required to accept or reject? 
I already gave one at the beginning of this thread. 

 
> 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. 
 
Of course you can and 
the same goes for governmental laws. 
As I said before.. 
It's all about deciding what's spam and what's not. Non-RFC compliant mail 
is just a good indication for spam.   Common sense should not be discarded 
here.  
But this is all getting out of hand. I merely want to see in my log what's 
going on and if a server which has been handling mail for more than 7 years 
for >800 toplevel domains doesn't want to receive one specific mail I'm not 
going reconfigure anything. 
-----Original Message-----   
 From: Alex Frunza 
<ad...@ascomex.ro>   
 To: ASSP development mailing list 
<assp-test@lists.sourceforge.net>   
 Date: Mon, 19 Oct 2009 
15:58:12 +0300   
 Subject: Re: [Assp-test] Bare LF's rejected by Qmail 
but undetected by ASSP   
   
   
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 [http://p.sf.net/sfu/devconference]     

 > 
_______________________________________________     
 > Assp-test 
mailing list     
 > Assp-test@lists.sourceforge.net     
 > 
https://lists.sourceforge.net/lists/listinfo/assp-test 
[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 [http://p.sf.net/sfu/devconference]     
 
_______________________________________________     
 Assp-test mailing 
list     
 Assp-test@lists.sourceforge.net     
 https://lists.sourceforge.net/lists/listinfo/assp-test 
[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

Reply via email to