You should also check out http://mxtoolbox.com. You can put your domain in and
find out all kinds of info, validate your SPF records and see what blacklists
your domain is on. It's a pretty cheap service, like $20 but works really well.
Shane
Sent from my iPhone
> On Mar 12, 2015, at 9:33 PM,
Are you using DKIM on outbound email? That should help:
https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail
Are you doing any forwarding from your personal domain to gmail
addresses? If so, setting up SRS on outbound email can help:
https://en.wikipedia.org/wiki/Sender_Rewriting_Scheme
Als
Apparently gmail is delivering some mail from me marked as spam and
trashing a lot of the rest. This is a horrible violation of the RFCs
and it's causing me some real problems in my life. How do I get them to
quit doing such evil things? I own my own domain and mail server and
I'm the only o
My team is standing up a product that uses Cassandra for one of its databases.
The default product install is a 3-node ring with standard nodes. For
resiliency and a better (no service degradation) upgrade path, we want to
convert the nodes to vnodes and add a new server to the ring.
We have do
Thanks Robert - was just typing up the followup, which said:
-
I guess I could cover the "http://webserver01"; URL case with changing the
httpd.conf rewrite to:
RewriteRule (.*) https://webserver01.mycompany.com%{REQUEST_URI} [R,L]
...and I guess I'm out of luck with the "https://webserver0
I just forgo the RewriteCond in *:80 and use:
RewriteRule ^ https://fully.qualified.name%{REQUEST_URI} [R,L]
If you get a connection on port 80 and you are not configured to talk
SSL on that port, and you want EVERYTHING to use HTTPS, then just one
rewrite rule works great.
For *:443 it is
To avoid this issue in IIS, we used two separate rules in the correct
order. The first rule redirect host to host.domain.com. The next rule in
the sequence was the HTTPs redirect rule.
-D
On Thu, Mar 12, 2015 at 2:29 PM, Robert Hajime Lanning
wrote:
> If you access the site via https://webserver
If you access the site via https://webserver01, then the certificate
mismatch error will happen before the HTTP transaction (and redirect)
can happen.
This is the same for http://webserver01, since your redirect to HTTPS
does not rewrite the hostname.
On 03/12/15 11:01, Will Dennis wrote:
H
Hi all,
I have an Apache site running that should only be accessed via HTTPS. What we
wish to ensure is that if the site is called by it's DNS shortname (example,
`https://webserver01` rather than `https://webserver01.mycompany.com`, that the
URL request is rewritten to be for "https://webserve
