How to forward the messages with the original IP in the header instead of senders IP address?
Created 2004-06-14 by Tamsila-Q-Siddique We are forwarding some of Syslog messages using WinSyslog / MonitorWare Agent, but when the message shows up at the other location, it appears with the forwarding servers IP address instead of the originating devices IP address in the header. Is there a way to forward the messages with the original IP in the header instead? What you experience is actually a shortcoming in the “Syslog Protocol” itself. The address is taken from the sender, so when a message is relayed, the sender’s address changes. However, there are a number of cures, each depending on your needs, configuration and eventually the edition to use. • If your devices are RFC 3164 compliant (many are unfortunately not), you can take the hostname from the Syslog header. There is an option in MonitorWare Agent / WinSyslog “RFC 314 parsing” which you can enable to get hold of this. Please note that it is disabled by default because non-compliant devices can really create very strange va
Related Questions
- Netscape on Unix is sending messages containing an unqualified user name in the Sender: header line, which Exim is rejecting because I have set verify = header_syntax. How can I fix this?
- How can I control the address to which bounced emails will be sent? Why do messages sent with an envelope sender have an X-Warning header?
- Can you forward fan letters or messages to Rahul?
