On 05/23/2011 03:35 AM, Jeffs wrote:
Hello All,
Assume the following setup:
Client from xyz.com logins to Many_Companies.com, accesses their email
campaign software running on Many_Companies.com and sends out
newsletters.
A short time later a client from def.com logins to
On 5/23/2011 3:33 AM, Jeroen Geilman wrote:
On 05/23/2011 03:35 AM, Jeffs wrote:
Hello All,
Assume the following setup:
Client from xyz.com logins to Many_Companies.com, accesses their
email campaign software running on Many_Companies.com and sends out
newsletters.
A short time later a
On 5/23/2011 9:30 AM, Jeffs wrote:
On 5/23/2011 3:33 AM, Jeroen Geilman wrote:
On 05/23/2011 03:35 AM, Jeffs wrote:
Hello All,
Assume the following setup:
Client from xyz.com logins to Many_Companies.com, accesses
their email campaign software running on Many_Companies.com
and sends out
On 5/23/2011 11:06 AM, Noel Jones wrote:
On 5/23/2011 9:30 AM, Jeffs wrote:
On 5/23/2011 3:33 AM, Jeroen Geilman wrote:
On 05/23/2011 03:35 AM, Jeffs wrote:
Hello All,
Assume the following setup:
Client from xyz.com logins to Many_Companies.com, accesses
their email campaign software
On 5/23/2011 10:19 AM, Jeffs wrote:
On 5/23/2011 11:06 AM, Noel Jones wrote:
The Received: header is added by the receiving system, not
by your server, and always shows the IP of the connection.
If you want each client to have their own identity, each
client will need its own IP. You can't
Hi, Neil,
My confusion lies in the fact that the email client campaign software is
actually initiating a connection to the virtual domain, and sending the
mail to it -- all on the same server, mind you -- then IT sends it out
through the interface with it's virtualized IP address.
I don't
Hello All,
Assume the following setup:
Client from xyz.com logins to Many_Companies.com, accesses their email
campaign software running on Many_Companies.com and sends out newsletters.
A short time later a client from def.com logins to Many_Companies.com,
accesses their email campaign
