Re: incorrect headers generated by CGatePro?

Hi!

[resending, as the previous mail somehow did not appear in the list]

"VBSSI" == Vladimir Butenko, Stalker Software, Inc writes:

>> CGatePro generates headers like:
>>
>> Reply-To: <CGatePro@mail.stalker.com> (CommuniGate Pro Discussions)
>> Sender: <CGatePro@mail.stalker.com> (CommuniGate Pro Discussions)
>> To: <CGatePro@mail.stalker.com> (CommuniGate Pro Discussions)
>>
>> Is this compliant with RFC specs? It seems that the correct form
>> is

 VBSSI> Yes, they are correct. The part in () is a "comment", while  VBSSI> the part in <> is the E-mail address.

Could you please explain how this could be correct by referencing syntax rules defined in the section 6 of RFC822:

     6. ADDRESS SPECIFICATION      6.1. SYNTAX

     address     =  mailbox                      ; one addressee
                 /  group                        ; named list

     group       =  phrase ":" [#mailbox] ";"

     mailbox     =  addr-spec                    ; simple address
                 /  phrase route-addr            ; name & addr-spec

     route-addr  =  "<" [route] addr-spec ">"

     route       =  1#("@" domain) ":"           ; path-relative

     addr-spec   =  local-part "@" domain        ; global address

     local-part  =  word *("." word)             ; uninterpreted
                                                 ; case-preserved

     domain      =  sub-domain *("." sub-domain)

     sub-domain  =  domain-ref / domain-literal

     domain-ref  =  atom                         ; symbolic reference
===============================

As can be seen from above, brackets "<" and ">" could only occur in a route-addr which could appear only after a phrase, which is defined as a non-empty sequence of words.

Thus, the header

Sender: <CGatePro@mail.stalker.com> (CommuniGate Pro Discussions)

is incorrect because a route-addr is not preceded by a phrase; it should be changed to one of the following:

Sender: CommuniGate Pro Discussions <CGatePro@mail.stalker.com>

(a phrase precedes a route-addr)

Sender: CGatePro@mail.stalker.com (CommuniGate Pro Discussions)

just an addr-spec.

BTW, CGatePro also generates incorrect "Received:" headers:

Received: from <CGatePro-report@mail.stalker.com>   by vsu.ru (CommuniGate Pro RULES 3.3.1)   with RULES id 1817958; Sat, 19 Aug 2000 06:20:24 +0400

here, <CGatePro-report@mail.stalker.com> should be really mail.stalker.com (it should be a domain), as explained in section 4.1 of RFC822.

i.e., headers generated by CGatePro should be re-examined on RFC-correctness imho.

>> To: CGatePro@mail.stalker.com (CommuniGate Pro Discussions)
>> To: CommuniGate Pro Discussions <CGatePro@mail.stalker.com>
>> To: "CommuniGate Pro Discussions" <CGatePro@mail.stalker.com>

 VBSSI> These are correct address formats, too - but they are more  VBSSI> like "special cases" in the RFC822 specs.

i'd say that on the contrary, -- these are THE standard, correct and correct address formats, mentioned many times in RFC822, while the format generated by CGatePro seems to be wrong.

-- 
Vladimir Volovich <vvv@vsu.ru>           Voronezh State University
Phone: +7 (0732) 522406                  Network Operation Center
Fax:   +7 (0732) 789820                  Voronezh, Russia


##################################################################
Вы получили это сообщение потому, что подписаны на список рассылки
  <CGatePro@mx.ru>.

Чтобы отписаться, отправьте сообщение на адрес <CGatePro-off@mx.ru>
Чтобы переключиться в режим дайджеста - mailto:<CGatePro-digest@mx.ru>
Чтобы переключиться в индексный режим - mailto:<CGatePro-index@mx.ru>
Для административных запросов адрес <CGatePro-request@mx.ru>