Bug 40516

Summary:	MAILMERGE: Server Authentication test fails
Product:	LibreOffice	Reporter:	Rainer Bielefeld Retired <LibreOffice>
Component:	Writer	Assignee:	Caolán McNamara <caolanm>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium	CC:	caolanm
Version:	Master old -3.6
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Rainer Bielefeld Retired 2011-08-31 08:23:49 UTC

Observed with Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID: a6adae1-4eb4f62-09af278)]". Steps to reproduce:

1. Open new WRITER document
2. Menu 'Tools -> Options -> Writer -> Mail Merge E-Mail'
3. Insert your settings as usual incl. Server Authentication
4. Click <Test settings>
   Expected: Success
   Actual: Message, please see below.

May be I already had that win 3.4. but problem was not visible because of "Bug 36763 - Mail Merge E-Mail stops with error "Invalid Address""? I am pretty sure that my settings are correct, I always copy/paste them from the same source.

Message:
LibO-dev could not connect to the outgoing mail server. Check your system's settings and the settings in LibO-dev. Check the server name, the port and the secure connections settings
--
<type 'exceptions.SyntaxError'>: invalid syntax (mailmerge.py, line 52), traceback follows
  C:\LOM110829\Basis\program\uno.py:263 in function _uno_import() [return _g_delegatee( name, *optargs, **kwargs )]
  C:\LOM110829\Basis\program\pythonloader.py:113 in function getModuleFromUrl() [return  __import__( dependent )]
  C:\LOM110829\Basis\program\pythonloader.py:125 in function activate() [mod = self.getModuleFromUrl( locationUrl )]

Comment 1 Caolán McNamara 2011-08-31 08:36:48 UTC

the good news is that the new "report the correct error" stuff is working anyway, i.e. the error is described correctly as a syntax error on line 52

fix with

http://cgit.freedesktop.org/libreoffice/core/commit/?id=a434088adf6c93b7e70f7a864c1a86edff3fd641

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.