Google apps smtp email and relay settings

from: https://support.google.com/a/answer/176600?hl=en

Google Apps SMTP settings to send mail from a printer, scanner, or app

You can set up your on-premises multifunction printer, scanner, fax, or application to send email through Google Apps. The three available options are: SMTP relay service, Gmail SMTP server and Restricted Gmail SMTP server.

For details about configuring your device or application to send SMTP messages, refer to its documentation. Google Support cannot assist with the configuration settings.

  1. SMTP relay service – used to send mail from your organization by authenticating with the IP address(s). You can send messages to anyone inside or outside of your domain.
  2. Gmail SMTP server – requires authentication with your Gmail/Google Apps account and password. Messages can be sent to anyone inside or outside of your domain.
  3. Restricted Gmail SMTP server – does not require authentication, and you will be restricted to send messages to Gmail or Google Apps users only.

The table below will help you decide which one of these options will best meet your needs:

Option Google Apps SMTP relay (recommended) Gmail SMTP server Restricted Gmail SMTP server
FQDN of SMTP Service smtp-relay.gmail.com smtp.gmail.com aspmx.l.google.com
Configuration requirements Port 25, 465, or 587
SSL/TLS optional.
One or more static IP addresses are required.
Port 465 (SSL required)
Port 587 (TLS required)
Dynamic IPs allowed
Port 25
TLS not required
Dynamic IPs allowed
Mail can only be sent to Gmail or Google Apps users
Requires authentication IP address provides authentication. Your full Gmail or Google Apps email address required for authentication No.
Bypasses anti-spam No. Suspicious emails may be filtered. No. Suspicious emails may be filtered. No. Suspicious emails may be filtered.
Sending Limits Limits for registered Google Apps users.
A registered user cannot relay messages to more than 10,000 recipients per day.
For full SMTP relay limits please see Sending limits for the SMTP relay service.
2000 Messages per day. See Sending limits for more detailed information. Per user receiving limits will apply.

You can use the SMTP relay service in the Google Admin console to relay mail from your device or application. This is possible once you add your network IP range to the SMTP relay service. You will need to configure your device to connect to smtp-relay.gmail.com on ports 25 or 465, 587. For more details about using this setting, see SMTP relay service setting.

Gmail SMTP Server could also be used to relay messages from your device or application. You can connect to Gmail mail servers using SMTP, SSL/TLS. If you connect using SMTP, you can only send mail to Gmail or Google Apps users; if you connect using SSL/TLS, you can send mail to anyone.

If your device or application supports SSL – connect to smtp.gmail.com on port 465.

To connect with SSL, you need to provide a Google username and password for authentication. Ensure that the username you use has cleared the CAPTCHA word verification test that appears when the user first logs in. We also recommend ensuring that the account has a secure password.

If your device or application does not support SSL – connect to aspmx.l.google.com on port 25.

You must configure an SPF record for your domain with the IP address of the device or application to ensure that recipients do not reject mail sent from it. You must also add this IP address to the Email Whitelist box in your Google Admin console. For example, if your sending device sends from 123.45.67.89, add that address to your SPF record without removing the Google Apps mail servers from the record: v=spf1 ip4:123.45.67.89 include:_spf.google.com ~all

Google Penguin update – same anchor text now hurts website SEO

If you have the same anchor text in your footer links on all the websites that you create this can now hurt your website SEO. This happened to edublogs, they had to remove more than 10,000 footer links.

Another way to avoid the Penguin update penalty is by making your anchor text footer links nofollow.

Find DNS server records mx cname ttl A record rDNS

Easily find your nameserver’s records including a, mx, cname and ttl for each:
Network-tools.com

My favorite overall DNS testing tool for 2012 is intoDNS.com, which will also show your rDNS record.

DNS propagation – how long does it take for a domain to change to the new server?

The Domain Name record “propagates” as fast or slow as your TTL (time to live) setting is on your A record.

Propagation is not technically correct. It’s cached for the amount of seconds for TTL.

86,400 = 1 day (long)

14,400 = 5 hours (typical)

300 = 5 minutes (short)

Getting ready to change servers? Change it to 300, but remember to set it longer after you’re done.

Don’t want to mess with it? Set it at 14400 (no commas!)

Watch your DNS record (domain name) propagate around the world

There is a DNS cache on your local computer too, to clear it on windows ipconfig /flushdns

If your computer’s DNS server is OpenDNS, you can clear the Master OpenDNS domain name cache here.

Cleaning up text using PHP – remove line breaks and paragraphs and tabs and replace with an empty space

How to tell if your website has a dedicated IP

http://www.robtex.com/ip/

Cannot see new version of website – updates not showing – sticky cache

1) Control-R (or Command-R) – Control – F5 does the same thing on Windows

2) Go through your options and empty the cache manually

3) Try another browser

Users do not normally notice the old website hasn’t changed because they are not talking to the developers and wouldn’t know when the website really has been updated. This happens all the time.

Most likely you have a “sticky cache” on your computer.

Here’s the trick: Whether you get to http://yourwebsite.com by clicking this link, or by going through google, once you see http://yourwebsite.com in the top line of Internet Explorer, Firefox or Chrome (The URL or Location bar), do a hard refresh.

Hard refresh is done when you are supposed to be seeing the new webpage that you are having trouble with, and reaching out to your keyboard, while holding the “control” key, tap and letup on the “r” key, then let go of the “control” key. (Ctrl-r)

This dumps the old cached page that is sitting on your computer and tells it to go load the new one from the internet.

This insures that you are seeing the latest changes to your website.

The “sticky cache” issue is common when developing new websites. Usually people don’t notice changed pages so much because they don’t know the page should have changed. It happens more often than people realize.

Note: If you have an alternate web browser installed that you haven’t used lately, just view the website in it, you should see the latest version automatically, since it’s not been “cached” lately. Browsers do not share each other’s cache.

—-

If you have a really sticky cache:

Log out of WordPress, clear your browser cache, quit and restart the browser and try again. If that does not work, there may be a caching proxy or network cache somewhere between you and your host. You may need to wait for a few hours until this cache expires.

—-

Note: CSS changes can cause a really sticky cache when background images are changed, they tend not to update unless you clear your cache.

My .htaccess tricks

To show a directory listing specifically in that directory only place this in the .htaccess file that resides in that folder:

IndexOptions -FancyIndexing
 Options +Indexes




To deny a directory listing, place this the the .htaccess in that directory or in a higher directory:

 Options -Indexes
 

Now a 403 error will be returned instead.



To redirect to a subdirectory or a folder:


RewriteEngine On
RewriteBase /
RewriteRule ^index.(.*)?$ http://domain.com/subfolder/ [r=301]

This will redirect any attempt to access a file named index.something to your subfolder, whether the file exists or not.

A simple HTML redirect is an alternative:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Your Page Title</title>
<meta http-equiv="REFRESH" content="0;url=http://www.the-domain-you-want-to-redirect-to.com"></HEAD>
<BODY>
Optional page text here.
</BODY>
</HTML>