Issue 26413 - Add X-Originating-IP: IP of the sender to the header
Summary: Add X-Originating-IP: IP of the sender to the header
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Mailing lists (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: CEE Rubicon
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-12 17:49 UTC by pavel
Modified: 2021-05-27 19:28 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description pavel 2004-03-12 17:49:10 UTC 
Hi,

to help identify the spammer, please add X-Originating-IP header to mailing lists.
Comment 1 lsuarezpotts 2004-03-12 19:21:28 UTC 
hi
reassigning to support as an RFE. Also, lowering the priority to p3; correct me if you think it really 
needs a p2, which is basically top priority.
louis
Comment 2 Unknown 2004-04-03 03:35:00 UTC 
Have filed for an RFE internally
Will provide the update as and when it is received
-Mohan
Comment 3 Unknown 2004-04-06 07:29:16 UTC 
The engineers Want to know who would be using the info & how do they plan 
using it?

Is this so that messages broadcast to the subscribers of the mailing list can 
be identified as not being spam?

Thanks

Mohan
Comment 4 pavel 2004-04-06 08:38:12 UTC 
By adding this info to the header, list subscribers can see what was the
original IP of the sender.

Yes, this is to identify spammers. The header From: is not authoritative and in
fact there were many From: *@sun.com mails in dev@ and users@ that were
spams/virus messages.

Recipients can check this address against RBL and other lists and protect themself.
Comment 5 Unknown 2004-04-15 10:36:46 UTC 
This request has been considered for Diablo

Support will continue monitoring this Enhancement & will review it in the 
corresponding release

Mohan
Comment 6 Unknown 2007-03-06 12:11:19 UTC 
Setting the Target Milestone as Consid-future.

Regards,
Karishma
Comment 7 Unknown 2007-07-07 04:23:36 UTC 
Confirmed that we are allowed to add additional header fields for all
messages/post in the New Discussion Services which would be made available in
the upcoming future release.
Comment 8 Unknown 2009-01-23 09:54:37 UTC 
CollabNet Support is currently reviewing the issues under Resolved-Later. If the
issues are fixed currently in any of the present CEE releases, then it will be
marked as Resolved-Fixed.

There might be a few issues which might not be in our future roadmap which might
be closed as Wontfix unless it does not lie under any custom request.
Comment 9 Unknown 2009-01-23 09:55:29 UTC 
Though PT is not enabled on OOo, Collabnet has fixed this PT which was developed
with IZ as a base

Yes, now in Rubicon it is possible to add required headers through 'Message
Filtering' feature in various levels.

Hence marking this issue as Fixed in Rubicon
Comment 10 Unknown 2009-01-23 09:57:14 UTC 
OOps..It should read like this

Yes, now in Rubicon it is possible to add required headers through 'Message
Filtering' feature in various levels.

Hence marking this issue as Fixed in Rubicon