Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: cscrs on April 15, 2011, 10:15:59 AM
-
Greetings to all,
In our faculty, we use SME Server 7.5.1 as Mail Server (server-only mode). The deal is I am asked to open port 24 (lmtp) as requested; but I couldn't succeed (although I tried several things)
- Firstly I tried the commands :
config set lmtp service access public status enabled TCPPort 24
signal-event remoteaccess-update
after that I tried the command :
nc -v -w 1 localhost -z 1-1500 [search the open ports between 1 and 1500] and got the result :
localhost [127.0.0.1] 995 (pop3s) open
localhost [127.0.0.1] 993 (imaps) open
localhost [127.0.0.1] 980 (http-admin) open
localhost [127.0.0.1] 548 (afpovertcp) open
localhost [127.0.0.1] 515 (printer) open
localhost [127.0.0.1] 465 (smtps) open
localhost [127.0.0.1] 443 (https) open
localhost [127.0.0.1] 389 (ldap) open
localhost [127.0.0.1] 143 (imap) open
localhost [127.0.0.1] 139 (netbios-ssn) open
localhost [127.0.0.1] 110 (pop3) open
localhost [127.0.0.1] 80 (http) open
localhost [127.0.0.1] 25 (smtp) open
localhost [127.0.0.1] 22 (ssh) open
localhost [127.0.0.1] 21 (ftp) open
after that I stopped and started the masq service :
/etc/init.d/masq stop
/etc/init.d/masq start [again no change]
Finally I created a custom-template named 41AllowLMTP in /etc/e-smith/templates/etc/rc.d/init.d/masq
{
$OUT .= <<'HERE';
/sbin/iptables --append INPUT -p tcp --dport 24 -i $OUTERIF -j ACCEPT
HERE
}
and finish it with
expand-template /etc/rc.d/init.d/masq
signal-event remoteaccess-update
service masq restart
iptables -L
Chain InboundTCP_7461 (1 references)
target prot opt source destination
denylog all -- anywhere !wsd.webserver.deneme.local
REJECT tcp -- anywhere wsd.webserver.deneme.local tcp dpt:auth reject-with tcp-reset
ACCEPT tcp -- anywhere wsd.webserver.deneme.local tcp dpt:ftp
ACCEPT tcp -- anywhere wsd.webserver.deneme.local tcp dpt:http
ACCEPT tcp -- anywhere wsd.webserver.deneme.local tcp dpt:lmtp
ACCEPT tcp -- anywhere wsd.webserver.deneme.local tcp dpt:https
ACCEPT tcp -- anywhere wsd.webserver.deneme.local tcp dpt:1723
ACCEPT tcp -- anywhere wsd.webserver.deneme.local tcp dpt:smtp
ACCEPT tcp -- anywhere wsd.webserver.deneme.local tcp dpt:ssh
ACCEPT tcp -- anywhere wsd.webserver.deneme.local tcp dpt:smtps
Still I couldn't open the port 24 although I see on iptables listing and netcat port results.
May I ask your assistance on that issue?
Regards,
Alper Akoguz
-
AFAIK there's no lmtp on SME
have you been asked to add lmtp on your SME or to forward lmtp port?
-
Thank you very much for the reply.
I have been asked to add lmtp (and some other custom ports) on our SME (not to forward).
-
I repeat, as far as I know there's no lmtp service on SME, and sincerely I don't know how to add it (if possible)
-
In order to "open" lmtp on your SME, you would need to figure out how to enable and configure an lmtp server.
It looks as thought there is an lmtp plugin for qpsmtpd, although it seems to provide only limited functionality:
http://ankh-morp.org/code/qpsmtpd/lmtp.html. You can try to set this up yourself, or you can open a "New Feature Request" in the bug tracker.
According to this page on the Zarafa wiki (http://www.zarafa.com/wiki/index.php/Zarafa_LMTP_delivery), zarafa versions 6.2 and up may support lmtp. You could try installing Zarafa on your SME (http://wiki.contribs.org/Zarafa) (I also found this bug report discussing Zarafa & lmtp on SME: http://bugs.contribs.org/show_bug.cgi?id=5783)
-
I have been asked to add lmtp (and some other custom ports) on our SME (not to forward).
Do you know why? What problem are you trying to solve?
As others have said, if you don't have an lmtp server running, there is no point in opening the port in the firewall.
-
Do you know why? What problem are you trying to solve?
As others have said, if you don't have an lmtp server running, there is no point in opening the port in the firewall.
The problem is that, as I learned from MS Sysadmin, when someone wants to add the mail account in MS Outlook, there is an authentication problem from MS Outlook to SME (because the authentication scheme uses lmtp port [24]).
-
The problem is that, as I learned from MS Sysadmin, when someone wants to add the mail account in MS Outlook, there is an authentication problem from MS Outlook to SME (because the authentication scheme uses lmtp port [24]).
MS Outlook works fine without any modification on SME Server (well, it works as fine as it can ;)). If you have issues, please, open a bug on bugzilla.
Regards
-
The problem is that, as I learned from MS Sysadmin, when someone wants to add the mail account in MS Outlook, there is an authentication problem from MS Outlook to SME (because the authentication scheme uses lmtp port [24]).
There's a fair change that the MS Sysadmin doesn't know what he is talking about. It's also very likely that if you change the MS Outlook configuration, it will work, without any SME server modification.
-
The problem is that, as I learned from MS Sysadmin, when someone wants to add the mail account in MS Outlook, there is an authentication problem from MS Outlook to SME (because the authentication scheme uses lmtp port [24]).
I think your sysadmin has been informed wrong. LMTP is a synonym for Local Mail Transport Protocol and RFC 2033 (http://tools.ietf.org/html/rfc2033) does not mention authentication AFAIK.
Since it is meant as a local mail transport medium I doubt that exchange will even communicate on port 24 outside of it's server, let alone to SME Server.
Perhaps you could answer Charlie's question:
Do you know why? What problem are you trying to solve?
Perhaps we can help you find a suitable solution for your problem.