Stopping messages without To: or Cc: header(s)

[Glenn Steen]

:-)
As said... I was pretty sure you already had looked at that angle.
... So then its just a matter of some SA rule hacking;-)... I'm not
the greatest re-designer, but I suppose a few rules to check for the
presence and one to combine and "invert" should do the trick... Should
be some rules you could piggyback, but... Can't check that ATM.
Btw, sorry for the quoting style... The wife is hogging all the
computers, and the gmail application on my phone kind of sucks in this
regard.
Cheers

2009/11/22, Hugo van der Kooij <hvdkooij at vanderkooij.org>:
> On 22/11/09 10:02, Glenn Steen wrote:
>> Is there explicit support for this type of rejection in the standard?
>> I thought it only implied...;-)
>> Many distribution list thingies use this, not only baddies. I suppose
>> you've analysed it a bit already...?
>
> Well. RFC5322 does not make them required.
>
>     +----------------+--------+------------+----------------------------+
>     | Field          | Min    | Max number | Notes                      |
>     |                | number |            |                            |
>     +----------------+--------+------------+----------------------------+
>     | trace          | 0      | unlimited  | Block prepended - see      |
>     |                |        |            | 3.6.7                      |
>     | resent-date    | 0*     | unlimited* | One per block, required if |
>     |                |        |            | other resent fields are    |
>     |                |        |            | present - see 3.6.6        |
>     | resent-from    | 0      | unlimited* | One per block - see 3.6.6  |
>     | resent-sender  | 0*     | unlimited* | One per block, MUST occur  |
>     |                |        |            | with multi-address         |
>     |                |        |            | resent-from - see 3.6.6    |
>     | resent-to      | 0      | unlimited* | One per block - see 3.6.6  |
>     | resent-cc      | 0      | unlimited* | One per block - see 3.6.6  |
>     | resent-bcc     | 0      | unlimited* | One per block - see 3.6.6  |
>     | resent-msg-id  | 0      | unlimited* | One per block - see 3.6.6  |
>     | orig-date      | 1      | 1          |                            |
>     | from           | 1      | 1          | See sender and 3.6.2       |
>     | sender         | 0*     | 1          | MUST occur with            |
>     |                |        |            | multi-address from - see   |
>     |                |        |            | 3.6.2                      |
>     | reply-to       | 0      | 1          |                            |
>     | to             | 0      | 1          |                            |
>     | cc             | 0      | 1          |                            |
>     | bcc            | 0      | 1          |                            |
>     | message-id     | 0*     | 1          | SHOULD be present - see    |
>     |                |        |            | 3.6.4                      |
>     | in-reply-to    | 0*     | 1          | SHOULD occur in some       |
>     |                |        |            | replies - see 3.6.4        |
>     | references     | 0*     | 1          | SHOULD occur in some       |
>     |                |        |            | replies - see 3.6.4        |
>     | subject        | 0      | 1          |                            |
>     | comments       | 0      | unlimited  |                            |
>     | keywords       | 0      | unlimited  |                            |
>     | optional-field | 0      | unlimited  |                            |
>     +----------------+--------+------------+----------------------------+
>
> But in my experience all newsletters I am expecting and all mailinglists
> I have subscribed to make proper use of at least the To: or Cc: header.
>
> Hugo.
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
>

-- 
Skickat från min mobila enhet

-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se