My customer wants to know the IP address of Adobe DTM Servers where it actually hosted.I am not understanding how to identify that.
Is there any method to know??
If anybody knows..please let me know.
Thanks,
Payal
If you are asking about the Akamai servers that Adobe uses to serve DTM from, there is no fixed IP Address. Akamai is a CDN that Adobe uses to serve the DTM Javascript library and assets. As such, depending on your location (and latency), the edge server serving you changes accordingly. As an extension, the IP Address changes as well.
The only way to acquire the list of IP Addresses (if any and if it is possible) is to ask your Adobe Consultant or Client Care for it.
Related
I have a website built with a GAE 2nd gen Python 3 app.
Scrapers are scraping my website by forging the Google Bot user agent. I'd like to validate the IP address of the scrapers so I can reject them but not reject real Google Bot traffic.
It seems that the best way to do this is with DNS lookups as described here. Doing DNS lookups, however, requires using socket.gethostbyaddr and socket.gethostbyname but sockets are not allowed in GAE standard. I know that sockets are available with GAE flex but I can't switch to GAE flex.
Thanks to Steffen's comment I see that you can download the google bot IP addresses, but I don't want to have to track this and update my code when it changes. The dynamic approach seems easier and safer.
Is it possible to dynamically validate that an IP address corresponds to the Google Bot in a GAE 2nd gen Python 3 app?
My organization has own email id and can be accessed through web-browser. Now I want to setup IMAP in Gmail app in android. This requires specific incoming/outgoing server ip, port, security certificate. However, to my surprise "Mail.ru" app automatically recognizes everything (I just need to provide my email id and pass) and works perfectly (both in the organization network or outside world). These informations are also required to setup email in thunderbird. Is there any way to know this, like tracing packet, or any other way?
N.B: Nadmin don't want to share these info. This page does not help much.
Many email clients support some kind of Autodiscovery, where based on the domain name certain well-known URLs are tried in an attempt to download an XML document containing information about the SMTP and IMAP settings applicable for that domain.
Here is some Microsoft documentation about it:
https://technet.microsoft.com/en-us/library/cc511507.aspx
See also:
https://serverfault.com/questions/172326/how-to-configure-email-autoconfiguration-for-a-domain
I'm wondering if it's possible, through perhaps pixel tracking or another means, to know an email recipient's IP address to provide location-based dynamic content?
The most reliable way would likely be to embed a tiny image in the header that links to one of your servers. Then when the open the image you can get their ip address based on where it was accessed.
Pixel tracking is easy,
but you mentioned "dynamic content".
This means you need to make your email content change after the recipients open their email, which can only be achieved by javascript.
As far as I know, some email clients will block javascript execution, see here.
If you can use the first mail to record user's ip address, and store in database, you can use the information in the second mail.
Or you can provide a link in your email content, which leads the user to a dynamic webpage.
#Aviator provided a nice solution of generating dynamic image to solve the problem.
We are planing to develop an extension for a software which will detect the email client software or interface of the recipients and report it.
In many forums this subject is told that is not possible but in this site they claim that they provide a reporting in a large scale.
http://www.adestra.com/email-client-detection-with-messagefocus/
I would be glad if someone could tell or show me a way to do it in any platform.
There are 2 situations here:
- detect the client email agent of the sender
- detect the client email agent of the receiver
The SMTP protocol does not define anything that would allow you to identify the client agent. So in theory you cannot guess it. Some clients will send some sort of identification in the header, though also this is not standard, and it can be fake. You can guess the client agent base on these identifiers though.
To find out the client agent of the receiver, you need to include content that will eventually connect to an http server. From there you can get the client agent (of the browser that opens it). So again, you have to do some guessing work. (ex. if it's yahoo.com and it is chrome .. then .. if it's ie then .. and so on.)
So to cut it short, there is not reliable way of finding out the client mail agents, it's more guessing and statistics.
The only way to do this is via the user-agent from a tracking image, you need the interaction via http. From there, you could determine, although not reliably, the email client in use.
I have a website with language ES-ES and I am launching its version in a new country ES-MEX.
I want to redirect all visitors to main website to the site for their country, choosing the best option to avoid overloads (I understand that running even one more script would increase the page download for all my local visitors, so I´d prefer to avoid that)
Would you use htaccess or php?
And what kind of code?
Thanks in advance
You need to set up the dns server that will serve the requests for your domain and provide different server addresses for DNS name requests originated from networks located in Mexico. The BIND DNS server feature that allows you to accomplish this is called view
Thus, you define a view that matches the clients in Mexico and then this view reports different address(es) for names in your domain while for the rest of the World you still report the original ones.
You need to analyse your server logs and find with whois service the locations of the networks you are getting the connections from.
The second option is to use the content negotiation module of the Apache httpd server in a way that the version negotiated for es_MX language of all pages at your original web server would return redirects to the other server.
Both methods are not 100% reliable so clients from Mexico may get connected to your original server and I think that you should use both solutions simultaneously