Issue 500574
Created on 2002-01-07 21:05 by pohly, last changed 2002-01-08 04:12 by richard.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2002-01-07 21:05:05 | pohly | create | |
Created on 2002-01-07 21:05 by pohly, last changed 2002-01-08 04:12 by richard.
| Messages | |||
|---|---|---|---|
| msg112 | Author: [hidden] (pohly) | Date: 2002-01-07 21:05 | |
According to rfc 822 a message id must be enclosed in <> and contain an address, i.e. some simple words separated with an @. I haven't tried it, just looked at the source, but messageid = "%s.%s.%s%s-%s"%(time.time(), random.random(), classname, nodeid, self.MAIL_DOMAIN) in mailgw.py and elsewhere breaks this rule. |
|||
| msg113 | Author: [hidden] (richard) | Date: 2002-01-07 23:18 | |
Logged In: YES user_id=6405 So would making the format be %s.%s.%s%s@%s be OK? If not, what's the part after the "@" supposed to be? |
|||
| msg114 | Author: [hidden] (richard) | Date: 2002-01-08 04:12 | |
Logged In: YES user_id=6405 Ah, righto. Yes, the message-id is supposed to be <some.string@SHOST> where SHOST is the sender's host. It's actually supposed to match the host part of the Sender: header, but that's obviously either changed in a later RFC or is just ignored (a few sample e-mails I just looked at had all sorts of combinations of things.) Upshot: I'll change it so the format is just "<%s.%s.%s%s@%s>" with the current arguments. Note the addition of the angle-brackets too... |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2002-01-07 21:05:05 | pohly | create | |
Supported by The Python Software Foundation,
Powered by Roundup