gmail
How to Set Up Google Fetcher for web mail
Reasons to Set Up Google Fetcher for web mail:
- Helps fight spam through automated spam detection,
- Reduce bandwidth usage by fetching mails without having to route it from webmail server &
- Assists saving disk space which normally gets occupied by mail box content.
Step by step guide to setup Google mail Fetcher:
- Create and log in into a Gmail account. This is where your web mails will be fetched.
- Check for the gear icon in upper right corner, click the gear and then click See all settings.
- Select Account and Import tab which is fourth from left in the list of tabs.
- Choose Check mail from other accounts – Add a mail account
- Input the details of secondary email address or your webmail address from where you would like to fetch mails.
- Select Next Step to resume process.
- Use the Password field to input the password of your webmail or secondary mail address mentioned.
- In case of a POP3 connection, Port 110.
- Check with your provider for the pop server, in the case of domains hosted on our servers, please use mail.yourdomain.com replacing your domain with your URL
- Label incoming messages (select New Label and create the label you want to use for this email address to keep the mail filtered and easy to find. It will appear on the left hand side of your Gmail interface)
- Archive incoming messages (skip the inbox)
- One click to the button Add Account would mean you are done setting up Google mail Fetcher for your webmail or secondary mail.
- Additionally you can use your newly added account to your ‘from’ addresses. This will allow you to email as webmaster from your Gmail account itself.
Why Google Fetch is a good idea
With the kind of promotion and SEO strategy we have in place, content and video marketing plays a crucial role in success of web ventures. Around 80% of the content produced in last decade is digital content. Webmaster is faced with a stiff challenge of maintaining disk space capable of containing the entire web content.
Saving Disk space is Essential:
When cost effective, moderate size disk space plan is subscribed, the challenge gets steeper. Promotion, bandwidth management and disk space management must go hand in hand to run a hassle free web service. Webmasters are looking out for every possible option to save space for more files and content.
Spammers are bad news:
To add up to the mess, several spammers and hackers try to take down website with vigorous email spamming. The amount of spam or junk mails received accounts to the headache of weeding them and saving space. Some web services run most business operations from mail to mail. Constant spamming could bring down the reputation of mail server too.
Issues with hosting company’s web mail server:
The kind of notification settings, user base, and interactivity could fill in your mail box located within your hosting account. Mail templates with enhanced graphics and themes means a lot of your web disk space is getting occupied by emails. Moreover the inconvenience of logging every time into your hosting account to check mail or wait for forward mails to your custom mail account isn’t quite enjoyable.
Google Fetch comes in handy:
Google tries to solve most day to day problems with their extensive lab applications and tools. One such tool to help webmasters and also the average users to save mail space on secondary accounts is Google Fetch. As the name suggest the tool fetches mails sent to your secondary mail boxes to your Gmail account. It is easy to manage fetched mails by categorizing with name labels to different secondary email accounts.
Google Fetch replaces Email Forwarder:
The process of setting up Google fetch requires minimal steps including server settings changes and mail verification for secondary email. Mail verification typically gives the authority to Gmail to fetch emails from your web email account. An email forwarder setting recognizes mails as spam when they are received in bulk. Nevertheless Google Fetch takes care of spam filtering and receives mail without it being routed from secondary server.