Category: Email

Exchange address book, calendar, and email for Thunderbird - Bridge Exchange to IMAP
article #398, updated 3042 days ago

Try DavMail:

http://davmail.sourceforge.net

It runs in the background on server, desktop, or laptop (Windows, Linux, or Mac), and it translates native Exchange protocols into that which Thunderbird and appropriate add-ins handle very well. In other words, it acts as a live bridge between Exchange protocols and Thunderbird with Lightning, for contacts and calendar. The instructions are thorough and functional.

Categories:      

==============

Sending mass email marketing via SMTP
article #843, updated 3205 days ago

A few methods:

https://sendgrid.com/

https://mandrill.com/

http://smtp.com

The first two have free-of-charge tiers.

Categories:      

==============

Populate the Autocomplete in Outlook 2013
article #809, updated 3310 days ago

  1. Create a new email.
  2. Click the To: button.
  3. Choose all of the contacts that you want to use to populate with.
  4. Click OK. Do NOT send!

Categories:      

==============

Migrate IMAP accounts
article #771, updated 3413 days ago

A recommended tool:

http://imapsync.lamiral.info/

Categories:      

==============

Really good Android email client
article #752, updated 3463 days ago

Try this:

https://play.google.com/store/apps/details?id=com.syntomo.email

Categories:      

==============

A for-pay Exchange connection plugin for Thunderbird
article #723, updated 3553 days ago

Something new, $10/year. Working great for me as of this writing.

https://addons.mozilla.org/en-US/thunderbird/addon/exquilla-exchange-web-services/

Categories:      

==============

Configuring Exchange Autodiscover
article #254, updated 4017 days ago

A Microsoft reference is here:

http://support.microsoft.com/kb/940881

with further notes here:

http://www.thirdtier.net/2009/02/setting-up-an-external-autodiscover-record-for-sbs-2008/

This has to be set at the Internet level only. We’ll use “domain.com” as the domain name, just replace it with yours.

  1. If there are any A or CNAME records pointing to “autodiscover.domain.com”, delete them. If the cert for your server uses “autodiscover.domain.com”, change it to something else, e.g., “remote.domain.com”.
  2. If there are any A or CNAME records pointing to “*.domain.com”, an asterisk for global, you’ll have to remove them too. You will need to replace with multiple specific records, or a subdomain, if you’re using a global configuration.
  3. In your Internet DNS, create a new SRV record:

At Network Solutions, the “Service” pulldown needs to have “_autodiscover”, the “Protocol” pulldown needs to have “_tcp”, “Priority” and “Weight” need to be zero, the “Port” needs to be 443, and the “Target” needs to be the A record name used in the MX record, e.g., “mail.domain.com”.

At GoDaddy, “Service” needs to contain “_autodiscover”, “Protocol” needs to contain “_tcp”, “Name” needs to contain “@”, “Priority” needs to be 0 (zero), “Weight” needs to be 0 (zero), “Port” needs to be 443, and “Target” needs to be the A record name used in the MX record, e.g., “mail.domain.com”.

You can test the setup with nslookup:

nslookup -querytype=SRV _autodiscover._tcp.domain.com

The result should be approximately thus:

Server:  dns.domain.local
Address:  99.88.77.66

Non-authoritative answer:
_autodiscover._tcp.domain.com        SRV service location:
          priority       = 0
          weight         = 0
          port           = 443
          svr hostname   = mail.domain.com

Categories:      

==============

Internet email whitelist
article #537, updated 4030 days ago

Something new, an Internet email whitelist:

http://www.dnswl.org

Categories:      

==============

Configure iPhone for Exchange Email
article #500, updated 4136 days ago

Here is a great set of instructions with screenshots:

http://support.verizonwireless.com/clc/devices/knowledge_base.html?id=47777

Categories:      

==============

Changes to all AT&T/Yahoo/SBCglobal email
article #455, updated 4310 days ago

Learned this today (7/31/2012). AT&T has changed the names of the POP and SMTP servers for all email accounts for att.net, sbcglobal.net, and several others (a list is below). Some users will immediately find that Outlook or other email software will not send or receive email, until it is reconfigured to match; it is not unlikely that the changes will not affect everyone at once, but will eventually become essential.

Previously, each of the domains below had different server names for sending and receiving; now, they are all the same, inbound.att.net for reception (POP) and outbound.att.net for transmission (SMTP). POP has to be done on port 995, SSL turned on; SMTP has to be done on port 465, also with SSL turned on.

ameritech.net
att.net
bellsouth.net
flash.net
nvbell.net
pacbell.net
prodigy.net
sbcglobal.net
snet.net
swbell.net
wans.net

Categories: