Logout

Alt-N Discussion Groups > MDaemon Discussion Groups > MDaemon Issues > Archive > Connection issues after server move

 [F] Alt-N Discussion Groups  / MDaemon Discussion Groups  / MDaemon Issues  / Archive  /

Connection issues after server move

[Stephan, Stephan]
Stephan Stephan
Novice
Novice
Posts: 193
Stephan Stephan - 05:52pm, Dec 4 2019

I had a hardware failure at the location where I run mdaemon. I have moved the entire installation and user files to a different location and now I am having issues with SMTP out service...

Initially I was unable to send any emails at all out. I narrowed it down to me being in a residence and Cox cable blocking Port 25. I bound the outgoing SMTP to Port 587 (this was suggested by someone but I have no idea why this port number worked).

After changing to this port number I thought all was good, but I have since discovered that any attempt to send an email directly to a recipient results in one of two things, either a socket 10060 error, or a different error (554) that seems to have soemthing to do with authentication. When mdaemon encounters these errors, it reroutes the email to my smart host and the email does end up getting sent to the recipient, just not by my server, but by the smarthost instead. While this works, it is not the way things should work and I would like to resolve the problem.

I think it has to do with the fact that I had DKIM, DMARC records set up at my original location that were tied to the IP address there. However, I have altered my dns records to reflect the new IP address for the server and this does not seem to have made a difference. I then disabled DKIM signing in mdaemon, removed the txt records dealing with DKIM, DMARC and SPF from my dns entirely, but still no joy.

Im hoping someone has some insight into what I am confuring incorrectly. I am also open to a paid consultant who is familiar with mdaemon and setting these things up to assist me if necessary.

Thanks, Stephan

  (older msg: 1)All MessagesOldest ItemsOlder ItemsNewer ItemsNewest Items

Stephan Stephan - Dec 26, 2019 12:19 am (#2 Total: 5)  

 

Photo of Author
Stephan Stephan
Novice
Novice
Posts: 193
For anyone reading this thread, ultimately what I ended up doing to get my emails going is to sign up with a third party smtp relay service called SMTP2GO.com.

With this service mdaemon is not doing any of the sending to recipients directly, instead the emails go to this service (via port 2525 which is not blocked in my residential situation) and then the service relays them from there.

I ran into one issue doing this, which is that I had several users who use a gmail or yahoo account to read work emails and I had set up mdaemon to autoforward emails for those users. SMTP2GO's policies prohibit automatic forwarding so I had to turn that off. Since it was only 3 users, I was able to work around this issue by creating rules to send incoming emails to those users as a NOTE to those users. It is functionally almost equivalent to automatic forwarding (esthetically, this solution inserts a line "Forwarded message" into the body of the email before showing the content of the forwarded message.

SMTP2GO has the advantage that they have a setting that inserts tracking into outgoing emails, so now I can see whether an email was delivered as well as whether it was opened and if so for how long and on what client.

Stephan Stephan - Dec 26, 2019 12:26 am (#3 Total: 5)  

 

Photo of Author
Stephan Stephan
Novice
Novice
Posts: 193
@AARON..

Further to your reply (thank you), I have another question. There seem to be 2 places where I can specify a smarthost as my delivery method. (1) One is Setup>Server Settings>Delivery .. (2) the other is Domain Manager>Domain>Smart Host.

My reading of the help file led me to believe that the settings in (2) would take precedence over anything in (1) but this seems to be not the case.

After solving my Port 25 issues by using an STMP relay service, I had left the settings in (1) untouched and just added the new smtp relay service into (2), but I discovered a large number of emails trying to use the settings in (1).

Are you supposed to set both of these locations to the smarthost settings of your choice (which is what I have now done) ?

[Last Editor: Stephan Stephan, Dec 26, 2019 12:26 am. Total Edits: 1]

Stephan Stephan - Dec 26, 2019 12:59 am (#4 Total: 5)  

 

Photo of Author
Stephan Stephan
Novice
Novice
Posts: 193
@aaron - Further to your commentary on my blcoked port 25 issue, you said the following:

"The best fix is to either obtain an internet connection that allows you to send email on port 25 or route all of your outbound mail through your ISPs server".

How do I do this ? I checked Cox.com and it sounds like in order to use their smtp servers to send mail, I have to log into those with my username and PW. The only place in mdaemon whwere i can see that is in the smarthost settings. So in your comment above, is that what you mean, use my ISP (cox) as a smarthost with the required settings filled in there ?

Stephan Stephan - Jan 11, 2020 10:32 pm (#5 Total: 5)  

 

Photo of Author
Stephan Stephan
Novice
Novice
Posts: 193
Replying to: Arron.Caruth@mdaemon.com (Dec 9, 2019 9:25 am)
Changing outbound SMTP traffic to port 587 is not a good idea.  Port 587 is the MSA port and is...

Aaron, when you have a moment, could you reply to the two additional comments I made in this thread ? Thank you



  All MessagesOldest ItemsOlder ItemsNewer ItemsNewest Items



 Content:

Read New | Search

 Guest:

Email to Admin



You are visiting as a Guest user.