elad wrote:mkalen wrote:I have successfully tested OpenEMM with an Apache 2.2 proxy on a public server and OpenEMM running on a private IP.
this is not true.
OK, if you tell me so. *cough*
Seriously: it is working. Please read on and try for yourself.
elad wrote:when the email is actually sent, the message source always show :8080/
What you do not understand is the notion of "redirection domain" in OpenEMM. When you configure OpenEMM you can specify any redirection domain, regardless of where your installation of OpenEMM is running and regardless if you point links directly to the application server (with changed ports) or to a web proxy/front-end.
Edit: the port number is also included in the redirection domain setting. Leaving out port will use standard 80/443 for http/-s.
When OpenEMM constructs link in the mails sent, it will insert the value of the redirection domain.
I currently have a redirection domain without port specified at all, something like
http://my.public.server.
My OpenEMM is running on another server (say otherserver.privatesubnet.local) but the links sent out point to "http://my.public.server".
Apache running at "my.public.server" sends proxy requests to OpenEMM to make the actual tracking calls/image fetching. It works perfectly.