Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: hackersoft on April 19, 2007, 08:37:06 AM
-
I've been trying to solve this problem for two days now and since I can't resolve it nor find any suitable solution in the forum, I'm now creating a new topic.
Here's the story:
I've upgraded my server to a new one and entered a different domain during the setup.
I performed a full restoration using Disk Archive and everything seems to work seemlessly with one exception, I can't use outlook, thunderbird, etc anymore as a mail client.
I try reconfiguring the server back to the original domain name but it seems that the mail settings are not affected. Mail send errors are sent to admin stating
Sorry, I couldn't find any host named niva-isdc.niva-isdc. (#5.1.2)
that's the same message even after changing it to the original domain name.
Any help here?
The following ports are open and accessible with telnet:
POP3S - 995
SSMTP - 465
different domain = niva-isdc
original domain = niva-is.net
-
different domain = niva-isdc
original domain = niva-is.net
I noticed that your original domain had a ".net" in it, but your new domain does not nor any other domain extension. This would certainly do it.
Grattman
-
I just included the different and original domain for reference.
I will clarify it a bit:
1. The old server is running email services smoothly under niva-is.net.
2. I installed a fresh copy of SME to a brand new server and I entered niva-isdc prior to restoration.
3. I yum updated the freshly installed SME and all completed successfully.
4. I installed the dar2 contribs from dmay and performed a full restoration of data/web/accounts/email to the new server. No problems with the restore process and all seem to be working fine.
5. I then logged in to the SME box as admin and changed the niva-isdc domain to niva-is.net.
6. niva-is.net/webmail is working fine but any Mail Client does not work as expected for different ports. e.g. SMTPS, IMAPS, POP3S, IMAP, POP3, SMTP (465, 993, 995, 143, 110, 25) All ports including HTTPS (443) are open from the SME box and the IPCOP box and is still working using the old SME box.
7. I set the standard pop3 to public access and SMTPD authentication to enabled and voila, I can now access the pop3 mailbox and send e-mail using Outlook and Thunderbird through ports 110 and 25.
HANGING QUESTIONS:
a. Why is it that I can no longer use the secured ports for my mail client whilst it seem to work fine in the old Server (old SME box)?
b. How will I know that the required processes are running and what are the required rpms/rpm checklist for mail to make sure secured ports are working?
c. telnet to those ports seem to work both for localhost and other computers on the network so how do I know which process is missing?
d. How can I make the secured ports to work properly? I repeat, all ports required are open from the SME box and the IPCOP box. nmap confirmed it as well. I checked the iptables rules for the mail ports and resulted as all:
ACCEPT tcp -- anywhere nisws1.niva-is.net tcp dpt:http
ACCEPT tcp -- anywhere nisws1.niva-is.net tcp dpt:imap
ACCEPT tcp -- anywhere nisws1.niva-is.net tcp dpt:imaps
ACCEPT tcp -- anywhere nisws1.niva-is.net tcp dpt:ldap
ACCEPT tcp -- anywhere nisws1.niva-is.net tcp dpt:https
ACCEPT tcp -- anywhere nisws1.niva-is.net tcp dpt:pop3
ACCEPT tcp -- anywhere nisws1.niva-is.net tcp dpt:pop3s
ACCEPT tcp -- anywhere nisws1.niva-is.net tcp dpt:smtp
ACCEPT tcp -- anywhere nisws1.niva-is.net tcp dpt:ssh
ACCEPT tcp -- anywhere nisws1.niva-is.net tcp dpt:smtps
e. server-manager e-mail settings are:
E-mail settings
POP3 server access Allow both POP3 and POP3S
IMAP server access Allow both IMAP and IMAPS
Webmail access Allow HTTPS (secure)
Virus scanning Enabled
Spam filtering Enabled
Executable content blocking Enabled
E-mail retrieval mode Standard (SMTP)
SMTP authentication Allow both SMTP and SSMTP
E-mail to unknown users Send to edan
Address of internal mail server
Address of Internet provider's mail server
Any further solution?
Thanks in advance!
-
Any hope on this? I still want to use the secured ports for the mail clients but there seems to be no solutions yet.
Is there a way to check if the required programs are running for it to work? If so, what programs do I need to check to make those features working?
Waiting....
-
6. niva-is.net/webmail is working fine but any Mail Client does not work as expected ...
Detail what works, what doesn't and how you are testing.
BTW, with all the changes you performed did you end with a post-upgrade; reboot?
Darrell
-
Detail what works, what doesn't and how you are testing.
a. Web server works fine.
b. PDC features also works fine.
c. FTPing also works fine.
d. /webmail also works fine.
e. Backup works fine as well.
f. With some tweaks, standard pop3 and smtp port works with any mail clients.
Detail of what doesn't and how you are testing.
a. pop3s, imaps, and smtps does not work - (probable cause: the process for handling pop3s is not running but which one? That is why I want to know any RPMs involved for mail function in SME)
How it was tested?
It still works in the old server with no glitch so there's no mistake in the mail client settings.
Anyway, here's what I did:
An account for a certain user is used for testing.
For outlook:
1. incoming/outgoing server are set to mail.niva-is.net
2. advanced settings for Outgoing is set to authenticate with similar account login settings for that certain user.
3. 995 for POP3S is set with the checkbox for requires ssl ticked. SMTPS is set to 465 requires ssl auth also ticked.
4. Testing is done by sending out e-mail to both external and internal mail addresses.
BTW, with all the changes you performed did you end with a post-upgrade; reboot?
These commands are properly taken care of.
signal-event post-upgrade
signal-event reboot
signal-event email-update
BTW, thanks for your reply! I appreciate it.
Still waiting....
-
Any luck here?
Thanks in advance!
-
I don't know of any simpler or clearer way to check if something is runing but...
ps aux|grep imaps
ps aux|grep smtp
ps aux|grep pop3s
should tell you if the process is runing. You should see something like
root 2445 0.0 0.0 2448 216 ? Ss Apr24 0:00 runsv pop3s
Which would mean that the process is started.
Or type config show pop3s and config show imaps to check the port and status of the process. You should see something like
pop3s=service
TCPPort=995
access=public
status=enabled
-
Here's the results for those commands:
ps aux|grep imaps
root 2812 0.0 0.0 3112 216 ? Ss Apr23 0:00 runsv imaps
imaplog 2876 0.0 0.0 2320 268 ? S Apr23 0:00 /usr/local/bin/multilog t s5000000 /var/log/imaps
root 3804 0.0 0.0 56 44 ? S Apr23 0:00 /usr/bin/tcpsvd -v -i ./peers -c 400 -C 12:421 per host concurrency limit reached\r\n -l 0 0 imaps sslio -vv -/ ../imap/ssl -C imapd.pem -u stunnel /usr/bin/imapfront-auth /usr/libexec/dovecot/imap
root 22846 0.0 0.0 5252 588 pts/0 S+ 18:13 0:00 grep imaps
ps aux | grep smtps
root 22859 0.0 0.0 5504 576 pts/0 S+ 18:14 0:00 grep smtps
ps aux | grep pop3s
root 2818 0.0 0.0 1672 216 ? Ss Apr23 0:00 runsv pop3s
smelog 2855 0.0 0.0 2976 268 ? S Apr23 0:00 /usr/local/bin/multilog t s5000000 /var/log/pop3s
root 3847 0.0 0.0 52 40 ? S Apr23 0:00 tcpsvd -v -i ./peers -c 40 -C 4:421 per host concurrency limit reached\r\n -l 0 0 pop3s sslio -vv -/ /service/imap/ssl -u stunnel -C imapd.pem /var/qmail/bin/qmail-popup nisws1.niva-is.net checkpassword /var/qmail/bin/qmail-pop3d Maildir
root 22867 0.0 0.0 4412 588 pts/0 S+ 18:15 0:00 grep pop3s
So that means the required processes are running? What then could be the problem? Strange....
-
Yes the processes are running.
What is the output of config show command? Status should be set on enabled.
-
Yes those are all enabled and and accessible for public.
Any hint?
-
The only thing i would think of is some sort of a firewall somwhere between the server and your clients.
edit: Do you use fetchmail contrib? Becuse i remember that this contrib had an option (Workstations on the internal LAN cannot access external POP and IMAP servers).
-
I would love to believe that it's the firewall but it's working fine with the old server with the same configuration of SME...
fetchmail? I don't...
I was able to allow the standard SMTP and POP3 to public access but I would really love to use the secured ports instead.
-
I suggest that you post a bug because i don't see anything wrong here. Your old server runs so the new should run as well. This is something for the bugtracker so the devs start to chew on it. :)
-
That is indeed the weirdest thing.
BTW, thanks for the reply... I'll try to create a ticket and see what the dev might have to say.