Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: koshakis on February 14, 2009, 03:35:53 AM
-
I try to allow external POP3 access on SME 7.4 with the below command but no luck.
config setprop pop3 access public
signal-event email-update
svc -t /service/pop3s
Please help
-
All you need to do is to enable it in the server-manager, just click on Email under the Configuration heading on the left hand side of the server-manager web page. Then forward the appropriate ports if you have a router between the server & the Internet. Remember that SME use secure POP, which uses port 995. Outlook, Outlook Express, Thunderbird & Apple Mail all support secure POP, so I imagine most other email clients do.
HTH
Peter
-
Thanks Peter, but this is not what i want.
Uses on external network must be ample to connect with POP3
without SSL.
Koshakis
-
Unfortunately this isn't possible. What are you trying to achieve exactly? Perhaps we can come up with another method if you can give us some background.
-
What I try to do is to allow User to retrieve mail without using SSL.
I have a mail server for 200 uses and most of them they want access
with POP3 not POP3s.
Koshakis
-
You could try putting the server into Server-Only mode, replacing SME with another gateway/router and then using port forwarding on your new gateway/router to forward SMTP & POP3 requests to the SME server.
I'm not sure whether this will work, but Server-Only mode disables most external security.
-
config setprop pop3 access public
signal-event email-update
signal-event remoteaccess-update
should work..
HTH
ciao
Stefano
-
Stefano,
I try
config setprop pop3 access public
signal-event email-update
signal-event remoteaccess-update
But still not working, any suggestion
Koshakis
-
well
first of all: is your server in server & gateway mode?
then: is port 110 open and forwarded in your router?
please describe your lan/wan setup
thank you
Ciao
Stefano
-
The server is on server & gateway mode
Running on a public ip address and is connected
to a bridge router, no firewall or anything to stop any port.
Up to SME 7.1 everything was fine, the trouble start when update
to 7.4.
Koshakis
-
hi
question: did you upgrade from 7.1 to 7.4?
please post the result of
iptables -L | grep pop3
BTW, if you think something is broken, please open a bug, thank you
Stefano
-
Up to SME 7.1 everything was fine, the trouble start when update
to 7.4.
Anything which you think should work, but doesn't, should be reported via the Bug Tracker.
Allowing plaintext remote access exposes your server to having usernames and passwords stolen. Your users are being either foolish or ignorant in wishing to use pop3 in preference to pop3s, and you'd be well advised to insist on only pop3s.
I presume pop3s does work, so your users "wanting" pop3 is preventing them from having access to their mail.
-
Charlie,
I agree with you but sometime we have to do things even
if don't want to.
Yes POP3s work fine but the question is, can i enable POP3.
I install a fresh SME 7.4 and try again the below command
but no luck.
config setprop pop3 access public
signal-event email-update
signal-event remoteaccess-update
I see an old post from you witch you said is possible with
some commands from the console, any idea?
Koshakis
-
I see an old post from you witch you said is possible with
some commands from the console, any idea?
I gave you this idea in the previous post:
Anything which you think should work, but doesn't, should be reported via the Bug Tracker.
-
Thank you Charlie,
You are very help full ?
I just ask if any one knows how i can do this --at my own risk--
The point is Yes or No.
To put it in the bug tracker must do something witch normally work first
and if is not work then you reported as bug.
Is the bellow commands correct yes or no ?
config setprop pop3 access public
signal-event email-update
signal-event remoteaccess-update
or this
config setprop pop3 access public
signal-event email-update
svc -t /service/pop3s
Thanks in advance.
Koshakis
-
svc -t /service/pop3s
At the very least, you're resetting the wrong service (pop3s instead of pop3). But signal-event is the correct command; you shouldn't need to use svc if everything is working correctly.
-
koshakis: please answer my questions and, of course, raise a bug, thank you
ciao
Stefano
-
Hi Stefano,
Yes I update 7.1 to 7.2, 7.3 then to 7.4
But as i said before even on fresh 7.4 install still no work.
I issue the command iptables -L | grep pop3
and I get: ACCEPT tcp -- anywhere ns1.domain.com.au tcp dpt:pop3s
The port 110 is open.
Koshakis
-
On one of my System SME 7.4
I issue the command
config setprop pop3 access public
signal-event email-update
Then from control Email panel I select
Allow pop3 and pop3s
this line was created after I issue the above command.
on another system the line (Allow pop3 and pop3s)
wasn't created but I Forward 110 to 110 and local ip
in the control Port Forwarding Panel and is work.
Now I can receive on both systems pop3 from external.
Koshakis
-
Solved
-
hi
it would be nice if you share the solution with others, wouldn't it? :-)
Ciao
Stefano
-
hi
it would be nice if you share the solution with others, wouldn't it? :-)
Ciao
Stefano
Yes it doze, if you look 2 post up there is the solution.
Koshakis
-
koshakis,
Can you post the output of:
config show pop3
from the server where it didn't create the new line in server-manager?
(If one worked and another didn't with the same command I would suspect a bug.)
Royce
-
koshakis,
Can you post the output of:
config show pop3
from the server where it didn't create the new line in server-manager?
(If one worked and another didn't with the same command I would suspect a bug.)
Royce
mercyh
Both servers show the same.
TCPPort=110
access=public
status=enabled
Koshakis
-
If you ran the correct signal-event that you listed above on this server and the Allow pop3 and pop3s was not created in server-manager email panel, this should definitely be raised as a bug as for some reason the DB entry is not writing out to the configuration file.
I realize you solved this with a workaround, however if the DB is not working correctly we need to figure out why for the next admin (and maybe for you if there is something mucked up on your server). The bug report is a small price to pay for the use of an excellent piece of software..............
http://wiki.contribs.org/Bugzilla_Help#Bugzilla_is_easy
-
All you need to do is to enable it in the server-manager, just click on Email under the Configuration heading on the left hand side of the server-manager web page. Then forward the appropriate ports if you have a router between the server & the Internet. Remember that SME use secure POP, which uses port 995. Outlook, Outlook Express, Thunderbird & Apple Mail all support secure POP, so I imagine most other email clients do.
HTH
Peter
On a 7.4 server in server-only mode I have done this.
I did the port forword for external pop (995)
the name of the server is wrpcsrvr.
for internal clients we have to set pop to the ip of the server.
for eternal clients I keep getting a pop up message "the certificates' CN name does not match the passed value" do you want to continue.
If I say yes it lets me on, but happens every time we open OE.
the name on cert is wrpcsrvr.theirdomain.com.
I have tried importing cert, same result.
POP is set to 995 on advanced.
any help greatly appreciated.
-
How are the external clients setup? Are they using the FQDN or an alias like www or mail? either of which do not match the CN name.
I personally use a modified version of the self signed scripts available in the how to's that enable support for wild cards on my servers.