[ZendTo] Issues with Zend.To 5.1

[Jules]

Richard,

Once you've changed the value of a setting, the comments above that 
setting are kept when you upgrade_preferences_php, as you might have 
added some comments of your own.

So I think the example you were looking at was probably an old one, as 
in the current file the example is definitely on 1 line.

If you haven't changed a particular setting, then 
upgrade_preferences_php replaces the comment block with the new one, as 
(a) you probably haven't added any comments of your own, and (b) if you 
do ever change the setting in the future, you will have the most recent 
description of it.

I have just added a note below the example to point out that settings 
mustn't be split across multiple lines.
Sadly, of course, because you have changed that setting, you won't ever 
see my new note. Ho hum. :-/

Cheers,
Jules.

On 07/07/2018 6:03 pm, Richard H. Burns wrote:
> It was split, so I assumed that was the issue. The only thing I would 
> point out if the example a few lines above that is also split. So I 
> was following the provided example.
>
> *Richard Burns*
>
> */Server and Systems Administrator/*
>
> Office 816.415.7633 <tel:816.415.7633>
>
> William Jewell College | www.jewell.edu <http://www.jewell.edu/>
>
>
>
> On Jul 7, 2018, at 11:38 AM, Jules <Jules at Zend.To 
> <mailto:Jules at Zend.To>> wrote:
>
>> Richard,
>>
>> Did you split the contents of the array over more than 1 line?
>> I can't tell from what you've pasted.
>>
>> If you did, that that would break my upgrader as it doesn't actually 
>> know anything about PHP at all. It just knows about
>>     key => value,
>> lines, comments, and the overall shape of the preferences.php file. 
>> It's language-agnostic.
>>
>> If you didn't split it, I'm going to need to do some digging as this 
>> doesn't happen to me.
>>
>> Cheers,
>> Jules.
>>
>> On 06/07/2018 10:59 pm, Richard H. Burns via ZendTo wrote:
>>>
>>> Actually, this problem is really with 5.09.13.
>>>
>>>                 I did the upgrade to 5.10.2, and found that emails 
>>> were no longer sending. I was getting “SMTP Error: data not 
>>> accepted. SMTP server error: DATA END command failed Detail: 5.7.60 
>>> SMTP; Client does not have permissions to send as this sender SMTP 
>>> code: 550.” The problem is we use relay authentication for the 
>>> Exchange connector and Exchange won’t allow you to authenticate as 
>>> one user, and then send as another. From what I see in the change 
>>> log, Zendto is now trying to send as the from user not the actual 
>>> sender and so it fails. An option to disable this would be beneficial.
>>>
>>> Secondly,
>>>
>>>                 This line - 'authLDAPBaseDN1'           => 
>>> array('OU=group1,DC=part1,DC=part2,DC=part3',
>>>
>>>   'OU=group2,DC=part1,DC=part2,DC=part3'),
>>>
>>>                 Became this line after the upgrade script - 
>>> 'authLDAPBaseDN1'         => 
>>> array('OU=group1,DC=part1,DC=part2,DC=part3',,
>>>
>>>   'OU=group2,DC=part1,DC=part2,DC=part3'),
>>>
>>> Note the second ‘,’ on the first line. This of course caused an error.
>>>
>>> It took a while to figure that one out.
>>>
>>> -- 
>>>
>>> Richard Burns
>>>
>>> Server and Systems Administrator
>>>
>>> Office 816.415.7633
>>>
>>> William Jewell College | www.jewell.edu
>>>
>>>
>>>
>>> _______________________________________________
>>> ZendTo mailing list
>>> ZendTo at zend.to
>>> http://jul.es/mailman/listinfo/zendto
>>
>> Jules
>>
>> -- 
>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>
>> 'When a man points a finger at someone else, he should remember
>>   that four of his fingers are pointing at himself.' - Louis Nizer
>>
>> www.Zend.To
>> Twitter: @JulesFM
>> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

IMPORTANT: This email is intended for the use of the individual
addressee(s) named above and may contain information that is
confidential, privileged or unsuitable for overly sensitive persons
with low self-esteem, no sense of humour or irrational religious
beliefs. If you are not the intended recipient, any dissemination,
distribution or copying of this email is not authorised (either
explicitly or implicitly) and constitutes an irritating social faux
pas.

Unless the word absquatulation has been used in its correct context
somewhere other than in this warning, it does not have any legal
or no grammatical use and may be ignored. No animals were harmed
in the transmission of this email, although the kelpie next door
is living on borrowed time, let me tell you. Those of you with an
overwhelming fear of the unknown will be gratified to learn that
there is no hidden message revealed by reading this warning backwards,
so just ignore that Alert Notice from Microsoft.

However, by pouring a complete circle of salt around yourself and
your computer you can ensure that no harm befalls you and your pets.
If you have received this email in error, please add some nutmeg
and egg whites, whisk and place in a warm oven for 40 minutes.

www.Zend.To
Twitter: @JulesFM
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20180707/929c225b/attachment-0001.html>