Re: Why is there a punctuation "rule" ?

Dennis Wynne <[email protected]> Wed, 22 Feb 2006 13:27:00 -0600
Newsgroups gmane.mail.spam.greylist.user
Message-ID <[email protected]>
Thanks for the reply.

My source has this:

      # Check for embedded brackets, parens, quotes, slashes, pipes 
(doublequotes are used at yahoo)
      if ($tstr =~ /[<>\[\]\{\}\(\)'"`\/\\\|]/) {
        $ctx->setreply("501", "5.1.7", "Malformed envelope from address: 
invalid punctuation characters");
        return SMFIS_REJECT;
      }

so clearly it is going to fail what the RFC allows.

I suppose it could be to prevent those characters from hosing the database 
commands?

I may have to edit the = and /  out of my source since I keep bouncing good 
mail that my users want due to that rule.

Dennis

===== Original Message from [email protected] (Greylisting 
Users and Developers Discuss) at 2/22/06 11:52 am
>Dennis Wynne wrote:
>> 1) What is the reason behind this "rule" in relaydelay.pl ?
>> 2) How can I accept this mail (assume I can't get the sender to remove the
>> punctuation characters) ?
>>    a) If I whitelist the sending IP will it bypass this check?
>>    b) Can I comment out this check or remove the = and / from it?
>
>This looks like a bug. RFC822 specifies the local-part of an address may
>contain both equal-sign and forward-slash characters explicitly.
>
>http://rfc.net/rfc2822.html, section 3.2.4
>
>--[Lance]
>
>--
> Celebrate The Circle   http://www.celebratethecircle.org/
> Carolina Spirit Quest  http://www.carolinaspiritquest.org/
> My LiveJournal  http://www.livejournal.com/users/labrown/
> GPG Fingerprint: 409B A409 A38D 92BF 15D9 6EEE 9A82 F2AC 69AC 07B9
> CACert.org Assurer
>_______________________________________________
>Greylist-users mailing list
>[email protected]
>http://lists.puremagic.com/cgi-bin/mailman/listinfo/greylist-users