Feng Forum
Support => Older versions => : gflower May 28, 2010, 05:29:41 AM
-
Hi,
I have a local installation of FengOffice. And, like many people here, I have problems configuring smtp.
I tried almost everything, using my provider smtp and gmail one. Both of them needs authentication, this is the iussue,
I read every post in this forum about smtp authenticatication and I noticed that also with a "standard" gmail server there isn't a clear solution. Why so little attention for a so big problem?
(still looking for how to make my smtp work :\ )
Gianluigi
-
Can you give us more information? When is this happening? When sending email from you account or when sending automatic notifications? What error(s) do you find logged? What Feng version are you using? PHP? Apache? OS? Mysql?
Why so little attention for a so big problem?
We pay attention to every problem.
In this particular case (as in many others) we have very little information to reproduce the issue ...
-
Hi,
error: usual one in this cases
Session "default" started at 2010-05-24T09:50:07+0000
#1 DEBUG: Swift Err: The MTA doesn't support any of Swift's loaded authentication mechanisms
Time since start: 0.26453804969788 seconds
PHP 5.3.1 on windows server 2003 (tried also on XP)
Apache/2.2.14 (Win32) DAV/2 mod_ssl/2.2.14 OpenSSL/0.9.8l mod_autoindex_color PHP/5.3.1 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1
Feng 1.7 beta (but same problem with 1.6 stable).
I use send test mail function in administration pannel.
Mail configuration:
smtp: smtp.gmail.com
port 456
authentication yes, ssl, with correct username & password.
Same thing with another smtp server with authentication.
No problem with an smtp server with no authentication (but I can send mail only in same domain).
Thx :)
-
Thanks
-
I didn't mean to be polemical, I was just wondering why this problem, that I found very often in this forum, has no fixes.
FengOffice is a wonderful project (I use groupwares and project managing tools for years) but with this smtp limitation it loses a lot.
Again, thx for you wonderful work.
-
Problem isolated.
We need to upgrade Swift Mail Library to fix this problem. We plan to do it for 1.7.1