That is very strange as I used the exact same config on my old system and it worked perfectly, it may have been running a slightly older version but has pymsnt's handling of that option been changed recently? On 19 Aug 2008, at 11:49, Norman Rasmussen wrote:
> On Tue, Aug 19, 2008 at 12:19 PM, argon <[EMAIL PROTECTED]> > wrote: > My config.xml is as follows, each ***** was replaced over my hostname, > for privacy reasons. having seen the previous issue someone had I > replaced host with 127.0.0.1 but it made no difference so I have set > it back to my hostname. The configuration is identical to my previous > setup bar the fact that I have moved the spool and pid locations: > > <host> MUST be a valid IP address on the host that is running the > transport. It's used as the default outgoing IP address, so > 127.0.0.1 will not work. Additionally if the name resolves to > 127.0.0.1 or to an IP address that is not present on that same > machine, then it will fail. > > if you 'ping <host>' from the machine running the transport, do you > get a non-127.0.0.1 IP address reply from _the same machine_. > > -- > - Norman Rasmussen > - Email: [EMAIL PROTECTED] > - Home page: http://norman.rasmussen.co.za/ > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "py-transports" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/py-transports?hl=en -~----------~----~----~----~------~----~------~--~---
