I'm seeing a lot of traffic where document.URL (and document.referer) are blank. This seems suspicious to me. Are there any valid reasons document.URL could be blank?
Thanks
Related
I'm managing a bulk email service for the company I work at and a recent change to SpamAssassin has started flagging emails sent by our bulk-email solution with 'RAND_MKTG_HEADER'. I can't find much about this on the internet other than 'Has partially-randomized marketing/tracking header(s)'. The thing is, the software doesn't randomize any of the marketing headers for the campaigns sent with it, so I'm a bit confused as to the hows and whys and what I can do to fix this issue.
Naturally campaigns IDs are randomized UIDs, that's the nature of indentifying things uniquely. If anyone has any insight as to what this particular flag entails and what I can do to fix the issue it would be GREATLY appreciated as it's starting to impact our legitimate customers with delivery issues.
Thanks in advance!
It's likely caused by a custom X- header prefix, i.e. you have an X-something- prefix in your mailer software. If you happen to use Mailwizz, here is the solution: https://kb.mailwizz.com/articles/low-score-in-spamassassin-because-of-the-rand_mktg_header-rule/
You can essentially fix the problem by changing the custom header prefix to a traditional X- prefix.
I have a problem with my outgoing emails: they all are redirect into spam folder.
I have done a lot of things to fix this issue, but I still have the problem...
I think my DNS settings are OK. I have configured SPF like this : v=spf1 a mx ip4:X.X.X.X ~all
And when I test my DNS settings on different websites (such as MxToolbox, Testdns, mail-tester and others), everything seems to be alright. You will find my DNS settings below
I really need some help, I've been trying to fix this for 3 weeks :(
Thanks
Geoffrey
You didn't give much information, anything I (or anyone else trying to help) say is just a wild guess of what the issue could be.
Anyway, I would say that you are having issues due to misconfigured or missing reverse DNS (RDNS) record.
I am not sure what you tested, however try out this page of MXToolBox and put in the hostname of your server.
In addition you should check what your log files say, they are located in /var/log if you are using Linux - one you are interested in is /var/log/maillog.
If this doesn't help, please provide additional information about your system.
Maybe someone knows what the cause of the error? I am trying to come and continue the activation of your NVP / SOAP API Apps, but the server responds with an error. Someone knows what's going on?enter image description here
UPDATE: It looks like over the weekend the app services went back online, so all should be fixed now. Let me know if you encounter any issues with it, and definitely very sorry for any issues this downtime caused you.
At the moment there are some issues at paypal-apps.com, which is affecting the site and ability to create new applications. The teams are working on the servers that are affected and will hopefully have more information soon. I'll update as soon as I have more details though.
I have PEAR Mail and Mail_mime all working very nicely using gmail's SMTP server to send. Thanks to some posts on here that helped me get that far!
But, in some scenarios, I need to send two emails, with different content, and to different recipients one right after the other. This is refusing to work.
I can confirm both the emails I am trying to send are well-formed and valid, as both will send with the other one commented out. But whenever I attempt to send them both, only the first gets through. I have tried putting php to sleep for 10 seconds in between, and I have tried sending the second email in a different script that gets called after the end of the first. Nothing.
I realise this is a pretty obscure problem as I found no other articles mentioning this. I haven't included any code because, as stated, I know the code works fine.
So I am hoping in vein that someone might have a bright idea as to why this might be.
Thanks in advance.
SOLVED: changing
include('Mail.php');
to
require_once('Mail.php');
fixed the problem.
I've spent the last 5 months developing a gwt app, and it's now become time for third party people to start using it. In preparation for this one of them has set up my app behind a reverse proxy, and this immediately resulted in problems with the browser's same origin policy. I guess there's a problem in the response headers, but I can't seem to rewrite them in any way to make the problem go away. I've tried this
response.setHeader("Server", request.getRemoteAddress());
in some sort of naive attempt to mimic the behaviour I want. Didn't work (to the surprise of no-one).
Anyone knowing anything about this will most likely snicker and shake their heads when reading this, and I do not blame them. I would snicker too, if it was me... I know nothing at all about this, and that naturally makes this problem awfully hard to solve. Any help at all will be greatly appreciated.
How can I get the header rewrite to work and get away from the SOP issues I'm dealing with?
Edit: The exact problem I'm getting is a pop-up saying:
"SmartClient can't directly contact
URL
'https://localhost/app/resource?action='doStuffs'"
due to browser same-origin policy.
Remove the host and port number (even
if localhost) to avoid this problem,
or use XJSONDataSource protocol (which
allows cross-site calls), or use the
server-side HttpProxy included with
SmartClient Server."
But I shouldn't need the smartclient HttpProxy, since I have a proxy on top of the server, should I? I've gotten no indications that this could be a serialisation problem, but maybe this message is hiding the real issue...
Solution
chris_l and saret both helped to find the solution, but since I can only mark one I marked the answer from chris_l. Readers are encouraged to bump them both up, they really came through for me here. The solution was quite simple, just remove any absolute paths to your server and use only relative ones, that did the trick for me. Thanks guys!
The SOP (for AJAX requests) applies, when the URL of the HTML page, and the URL of the AJAX requests differ in their "origin". The origin includes host, port and protocol.
So if the page is http://www.example.com/index.html, your AJAX request must also point to something under http://www.example.com. For the SOP, it doesn't matter, if there is a reverse proxy - just make sure, that the URL - as it appears to the browser (including port and protocol) - isn't different. The URL you use internally is irrelevant - but don't use that internal URL in your GWT app!
Note: The solution in the special case of SmartClient turned out to be using relative URLs (instead of absolute URLs to the same origin). Since relative URLs aren't an SOP requirement in browsers, I'd say that's a bug in SmartClient.
What issue are you having exactly?
Having previously had to write a reverseproxy for a GWT app I can't remember hitting any SOP issues, one thing you need to do though is make sure response headers and uri's are rewritten to the reverseproxies url - this includes ajax callback urls.
One issue I hit (which you might also experience) when running behind a reverseproxy was with the serialization policy of GWT server.
Fixing this required writing an implementation of RemoteServiceServlet. While this was in early/mid 2009, it seems the issue still exists.
Seems like others have hit this as well - see this for further details (the answer by Michele Renda in particular)