palinka wrote: ↑
I was never good with routes. I'm clearly lacking in understanding something. Running hmailserver 5.7.0 and using a paid relay service.
Company has a google apps domain example.com set up with several mailboxes hosted by gmail, including firstname.lastname@example.org
On hmailserver, I set up new domain example.com and added one account: email@example.com
. I plan to download from gmail via pop3.
I am probably more confused than you but I have been wanting to understand Routes a bit myself so I looked at your problem to see if I can get a better understanding myself and I have these questions.
1. If I read correctly what you are trying to do, you want to download from firstname.lastname@example.org
located on GMail Server to the same email account email@example.com
located on your hMailServer (firstname.lastname@example.org
2. You are not wanting to send email to email@example.com
located on hMailServer to be delivered to firstname.lastname@example.org
(located on GMail).
3. Email sent to email@example.com
(GMail) from some Sender external to hMailServer should be downloaded to firstname.lastname@example.org
As I read the Help Documentation on hMailServer, Routes deliver email to the Target Server hostname. With the Route you specified this is how I understand what would happen:
1. Email sent from email@example.com
(located on hMailServer) would be sent to firstname.lastname@example.org
(located on hMailServer). This is because according to the Help Documentation, hMailServer will send the email to hMailServer if the recipient Email Id (email@example.com
) exists locally on hMailServer (firstname.lastname@example.org
exists on your hMailServer).
2. I interpret the IP Range set up to define what is considered local or external domains on the Target Hostname (GMail.Com in your example). So if i read the Help Documentation correctly your email sent from hMailServer would never leave hMailServer.
3. However, Matt seems to believe he has done this and I would trust Matt's understanding better than mine as I am just now really trying to interpret the Help Documentation.
However again if I read the Help Documentation correctly and I have correctly understood what you want to do is really to download using POP3 from email@example.com
(located on GMail) then I would believe you should be using on hMailServer Domains>example.com>firstname.lastname@example.org
then select External Accounts Tab. The following instructions would be what I would think you would want to do:
From the Help Documentation:
Using the external account functionality, you can configure hMailServer to download email from other e-mail servers, using the POP3 protocol. After the messages have been downloaded, global rules, virus scanning and etc are applied on the messages. After that, they are normally delivered to one or several local accounts.
You have a hMailServer installation where you host email for your domain. You want to download email from another email server and put it in one of the local accounts.
1.Open the account settings for the account you want to download email to (In Your Example the account would be email@example.com
2.Select the External accounts tab
3.Click Add to add a new account.
4.Enter a name for the external account.
5.Enter the login information. (Presumably in your example this would GMail account firstname.lastname@example.org
and its Password).
6.De-select "Deliver to recipients in MIME-headers" (if it is selected)
7.Specify how often you want hMailServer to download messages, and how long they should be stoerd on the remote POP3 server.
8.Save the account
After you have performed the steps above, hMailServer will download the messages and put them in the account in which you created the external account.
END OF Help Documentation External Accounts.
However if you use email@example.com
also on your hMailServer then I do not believe you would be able to send to firstname.lastname@example.org
(located on GMail.com) as hMailServer would send to email@example.com
located on hMailServer. Now for this if you wanted to send with firstname.lastname@example.org
to external email addresses then possibly a Route would be appropriate.
Again as I read the Help Documentation, Routes looked like they were used to send to External Servers not receive from External Servers. External Accounts looked like they were intended to be used to receive from External Email Servers.
Disclaimer: I know nothing about Routes and/or External Accounts save for what I read in the Help Documentation which was confusing enough to read and decipher but then who knows maybe I got it close to right.