/ Forside / Teknologi / Internet / E-Mail / Nyhedsindlæg
Login
Glemt dit kodeord?
Brugernavn

Kodeord


Reklame
Top 10 brugere
E-Mail
#NavnPoint
o.v.n. 20481
miritdk 16341
Klaudi 15149
refi 14168
dk 5555
tedd 5322
webnoob 5265
BjarneD 5014
emesen 4154
10  bentjuul 3460
Mailserver der klistrer ekstra Message-ID ~
Fra : Arne Jørgensen


Dato : 23-04-03 10:05

Hej,

Jeg har netop investeret i et mailhotel til et af mine domæner og til
min gru opdager jeg at mailserveren minsandten klistrer en (ekstra)
Message-ID header på når den modtager mailene!

Jeg opfatter det som en fejl at serveren klistrer headeren på og vil
gerne have udbyderen til at ændre dette. Før jeg henvender mig vil jeg
dog lige høre andres vurdering af om en mailserver må sætte en ekstra
Message-ID i mails den modtager.

RFC 2822 siger bla:

The "Message-ID:" field provides a unique message identifier that
refers to a particular version of a particular message. The
uniqueness of the message identifier is guaranteed by the host that
generates it (see below). This message identifier is intended to be
machine readable and not necessarily meaningful to humans. A
message identifier pertains to exactly one instantiation of a
particular message; subsequent revisions to the message each
receive new message identifiers.

Note: There are many instances when messages are "changed", but
those changes do not constitute a new instantiation of that
message, and therefore the message would not get a new message
identifier. For example, when messages are introduced into the
transport system, they are often prepended with additional header
fields such as trace fields (described in section 3.6.7) and resent
fields (described in section 3.6.6). The addition of such header
fields does not change the identity of the message and therefore
the original "Message-ID:" field is retained. In all cases, it is
the meaning that the sender of the message wishes to convey (i.e.,
whether this is the same message or a different message) that
determines whether or not the "Message-ID:" field changes, not any
particular syntactic difference that appears (or does not appear)
in the message.

En anden ting er så at den message-id de klistrer på ikke har FQDN på
højre siden af @ men blot mailserv03 ...

mvh
/arne
--
stud. scient. Arne Jørgensen
Kollegium 5, 2., v. 222, Universitetsparken, 8000 Århus C
tlf: 89 42 72 22, mobil: 21 65 01 13
e-post: arne@daimi.au.dk, <http://www.daimi.au.dk/~arne/>

 
 
Jesper Harder (23-04-2003)
Kommentar
Fra : Jesper Harder


Dato : 23-04-03 11:18

Arne Jørgensen <arne@daimi.au.dk> writes:

> Jeg opfatter det som en fejl at serveren klistrer headeren på og vil
> gerne have udbyderen til at ændre dette. Før jeg henvender mig vil jeg
> dog lige høre andres vurdering af om en mailserver må sætte en ekstra
> Message-ID i mails den modtager.

Det mener jeg ikke den må. Her er et andet relevant citat fra RFC 2821:

The following changes to a message being processed MAY be applied
when necessary by an originating SMTP server, or one used as the
target of SMTP as an initial posting protocol:

- Addition of a message-id field when none appears [..]

The less information the server has about the client, the less likely
these changes are to be correct and the more caution and conservatism
should be applied when considering whether or not to perform fixes
and how. These changes MUST NOT be applied by an SMTP server that
provides an intermediate relay function.

In all cases, properly-operating clients supplying correct
information are preferred to corrections by the SMTP server. In all
cases, documentation of actions performed by the servers (in trace
fields and/or header comments) is strongly encouraged.

Arne Jørgensen (23-04-2003)
Kommentar
Fra : Arne Jørgensen


Dato : 23-04-03 12:08

Jesper Harder <harder@myrealbox.com> writes:

> Her er et andet relevant citat fra RFC 2821:
>
> The following changes to a message being processed MAY be applied
> when necessary by an originating SMTP server, or one used as the
> target of SMTP as an initial posting protocol:
>
> - Addition of a message-id field when none appears [..]
>
> The less information the server has about the client, the less likely
> these changes are to be correct and the more caution and conservatism
> should be applied when considering whether or not to perform fixes
> and how. These changes MUST NOT be applied by an SMTP server that
> provides an intermediate relay function.
>
> In all cases, properly-operating clients supplying correct
> information are preferred to corrections by the SMTP server. In all
> cases, documentation of actions performed by the servers (in trace
> fields and/or header comments) is strongly encouraged.

Det sad jeg faktisk også og så på i går -- havde glemt det igen (det
er vist ikke for godt med hukommelsen).

Tak, Jepser!

/arne
--
stud. scient. Arne Jørgensen
Kollegium 5, 2., v. 222, Universitetsparken, 8000 Århus C
tlf: 89 42 72 22, mobil: 21 65 01 13
e-post: arne@daimi.au.dk, <http://www.daimi.au.dk/~arne/>

Søg
Reklame
Statistik
Spørgsmål : 177553
Tips : 31968
Nyheder : 719565
Indlæg : 6408849
Brugere : 218888

Månedens bedste
Årets bedste
Sidste års bedste