Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: AaronG on February 27, 2006, 01:22:44 AM
-
Hi,
Can someone please explain to me the default functionality of the SMTP server in SMEp3?
Is it REQUIRED to use SSL for SMTP auth to work?
I have only JUST switched our mail server over to this from SME 6.0 (with SMTP Auth Contrib) - i had it tested and working great when it was on version Pre1 and below but since Pre3 I am having all sorts of problems sending emails from NON local Networks. My users are reporting system undeliverable messages.
Can just plain old - SMTP AUTH work? Can i set it as a DB config item?
Something similar to: db configuration setprop pop3 access public
Is this the service I need to change??? Change the Port to 25???
ssmtpd=service
TCPPort=465
access=public
status=enabled
And yes I do understand the security risks of using unencrypted SMTP Auth.
This is quite urgent :-D
-
Aaron,
No you need to change the service smtpd
db configuration setprop smtpd access public
/sbin/e-smith/signal-event email-update
You will now notice that in the server manger you have the option for ssmtp and smtp
Jon
-
Thankyou!!! particularly for your quick response!
I will set this db config item and test it again.
Cheers
Aaron
-
I have only JUST switched our mail server over to this from SME 6.0 (with SMTP Auth Contrib) - i had it tested and working great when it was on version Pre1 and below but since Pre3 I am having all sorts of problems sending emails from NON local Networks. My users are reporting system undeliverable messages.
Please report all issues with SME7 pre releases via the bug tracker. Please provide all details - not "all sorts of problems", but a specific list of problems. This will help you to have a functional system, but also help us to iron out any bugs.
Thanks.
-
Hi Charlie,
I have used the Bug Tracker on numerous occasions for legitimate bugs in the past.
This was a configuration issue rather than a bug - the reports I also getting from my users was also not "specific" however i knew/suspected that they were related to the SMTP auth/SMTP not being allowed for Public Access.
If I still continue to have errors then I will consider this a bug at which time I will log as a bug in the tracker.
Cheers
Aaron
-
I have now entered this as a bug in the bug tracker:
Bug 894
Summary of Bug
Even after allowing PUBLIC access to the SMTPD service as suggested by JonB I still could not use SMTP Auth from an external network.
On investigation I found the following settings in my DB (See below dotted
line)
I noticed there are TWO "Authentication" properties. One with a Capital "A",
the other with a LowerCase "a"
I have since changed the "Authentication" entry to =Enabled and my server now allows Public PLAIN SMTP Auth.
-----------------------------------------------------------
smtpd=service
Authentication=disabled
ExternalInterfacesFilter=/usr/bin/qmail-queue.amavis
Instances=40
InstancesPerIP=5
InternalInterfacesFilter=/usr/bin/qmail-queue.amavis
MaximumDateOffset=0
PatternsScan=disabled
Proxy=enabled
TCPPort=25
TCPProxyPort=25
VirusScan=enabled
access=public
authentication=enabled
status=enabled
tnef2mime=enabled[code][/code]