ah thanks for the tips guys, I still however have not figured out what 'Identify myself as' means yet, I have always put my domain name in there 'just to be sure' lol

Hi, I will keep it simple and get to the point.

On MercuryS SMTP Server in the IP Interface to use, if I enter 127.0.0.1 it will send mail from my computer to anywhere internal network or outside of the network(internet) but will not receive incomming mail.

If I change the IP Interface to listen on 192.168.1.2 (the computer which hosts the mail server) it will receive mail from anywhere but not send mail at all outside of the network. 

My router has ports setup for 25, 110, and forwarded to IP 192.268.1.2.

My OS is windows 10 64bit and I am using  Mercuty v4.62 (because newer versions will not work properly on this machine).

Any help would be much appreciated, thanks

My "IP Interface" field is blank so that Mercury listens on all available interfaces. 

BTW, I have Mercury v4.80.149 running on Win 10 1909.

MercuryS handles incoming SMTP traffic (local or from the Internet), and as Brian says it's recommended to leave the interface setting blank.

Outgoing SMTP is handled by either MercuryE (direct delivery) or MercuryC (delivery through relay server), so that's where to look if there are problems with outgoing mail.

In both cases there can be settings for Mercury core that need to be adjusted as well. Check Mercury help for more information, or post your mercury.ini file here for advise.

What was the issue with v4.80 that prevents you from using it? Running v4.62 under Windows 10 could by itself be problematic.

I changed it to 0.0.0.0 and it now works fine. I can't remember why the newer version wouldn't work but I do remember having a lot of problems with it so reverted back to an older version. It has been fun n games getting it all to work properly but finally I am happy with it now it does all work. thanks for your replies much appreciated.

Mercury 4.80 (4.81.187) is running fine with us on Windows Server 2016 Standard 1607 (which is using the W10 engine as well). For the IP interface we are using server's own local IP 192.168.21.234 without any problems.

In past we experienced problems with Mercury only when too many of my 20 users have activated their FORWARD file function where a lot of incoming internet mails with big attachments have been immediately  forwarded to other internet addresses again. This causes that MercuryC became slower and slower and we had to restart Mercury very often. But since we do not longer use the FORWARD function, and have additionally limited outgoing attachments to 5 MB max, Mercury is running without any problems.

seems a new problem has popped up. for some reason some mail is not sending and ends up in the pending folder whilst others are sending fine. When people use the registration form on my site it generates the email and places them in the pending folder but some are actually sent without any problems. Another issue is that when those that do register and get an email it always seems to go in their junk or spam folder?

[quote user="dchubad"]Another issue is that when those that do register and get an email it always seems to go in their junk or spam folder?
[/quote]

How Mercury is sending emails, via MercuryC or MercuryE?

Check log files for relevant Mercury modules to see if there are any error messages.

There could be a lot of things that trigger messages being classified as spam. Make sure that the generated emails contain all normally expected headers with correct syntax, and add an SPF information in DNS identifying your IP address as permitted sender for the domain if there isn't already such a record.

I am using MercutyE smtp Client because it is easier to configure. I deleted all the logs and queue files to clear the queues. When they start queueing up again I will post back and let you know what the logs show. thanks

[quote user="dchubad"]I am using MercutyE smtp Client because it is easier to configure.[/quote]

I would recommend to switch to MercuryC. With MercuryE you have to take care of the reputation of your mail server by yourself. And in times of spam etc. many mail servers do not accept mails from unknown mailservers or graylisting them where you have to send mails different times until they accept them.

Try using MercuryC instead. We've got about 20 mailboxes with our ISP which will be polled by Mercury regularly and forwarded to our local users. For sending purposes (for all users) we are using only one of the mail user accounts of our ISP. And our ISP, which is a big player in e-mailing, is forwarding all of our mails to the destination mail server, using its own mail server with good reputation with other ISPs. 

Good experiences since years with MercuryC.

the above image are the settings i have when logging into my ISP, I have no idea which one to use or how to use them in mercuryC this is why i used mercuryE for simplicity.  where it says username@talktalk..... do i actualy use username or would i change that to my actual talktalk login username?

I changed to MercutyC, and all is working now. I have tested it with my own hotmail address anyway and seems to work, now lets hope it works for everyone else who tries to use it. This has been a real rollercoaster ride getting this to work properly :)

Try the following settings in MercuryC: MercuryC settings

I've choosen column "Authenticated SMTP" from your provided table above. Might be you have to play around a little bit with "SSL Encryption via STARTTLS command" since your ISP table sais "Outgoing SSL: NO".

The magenta colored area is not soo important for the connection to SMTP server of your ISP but should be adjusted to the paths at your computer. Is needed to say Mercury where it can drop the log files for bugfixing.

thanks for your reply, i edited my last post as I managed to get it working finally. just going to wait for another member to use it and see if they have issues with it. hopefully it will all be fixed now. thanks

Just seen, there are two available SMTP server at your tables above. Don't know why you've got two mail provider. But anyway, you could also use:

SMTP Server: smtp.talktalkbusines.net

User: user@talktalkbusiness.net (enter your particular talktalkbusiness e-mail address)

PW: enter your password

Connection Port: 25

Connection Type: Normal (without encryption) - normally no mail provider still allows an unencryted transmission over port 25. You could also try to use port 587 instead with SSL encryption since these are standard ports.

But anyway. If you have contracts with all of the listed ISPs above, you could take any of these SMTP servers for submittng e-mails.

I used the settings at the top (1st) in the list which seems to be working so much better and trouble free. Emails are now sending AND receiving locally and externally. For once it seems to be working with no issues. thanks

Be aware that MercuryC can be a problem in instances where the SMTP server requires the From: address be one from the credentialed sender.   In this case, all bounces (forwards without edit) fail.

e.g.: The ISP has credentialed MYDOMAIN.COM so allows mail to be processed by their SMTP server only if it contains "@MYDOMAIN.COM" in the From: header.  Everything else is blocked.

I'm still using MercuryE as a result of such an ISP.  I don't need it now but don't have a compelling reason to change back to MercuryC.  I recall some effort was required to get the SPF record set so that messages sent with MercuryE weren't routinely flagged as spam or rejected.

And our experiences are completely opposing. Mail bounces were never a problem with our ISP (of cource depending from ISP rules) when using only one user credentails for all user SMTP traffic. But MercuryE made problems since we are mailing to soo many customers worldwide with soo many different receiving MX servers that we regularly got problems with black- and grey listing. Insread of this, MercuryC is running fine.
Finally everybody have to find out the best solution for the own needs and that's why Mercury is offereing two different SMTP modules.