Receiving Email With Your Outgoing Mail SMTP Server – Several Easy Steps to Follow

You’ve just set up your outgoing SMTP server and sent mass emails to your customers. You are ready to receive emails and to get answers and orders and you are clicking on the button “Get new messages”, but something is wrong: you have not received any emails.

Don’t panic, there is a solution. This article will tell you some secrets that will help you not only send, but also receive messages with your local outgoing mail SMTP server. Of course, this comical situation is just a joke and you should make sure to set your server to receive before you send.

Make sure you have provisions for your server to run 24/7 without interruption, because you don’t know when someone might email you, so your server has to be up all the time waiting let something come Of course, if it goes down for a few minutes, it’s not critical, since all servers are programmed to retry each email many times.
get static ip

If you read the previous articles you will know that the main thing you should do is:

“Get a static IP from your provider!”

IP is like your postal address: if you have it, a “postman” will not go through your mailbox. So if you talk to your provider and get a static IP, your messages won’t be lost on your server.

If your outgoing SMTP server is behind a router or network address translator (NAT), you will also need to set up a static IP for your PC in addition to the above.
Add DNS record

Your server will not be able to receive email if you forget a single DNS record, called an MX record.

The MX record (or mail exchanger record) specifies a mail server responsible for displaying messages to addresses in the specified domain. The set of MX records for a domain name specifies how email should be routed using SMTP.

Let’s look at an example: your domain is “josh.com

* your IP is “134.54.65.23”

Your MX record will look like this:

* “josh.com MX 10 mail.josh.com” (10 is a priority. If you only have one IP, this doesn’t matter too much

This record is then resolved as an A record for your IP and looks like this:

* “mail.josh.com TO 134.54.65.23”

This means that any server looking to send an email to “peter” at “josh.com” will find that josh.com is entered correctly with an IP of 134.54.65.23 and will be able to connect and send the email. mail.
check your router

The next step is useful for router users. If your computer or server is connected to the router, it is not enough to get a static IP and add an MX record. You also need to configure your router.

Your router usually forwards incoming packets on its own, but if you don’t specifically configure it, there’s no guarantee that incoming connections on port 25 will get through to your PC.

To help your incoming mail not get stuck, you need to set up forwarding of your received email from your router to your internal IP. Internal IP is the static IP of your computer and you need to set it yourself. For example, your router IP is 192.168.1.1 (as usual) and you declared your internal IP as 192.168.1.105 (you need to hardcode it in Windows settings).

So you need to check that your router has a route for port 25 (port 25 => 192.168.1.105). This means that your router will forward any traffic that arrives at your router on port 25 (your port for receiving email) to your internal static IP.

Each type of router is slightly different, but most of them are fairly standardized with how to configure it. You need to access your router, using your web browser by connecting to your router’s internal private IP, and then refer to its internal documentation to configure port forwarding or application sharing (various brands would name this same activity differently).
Check protective suits

Always check your built-in Windows Firewall, Internet security suits, protection and antivirus software. From time to time they can block your incoming traffic, so pay special attention to them. Some firewalls may alert you when software is trying to connect from the outside or getting a connection from the outside, but since you may not be in front of your computer screen when such a message arrives, we recommend that you allow all traffic on the necessary ports manually, or even completely excluding your outgoing SMTP server from your firewall checks.
Add your local domain and local users

Now you need to tell your outgoing SMTP server that you want to accept messages for certain domains. Different mail servers have different ways of doing this, so we’ll show you how it can be done, using our own SMTP server software. Setting up your local domain and local users gives you the ability to receive emails with your outgoing SMTP server and it couldn’t be easier, just don’t forget to provide them with your private usernames and passwords.

Remember to add only the domain part. For example, if you plan to accept email for “peter” at “josh.com”, then you would create a domain called “josh.com” and within this domain, create a user called peter.

Set up your customer email

Now your outgoing SMTP server is ready to receive your emails and all you have to do is customize your email client to read your messages.

To do this, open your Windows Mail or the email client of your choice and:

* Enter the name you want to appear in the “From” field of your outgoing messages (for example, “Josh” or “Peter”)

* Enter your email address – you just configured it in the “Local Users” field of the SMTP server

* Set the IP or hostname of your mail server as SMTP or POP3 servers. If you have installed your SMTP server on the same machine as your mail client, you can enter “localhost” (or 127.0.0.1) as the hostname.

* Enter the username and password given to you in the “Domain Users” menu item of your SMTP server.

Click OK. Now ready! Firm! Go and receive your incoming messages, replies and email requests with your own outgoing SMTP server.

Leave a Reply

Your email address will not be published. Required fields are marked *