From klou at themusiclink.net  Wed Jul  1 21:35:18 2020
From: klou at themusiclink.net (Kris Lou)
Date: Wed, 1 Jul 2020 13:35:18 -0700
Subject: [ZendTo] Automatic Reminders: expiration date
References: <CAGyTNKGTb8jcGF4o_N_BpNLhAQ67wWg6NS87OM2O7YUXEc1iyg@mail.gmail.com>
Message-ID: <WM!209537f7c597e8164fd850fffa1d7526159faf9b70fed1a6aa3487db374bbfa85a8d870b4a5ee89504f6489ce01059fd!@mx.jul.es>

So, this is hilarious.  An email reminder of the drop-off lists the
expiration date of 30 years in the future.



*This is a reminder about a drop-off sent to you, that no one has picked
up.The drop-off will expire in 10919 days and 23 hours after which it will
be automatically deleted.*

6.01-2, CentOS 7, install via repo.

'numberOfDaysToRetain' => 7

The system date is correct.

Any ideas?


Kris Lou
klou at themusiclink.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200701/a1fb976d/attachment.html>

From klou at themusiclink.net  Wed Jul  1 21:37:39 2020
From: klou at themusiclink.net (Kris Lou)
Date: Wed, 1 Jul 2020 13:37:39 -0700
Subject: [ZendTo] Automatic Reminders: expiration date
In-Reply-To: <CAGyTNKGTb8jcGF4o_N_BpNLhAQ67wWg6NS87OM2O7YUXEc1iyg@mail.gmail.com>
References: <CAGyTNKGTb8jcGF4o_N_BpNLhAQ67wWg6NS87OM2O7YUXEc1iyg@mail.gmail.com>
 <CAGyTNKE+sd5VzyG1kfGHh1GpXisf+veNcZ5CGsdeeUdGoYxhUQ@mail.gmail.com>
Message-ID: <WM!d4b93e14e09bbe90da0ea70a4adc840be2c35ea0ffe92e5706fb454e8f497e544494ab7a60a7a5d67534d08de3eda840!@mx.jul.es>

Oops, just saw the 6.02-5 Beta changelog.

Thanks for addressing this!

Kris Lou
klou at themusiclink.net


On Wed, Jul 1, 2020 at 1:35 PM Kris Lou <klou at themusiclink.net> wrote:

> So, this is hilarious.  An email reminder of the drop-off lists the
> expiration date of 30 years in the future.
>
>
>
> *This is a reminder about a drop-off sent to you, that no one has picked
> up.The drop-off will expire in 10919 days and 23 hours after which it will
> be automatically deleted.*
>
> 6.01-2, CentOS 7, install via repo.
>
> 'numberOfDaysToRetain' => 7
>
> The system date is correct.
>
> Any ideas?
>
>
> Kris Lou
> klou at themusiclink.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200701/f6051d9d/attachment.html>

From douglagm at gmail.com  Wed Jul  8 18:08:50 2020
From: douglagm at gmail.com (Gregg Douglas)
Date: Wed, 8 Jul 2020 19:08:50 +0200
Subject: [ZendTo] Predefined Drop Offs
References: <CAKE9jaZw4eZ4JsR7gQVQna032t6c5bOJ=oV7gvAYE=9RJwp2Ew@mail.gmail.com>
Message-ID: <WM!456ff6fe50ae796f1142d9f20c87847d6b2cc0cf898db081c2f24308f181b1e54cc95fde0c7fa91397fb4f7f1311f04b!@mx.jul.es>

Hey Jules,


I hope you are keeping safe and healthy.


I would like to bounce an idea with you?



Take a Lecturer or Tender Officer, they need to request students to submit
assignments or suppliers to submit tenders.



This person (Lecturer or Tender Officer) would then access ZendTO and
create a ?Predefined Drop Off(PDO)?. In this PDO, one would preselect or
predefine all the fields and options. The Subject, would also be
predefined, but would be used as a field to group the PDOs. So, for a
Lecturer they would use the Subject to define the name of the assignment
that the students must submit. A Tender Officer would use the Subject to
define the Tender Reference. The Short Note Field could be left as a free
text block, allowing the Student or Supplier to include a note. There would
also need to be Start and End Date fields, which would define the period
the PDO will be active for.



Then, there would need to be an ?Alternative? Interface for ZendTO. In this
?Alternative? Interface a student or supplier could select the relevant
active Assignment or Tender form a list of all active ones. On selecting
the required item from the list, the normal process of ?Requesting a Drop
Off? would follow, like confirming the email address of the student or
supplier via the verification email. The link in this email would open the
PDO with all the predefined fields and the student or supplier can then
upload and submit the information.


It was a thought I have for a future feature.


Regards

Gregg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200708/658b64e5/attachment-0001.html>

From Jules at Zend.To  Wed Jul  8 18:54:52 2020
From: Jules at Zend.To (Jules)
Date: Wed, 8 Jul 2020 18:54:52 +0100
Subject: [ZendTo] Predefined Drop Offs
In-Reply-To: <WM!456ff6fe50ae796f1142d9f20c87847d6b2cc0cf898db081c2f24308f181b1e54cc95fde0c7fa91397fb4f7f1311f04b!@mx.jul.es>
References: <CAKE9jaZw4eZ4JsR7gQVQna032t6c5bOJ=oV7gvAYE=9RJwp2Ew@mail.gmail.com>
 <WM!456ff6fe50ae796f1142d9f20c87847d6b2cc0cf898db081c2f24308f181b1e54cc95fde0c7fa91397fb4f7f1311f04b!@mx.jul.es>
Message-ID: <09b6725b-f9a5-d072-e35f-70417d903046@Zend.To>

Gregg,

You can basically do all of this now.

Your "Predefined Drop Off(PDO)" is what ZendTo calls a "request for a 
drop-off". There is a button on the main menu to do exactly this.
You can send these to multiple recipients by putting multiple email 
addresses in the "Request a drop-off" form, just separate them with 
commas or spaces.

The rest of it you can do with ZendTo's automation feature, where you 
can create a "request for a drop-off" from the command-line, and hence 
from a script. You would need to write something to tie that in to your 
existing coursework management system, but the scripts that drive ZendTo 
automatically are actually nothing more than a long "curl" command to do 
an HTTP POST operation that supplies all the information in 1 hit.

The automation stuff is documented here
 ??? zend.to/automation
and there is a script called "autorequest" which automates the "request 
a drop-off" process.

Any more questions, problems, or any other way I can help, please do no 
hesitate to get in touch.

I work for a University myself, and have written coursework submission 
systems before. A few of our academics use our instance of ZendTo to get 
coursework submissions from students, especially when they are large 
submissions like videos of interviews.

Hope that helps,
Jules.

On 08/07/2020 18:08, Gregg Douglas via ZendTo wrote:
>
> Hey Jules,
>
>
> I hope you are keeping safe and healthy.
>
>
> I would like to bounce an idea with you?
>
> Take a Lecturer or Tender Officer, they need to request students to 
> submit assignments or suppliers to submit tenders.
>
> This person (Lecturer or Tender Officer) would then access ZendTO and 
> create a ?Predefined Drop Off(PDO)?. In this PDO, one would preselect 
> or predefine all the fields and options. The Subject, would also be 
> predefined, but would be used as a field to group the PDOs. So, for a 
> Lecturer they would use the Subject to define the name of the 
> assignment that the students must submit. A Tender Officer would use 
> the Subject to define the Tender Reference. The Short Note Field could 
> be left as a free text block, allowing the Student or Supplier to 
> include a note. There would also need to be Start and End Date fields, 
> which would define the period the PDO will be active for.
>
> Then, there would need to be an ?Alternative? Interface for ZendTO. In 
> this ?Alternative? Interface a student or supplier could select the 
> relevant active Assignment or Tender form a list of all active ones. 
> On selecting the required item from the list, the normal process of 
> ?Requesting a Drop Off? would follow, like confirming the email 
> address of the student or supplier via the verification email. The 
> link in this email would open the PDO with all the predefined fields 
> and the student or supplier can then upload and submit the information.
>
>
> It was a thought I have for a future feature.
>
>
> Regards
>
> Gregg
>
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Probability factor of one to one. We have normality. I repeat, we
  have normality. Anything you still can't cope with is therefore
  your own problem.' - Trillian, The Hitch Hikers Guide to the Galaxy

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200708/e9d1beba/attachment.html>

From dsolodow at gaylor.com  Thu Jul  9 14:14:52 2020
From: dsolodow at gaylor.com (Solodow, Damien)
Date: Thu, 9 Jul 2020 13:14:52 +0000
Subject: [ZendTo] Chunk name missing or too long
References: <DM5PR04MB08920358BB35E1CAA0D611CABC640@DM5PR04MB0892.namprd04.prod.outlook.com>
Message-ID: <WM!e19ccb01835f4f9fb8d7fe06a03a0661c6de93dcfd499c5b398ca18bd82ea45200d3d5d2d83e032743631f966a3390f5!@mx.jul.es>

Running 6.03-3 on Ubuntu 18.04 LTS
Seeing a few lines of ?Error: Chunk name missing or too long? in the system log. Chunk size is set to the default 50mb, but I didn?t see anything in preferences.php about chunk name.

 ?
[Gaylor Electric logo]<https://gaylor.com/>
[Gaylor Electric Website]<https://gaylor.com/>
[Facebook]<https://www.facebook.com/gaylorelectric>
[Twitter]<https://www.twitter.com/gaylorelectric>
[LinkedIn]<https://www.linkedin.com/company/gaylor-inc-/>
Damien Solodow
IS System Administrator
Gaylor Electric, Inc.
5750 Castle Creek Pkwy N Drive, Suite 400
Indianapolis
,
IN
.
46250
O: 317.815.3103<tel:317.815.3103>
|
M: 317.506.8521<tel:317.506.8521>
317.759.0077 <https://help.gaylor.com/> emergency <https://help.gaylor.com/> IS support<https://help.gaylor.com/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200709/d9d20550/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5535 bytes
Desc: image001.png
URL: <http://jul.es/pipermail/zendto/attachments/20200709/d9d20550/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1014 bytes
Desc: image002.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200709/d9d20550/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 713 bytes
Desc: image003.png
URL: <http://jul.es/pipermail/zendto/attachments/20200709/d9d20550/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 852 bytes
Desc: image004.png
URL: <http://jul.es/pipermail/zendto/attachments/20200709/d9d20550/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 774 bytes
Desc: image005.png
URL: <http://jul.es/pipermail/zendto/attachments/20200709/d9d20550/attachment-0007.png>

From Jules at Zend.To  Thu Jul  9 16:16:10 2020
From: Jules at Zend.To (Jules)
Date: Thu, 9 Jul 2020 16:16:10 +0100
Subject: [ZendTo] Chunk name missing or too long
In-Reply-To: <WM!e19ccb01835f4f9fb8d7fe06a03a0661c6de93dcfd499c5b398ca18bd82ea45200d3d5d2d83e032743631f966a3390f5!@mx.jul.es>
References: <DM5PR04MB08920358BB35E1CAA0D611CABC640@DM5PR04MB0892.namprd04.prod.outlook.com>
 <WM!e19ccb01835f4f9fb8d7fe06a03a0661c6de93dcfd499c5b398ca18bd82ea45200d3d5d2d83e032743631f966a3390f5!@mx.jul.es>
Message-ID: <fb57acef-8e79-8132-b556-dd17fb7e3c7c@Zend.To>

Damien,

Does the log show if any of the errors have anything in common, at all?
Same user, same IP, same anything?
Are you still getting these errors?
If so, how often (compared with some indication of the traffic your 
ZendTo site usually gets)?

The "chunk name" is a random string created by the user's web browser. 
But I do sanity-check it thoroughly on the server.
So it may be nothing more than some "penetration tester" (to be polite) 
trying to use all sorts of other strings and disallowed characters in 
the "chunk name" in order to see if they can break it.

Because the chunked uploading is relatively new in ZendTo, there are 
probably all sorts of lovely people out there trying to see if they can 
do JavaScript injection, SQL injection, all sorts of unpleasant things 
by subverting the new feature.

If none of your users are complaining, and you only see these 
occasionally, then I wouldn't worry too much about this.

Cheers,
Jules.


On 09/07/2020 14:14, Solodow, Damien via ZendTo wrote:
>
> Running 6.03-3 on Ubuntu 18.04 LTS
>
> Seeing a few lines of ?Error: Chunk name missing or too long? in the 
> system log. Chunk size is set to the default 50mb, but I didn?t see 
> anything in preferences.php about chunk name.
>
> ?
>
> Gaylor Electric logo <https://gaylor.com/>
>
> Gaylor Electric Website <https://gaylor.com/>
>
> 	
>
> Facebook <https://www.facebook.com/gaylorelectric>
>
> 	
>
> Twitter <https://www.twitter.com/gaylorelectric>
>
> 	
>
> LinkedIn <https://www.linkedin.com/company/gaylor-inc-/>
>
> 	
>
> *Damien?Solodow*
>
> *IS?System?Administrator*
>
> Gaylor?Electric,?Inc.
>
> 5750?Castle?Creek?Pkwy?N?Drive,?Suite?400
>
> Indianapolis
>
> 	
>
> ,
>
> 	
>
> IN
>
> 	
>
> .
>
> 	
>
> 46250
>
> O: 317.815.3103 <tel:317.815.3103>
>
> 	
>
> |
>
> 	
>
> M: 317.506.8521 <tel:317.506.8521>
>
> *317.759.0077 <https://help.gaylor.com/>emergency 
> <https://help.gaylor.com/>IS?support <https://help.gaylor.com/>*
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'The best and most beautiful things in life cannot be seen or even
  touched; they must be felt with the heart.' - Helen Keller

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200709/9b5151dc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5535 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/9b5151dc/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1014 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/9b5151dc/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 713 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/9b5151dc/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 852 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/9b5151dc/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 774 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/9b5151dc/attachment-0007.png>

From dsolodow at gaylor.com  Thu Jul  9 16:18:54 2020
From: dsolodow at gaylor.com (Solodow, Damien)
Date: Thu, 9 Jul 2020 15:18:54 +0000
Subject: [ZendTo] Chunk name missing or too long
In-Reply-To: <WM!8af257cc6ae1368e16e533b6ecd2903f809bb01098ff759f777b78e16a1bf98387c0b1a51ccf6c3f74bd92962a8154f5!@mx.jul.es>
References: <DM5PR04MB08920358BB35E1CAA0D611CABC640@DM5PR04MB0892.namprd04.prod.outlook.com>
 <WM!e19ccb01835f4f9fb8d7fe06a03a0661c6de93dcfd499c5b398ca18bd82ea45200d3d5d2d83e032743631f966a3390f5!@mx.jul.es>
 <fb57acef-8e79-8132-b556-dd17fb7e3c7c@Zend.To>
 <WM!8af257cc6ae1368e16e533b6ecd2903f809bb01098ff759f777b78e16a1bf98387c0b1a51ccf6c3f74bd92962a8154f5!@mx.jul.es>
 <DM5PR04MB08928F3C404F329EBA4F74B1BC640@DM5PR04MB0892.namprd04.prod.outlook.com>
Message-ID: <WM!9dc9fe93d78f5f813e05665430ea2d125c921091d497935af6eb95589e1cba06a9a7768e85a67ab410d5c0e1c8051455!@mx.jul.es>

It was the same user, IP, etc.
Looks to be a single user thus far; using Firefox.
Found out about it because they hit me up to report that ?shows an upload window, then kaput; no error messages?. Was only like a 60mb file they were trying to upload.

 ?
[Gaylor Electric logo]<https://gaylor.com/>
[Gaylor Electric Website]<https://gaylor.com/>
[Facebook]<https://www.facebook.com/gaylorelectric>
[Twitter]<https://www.twitter.com/gaylorelectric>
[LinkedIn]<https://www.linkedin.com/company/gaylor-inc-/>
Damien Solodow
IS System Administrator
Gaylor Electric, Inc.
5750 Castle Creek Pkwy N Drive, Suite 400
Indianapolis
,
IN
.
46250
O: 317.815.3103<tel:317.815.3103>
|
M: 317.506.8521<tel:317.506.8521>
317.759.0077 <https://help.gaylor.com/> emergency <https://help.gaylor.com/> IS support<https://help.gaylor.com/>

From: Jules <Jules at Zend.To>
Sent: Thursday, July 9, 2020 11:16 AM
To: ZendTo Users <zendto at zend.to>
Cc: Solodow, Damien <dsolodow at gaylor.com>
Subject: Re: [ZendTo] Chunk name missing or too long

Damien,

Does the log show if any of the errors have anything in common, at all?
Same user, same IP, same anything?
Are you still getting these errors?
If so, how often (compared with some indication of the traffic your ZendTo site usually gets)?

The "chunk name" is a random string created by the user's web browser. But I do sanity-check it thoroughly on the server.
So it may be nothing more than some "penetration tester" (to be polite) trying to use all sorts of other strings and disallowed characters in the "chunk name" in order to see if they can break it.

Because the chunked uploading is relatively new in ZendTo, there are probably all sorts of lovely people out there trying to see if they can do JavaScript injection, SQL injection, all sorts of unpleasant things by subverting the new feature.

If none of your users are complaining, and you only see these occasionally, then I wouldn't worry too much about this.

Cheers,
Jules.

On 09/07/2020 14:14, Solodow, Damien via ZendTo wrote:
Running 6.03-3 on Ubuntu 18.04 LTS
Seeing a few lines of ?Error: Chunk name missing or too long? in the system log. Chunk size is set to the default 50mb, but I didn?t see anything in preferences.php about chunk name.

 ?
[Gaylor                                                            Electric logo]<https://gaylor.com/>
[Gaylor                                                            Electric                                                            Website]<https://gaylor.com/>
[Facebook]<https://www.facebook.com/gaylorelectric>
[Twitter]<https://www.twitter.com/gaylorelectric>
[LinkedIn]<https://www.linkedin.com/company/gaylor-inc-/>
Damien Solodow
IS System Administrator
Gaylor Electric, Inc.
5750 Castle Creek Pkwy N Drive, Suite 400
Indianapolis
,
IN
.
46250
O: 317.815.3103<tel:317.815.3103>
|
M: 317.506.8521<tel:317.506.8521>
317.759.0077 <https://help.gaylor.com/> emergency <https://help.gaylor.com/> IS support<https://help.gaylor.com/>




_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto:ZendTo at zend.to>

http://jul.es/mailman/listinfo/zendto



Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'The best and most beautiful things in life cannot be seen or even

 touched; they must be felt with the heart.' - Helen Keller



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200709/75b82b17/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 1014 bytes
Desc: image006.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200709/75b82b17/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5535 bytes
Desc: image001.png
URL: <http://jul.es/pipermail/zendto/attachments/20200709/75b82b17/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 1014 bytes
Desc: image007.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200709/75b82b17/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 713 bytes
Desc: image008.png
URL: <http://jul.es/pipermail/zendto/attachments/20200709/75b82b17/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 852 bytes
Desc: image009.png
URL: <http://jul.es/pipermail/zendto/attachments/20200709/75b82b17/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 774 bytes
Desc: image010.png
URL: <http://jul.es/pipermail/zendto/attachments/20200709/75b82b17/attachment-0007.png>

From Jules at Zend.To  Thu Jul  9 16:24:05 2020
From: Jules at Zend.To (Jules)
Date: Thu, 9 Jul 2020 16:24:05 +0100
Subject: [ZendTo] Chunk name missing or too long
In-Reply-To: <WM!9dc9fe93d78f5f813e05665430ea2d125c921091d497935af6eb95589e1cba06a9a7768e85a67ab410d5c0e1c8051455!@mx.jul.es>
References: <DM5PR04MB08920358BB35E1CAA0D611CABC640@DM5PR04MB0892.namprd04.prod.outlook.com>
 <WM!e19ccb01835f4f9fb8d7fe06a03a0661c6de93dcfd499c5b398ca18bd82ea45200d3d5d2d83e032743631f966a3390f5!@mx.jul.es>
 <fb57acef-8e79-8132-b556-dd17fb7e3c7c@Zend.To>
 <WM!8af257cc6ae1368e16e533b6ecd2903f809bb01098ff759f777b78e16a1bf98387c0b1a51ccf6c3f74bd92962a8154f5!@mx.jul.es>
 <DM5PR04MB08928F3C404F329EBA4F74B1BC640@DM5PR04MB0892.namprd04.prod.outlook.com>
 <WM!9dc9fe93d78f5f813e05665430ea2d125c921091d497935af6eb95589e1cba06a9a7768e85a67ab410d5c0e1c8051455!@mx.jul.es>
Message-ID: <c8c79309-0497-e195-cb04-719857856a53@Zend.To>

Ask them to clear their browser cache completely. Does it behave the 
same in a Firefox "Private Window"?
What exact version of Firefox are they running, and on what OS/platform?

I haven't had complaints from anyone else about the chunked uploading 
not working, and I tested it myself on just about every browser I could 
lay my hands on.

I would be very interested to work out what's going on here...

Cheers,
Jules.

On 09/07/2020 16:18, Solodow, Damien wrote:
>
> It was the same user, IP, etc.
>
> Looks to be a single user thus far; using Firefox.
>
> Found out about it because they hit me up to report that ?shows an 
> upload window, then kaput; no error messages?. Was only like a 60mb 
> file they were trying to upload.
>
> ?
>
> Gaylor Electric logo <https://gaylor.com/>
>
> Gaylor Electric Website <https://gaylor.com/>
>
> 	
>
> Facebook <https://www.facebook.com/gaylorelectric>
>
> 	
>
> Twitter <https://www.twitter.com/gaylorelectric>
>
> 	
>
> LinkedIn <https://www.linkedin.com/company/gaylor-inc-/>
>
> 	
>
> *Damien?Solodow*
>
> *IS?System?Administrator*
>
> Gaylor?Electric,?Inc.
>
> 5750?Castle?Creek?Pkwy?N?Drive,?Suite?400
>
> Indianapolis
>
> 	
>
> ,
>
> 	
>
> IN
>
> 	
>
> .
>
> 	
>
> 46250
>
> O: 317.815.3103 <tel:317.815.3103>
>
> 	
>
> |
>
> 	
>
> M: 317.506.8521 <tel:317.506.8521>
>
> *317.759.0077 <https://help.gaylor.com/>emergency 
> <https://help.gaylor.com/>IS?support <https://help.gaylor.com/>*
>
> *From:* Jules <Jules at Zend.To>
> *Sent:* Thursday, July 9, 2020 11:16 AM
> *To:* ZendTo Users <zendto at zend.to>
> *Cc:* Solodow, Damien <dsolodow at gaylor.com>
> *Subject:* Re: [ZendTo] Chunk name missing or too long
>
> Damien,
>
> Does the log show if any of the errors have anything in common, at all?
> Same user, same IP, same anything?
> Are you still getting these errors?
> If so, how often (compared with some indication of the traffic your 
> ZendTo site usually gets)?
>
> The "chunk name" is a random string created by the user's web browser. 
> But I do sanity-check it thoroughly on the server.
> So it may be nothing more than some "penetration tester" (to be 
> polite) trying to use all sorts of other strings and disallowed 
> characters in the "chunk name" in order to see if they can break it.
>
> Because the chunked uploading is relatively new in ZendTo, there are 
> probably all sorts of lovely people out there trying to see if they 
> can do JavaScript injection, SQL injection, all sorts of unpleasant 
> things by subverting the new feature.
>
> If none of your users are complaining, and you only see these 
> occasionally, then I wouldn't worry too much about this.
>
> Cheers,
> Jules.
>
> On 09/07/2020 14:14, Solodow, Damien via ZendTo wrote:
>
>     Running 6.03-3 on Ubuntu 18.04 LTS
>
>     Seeing a few lines of ?Error: Chunk name missing or too long? in
>     the system log. Chunk size is set to the default 50mb, but I
>     didn?t see anything in preferences.php about chunk name.
>
>     ?
>
>     Gaylor Electric logo <https://gaylor.com/>
>
>     Gaylor Electric Website <https://gaylor.com/>
>
>     	
>
>     Facebook <https://www.facebook.com/gaylorelectric>
>
>     	
>
>     Twitter <https://www.twitter.com/gaylorelectric>
>
>     	
>
>     LinkedIn <https://www.linkedin.com/company/gaylor-inc-/>
>
>     	
>
>     *Damien?Solodow*
>
>     *IS?System?Administrator*
>
>     Gaylor?Electric,?Inc.
>
>     5750?Castle?Creek?Pkwy?N?Drive,?Suite?400
>
>     Indianapolis
>
>     	
>
>     ,
>
>     	
>
>     IN
>
>     	
>
>     .
>
>     	
>
>     46250
>
>     O: 317.815.3103 <tel:317.815.3103>
>
>     	
>
>     |
>
>     	
>
>     M: 317.506.8521 <tel:317.506.8521>
>
>     *317.759.0077 <https://help.gaylor.com/>emergency
>     <https://help.gaylor.com/>IS?support <https://help.gaylor.com/>*
>
>
>
>     _______________________________________________
>
>     ZendTo mailing list
>
>     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>
>     http://jul.es/mailman/listinfo/zendto  <http://jul.es/mailman/listinfo/zendto>
>
>
>
> Jules
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> 'The best and most beautiful things in life cannot be seen or even
>   touched; they must be felt with the heart.' - Helen Keller
> www.Zend.To  <http://www.Zend.To>
> Twitter: @JulesFM

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'The best and most beautiful things in life cannot be seen or even
  touched; they must be felt with the heart.' - Helen Keller

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200709/e47d62cf/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5535 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/e47d62cf/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 1014 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/e47d62cf/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 713 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/e47d62cf/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 852 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/e47d62cf/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 774 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/e47d62cf/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 1014 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/e47d62cf/attachment-0003.jpg>

From john.thurston at alaska.gov  Thu Jul  9 17:32:21 2020
From: john.thurston at alaska.gov (John Thurston)
Date: Thu, 9 Jul 2020 08:32:21 -0800
Subject: [ZendTo] Call to undefined method in savechunk
References: <e4863054-a6a7-f90d-8413-009245cd78dc@alaska.gov>
Message-ID: <WM!adab14eeb11cc2f2f7e18bd3acb99aecccfc1065f3a29174d395c95fe8e4e32ffd4592311a0e8984d96f4aa60eacfeae!@mx.jul.es>

I'm seeing several of these:

> PHP Fatal error:  Uncaught Error: Call to undefined method NSSDropbox::_authorizedUser() in /opt/zendto/www/savechunk.php:108\nStack trace:\n#0 {main}\n  thrown in /opt/zendto/www/savechunk.php on line 108


in my apache log

In the zendto log, at that same time, I see this activity* logged:

> Info: downloading claimID b.3MJ as single zip file Alaska ZendTo-b.3MJ.zip
> Info: no need to send confirmation email to john.doe at alaska.gov for claim b.3MJ
> Info: pickup of claimID b.3MJ as zip by jane.doe at alaska.gov completed.
> Info: Virus scan of dropped-off files  /var/zendto/incoming/G.FY.1 /var/zendto/incoming/G.FY.2 for  passed successfully


I don't understand how there can be an occasional "undefined method" 
error. Isn't it "defined" or "undefined"? Why does something like that 
only show up a couple of times a day?

Version 6.01-2 on CentOS 7

* somewhat redacted
-- 
--
Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska


From Jules at Zend.To  Thu Jul  9 18:02:03 2020
From: Jules at Zend.To (Jules)
Date: Thu, 9 Jul 2020 18:02:03 +0100
Subject: [ZendTo] Chunk name missing or too long
In-Reply-To: <c8c79309-0497-e195-cb04-719857856a53@Zend.To>
References: <DM5PR04MB08920358BB35E1CAA0D611CABC640@DM5PR04MB0892.namprd04.prod.outlook.com>
 <WM!e19ccb01835f4f9fb8d7fe06a03a0661c6de93dcfd499c5b398ca18bd82ea45200d3d5d2d83e032743631f966a3390f5!@mx.jul.es>
 <fb57acef-8e79-8132-b556-dd17fb7e3c7c@Zend.To>
 <WM!8af257cc6ae1368e16e533b6ecd2903f809bb01098ff759f777b78e16a1bf98387c0b1a51ccf6c3f74bd92962a8154f5!@mx.jul.es>
 <DM5PR04MB08928F3C404F329EBA4F74B1BC640@DM5PR04MB0892.namprd04.prod.outlook.com>
 <WM!9dc9fe93d78f5f813e05665430ea2d125c921091d497935af6eb95589e1cba06a9a7768e85a67ab410d5c0e1c8051455!@mx.jul.es>
 <c8c79309-0497-e195-cb04-719857856a53@Zend.To>
Message-ID: <f70dcb1e-3cff-7c7d-58a1-47e3b8d9a8b6@Zend.To>

Damien,

Sorry, I take back what I said.

I went on a hunt for the same error in my production ZendTo server. And 
lo and behold, it happened to the same user a whole row of times. Just 
like it did for you.

A bit of cross-checking with the Apache logs showed that indeed there is 
a bug.
Basically, if the upload of a chunk failed, it should try again.
Because of a stray "_" it was simply failing instead.

So I've fixed that, and have improved the logging of chunk upload 
problems, so that you can easily see whether someone is really having 
problems, or they're just trying to break your ZendTo server by sending 
nasty stuff.

(Oh, and the chunk name is generated by ZendTo and passed to the 
browser, it's not actually created by the browser.)

So these fixes will be in the next release, which I will do hopefully 
tomorrow.

Thanks!
Jules.

On 09/07/2020 16:24, Jules via ZendTo wrote:
> Ask them to clear their browser cache completely. Does it behave the 
> same in a Firefox "Private Window"?
> What exact version of Firefox are they running, and on what OS/platform?
>
> I haven't had complaints from anyone else about the chunked uploading 
> not working, and I tested it myself on just about every browser I 
> could lay my hands on.
>
> I would be very interested to work out what's going on here...
>
> Cheers,
> Jules.
>
> On 09/07/2020 16:18, Solodow, Damien wrote:
>>
>> It was the same user, IP, etc.
>>
>> Looks to be a single user thus far; using Firefox.
>>
>> Found out about it because they hit me up to report that ?shows an 
>> upload window, then kaput; no error messages?. Was only like a 60mb 
>> file they were trying to upload.
>>
>> ?
>>
>> Gaylor Electric logo <https://gaylor.com/>
>>
>> Gaylor Electric Website <https://gaylor.com/>
>>
>> 	
>>
>> Facebook <https://www.facebook.com/gaylorelectric>
>>
>> 	
>>
>> Twitter <https://www.twitter.com/gaylorelectric>
>>
>> 	
>>
>> LinkedIn <https://www.linkedin.com/company/gaylor-inc-/>
>>
>> 	
>>
>> *Damien?Solodow*
>>
>> *IS?System?Administrator*
>>
>> Gaylor?Electric,?Inc.
>>
>> 5750?Castle?Creek?Pkwy?N?Drive,?Suite?400
>>
>> Indianapolis
>>
>> 	
>>
>> ,
>>
>> 	
>>
>> IN
>>
>> 	
>>
>> .
>>
>> 	
>>
>> 46250
>>
>> O: 317.815.3103 <tel:317.815.3103>
>>
>> 	
>>
>> |
>>
>> 	
>>
>> M: 317.506.8521 <tel:317.506.8521>
>>
>> *317.759.0077 <https://help.gaylor.com/>emergency 
>> <https://help.gaylor.com/>IS?support <https://help.gaylor.com/>*
>>
>> *From:* Jules <Jules at Zend.To>
>> *Sent:* Thursday, July 9, 2020 11:16 AM
>> *To:* ZendTo Users <zendto at zend.to>
>> *Cc:* Solodow, Damien <dsolodow at gaylor.com>
>> *Subject:* Re: [ZendTo] Chunk name missing or too long
>>
>> Damien,
>>
>> Does the log show if any of the errors have anything in common, at all?
>> Same user, same IP, same anything?
>> Are you still getting these errors?
>> If so, how often (compared with some indication of the traffic your 
>> ZendTo site usually gets)?
>>
>> The "chunk name" is a random string created by the user's web 
>> browser. But I do sanity-check it thoroughly on the server.
>> So it may be nothing more than some "penetration tester" (to be 
>> polite) trying to use all sorts of other strings and disallowed 
>> characters in the "chunk name" in order to see if they can break it.
>>
>> Because the chunked uploading is relatively new in ZendTo, there are 
>> probably all sorts of lovely people out there trying to see if they 
>> can do JavaScript injection, SQL injection, all sorts of unpleasant 
>> things by subverting the new feature.
>>
>> If none of your users are complaining, and you only see these 
>> occasionally, then I wouldn't worry too much about this.
>>
>> Cheers,
>> Jules.
>>
>> On 09/07/2020 14:14, Solodow, Damien via ZendTo wrote:
>>
>>     Running 6.03-3 on Ubuntu 18.04 LTS
>>
>>     Seeing a few lines of ?Error: Chunk name missing or too long? in
>>     the system log. Chunk size is set to the default 50mb, but I
>>     didn?t see anything in preferences.php about chunk name.
>>
>>     ?
>>
>>     Gaylor Electric logo <https://gaylor.com/>
>>
>>     Gaylor Electric Website <https://gaylor.com/>
>>
>>     	
>>
>>     Facebook <https://www.facebook.com/gaylorelectric>
>>
>>     	
>>
>>     Twitter <https://www.twitter.com/gaylorelectric>
>>
>>     	
>>
>>     LinkedIn <https://www.linkedin.com/company/gaylor-inc-/>
>>
>>     	
>>
>>     *Damien?Solodow*
>>
>>     *IS?System?Administrator*
>>
>>     Gaylor?Electric,?Inc.
>>
>>     5750?Castle?Creek?Pkwy?N?Drive,?Suite?400
>>
>>     Indianapolis
>>
>>     	
>>
>>     ,
>>
>>     	
>>
>>     IN
>>
>>     	
>>
>>     .
>>
>>     	
>>
>>     46250
>>
>>     O: 317.815.3103 <tel:317.815.3103>
>>
>>     	
>>
>>     |
>>
>>     	
>>
>>     M: 317.506.8521 <tel:317.506.8521>
>>
>>     *317.759.0077 <https://help.gaylor.com/>emergency
>>     <https://help.gaylor.com/>IS?support <https://help.gaylor.com/>*
>>
>>
>>
>>     _______________________________________________
>>
>>     ZendTo mailing list
>>
>>     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>>
>>     http://jul.es/mailman/listinfo/zendto  <http://jul.es/mailman/listinfo/zendto>
>>
>>
>>
>> Jules
>> -- 
>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>> 'The best and most beautiful things in life cannot be seen or even
>>   touched; they must be felt with the heart.' - Helen Keller
>> www.Zend.To  <http://www.Zend.To>
>> Twitter: @JulesFM
>
> Jules
>
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
>
> 'The best and most beautiful things in life cannot be seen or even
>   touched; they must be felt with the heart.' - Helen Keller
>
> www.Zend.To
> Twitter: @JulesFM
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Talent is God-given ... be humble;
  fame is man-given ... be grateful;
  conceit is self-given ... be careful.' - John Wooden

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200709/fed78f44/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5535 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/fed78f44/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 1014 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/fed78f44/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 713 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/fed78f44/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 852 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/fed78f44/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 774 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/fed78f44/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 1014 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200709/fed78f44/attachment-0003.jpg>

From Jules at Zend.To  Thu Jul  9 18:05:29 2020
From: Jules at Zend.To (Jules)
Date: Thu, 9 Jul 2020 18:05:29 +0100
Subject: [ZendTo] Call to undefined method in savechunk
In-Reply-To: <WM!adab14eeb11cc2f2f7e18bd3acb99aecccfc1065f3a29174d395c95fe8e4e32ffd4592311a0e8984d96f4aa60eacfeae!@mx.jul.es>
References: <e4863054-a6a7-f90d-8413-009245cd78dc@alaska.gov>
 <WM!adab14eeb11cc2f2f7e18bd3acb99aecccfc1065f3a29174d395c95fe8e4e32ffd4592311a0e8984d96f4aa60eacfeae!@mx.jul.es>
Message-ID: <cb123b79-bfcb-e497-6879-52360367c8be@Zend.To>

John,

Please see my recent posting to the list re "Chunk name missing or too 
long".
This is all the same problem, which I have just fixed.

It only happens relatively rarely, because only a broken upload will 
cause that line of code to be executed.

John ? One thing: assuming that drop-off is still sat on your server, 
could you run it through "unzip -v" to see if it's actually all there, 
and the zip file "works"?

Cheers,
Jules.

On 09/07/2020 17:32, John Thurston via ZendTo wrote:
> I'm seeing several of these:
>
>> PHP Fatal error:? Uncaught Error: Call to undefined method 
>> NSSDropbox::_authorizedUser() in 
>> /opt/zendto/www/savechunk.php:108\nStack trace:\n#0 {main}\n thrown 
>> in /opt/zendto/www/savechunk.php on line 108
>
>
> in my apache log
>
> In the zendto log, at that same time, I see this activity* logged:
>
>> Info: downloading claimID b.3MJ as single zip file Alaska 
>> ZendTo-b.3MJ.zip
>> Info: no need to send confirmation email to john.doe at alaska.gov for 
>> claim b.3MJ
>> Info: pickup of claimID b.3MJ as zip by jane.doe at alaska.gov completed.
>> Info: Virus scan of dropped-off files /var/zendto/incoming/G.FY.1 
>> /var/zendto/incoming/G.FY.2 for passed successfully
>
>
> I don't understand how there can be an occasional "undefined method" 
> error. Isn't it "defined" or "undefined"? Why does something like that 
> only show up a couple of times a day?
>
> Version 6.01-2 on CentOS 7
>
> * somewhat redacted

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'A good programmer is someone who always looks both ways
  before crossing a one-way street.' - Doug Linder

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200709/f9563416/attachment.html>

From Jules at Zend.To  Fri Jul 10 11:48:24 2020
From: Jules at Zend.To (Jules)
Date: Fri, 10 Jul 2020 11:48:24 +0100
Subject: [ZendTo] Bug-fix release 6.03-4
Message-ID: <28f9733d-0aa9-1884-f88d-4630705ad700@Zend.To>

Folks,

Many thanks to those who have reported the occasional strange error 
message in the logs.
I have found and fixed the reasons why these were happening, and have 
improved the logging detail too.

I have just released version 6.03-4, so you should be able to apt/yum 
upgrade to it.

Otherwise you can fetch the packages as usual from
 ??? https://zend.to/downloads

The full Change Log for this release is:

- HTML emails now display correctly on systems running in Dark mode.
- 'showEmailPasscodeCheckbox' now has the expected result in the New
 ? Drop-off form.
- Fixed bug where failed upload of 1 file chunk would cause whole drop-
 ? off upload to fail without reporting error correctly.
- Fixed 2 Javascript bugs in error reporting for "new drop-off" upload code.
- Improved logging of chunk upload errors.
- Logging of new drop-offs and downloaded files now includes the user's
 ? language/locale code, so you can see your users' most common languages.
- Tiny formatting change in drop-off summary page to improve readibility.

Cheers,

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

The current UK shipping forecast:
South Fitzroy: Northerly or northeasterly 5 to 7, perhaps gale 8 later in
east. Moderate or rough. Fair. Good.

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200710/b9e70810/attachment.html>

From MDeerr at hshlawyers.com  Sat Jul 11 02:57:52 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Sat, 11 Jul 2020 01:57:52 +0000
Subject: [ZendTo] Recommended Ubuntu setup for zend.to server
References: <501d6a679ef64cc1897b1f3d02472231@HSH-MAIL.HSH.local>
Message-ID: <WM!74cd3d809c6aaa62f8cb0c2549c5fb4ceccc3ea708ec7ec21c96abef5d402653b7162c2660d56c26f3e1bb61b65150f5!@mx.jul.es>

Hello All,

It?s been roughly 5+ years since I have used Zend.to and roughly the same amount of time since managing one from a Citrix XenServer host with Ubuntu as the Linux server hosting Zend.to.  I would like to eventually put zend.to services into production.  I have access to HP ProLiant server that is now out of official production so I thought I would use it to demo to upper management what zend.to can do for our environment.

I was wondering if someone can provide a bit of advice on best way to set things up.


1.       I have roughly 800GB of storage

2.       I?ll be installing Ubuntu 19.10 (fresh install)

a.       How should I allocate storage? I?m assuming either of these are my choices

                                                               i.      One large partition for OS as well as drop-offs ?

                                                             ii.      One partition for OS and one partition for drop-offs?

b.      When I install Ubuntu, should I leave it fresh without any additional software/services installed during installation?

Any help on best setup would be greatly appreciated.

Many thanks,
Marlon


Marlon Deerr, Technology Manager
416-572-8795 (direct) | MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>
[cid:image9affd7.JPG at 9231f5af.4eb2973d]<https://www.hshlawyers.com>
[cid:image737703.JPG at df3b011b.42b939d7]<https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> [cid:image9df170.JPG at d59c161f.43881377] <https://twitter.com/hshlawyers>  [cid:image5baed2.JPG at 7a109ed4.4483879b] <https://www.facebook.com/HSHPersonalInjuryLawyers/>  [cid:image888a0e.JPG at a9ddc8c1.4791574f] <https://www.youtube.com/user/hshlawyers>      3500 - 20 Queen St. W., Toronto, ON M5H 3R3
Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com<https://www.hshlawyers.com>


This Howie Sacks & Henry e-mail is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200711/c80bd317/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image9affd7.JPG
Type: image/jpeg
Size: 125353 bytes
Desc: image9affd7.JPG
URL: <http://jul.es/pipermail/zendto/attachments/20200711/c80bd317/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image737703.JPG
Type: image/jpeg
Size: 7976 bytes
Desc: image737703.JPG
URL: <http://jul.es/pipermail/zendto/attachments/20200711/c80bd317/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image9df170.JPG
Type: image/jpeg
Size: 7843 bytes
Desc: image9df170.JPG
URL: <http://jul.es/pipermail/zendto/attachments/20200711/c80bd317/attachment-0007.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image5baed2.JPG
Type: image/jpeg
Size: 7268 bytes
Desc: image5baed2.JPG
URL: <http://jul.es/pipermail/zendto/attachments/20200711/c80bd317/attachment-0008.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image888a0e.JPG
Type: image/jpeg
Size: 7059 bytes
Desc: image888a0e.JPG
URL: <http://jul.es/pipermail/zendto/attachments/20200711/c80bd317/attachment-0009.jpe>

From Jules at Zend.To  Sat Jul 11 09:49:25 2020
From: Jules at Zend.To (Jules)
Date: Sat, 11 Jul 2020 09:49:25 +0100
Subject: [ZendTo] Recommended Ubuntu setup for zend.to server
In-Reply-To: <WM!74cd3d809c6aaa62f8cb0c2549c5fb4ceccc3ea708ec7ec21c96abef5d402653b7162c2660d56c26f3e1bb61b65150f5!@mx.jul.es>
References: <501d6a679ef64cc1897b1f3d02472231@HSH-MAIL.HSH.local>
 <WM!74cd3d809c6aaa62f8cb0c2549c5fb4ceccc3ea708ec7ec21c96abef5d402653b7162c2660d56c26f3e1bb61b65150f5!@mx.jul.es>
Message-ID: <b3571514-a7cd-668a-696c-8df315603598@Zend.To>

Marlon,

Considering the timescales you work on, I would advise using the latest 
LTS release of Ubuntu. It may well save you time in the long run.

For the storage, you might want to let Ubuntu do its default behaviour, 
but put /var/zendto in a volume of its own at the end of the disk. 
Everything in /var/zendto needs to be in the same volume/partition.

But if it's only a "throwaway" demo server for The Management(tm), then 
it won't matter much as you'll almost certainly rebuild it before making 
it a production service anyway.

When installing Ubuntu, just do a minimal install. You might want to 
install the openssh-server package to give yourself remote ssh access to 
it, but beyond that the ZendTo Installer will add everything it needs.

Hope that helps,
Jules.

On 11/07/2020 02:57, Marlon Deerr via ZendTo wrote:
>
> Hello All,
>
> It?s been roughly 5+ years since I have used Zend.to and roughly the 
> same amount of time since managing one from a Citrix XenServer host 
> with Ubuntu as the Linux server hosting Zend.to.? I would like to 
> eventually put zend.to services into production.? I have access to HP 
> ProLiant server that is now out of official production so I thought I 
> would use it to demo to upper management what zend.to can do for our 
> environment.
>
> I was wondering if someone can provide a bit of advice on best way to 
> set things up.
>
> 1.I have roughly 800GB of storage
>
> 2.I?ll be installing Ubuntu 19.10 (fresh install)
>
> a.How should I allocate storage? I?m assuming either of these are my 
> choices
>
> i.One large partition for OS as well as drop-offs ?
>
> ii.One partition for OS and one partition for drop-offs?
>
> b.When I install Ubuntu, should I leave it fresh without any 
> additional software/services installed during installation?
>
> Any help on best setup would be greatly appreciated.
>
> Many thanks,
>
> Marlon
>
>
> Marlon Deerr, Technology Manager
> 416-572-8795(direct) | MDeerr at hshlawyers.com 
> <mailto:MDeerr at hshlawyers.com>
> <https://www.hshlawyers.com>
> <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> 
> <https://twitter.com/hshlawyers> 
> <https://www.facebook.com/HSHPersonalInjuryLawyers/> 
> <https://www.youtube.com/user/hshlawyers> 	3500 - 20 Queen St. W., 
> Toronto, ON M5H 3R3
> Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com 
> <https://www.hshlawyers.com>
>
>
> This Howie Sacks & Henry e-mail is privileged, confidential and 
> subject to copyright. Any unauthorized use or disclosure is prohibited.
>
>
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'It's very unlikely indeed he will ever recover consciousness, and
  if he does he won't be the Julian you knew.'
   - A hospital consultant I proved very wrong in 2007 :-)

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200711/c299c66c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image9affd7.JPG
Type: image/jpeg
Size: 125353 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200711/c299c66c/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image737703.JPG
Type: image/jpeg
Size: 7976 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200711/c299c66c/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image9df170.JPG
Type: image/jpeg
Size: 7843 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200711/c299c66c/attachment-0007.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image5baed2.JPG
Type: image/jpeg
Size: 7268 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200711/c299c66c/attachment-0008.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image888a0e.JPG
Type: image/jpeg
Size: 7059 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200711/c299c66c/attachment-0009.jpe>

From l.capriotti at tiscali.it  Sun Jul 12 14:29:51 2020
From: l.capriotti at tiscali.it (Luigi Capriotti)
Date: Sun, 12 Jul 2020 15:29:51 +0200
Subject: [ZendTo] Predefined Drop Offs
In-Reply-To: <WM!63417b4327016709a5da7879eade76ad0bdf6be5eda6485bad02331d5fecdf3538af0d4dcceefe1797bfcd5ed63d4f92!@mx.jul.es>
References: <CAKE9jaZw4eZ4JsR7gQVQna032t6c5bOJ=oV7gvAYE=9RJwp2Ew@mail.gmail.com>
 <09b6725b-f9a5-d072-e35f-70417d903046@Zend.To>
 <WM!456ff6fe50ae796f1142d9f20c87847d6b2cc0cf898db081c2f24308f181b1e54cc95fde0c7fa91397fb4f7f1311f04b!@mx.jul.es>
 <WM!63417b4327016709a5da7879eade76ad0bdf6be5eda6485bad02331d5fecdf3538af0d4dcceefe1797bfcd5ed63d4f92!@mx.jul.es>
 <CAFwmc2AZYLXfsNitGiV1=P+Ystfamdy74JGzfcT_mRczdjxRhQ@mail.gmail.com>
Message-ID: <WM!d60eddf2012381f1321d1a13dfde672e8072982f03364a79b7d8f139d2c43c2d4046cbd8ecd578cacf8c273cbdf1d071!@mx.jul.es>

Hi Jules,

>There would also need to be Start and End Date fields, which would define
the period the PDO will be active for.
this is not 100% feasible right now, isn't it.
Acknowledging the start date is not easily implemented with the current
backend library, I would envisage the availability of an "advanced" PDO
setup option where the end of the drop-off validity can be set based on
calendar/time pickers. The specified timestamp would be used to calculate
the validity of the drop-off in minutes.

Luigi


On Wed, Jul 8, 2020 at 7:55 PM Jules via ZendTo <zendto at zend.to> wrote:

> Gregg,
>
> You can basically do all of this now.
>
> Your "Predefined Drop Off(PDO)" is what ZendTo calls a "request for a
> drop-off". There is a button on the main menu to do exactly this.
> You can send these to multiple recipients by putting multiple email
> addresses in the "Request a drop-off" form, just separate them with commas
> or spaces.
>
> The rest of it you can do with ZendTo's automation feature, where you can
> create a "request for a drop-off" from the command-line, and hence from a
> script. You would need to write something to tie that in to your existing
> coursework management system, but the scripts that drive ZendTo
> automatically are actually nothing more than a long "curl" command to do an
> HTTP POST operation that supplies all the information in 1 hit.
>
> The automation stuff is documented here
>     zend.to/automation
> and there is a script called "autorequest" which automates the "request a
> drop-off" process.
>
> Any more questions, problems, or any other way I can help, please do no
> hesitate to get in touch.
>
> I work for a University myself, and have written coursework submission
> systems before. A few of our academics use our instance of ZendTo to get
> coursework submissions from students, especially when they are large
> submissions like videos of interviews.
>
> Hope that helps,
> Jules.
>
> On 08/07/2020 18:08, Gregg Douglas via ZendTo wrote:
>
> Hey Jules,
>
>
> I hope you are keeping safe and healthy.
>
>
> I would like to bounce an idea with you?
>
>
>
> Take a Lecturer or Tender Officer, they need to request students to submit
> assignments or suppliers to submit tenders.
>
>
>
> This person (Lecturer or Tender Officer) would then access ZendTO and
> create a ?Predefined Drop Off(PDO)?. In this PDO, one would preselect or
> predefine all the fields and options. The Subject, would also be
> predefined, but would be used as a field to group the PDOs. So, for a
> Lecturer they would use the Subject to define the name of the assignment
> that the students must submit. A Tender Officer would use the Subject to
> define the Tender Reference. The Short Note Field could be left as a free
> text block, allowing the Student or Supplier to include a note. There would
> also need to be Start and End Date fields, which would define the period
> the PDO will be active for.
>
>
>
> Then, there would need to be an ?Alternative? Interface for ZendTO. In
> this ?Alternative? Interface a student or supplier could select the
> relevant active Assignment or Tender form a list of all active ones. On
> selecting the required item from the list, the normal process of
> ?Requesting a Drop Off? would follow, like confirming the email address of
> the student or supplier via the verification email. The link in this email
> would open the PDO with all the predefined fields and the student or
> supplier can then upload and submit the information.
>
>
> It was a thought I have for a future feature.
>
>
> Regards
>
> Gregg
>
>
>
> _______________________________________________
> ZendTo mailing listZendTo at zend.tohttp://jul.es/mailman/listinfo/zendto
>
>
> Jules
>
> --
> Julian Field MEng CEng CITP MBCS MIEEE MACM
>
> 'Probability factor of one to one. We have normality. I repeat, we
>  have normality. Anything you still can't cope with is therefore
>  your own problem.' - Trillian, The Hitch Hikers Guide to the Galaxy
> www.Zend.To
> Twitter: @JulesFM
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200712/0d64ba10/attachment.html>

From Jules at Zend.To  Sun Jul 12 15:30:27 2020
From: Jules at Zend.To (Jules)
Date: Sun, 12 Jul 2020 15:30:27 +0100
Subject: [ZendTo] Predefined Drop Offs
In-Reply-To: <WM!d0ad96999c79c93158e02dce71309d35cb34eafda26939cbdc949f37429c39a68f5373a8019fe0ff02c95cc61d3c4356!@mx.jul.es>
References: <CAKE9jaZw4eZ4JsR7gQVQna032t6c5bOJ=oV7gvAYE=9RJwp2Ew@mail.gmail.com>
 <09b6725b-f9a5-d072-e35f-70417d903046@Zend.To>
 <WM!456ff6fe50ae796f1142d9f20c87847d6b2cc0cf898db081c2f24308f181b1e54cc95fde0c7fa91397fb4f7f1311f04b!@mx.jul.es>
 <WM!63417b4327016709a5da7879eade76ad0bdf6be5eda6485bad02331d5fecdf3538af0d4dcceefe1797bfcd5ed63d4f92!@mx.jul.es>
 <CAFwmc2AZYLXfsNitGiV1=P+Ystfamdy74JGzfcT_mRczdjxRhQ@mail.gmail.com>
 <WM!d0ad96999c79c93158e02dce71309d35cb34eafda26939cbdc949f37429c39a68f5373a8019fe0ff02c95cc61d3c4356!@mx.jul.es>
Message-ID: <5a0398cb-6f4b-01f0-69c2-4b3823bb11d5@Zend.To>

Luigi,

On 12/07/2020 14:29, Luigi Capriotti wrote:
> Hi Jules,
>
> >There would also need to be Start and End Date fields, which would 
> define the period the PDO will be active for.
> this is not 100% feasible right now, isn't it.
> Acknowledging the?start date is not easily implemented with the 
> current backend library, I would envisage the availability of an 
> "advanced" PDO setup option where the end of the drop-off validity can 
> be set based on calendar/time pickers. The specified timestamp would 
> be used to calculate the validity of the drop-off in minutes.
The "start date" is the time when you create the request.
The "end date" is now + the lifetime of the drop-off. But agreed, 
currently the request doesn't let you set the individual dropoff's 
lifetime. You can only set that when you create a drop-off.

But yes, a couple of date/time pickers in the UI would be the ideal 
solution.

I'll add it to the list...

Cheers,
Jules.




>
> Luigi
>
> On Wed, Jul 8, 2020 at 7:55 PM Jules via ZendTo <zendto at zend.to 
> <mailto:zendto at zend.to>> wrote:
>
>     Gregg,
>
>     You can basically do all of this now.
>
>     Your "Predefined Drop Off(PDO)" is what ZendTo calls a "request
>     for a drop-off". There is a button on the main menu to do exactly
>     this.
>     You can send these to multiple recipients by putting multiple
>     email addresses in the "Request a drop-off" form, just separate
>     them with commas or spaces.
>
>     The rest of it you can do with ZendTo's automation feature, where
>     you can create a "request for a drop-off" from the command-line,
>     and hence from a script. You would need to write something to tie
>     that in to your existing coursework management system, but the
>     scripts that drive ZendTo automatically are actually nothing more
>     than a long "curl" command to do an HTTP POST operation that
>     supplies all the information in 1 hit.
>
>     The automation stuff is documented here
>     zend.to/automation <http://zend.to/automation>
>     and there is a script called "autorequest" which automates the
>     "request a drop-off" process.
>
>     Any more questions, problems, or any other way I can help, please
>     do no hesitate to get in touch.
>
>     I work for a University myself, and have written coursework
>     submission systems before. A few of our academics use our instance
>     of ZendTo to get coursework submissions from students, especially
>     when they are large submissions like videos of interviews.
>
>     Hope that helps,
>     Jules.
>
>     On 08/07/2020 18:08, Gregg Douglas via ZendTo wrote:
>>
>>     Hey Jules,
>>
>>
>>     I hope you are keeping safe and healthy.
>>
>>
>>     I would like to bounce an idea with you?
>>
>>     Take a Lecturer or Tender Officer, they need to request students
>>     to submit assignments or suppliers to submit tenders.
>>
>>     This person (Lecturer or Tender Officer) would then access ZendTO
>>     and create a ?Predefined Drop Off(PDO)?. In this PDO, one would
>>     preselect or predefine all the fields and options. The Subject,
>>     would also be predefined, but would be used as a field to group
>>     the PDOs. So, for a Lecturer they would use the Subject to define
>>     the name of the assignment that the students must submit. A
>>     Tender Officer would use the Subject to define the Tender
>>     Reference. The Short Note Field could be left as a free text
>>     block, allowing the Student or Supplier to include a note. There
>>     would also need to be Start and End Date fields, which would
>>     define the period the PDO will be active for.
>>
>>     Then, there would need to be an ?Alternative? Interface for
>>     ZendTO. In this ?Alternative? Interface a student or supplier
>>     could select the relevant active Assignment or Tender form a list
>>     of all active ones. On selecting the required item from the list,
>>     the normal process of ?Requesting a Drop Off? would follow, like
>>     confirming the email address of the student or supplier via the
>>     verification email. The link in this email would open the PDO
>>     with all the predefined fields and the student or supplier can
>>     then upload and submit the information.
>>
>>
>>     It was a thought I have for a future feature.
>>
>>
>>     Regards
>>
>>     Gregg
>>
>>
>>
>>     _______________________________________________
>>     ZendTo mailing list
>>     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>>     http://jul.es/mailman/listinfo/zendto  <http://jul.es/mailman/listinfo/zendto>
>
>     Jules
>
>     -- 
>     Julian Field MEng CEng CITP MBCS MIEEE MACM
>
>     'Probability factor of one to one. We have normality. I repeat, we
>       have normality. Anything you still can't cope with is therefore
>       your own problem.' - Trillian, The Hitch Hikers Guide to the Galaxy
>
>     www.Zend.To  <http://www.Zend.To>
>     Twitter: @JulesFM
>
>     _______________________________________________
>     ZendTo mailing list
>     ZendTo at zend.to <mailto:ZendTo at zend.to>
>     http://jul.es/mailman/listinfo/zendto
>     <http://jul.es/mailman/listinfo/zendto>
>

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'There is silent poetry in the stillness of morning;
  in the calm, the cries & sighs of life sound like gentle music.'
  - @Astro_Wheels

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200712/39ae1803/attachment-0001.html>

From MDeerr at hshlawyers.com  Sun Jul 12 19:12:27 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Sun, 12 Jul 2020 18:12:27 +0000
Subject: [ZendTo] Recommended Ubuntu setup for zend.to server
In-Reply-To: <WM!fc85f63935c54d20cc03850c63796f116426647b8c3656d68091497af810f291f70d0cde8b5fc5e9959bb9c7d8aecc7f!@mx.jul.es>
References: <501d6a679ef64cc1897b1f3d02472231@HSH-MAIL.HSH.local>
 <WM!74cd3d809c6aaa62f8cb0c2549c5fb4ceccc3ea708ec7ec21c96abef5d402653b7162c2660d56c26f3e1bb61b65150f5!@mx.jul.es>
 <b3571514-a7cd-668a-696c-8df315603598@Zend.To>
 <WM!fc85f63935c54d20cc03850c63796f116426647b8c3656d68091497af810f291f70d0cde8b5fc5e9959bb9c7d8aecc7f!@mx.jul.es>
 <ecb401bb61ea4929b94bf3233f790446@HSH-MAIL.HSH.local>
Message-ID: <WM!2fc026cf8a243d3d2e0067f3254575be265b23fb1379b313ed597d0db8cff87b898fdc4ae438438a17d0f0ec5d7932f2!@mx.jul.es>

Thanks Jules,

I appreciate the response.  I?ll rebuild using Ubuntu 20.04 instead.

What about sizing out memory? We have roughly 90+ employees but of that, I would say roughly 40+ of those will be actively using the service. I was thinking of assigning 32GB to it but is that overkill?



From: Jules [mailto:Jules at Zend.To]
Sent: Saturday, July 11, 2020 4:49 AM
To: ZendTo Users <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] Recommended Ubuntu setup for zend.to server

Marlon,

Considering the timescales you work on, I would advise using the latest LTS release of Ubuntu. It may well save you time in the long run.

For the storage, you might want to let Ubuntu do its default behaviour, but put /var/zendto in a volume of its own at the end of the disk. Everything in /var/zendto needs to be in the same volume/partition.

But if it's only a "throwaway" demo server for The Management(tm), then it won't matter much as you'll almost certainly rebuild it before making it a production service anyway.

When installing Ubuntu, just do a minimal install. You might want to install the openssh-server package to give yourself remote ssh access to it, but beyond that the ZendTo Installer will add everything it needs.

Hope that helps,
Jules.
On 11/07/2020 02:57, Marlon Deerr via ZendTo wrote:
Hello All,

It?s been roughly 5+ years since I have used Zend.to and roughly the same amount of time since managing one from a Citrix XenServer host with Ubuntu as the Linux server hosting Zend.to.  I would like to eventually put zend.to services into production.  I have access to HP ProLiant server that is now out of official production so I thought I would use it to demo to upper management what zend.to can do for our environment.

I was wondering if someone can provide a bit of advice on best way to set things up.


1.       I have roughly 800GB of storage

2.       I?ll be installing Ubuntu 19.10 (fresh install)

1.       How should I allocate storage? I?m assuming either of these are my choices

1. One large partition for OS as well as drop-offs ?

2. One partition for OS and one partition for drop-offs?

2.       When I install Ubuntu, should I leave it fresh without any additional software/services installed during installation?

Any help on best setup would be greatly appreciated.

Many thanks,
Marlon


Marlon Deerr, Technology Manager
416-572-8795 (direct) | MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>
[cid:image001.jpg at 01D65856.792FDD20]<https://www.hshlawyers.com>
[cid:image002.jpg at 01D65856.792FDD20]<https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> [cid:image003.jpg at 01D65856.792FDD20] <https://twitter.com/hshlawyers>  [cid:image004.jpg at 01D65856.792FDD20] <https://www.facebook.com/HSHPersonalInjuryLawyers/>  [cid:image005.jpg at 01D65856.792FDD20] <https://www.youtube.com/user/hshlawyers>

3500 - 20 Queen St. W., Toronto, ON M5H 3R3
Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com<https://www.hshlawyers.com>



This Howie Sacks & Henry e-mail is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited.






_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto:ZendTo at zend.to>

http://jul.es/mailman/listinfo/zendto



Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'It's very unlikely indeed he will ever recover consciousness, and

 if he does he won't be the Julian you knew.'

  - A hospital consultant I proved very wrong in 2007 :-)



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200712/9cc5f993/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 12435 bytes
Desc: image001.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200712/9cc5f993/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 777 bytes
Desc: image002.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200712/9cc5f993/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 768 bytes
Desc: image003.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200712/9cc5f993/attachment-0007.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 756 bytes
Desc: image004.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200712/9cc5f993/attachment-0008.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 752 bytes
Desc: image005.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200712/9cc5f993/attachment-0009.jpg>

From KLE at msktd.com  Mon Jul 13 14:21:47 2020
From: KLE at msktd.com (Ken Etter)
Date: Mon, 13 Jul 2020 09:21:47 -0400
Subject: [ZendTo] Recommended Ubuntu setup for zend.to server
In-Reply-To: <WM!559d79b4fb237941d6bf49ebae6c5419b4437b9b24d209e16cbeb82151168fdae0b545471b9c022fdbcd99519ffdf99f!@mx.jul.es>
References: <501d6a679ef64cc1897b1f3d02472231@HSH-MAIL.HSH.local>
 <WM!74cd3d809c6aaa62f8cb0c2549c5fb4ceccc3ea708ec7ec21c96abef5d402653b7162c2660d56c26f3e1bb61b65150f5!@mx.jul.es>
 <b3571514-a7cd-668a-696c-8df315603598@Zend.To>
 <WM!fc85f63935c54d20cc03850c63796f116426647b8c3656d68091497af810f291f70d0cde8b5fc5e9959bb9c7d8aecc7f!@mx.jul.es>
 <ecb401bb61ea4929b94bf3233f790446@HSH-MAIL.HSH.local>
 <WM!2fc026cf8a243d3d2e0067f3254575be265b23fb1379b313ed597d0db8cff87b898fdc4ae438438a17d0f0ec5d7932f2!@mx.jul.es>
 <WM!559d79b4fb237941d6bf49ebae6c5419b4437b9b24d209e16cbeb82151168fdae0b545471b9c022fdbcd99519ffdf99f!@mx.jul.es>
 <5F0C5FEB020000130014617E@mail.msktd.com>
Message-ID: <WM!4fec8867520d9c3e5712c20aaf59ca573d073bdcc6fe3e0eef647255bd4b2db7b2094778f1fc1bd18fdf6903e8eebfec!@mx.jul.es>

32 GB is way overkill unless you have something going on that we aren't
aware of.  The employee count at my office is similar to yours and I run
my ZendTo server with 4 GB and it doesn't break a sweat.  :-)
>>> Marlon Deerr via ZendTo <zendto at zend.to> 7/12/2020 2:12 PM >>>
Thanks Jules,
 
I appreciate the response.  I?ll rebuild using Ubuntu 20.04 instead. 
 
What about sizing out memory? We have roughly 90+ employees but of
that, I would say roughly 40+ of those will be actively using the
service. I was thinking of assigning 32GB to it but is that overkill?
 
 
 
From: Jules [mailto:Jules at Zend.To] 
Sent: Saturday, July 11, 2020 4:49 AM
To: ZendTo Users <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] Recommended Ubuntu setup for zend.to server
 
Marlon,

Considering the timescales you work on, I would advise using the latest
LTS release of Ubuntu. It may well save you time in the long run.

For the storage, you might want to let Ubuntu do its default behaviour,
but put /var/zendto in a volume of its own at the end of the disk.
Everything in /var/zendto needs to be in the same volume/partition.

But if it's only a "throwaway" demo server for The Management(tm), then
it won't matter much as you'll almost certainly rebuild it before making
it a production service anyway.

When installing Ubuntu, just do a minimal install. You might want to
install the openssh-server package to give yourself remote ssh access to
it, but beyond that the ZendTo Installer will add everything it needs.

Hope that helps,
Jules.
On 11/07/2020 02:57, Marlon Deerr via ZendTo wrote:


Hello All,
 
It?s been roughly 5+ years since I have used Zend.to and roughly the
same amount of time since managing one from a Citrix XenServer host with
Ubuntu as the Linux server hosting Zend.to.  I would like to eventually
put zend.to services into production.  I have access to HP ProLiant
server that is now out of official production so I thought I would use
it to demo to upper management what zend.to can do for our environment.
 
I was wondering if someone can provide a bit of advice on best way to
set things up.
 
1.	  I have roughly 800GB of storage
2.	  I?ll be installing Ubuntu 19.10 (fresh install)
1.	  How should I allocate storage? I?m assuming either of these
are my choices
1.One large partition for OS as well as drop-offs ?
2.One partition for OS and one partition for drop-offs?
2.	  When I install Ubuntu, should I leave it fresh without any
additional software/services installed during installation?
 
Any help on best setup would be greatly appreciated.
 
Many thanks,
Marlon
 
Marlon Deerr,Technology Manager
416-572-8795 (direct) | MDeerr at hshlawyers.com
 

   
3500 - 20 Queen St. W., Toronto, ON M5H 3R3
Fax: 416-361-0083 | Toll Free: 877-474-5997 |www.hshlawyers.com
( https://www.hshlawyers.com) 
 

This Howie Sacks & Henry e-mail is privileged, confidential and subject
to copyright. Any unauthorized use or disclosure is prohibited.
   


_______________________________________________ZendTo mailing
listZendTo at zend.tohttp://jul.es/mailman/listinfo/zendto

Jules -- Julian Field MEng CEng CITP MBCS MIEEE MACM 'It's very
unlikely indeed he will ever recover consciousness, and if he does he
won't be the Julian you knew.'  - A hospital consultant I proved very
wrong in 2007 :-) www.Zend.ToTwitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200713/2990e18b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE.jpeg
Type: image/jpeg
Size: 12435 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200713/2990e18b/attachment-0005.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE_1.jpeg
Type: image/jpeg
Size: 777 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200713/2990e18b/attachment-0006.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE_2.jpeg
Type: image/jpeg
Size: 768 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200713/2990e18b/attachment-0007.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE_3.jpeg
Type: image/jpeg
Size: 756 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200713/2990e18b/attachment-0008.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE_4.jpeg
Type: image/jpeg
Size: 752 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200713/2990e18b/attachment-0009.jpeg>

From ricky.boone at gmail.com  Mon Jul 13 17:32:10 2020
From: ricky.boone at gmail.com (Ricky Boone)
Date: Mon, 13 Jul 2020 12:32:10 -0400
Subject: [ZendTo] Reminder email sent to wrong recipients
References: <CAHAhptXJcSa2Hka+4k-iHMy8hcHtr53i+mEKV3MrwNo1GnH7bA@mail.gmail.com>
Message-ID: <WM!d5dc43789c9d088f8bfbb01aa2504defab832d0e89bc84a42e46a313626d1b5b715d65a36d76502d311086a14f357619!@mx.jul.es>

I'm looking into an issue that was reported to me this morning.  What
appears to have happened was that reminder emails for a drop-off were sent,
and the log indicates that multiple internal recipients were sent
reminders, but the emails they received were for someone else's dropoff.
Specifically, the log indicates they were notified about dropoffs ABC and
DEF, but the email they received included dropoff details for XYZ.  The
logs do not indicate anything related to XYZ was sent to these recipients,
but I do have a sample email from one of the incorrect recipients that
indicates they did.  The system logs indicate that ZendTo was updated the
day before, however the upgrade script did not kick off.  Nothing in the
logs indicate an issue with the notification script running.  The system in
question is running CentOS 7.

The instance uses a MariaDB backend instead of SQLite (used SQLite before,
ran into an unrelated corruption issue that made it difficult to
troubleshoot, so hard-cut over to a MariaDB backend during low usage).  I
confirmed the related IDs do not include the recipients in question.

This is the first time I've seen this, so I'm not sure it was due to the
upgrade step not being completed (though that should only impact
configuration settings, not DB schema, etc.).  I'm not sure how I would be
able to reproduce this yet, but I'm suspecting a value for one drop-off was
inadvertently reused before it was cleared and updated with the correct
value.  For now, I just wanted to ping the mailing list to see if they've
seen similar, or to at least alert Jules to a possible bug that may need
additional research.  When I get a chance today I'm going to check through
some of the related scripts to see if anything stands out.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200713/e0816d49/attachment.html>

From Jules at Zend.To  Mon Jul 13 17:41:08 2020
From: Jules at Zend.To (Jules)
Date: Mon, 13 Jul 2020 17:41:08 +0100
Subject: [ZendTo] Reminder email sent to wrong recipients
In-Reply-To: <WM!d5dc43789c9d088f8bfbb01aa2504defab832d0e89bc84a42e46a313626d1b5b715d65a36d76502d311086a14f357619!@mx.jul.es>
References: <CAHAhptXJcSa2Hka+4k-iHMy8hcHtr53i+mEKV3MrwNo1GnH7bA@mail.gmail.com>
 <WM!d5dc43789c9d088f8bfbb01aa2504defab832d0e89bc84a42e46a313626d1b5b715d65a36d76502d311086a14f357619!@mx.jul.es>
Message-ID: <6fb250d9-8068-5ff1-983d-0588996caf13@Zend.To>

Ricky,

This is an interesting one!

You say ZendTo was updated the day before.
 From what version to what version?

rpm -q zendto
will get your current version, and if you look in /opt/zendto/config/old 
you should have all the previous preferences.php filles, which should 
give you enough to work out what the previous running version was.

The recipients of the reminder about XYZ: did they also receive their 
correct reminders for ABC and/or DEF? Or weren't they due to be sent anyway?

In what order were dropoffs ABC, DEF and XYZ created? The creation date 
is one of the available columns in the Global List of dropoffs page.

If you can answer that lot, I will hopefully have more information to 
see if I can spot a bug.

Cheers,
Jules.

On 13/07/2020 17:32, Ricky Boone via ZendTo wrote:
> I'm looking into an issue that was reported to me this morning.? What 
> appears to have happened was that reminder emails for a drop-off were 
> sent, and the log indicates that multiple internal recipients were 
> sent reminders, but the emails they received were for someone else's 
> dropoff. Specifically, the log indicates they were notified about 
> dropoffs ABC and DEF, but the email they received included dropoff 
> details for XYZ.? The logs do not indicate anything related to XYZ was 
> sent to these recipients, but I do have a sample email from one of the 
> incorrect recipients that indicates they did.? The system logs 
> indicate that ZendTo was updated the day before, however the upgrade 
> script did not kick off.? Nothing in the logs indicate an issue with 
> the notification script running.? The system in question is running 
> CentOS 7.
>
> The instance uses a MariaDB backend instead of SQLite (used SQLite 
> before, ran into an unrelated corruption issue that made it difficult 
> to troubleshoot, so hard-cut over to a MariaDB backend during low 
> usage).? I confirmed the related IDs do not include the recipients in 
> question.
>
> This is the first time I've seen this, so I'm not sure it was due to 
> the upgrade step not being completed (though that should only impact 
> configuration settings, not DB schema, etc.).? I'm not sure how I 
> would be able to reproduce this yet, but I'm suspecting a value for 
> one drop-off was inadvertently reused before it was cleared and 
> updated with the correct value.? For now, I just wanted to ping the 
> mailing list to see if they've seen similar, or to at least alert 
> Jules to a possible bug that may need additional research. When I get 
> a chance today I'm going to check through some of the related scripts 
> to see if anything stands out.
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Split apart, reunited, or adjusting for new conditions on the
  ground, a family is a double-edged sword. They're the best of times,
  the worst of times, your keys to the kingdom and the skeletons in
  your closet. If only we didn't have to eat dinner with them.'
  -- Mary, "In Plain Sight"

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200713/2d6e00ad/attachment.html>

From kbe2 at lehigh.edu  Mon Jul 13 20:01:28 2020
From: kbe2 at lehigh.edu (Keith Erekson)
Date: Mon, 13 Jul 2020 15:01:28 -0400
Subject: [ZendTo] Recommended Ubuntu setup for zend.to server
In-Reply-To: <WM!0abe8bf52cc964c0a95107ef025ccb3aeda745e2082e7ad3882572bcd9556ad28bbc058150f25055564a4d53f29739ab!@mx.jul.es>
References: <501d6a679ef64cc1897b1f3d02472231@HSH-MAIL.HSH.local>
 <WM!74cd3d809c6aaa62f8cb0c2549c5fb4ceccc3ea708ec7ec21c96abef5d402653b7162c2660d56c26f3e1bb61b65150f5!@mx.jul.es>
 <b3571514-a7cd-668a-696c-8df315603598@Zend.To>
 <WM!fc85f63935c54d20cc03850c63796f116426647b8c3656d68091497af810f291f70d0cde8b5fc5e9959bb9c7d8aecc7f!@mx.jul.es>
 <ecb401bb61ea4929b94bf3233f790446@HSH-MAIL.HSH.local>
 <WM!2fc026cf8a243d3d2e0067f3254575be265b23fb1379b313ed597d0db8cff87b898fdc4ae438438a17d0f0ec5d7932f2!@mx.jul.es>
 <WM!559d79b4fb237941d6bf49ebae6c5419b4437b9b24d209e16cbeb82151168fdae0b545471b9c022fdbcd99519ffdf99f!@mx.jul.es>
 <5F0C5FEB020000130014617E@mail.msktd.com>
 <WM!4fec8867520d9c3e5712c20aaf59ca573d073bdcc6fe3e0eef647255bd4b2db7b2094778f1fc1bd18fdf6903e8eebfec!@mx.jul.es>
 <WM!0abe8bf52cc964c0a95107ef025ccb3aeda745e2082e7ad3882572bcd9556ad28bbc058150f25055564a4d53f29739ab!@mx.jul.es>
 <163d78fa-fe51-8603-6cd5-5585a0aed117@lehigh.edu>
Message-ID: <WM!6029837f1092126bc15f336d0df1ddfd9ca2486804afec45a4d0ae5a22347aaf74ee49b2ba919cf67ca4f651453e8c46!@mx.jul.es>

I run it on a Debian VM with 2GB of RAM and ~100GB of disk (but limited
to 2GB dropoffs), in a setting with thousands of users.

(Looking at that now, it seems low. But it's been that way since before
it was ZendTo and has never thrown an alert.)

~Keith

On 7/13/20 9:21 AM, Ken Etter via ZendTo wrote:
> 32 GB is way overkill unless you have something going on that we
> aren't aware of.? The employee count at my office is similar to yours
> and I run my ZendTo server with 4 GB and it doesn't break a sweat.? :-)
> >>> Marlon Deerr via ZendTo <zendto at zend.to> 7/12/2020 2:12 PM >>>
> Thanks Jules,
> ?
> I appreciate the response.? I?ll rebuild using Ubuntu 20.04 instead.?
> ?
> What about sizing out memory? We have roughly 90+ employees but of
> that, I would say roughly 40+ of those will be actively using the
> service. I was thinking of assigning 32GB to it but is that overkill?
> ?
> ?
> ?
> *From:* Jules [mailto:Jules at Zend.To]
> *Sent:* Saturday, July 11, 2020 4:49 AM
> *To:* ZendTo Users <zendto at zend.to>
> *Cc:* Marlon Deerr <MDeerr at hshlawyers.com>
> *Subject:* Re: [ZendTo] Recommended Ubuntu setup for zend.to server
> ?
> Marlon,
>
> Considering the timescales you work on, I would advise using the
> latest LTS release of Ubuntu. It may well save you time in the long run.
>
> For the storage, you might want to let Ubuntu do its default
> behaviour, but put /var/zendto in a volume of its own at the end of
> the disk. Everything in /var/zendto needs to be in the same
> volume/partition.
>
> But if it's only a "throwaway" demo server for The Management(tm),
> then it won't matter much as you'll almost certainly rebuild it before
> making it a production service anyway.
>
> When installing Ubuntu, just do a minimal install. You might want to
> install the openssh-server package to give yourself remote ssh access
> to it, but beyond that the ZendTo Installer will add everything it needs.
>
> Hope that helps,
> Jules.
> On 11/07/2020 02:57, Marlon Deerr via ZendTo wrote:
>
>     Hello All,
>     ?
>     It?s been roughly 5+ years since I have used Zend.to and roughly
>     the same amount of time since managing one from a Citrix XenServer
>     host with Ubuntu as the Linux server hosting Zend.to.? I would
>     like to eventually put zend.to services into production.? I have
>     access to HP ProLiant server that is now out of official
>     production so I thought I would use it to demo to upper management
>     what zend.to can do for our environment.
>     ?
>     I was wondering if someone can provide a bit of advice on best way
>     to set things up.
>     ?
>     1.?????? I have roughly 800GB of storage
>     2.?????? I?ll be installing Ubuntu 19.10 (fresh install)
>     1.?????? How should I allocate storage? I?m assuming either of
>     these are my choices
>     1.One large partition for OS as well as drop-offs ?
>     2.One partition for OS and one partition for drop-offs?
>     2.?????? When I install Ubuntu, should I leave it fresh without
>     any additional software/services installed during installation?
>     ?
>     Any help on best setup would be greatly appreciated.
>     ?
>     Many thanks,
>     Marlon
>     ?
>     *Marlon Deerr*, *Technology Manager*
>     416-572-8795?(direct)| MDeerr at hshlawyers.com
>     <mailto:MDeerr at hshlawyers.com>
>     <https://www.hshlawyers.com>?
>     <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/>?<https://twitter.com/hshlawyers>?<https://www.facebook.com/HSHPersonalInjuryLawyers/>?<https://www.youtube.com/user/hshlawyers>
>     	
>     3500 - 20 Queen St. W., Toronto, ON M5H 3R3
>     Fax: 416-361-0083 | Toll Free: 877-474-5997| www.hshlawyers.com
>     <https://www.hshlawyers.com>
>
>     ?
>     This Howie Sacks & Henry e-mail is privileged, confidential and
>     subject to copyright. Any unauthorized use or disclosure is
>     prohibited.
>
>     ???
>
>
>     _______________________________________________
>
>     ZendTo mailing list
>
>     ZendTo at zend.to <mailto:ZendTo at zend.to>
>
>     http://jul.es/mailman/listinfo/zendto
>
>
>
> Jules
> ?
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> ?
> 'It's very unlikely indeed he will ever recover consciousness, and
>  if he does he won't be the Julian you knew.'
> ? - A hospital consultant I proved very wrong in 2007 :-)
> ?
> www.Zend.To <http://www.Zend.To>
> Twitter: @JulesFM
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200713/9bfa3727/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE.jpeg
Type: image/jpeg
Size: 12435 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200713/9bfa3727/attachment-0005.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE_1.jpeg
Type: image/jpeg
Size: 777 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200713/9bfa3727/attachment-0006.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE_2.jpeg
Type: image/jpeg
Size: 768 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200713/9bfa3727/attachment-0007.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE_3.jpeg
Type: image/jpeg
Size: 756 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200713/9bfa3727/attachment-0008.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE_4.jpeg
Type: image/jpeg
Size: 752 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200713/9bfa3727/attachment-0009.jpeg>

From MDeerr at hshlawyers.com  Mon Jul 13 23:27:42 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Mon, 13 Jul 2020 22:27:42 +0000
Subject: [ZendTo] New ZendTo Site Not loading
References: <785aa2751d1d43c3813ff1ff2873b785@HSH-MAIL.HSH.local>
Message-ID: <WM!25eae09b40d2852949fc77faee61fa4614ac4ac9201ac0787a64d6cdd2f28a41b7d76be97c9a7c1929f1ae1d1b38dbff!@mx.jul.es>

Hello,

I'm in the process of setting up a  brand new install of ZendTo site on a Ubuntu 20.04 server.  I've run into an issue where I just can no longer get the home page to load. After a successful install of Zendto, here are the steps I performed until the issue arose


1.       Created a test user successfully

2.       Logged in as that test user successfully

3.       Changed the ServiceTitle in the zendto.conf file without problem.

a.       I 'm able to access the site and see all instances where that variable would display that variable.

4.       Acquired the required Captcha keys from Google an inserted them successfully within preferences.php

a.       Launch website after this successfully

5.       Edited preferences.php again but this time changed all AD authentication related entries

a.       Attempted to access webpage to see if I it work BUT now the site does not load at all.

I am stumped at 5a. I can't figure out why the home page won't load.  Apart from an Error 500 from Google Chrome, no other error is give.  Is this possibly related to it having a self-signed certificate?  Any guidance on this would be grated appreciated as I am at a loss.

Thanks,
Marlon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200713/c0167072/attachment.html>

From ssilva at sgvwater.com  Mon Jul 13 23:34:26 2020
From: ssilva at sgvwater.com (Scott Silva)
Date: Mon, 13 Jul 2020 22:34:26 +0000
Subject: [ZendTo] New ZendTo Site Not loading
In-Reply-To: <WM!7afb9fbe9c62d22ad80e77094ba8d542f183d592925cbfc58e5501d46e6ff96837e1dffbb64ddd2d6e21b35e9e1395e7!@mx.jul.es>
References: <785aa2751d1d43c3813ff1ff2873b785@HSH-MAIL.HSH.local>
 <WM!25eae09b40d2852949fc77faee61fa4614ac4ac9201ac0787a64d6cdd2f28a41b7d76be97c9a7c1929f1ae1d1b38dbff!@mx.jul.es>
 <WM!7afb9fbe9c62d22ad80e77094ba8d542f183d592925cbfc58e5501d46e6ff96837e1dffbb64ddd2d6e21b35e9e1395e7!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F42ECFEC1B@FONEXCH01.sgvwc.local>
Message-ID: <WM!b66ed1e48ffcc9e5d8d7dadfc406d2a2dc8c34b862287386664e8a8e6044e2a1767febf8ced53be0a7c9ac0853f7489d!@mx.jul.es>

A self signed cert gives a security error, but you can usually get it to load.
Recheck your last step for a typo since you said that is where it choked.


From: ZendTo <zendto-bounces at zend.to> On Behalf Of Marlon Deerr via ZendTo
Sent: Monday, July 13, 2020 3:28 PM
To: ZendTo Users <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: [ZendTo] New ZendTo Site Not loading

Hello,

I'm in the process of setting up a  brand new install of ZendTo site on a Ubuntu 20.04 server.  I've run into an issue where I just can no longer get the home page to load. After a successful install of Zendto, here are the steps I performed until the issue arose


1.       Created a test user successfully

2.       Logged in as that test user successfully

3.       Changed the ServiceTitle in the zendto.conf file without problem.

a.       I 'm able to access the site and see all instances where that variable would display that variable.

4.       Acquired the required Captcha keys from Google an inserted them successfully within preferences.php

a.       Launch website after this successfully

5.       Edited preferences.php again but this time changed all AD authentication related entries

a.       Attempted to access webpage to see if I it work BUT now the site does not load at all.

I am stumped at 5a. I can't figure out why the home page won't load.  Apart from an Error 500 from Google Chrome, no other error is give.  Is this possibly related to it having a self-signed certificate?  Any guidance on this would be grated appreciated as I am at a loss.

Thanks,
Marlon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200713/5dfb372d/attachment.html>

From kbe2 at lehigh.edu  Tue Jul 14 04:41:13 2020
From: kbe2 at lehigh.edu (Keith Erekson)
Date: Mon, 13 Jul 2020 23:41:13 -0400
Subject: [ZendTo] New ZendTo Site Not loading
In-Reply-To: <WM!e329825a9e56ffb2bc55c609b91387352956993169558e85d80ff99e58a1353428655492acba6427c2890b499e76ed9f!@mx.jul.es>
References: <WM!e329825a9e56ffb2bc55c609b91387352956993169558e85d80ff99e58a1353428655492acba6427c2890b499e76ed9f!@mx.jul.es>
 <DE15582F-5124-4F47-999C-EAA8542FA51F@lehigh.edu>
Message-ID: <WM!174c9d7bf3f85f3e11811ae22313b309d7ce4f6fa4cac37d201967a9e94c3cc27110be61e46d6ab1e90306ac7430b445!@mx.jul.es>

Sounds like you may have a syntax error from step 5a.

Check the apache error log to see what?s causing the 500 error.

Sent from my iPhone

> On Jul 13, 2020, at 6:28 PM, Marlon Deerr via ZendTo <zendto at zend.to> wrote:
> 
> ?
> Hello,
>  
> I?m in the process of setting up a  brand new install of ZendTo site on a Ubuntu 20.04 server.  I?ve run into an issue where I just can no longer get the home page to load. After a successful install of Zendto, here are the steps I performed until the issue arose
>  
> 1.       Created a test user successfully
> 2.       Logged in as that test user successfully
> 3.       Changed the ServiceTitle in the zendto.conf file without problem.
> a.       I ?m able to access the site and see all instances where that variable would display that variable.
> 4.       Acquired the required Captcha keys from Google an inserted them successfully within preferences.php
> a.       Launch website after this successfully
> 5.       Edited preferences.php again but this time changed all AD authentication related entries
> a.       Attempted to access webpage to see if I it work BUT now the site does not load at all.
>  
> I am stumped at 5a. I can?t figure out why the home page won?t load.  Apart from an Error 500 from Google Chrome, no other error is give.  Is this possibly related to it having a self-signed certificate?  Any guidance on this would be grated appreciated as I am at a loss.
>  
> Thanks,
> Marlon
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200713/224ef146/attachment-0001.html>

From alt36 at cam.ac.uk  Tue Jul 14 08:19:23 2020
From: alt36 at cam.ac.uk (Adam Thorn)
Date: Tue, 14 Jul 2020 08:19:23 +0100
Subject: [ZendTo] Recommended Ubuntu setup for zend.to server
In-Reply-To: <WM!e905db40c9eb271ee0d524a1e6e0f56f55d0bf59a36bc1f4017e386ac84d1b3064e00d5dfbba26903778533bfbcbd75d!@mx.jul.es>
References: <501d6a679ef64cc1897b1f3d02472231@HSH-MAIL.HSH.local>
 <WM!74cd3d809c6aaa62f8cb0c2549c5fb4ceccc3ea708ec7ec21c96abef5d402653b7162c2660d56c26f3e1bb61b65150f5!@mx.jul.es>
 <b3571514-a7cd-668a-696c-8df315603598@Zend.To>
 <WM!fc85f63935c54d20cc03850c63796f116426647b8c3656d68091497af810f291f70d0cde8b5fc5e9959bb9c7d8aecc7f!@mx.jul.es>
 <ecb401bb61ea4929b94bf3233f790446@HSH-MAIL.HSH.local>
 <WM!2fc026cf8a243d3d2e0067f3254575be265b23fb1379b313ed597d0db8cff87b898fdc4ae438438a17d0f0ec5d7932f2!@mx.jul.es>
 <WM!e905db40c9eb271ee0d524a1e6e0f56f55d0bf59a36bc1f4017e386ac84d1b3064e00d5dfbba26903778533bfbcbd75d!@mx.jul.es>
 <d6828e33-339a-2c3f-b0e6-33e1d9cb2361@cam.ac.uk>
Message-ID: <WM!86c698eaf173a2d2efcdb15146ac0ba05c07769d1215b59789b750d61c6979cc570249beecbb90c017ea09600c99d754!@mx.jul.es>

On 12/07/2020 19:12, Marlon Deerr via ZendTo wrote:
> Thanks Jules,
> 
> I appreciate the response.? I?ll rebuild using Ubuntu 20.04 instead.
> 
> What about sizing out memory? We have roughly 90+ employees but of that, 
> I would say roughly 40+ of those will be actively using the service. I 
> was thinking of assigning 32GB to it but is that overkill?

32GB sounds excessive to me. I'm running on Ubuntu 18.04 with 512MB; the 
VM is dedicated to ZendTo so is basically only running apache. Our usage 
is light enough that I'm happy using sqlite, so you may need to allow a 
little extra if you use a "real" database server.

Even if you expect 40 active users, how likely is it that they'll all be 
up/downloading at the same point in time...?

Adam


From leratochipa at gmail.com  Tue Jul 14 09:56:49 2020
From: leratochipa at gmail.com (Lerato Chipa)
Date: Tue, 14 Jul 2020 10:56:49 +0200
Subject: [ZendTo] Predefined Drop Offs
In-Reply-To: <WM!c019fc8407fd3f3022208bcbec13fb5edf7e152d2fd23cd5d4352fb7faaad6825d3fd2e31cf8f588115da237a8cb29c9!@mx.jul.es>
References: <CAKE9jaZw4eZ4JsR7gQVQna032t6c5bOJ=oV7gvAYE=9RJwp2Ew@mail.gmail.com>
 <WM!456ff6fe50ae796f1142d9f20c87847d6b2cc0cf898db081c2f24308f181b1e54cc95fde0c7fa91397fb4f7f1311f04b!@mx.jul.es>
 <09b6725b-f9a5-d072-e35f-70417d903046@Zend.To>
 <WM!c019fc8407fd3f3022208bcbec13fb5edf7e152d2fd23cd5d4352fb7faaad6825d3fd2e31cf8f588115da237a8cb29c9!@mx.jul.es>
 <B863B464-AEA2-49AF-8441-A264282DFBCE@gmail.com>
Message-ID: <WM!39a96abd5eb4b92b2f4111e6e41b9cc7dbf78d6c24965111e6041530bd42ddee27de9c5695df340f505ee4b04b591521!@mx.jul.es>

Hi All 

May I please be removed from your internal communication. 

To be honest, I don?t know how I got onto this list begin with. I do not know anyone here, if there was a link I would understand because I would be able to link being part of this commutation with that person. 

Thanks

> On 08 Jul 2020, at 19:54, Jules via ZendTo <zendto at zend.to> wrote:
> 
> Gregg,
> 
> You can basically do all of this now.
> 
> Your "Predefined Drop Off(PDO)" is what ZendTo calls a "request for a drop-off". There is a button on the main menu to do exactly this.
> You can send these to multiple recipients by putting multiple email addresses in the "Request a drop-off" form, just separate them with commas or spaces.
> 
> The rest of it you can do with ZendTo's automation feature, where you can create a "request for a drop-off" from the command-line, and hence from a script. You would need to write something to tie that in to your existing coursework management system, but the scripts that drive ZendTo automatically are actually nothing more than a long "curl" command to do an HTTP POST operation that supplies all the information in 1 hit.
> 
> The automation stuff is documented here
>     zend.to/automation
> and there is a script called "autorequest" which automates the "request a drop-off" process.
> 
> Any more questions, problems, or any other way I can help, please do no hesitate to get in touch.
> 
> I work for a University myself, and have written coursework submission systems before. A few of our academics use our instance of ZendTo to get coursework submissions from students, especially when they are large submissions like videos of interviews.
> 
> Hope that helps,
> Jules.
> 
> On 08/07/2020 18:08, Gregg Douglas via ZendTo wrote:
>> Hey Jules,
>> 
>> I hope you are keeping safe and healthy. 
>> 
>> I would like to bounce an idea with you?
>>  
>> Take a Lecturer or Tender Officer, they need to request students to submit assignments or suppliers to submit tenders.
>>  
>> This person (Lecturer or Tender Officer) would then access ZendTO and create a ?Predefined Drop Off(PDO)?. In this PDO, one would preselect or predefine all the fields and options. The Subject, would also be predefined, but would be used as a field to group the PDOs. So, for a Lecturer they would use the Subject to define the name of the assignment that the students must submit. A Tender Officer would use the Subject to define the Tender Reference. The Short Note Field could be left as a free text block, allowing the Student or Supplier to include a note. There would also need to be Start and End Date fields, which would define the period the PDO will be active for.
>>   
>> Then, there would need to be an ?Alternative? Interface for ZendTO. In this ?Alternative? Interface a student or supplier could select the relevant active Assignment or Tender form a list of all active ones. On selecting the required item from the list, the normal process of ?Requesting a Drop Off? would follow, like confirming the email address of the student or supplier via the verification email. The link in this email would open the PDO with all the predefined fields and the student or supplier can then upload and submit the information.
>> 
>> It was a thought I have for a future feature.
>> 
>> Regards
>> Gregg
>> 
>> 
>> 
>> _______________________________________________
>> ZendTo mailing list
>> ZendTo at zend.to <mailto:ZendTo at zend.to>
>> http://jul.es/mailman/listinfo/zendto <http://jul.es/mailman/listinfo/zendto>
> 
> Jules
> 
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> 
> 'Probability factor of one to one. We have normality. I repeat, we
>  have normality. Anything you still can't cope with is therefore
>  your own problem.' - Trillian, The Hitch Hikers Guide to the Galaxy
> 
> www.Zend.To <http://www.zend.to/>
> Twitter: @JulesFM
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200714/8d14f6d9/attachment.html>

From zend.to at neilzone.co.uk  Tue Jul 14 10:01:26 2020
From: zend.to at neilzone.co.uk (zend.to at neilzone.co.uk)
Date: Tue, 14 Jul 2020 10:01:26 +0100
Subject: [ZendTo] Predefined Drop Offs
In-Reply-To: <WM!4868dffd2e6d8b78d0626212c3366535fedf39e7444729bdc5fe126698a89c83f8cb34a3ada4c112f31d69134f0a9aca!@mx.jul.es>
References: <CAKE9jaZw4eZ4JsR7gQVQna032t6c5bOJ=oV7gvAYE=9RJwp2Ew@mail.gmail.com>
 <WM!456ff6fe50ae796f1142d9f20c87847d6b2cc0cf898db081c2f24308f181b1e54cc95fde0c7fa91397fb4f7f1311f04b!@mx.jul.es>
 <09b6725b-f9a5-d072-e35f-70417d903046@Zend.To>
 <WM!c019fc8407fd3f3022208bcbec13fb5edf7e152d2fd23cd5d4352fb7faaad6825d3fd2e31cf8f588115da237a8cb29c9!@mx.jul.es>
 <B863B464-AEA2-49AF-8441-A264282DFBCE@gmail.com>
 <WM!39a96abd5eb4b92b2f4111e6e41b9cc7dbf78d6c24965111e6041530bd42ddee27de9c5695df340f505ee4b04b591521!@mx.jul.es>
 <WM!4868dffd2e6d8b78d0626212c3366535fedf39e7444729bdc5fe126698a89c83f8cb34a3ada4c112f31d69134f0a9aca!@mx.jul.es>
 <C368EA07-2A60-458E-9E19-17A91A33FDB7@neilzone.co.uk>
Message-ID: <WM!1b0c15d9aaa5fa1eff0f1b56579851434b08f732aaa33c61cc0f4cfbe046d91e186e004bfc0f19dcb5182a874f2b980b!@mx.jul.es>



> On 14 Jul 2020, at 09:56, Lerato Chipa via ZendTo <zendto at zend.to> wrote:

Hello Lerato
> 
> May I please be removed from your internal communication. 

This is a mailing list about a piece of software, zend.to. 

Jules (the list admin) might be able to remove you but, if you go to the list admin page (http://jul.es/mailman/listinfo/zendto <http://jul.es/mailman/listinfo/zendto>), there is an option at the bottom to unsubscribe. If you put in your email address and click ?Unsubscribe", it will probably send you a confirmation link to click, and then you should be removed.

Best wishes

Neil



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

From mailinglists at pcfreak.de  Tue Jul 14 10:02:33 2020
From: mailinglists at pcfreak.de (Der PCFreak)
Date: Tue, 14 Jul 2020 11:02:33 +0200
Subject: [ZendTo] Expire Time Incorrect
In-Reply-To: <WM!512bec053387b578d2b0480f6c7da58b1b4d1f7e284bd6d44ccd22fc4bc2ae131dcc16747430f631eb199845eace6109!@mx.jul.es>
References: <BN6PR1801MB1857195A295C573D911454AFD6830@BN6PR1801MB1857.namprd18.prod.outlook.com>
 <WM!13120fee741facac97f09cd93188485daeb5d83ff192787b66b95bb88c653fb0c8a74261a2969d60c60e71b3a41e3d24!@mx.jul.es>
 <c41f03dc-0658-c3c9-33c4-75885fef9367@Zend.To>
 <WM!512bec053387b578d2b0480f6c7da58b1b4d1f7e284bd6d44ccd22fc4bc2ae131dcc16747430f631eb199845eace6109!@mx.jul.es>
 <2eae023e-c1b6-7bb0-30a1-67c1188fcef3@pcfreak.de>
Message-ID: <WM!d51b52ac221d0cff6011a83a1e5295de6d6024f04ef3c38ef5d8aa40281562f79bfafe5bd331b80433e126cb8be489d9!@mx.jul.es>

Hi Jules,

I am currently facing the same problem with a Dropoff made from an 
external user via the public site.


It shows exactly the same days as Michael Imlay wrote (10919 days + some 
hours).

I am running

```
Installed Packages
Name??????? : zendto
Arch??????? : noarch
Version???? : 6.01
Release???? : 2
Size??????? : 9.5 M
Repo??????? : installed
 From repo?? : ZendTo
Summary???? : Web-based File Transfer and Storage System
```

on `CentOS Linux release 7.8.2003 (Core)`.


In the admin interface (Global Drop-off List) the `Created` date is 
`2020-07-08 10:31:19`. This is also stated in the corresponding emails.

We have a retention time of 7 days. The DropOff was sent to 2 recipients 
within our companies (if that matters somehow?).
The size was 3.9 GB and SHa-256 Checksum was `Not calculated`.

Btw. in the `Drop-Off Summary` it correctly shows `This drop-off will 
expire in 23 hours and 31 minutes.` which is correct.

Any ideas?

Kind regards

Peter

On 10/06/2020 18:11, Jules via ZendTo wrote:
> Michael,
>
> What version are you running?
> And what are you running it on?
>
> Jules.
>
> On 10/06/2020 16:55, Michael Imlay via ZendTo wrote:
>>
>> Hey,
>>
>> I have my ZendTo configured to send out a notification started 3 days 
>> prior to removing the files. On the site it shows correct, but the 
>> user who receives the e-mails gets something like this:
>>
>> *This is a reminder about a drop-off sent to you, that no one has 
>> picked up.**
>> *The drop-off will expire in 10911 days and 16 hours after which it 
>> will be automatically deleted.**
>>
>> **
>>
>> *This is a reminder about a drop-off sent to you, that no one has 
>> picked up.**
>> *The drop-off will expire in 10912 days and 16 hours after which it 
>> will be automatically deleted.**
>>
>> **
>>
>> *This is a reminder about a drop-off sent to you, that no one has 
>> picked up.**
>> *The drop-off will expire in 10913 days and 16 hours after which it 
>> will be automatically deleted.**
>>
>> **
>>
>> Any idea why this might be happening on just the reminder e-mails?
>>
>> Thanks,
>>
>> Michael Imlay
>>
>> DELL LOGO
>>
>> Michael Imlay
>>
>> IT & Telecommunications Designer
>>
>> 129 East Government Street
>>
>> Pensacola, FL 32502
>>
>> Direct:? 850-332-2084
>> Office:? 850-332-5687 x117
>>
>> Cell: ????? 850-737-9219
>>
>> IT at DellConsultingLLC.com <mailto:IT at DellConsultingLLC.com>
>>
>> This email and any files transmitted with it may contain PRIVILEGED 
>> or CONFIDENTIAL information and may be read or used only by the 
>> intended recipient. If you are not the intended recipient of the 
>> email or any of its attachments, please be advised that you have 
>> received this email in error and that any use, dissemination, 
>> distribution, forwarding, printing, or copying of this email or any 
>> attached files is strictly prohibited. If you have received this 
>> email in error, please immediately purge it and all attachments and 
>> notify the sender by reply email or contact the sender at the number 
>> listed.
>>
>>
>> _______________________________________________
>> ZendTo mailing list
>> ZendTo at zend.to
>> http://jul.es/mailman/listinfo/zendto
>
> Jules
>
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
>
> 'It's very unlikely indeed he will ever recover consciousness, and
>   if he does he won't be the Julian you knew.'
>    - A hospital consultant I proved very wrong in 2007 :-)
>
> www.Zend.To
> Twitter: @JulesFM
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200714/22f405a9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 9426 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200714/22f405a9/attachment-0001.png>

From MDeerr at hshlawyers.com  Tue Jul 14 10:53:47 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Tue, 14 Jul 2020 09:53:47 +0000
Subject: [ZendTo] Recommended Ubuntu setup for zend.to server
In-Reply-To: <WM!249f09c5845b88908a05b01b908ed53cd1fc3009a6488454c9562a9a58e67d5eb1030c78ff165e95d15cb38a6d1c9c0c!@mx.jul.es>
References: <WM!e905db40c9eb271ee0d524a1e6e0f56f55d0bf59a36bc1f4017e386ac84d1b3064e00d5dfbba26903778533bfbcbd75d!@mx.jul.es>
 <WM!249f09c5845b88908a05b01b908ed53cd1fc3009a6488454c9562a9a58e67d5eb1030c78ff165e95d15cb38a6d1c9c0c!@mx.jul.es>
 <c-35d86-kclrcz81-pzz48v=ap6cae@2.gethop.com>
Message-ID: <WM!c50160e122081547ca08ef50cb6599e5592734dcc2612c1f45a8219a5727018192ef1d12f219eaf3d99661c5270566d2!@mx.jul.es>

Very true @Adam. I'll definately be reducing RAM on my ZendTo VM.

Thanks to all who responded on my question.

Sent from my mobile device.


On July 14, 2020 at 7:20 GMT, Adam Thorn via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> wrote:

On 12/07/2020 19:12, Marlon Deerr via ZendTo wrote:
> Thanks Jules,
>
> I appreciate the response.  I?ll rebuild using Ubuntu 20.04 instead.
>
> What about sizing out memory? We have roughly 90+ employees but of that,
> I would say roughly 40+ of those will be actively using the service. I
> was thinking of assigning 32GB to it but is that overkill?

32GB sounds excessive to me. I'm running on Ubuntu 18.04 with 512MB; the
VM is dedicated to ZendTo so is basically only running apache. Our usage
is light enough that I'm happy using sqlite, so you may need to allow a
little extra if you use a "real" database server.

Even if you expect 40 active users, how likely is it that they'll all be
up/downloading at the same point in time...?

Adam

_______________________________________________
ZendTo mailing list
ZendTo at zend.to<mailto:ZendTo at zend.to>
http://jul.es/mailman/listinfo/zendto


[https://bolt.im/t/?hs76_6vS5AQxYGImcnf2yJQUCMelaJ-Lvg_zpB3BIOuslOo7UsbN2atAetcaLhz2O_lVEr_N_XcsfNNnKKLj7w]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200714/8540c929/attachment.html>

From m.v.sangster at abdn.ac.uk  Tue Jul 14 11:20:33 2020
From: m.v.sangster at abdn.ac.uk (Sangster, Mark)
Date: Tue, 14 Jul 2020 10:20:33 +0000
Subject: [ZendTo] Reminder email sent to wrong recipients
References: <AM0PR04MB6082681B3AD8C20A8BE78CB0FF610@AM0PR04MB6082.eurprd04.prod.outlook.com>
Message-ID: <WM!4dea89553e06633e843e5f96df3ed86bfb13dd7c38011a75f39c367734c60df7e123bcc3ef3491d585a5588e4e598b7a!@mx.jul.es>

Hello,

We also had the reminder emails send to the wrong recipients this morning (sorry I can?t reply to the original thread as I just signed up).

But in answer to the questions Jules asked ?

# rpm -q zendto
zendto-6.03-4.noarch

Previous version was v5.03.

The reminder emails about XYZ were sent in place of ABC/DEF.

The log correctly shows the email/claimID for each reminder to be sent.

XYZ was the first created.

Finally .. I believe that warnDaysBeforeDeletion will prevent the email reminders, can you confirm?

Thanks
Mark

------------------------------------------------------------------------
Mark Sangster
Server Infrastructure Specialist

Information Technology Services | University of Aberdeen
t: +44 (0)1224 27-3315 | e: mark at abdn.ac.uk<mailto:mark at abdn.ac.uk> | u: http://www.abdn.ac.uk/it/



The University of Aberdeen is a charity registered in Scotland, No SC013683.
Tha Oilthigh Obar Dheathain na charthannas cl?raichte ann an Alba, ?ir. SC013683.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200714/c8288353/attachment-0001.html>

From ebbernardi at gmail.com  Tue Jul 14 14:02:48 2020
From: ebbernardi at gmail.com (Everton Bruno Bernardi)
Date: Tue, 14 Jul 2020 10:02:48 -0300
Subject: [ZendTo] 24 hour drop-off summary
References: <CAD1KJM7wdKNkAb33gXeScPxuDu_mz26wFtVm8bjt+oO8-7f7uQ@mail.gmail.com>
Message-ID: <WM!6565c3d4683aeb243828bb4cc2da049b4e071ef46f40bba5e9ffb79597d395b8285fa3c30809beebbc24ca5af88148fb!@mx.jul.es>

Hello there,

I've just brought up a new instance of ZendTo (6.03-4) to a new Ubuntu
20.04 LTS server. I noticed an undesired behavior related to the daily
drop-off summary:

If a user sends a drop-off and deletes it the related drop off won't appear
in the summary - even if it was picked-up.

Is it expected? I think it would be more accurate if all of the drop-offs
would be listed.


Kind regards,

-- 
*Everton Bruno Bernardi*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200714/06060d32/attachment.html>

From ssilva at sgvwater.com  Tue Jul 14 16:32:46 2020
From: ssilva at sgvwater.com (Scott Silva)
Date: Tue, 14 Jul 2020 15:32:46 +0000
Subject: [ZendTo] Predefined Drop Offs
In-Reply-To: <WM!a1c1b70ec79100faa7fb799152533871fe9772c87b215c3696265eee710b3b9889516949885725881c8adf8a455e81c4!@mx.jul.es>
References: <CAKE9jaZw4eZ4JsR7gQVQna032t6c5bOJ=oV7gvAYE=9RJwp2Ew@mail.gmail.com>
 <WM!456ff6fe50ae796f1142d9f20c87847d6b2cc0cf898db081c2f24308f181b1e54cc95fde0c7fa91397fb4f7f1311f04b!@mx.jul.es>
 <09b6725b-f9a5-d072-e35f-70417d903046@Zend.To>
 <WM!c019fc8407fd3f3022208bcbec13fb5edf7e152d2fd23cd5d4352fb7faaad6825d3fd2e31cf8f588115da237a8cb29c9!@mx.jul.es>
 <B863B464-AEA2-49AF-8441-A264282DFBCE@gmail.com>
 <WM!39a96abd5eb4b92b2f4111e6e41b9cc7dbf78d6c24965111e6041530bd42ddee27de9c5695df340f505ee4b04b591521!@mx.jul.es>
 <WM!a1c1b70ec79100faa7fb799152533871fe9772c87b215c3696265eee710b3b9889516949885725881c8adf8a455e81c4!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F42ED00BA4@FONEXCH01.sgvwc.local>
Message-ID: <WM!c6ed04dcdcc87a3c021a9aa981b1e50886ce147c52779958e7ad9d4cf0725cfa16d26fe203279cc8c9a53b12ff2b659f!@mx.jul.es>

You would have had to join this list. And then respond to an email? No one else can add you, and you will have to unsubscribe.
Go here to unsubscribe.
http://jul.es/mailman/listinfo/zendto



From: ZendTo <zendto-bounces at zend.to> On Behalf Of Lerato Chipa via ZendTo
Sent: Tuesday, July 14, 2020 1:58 AM
To: ZendTo Users <zendto at zend.to>
Cc: Lerato Chipa <leratochipa at gmail.com>
Subject: Re: [ZendTo] Predefined Drop Offs

Hi All

May I please be removed from your internal communication.

To be honest, I don?t know how I got onto this list begin with. I do not know anyone here, if there was a link I would understand because I would be able to link being part of this commutation with that person.

Thanks


On 08 Jul 2020, at 19:54, Jules via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> wrote:

Gregg,

You can basically do all of this now.

Your "Predefined Drop Off(PDO)" is what ZendTo calls a "request for a drop-off". There is a button on the main menu to do exactly this.
You can send these to multiple recipients by putting multiple email addresses in the "Request a drop-off" form, just separate them with commas or spaces.

The rest of it you can do with ZendTo's automation feature, where you can create a "request for a drop-off" from the command-line, and hence from a script. You would need to write something to tie that in to your existing coursework management system, but the scripts that drive ZendTo automatically are actually nothing more than a long "curl" command to do an HTTP POST operation that supplies all the information in 1 hit.

The automation stuff is documented here
    zend.to/automation<http://zend.to/automation>
and there is a script called "autorequest" which automates the "request a drop-off" process.

Any more questions, problems, or any other way I can help, please do no hesitate to get in touch.

I work for a University myself, and have written coursework submission systems before. A few of our academics use our instance of ZendTo to get coursework submissions from students, especially when they are large submissions like videos of interviews.

Hope that helps,
Jules.
On 08/07/2020 18:08, Gregg Douglas via ZendTo wrote:
Hey Jules,

I hope you are keeping safe and healthy.

I would like to bounce an idea with you?

Take a Lecturer or Tender Officer, they need to request students to submit assignments or suppliers to submit tenders.

This person (Lecturer or Tender Officer) would then access ZendTO and create a ?Predefined Drop Off(PDO)?. In this PDO, one would preselect or predefine all the fields and options. The Subject, would also be predefined, but would be used as a field to group the PDOs. So, for a Lecturer they would use the Subject to define the name of the assignment that the students must submit. A Tender Officer would use the Subject to define the Tender Reference. The Short Note Field could be left as a free text block, allowing the Student or Supplier to include a note. There would also need to be Start and End Date fields, which would define the period the PDO will be active for.

Then, there would need to be an ?Alternative? Interface for ZendTO. In this ?Alternative? Interface a student or supplier could select the relevant active Assignment or Tender form a list of all active ones. On selecting the required item from the list, the normal process of ?Requesting a Drop Off? would follow, like confirming the email address of the student or supplier via the verification email. The link in this email would open the PDO with all the predefined fields and the student or supplier can then upload and submit the information.

It was a thought I have for a future feature.

Regards
Gregg




_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto:ZendTo at zend.to>

http://jul.es/mailman/listinfo/zendto



Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'Probability factor of one to one. We have normality. I repeat, we

 have normality. Anything you still can't cope with is therefore

 your own problem.' - Trillian, The Hitch Hikers Guide to the Galaxy



www.Zend.To<http://www.zend.to/>

Twitter: @JulesFM
_______________________________________________
ZendTo mailing list
ZendTo at zend.to<mailto:ZendTo at zend.to>
http://jul.es/mailman/listinfo/zendto

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

From Jules at Zend.To  Tue Jul 14 16:37:48 2020
From: Jules at Zend.To (Jules)
Date: Tue, 14 Jul 2020 16:37:48 +0100
Subject: [ZendTo] Recommended Ubuntu setup for zend.to server
In-Reply-To: <WM!86c698eaf173a2d2efcdb15146ac0ba05c07769d1215b59789b750d61c6979cc570249beecbb90c017ea09600c99d754!@mx.jul.es>
References: <501d6a679ef64cc1897b1f3d02472231@HSH-MAIL.HSH.local>
 <WM!74cd3d809c6aaa62f8cb0c2549c5fb4ceccc3ea708ec7ec21c96abef5d402653b7162c2660d56c26f3e1bb61b65150f5!@mx.jul.es>
 <b3571514-a7cd-668a-696c-8df315603598@Zend.To>
 <WM!fc85f63935c54d20cc03850c63796f116426647b8c3656d68091497af810f291f70d0cde8b5fc5e9959bb9c7d8aecc7f!@mx.jul.es>
 <ecb401bb61ea4929b94bf3233f790446@HSH-MAIL.HSH.local>
 <WM!2fc026cf8a243d3d2e0067f3254575be265b23fb1379b313ed597d0db8cff87b898fdc4ae438438a17d0f0ec5d7932f2!@mx.jul.es>
 <WM!e905db40c9eb271ee0d524a1e6e0f56f55d0bf59a36bc1f4017e386ac84d1b3064e00d5dfbba26903778533bfbcbd75d!@mx.jul.es>
 <d6828e33-339a-2c3f-b0e6-33e1d9cb2361@cam.ac.uk>
 <WM!86c698eaf173a2d2efcdb15146ac0ba05c07769d1215b59789b750d61c6979cc570249beecbb90c017ea09600c99d754!@mx.jul.es>
Message-ID: <11812482-fa56-c4bd-dc3e-ffb3622088b3@Zend.To>

Adam,

With only 512MB, do you use the encryption feature?
If so, what's the peak memory use just as it starts the encryption process?
That's when it is turning your passphrase into something suitable for 
use as a key, and usually that's where you're most likely to run out of RAM.

P.S. Do you run it for cam.ac.uk? (You don't appear to be a cl.cam.ac.uk 
address). Or just a bit of cam.ac..uk?

Cheers,
Jules.

On 14/07/2020 08:19, Adam Thorn via ZendTo wrote:
> On 12/07/2020 19:12, Marlon Deerr via ZendTo wrote:
>> Thanks Jules,
>>
>> I appreciate the response.? I?ll rebuild using Ubuntu 20.04 instead.
>>
>> What about sizing out memory? We have roughly 90+ employees but of 
>> that, I would say roughly 40+ of those will be actively using the 
>> service. I was thinking of assigning 32GB to it but is that overkill?
>
> 32GB sounds excessive to me. I'm running on Ubuntu 18.04 with 512MB; 
> the VM is dedicated to ZendTo so is basically only running apache. Our 
> usage is light enough that I'm happy using sqlite, so you may need to 
> allow a little extra if you use a "real" database server.
>
> Even if you expect 40 active users, how likely is it that they'll all 
> be up/downloading at the same point in time...?
>
> Adam
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'In Flanders fields the poppies blow
  Between the crosses, row on row,
  That mark our place: and in the sky
  The larks still bravely singing fly
  Scarce heard amid the guns below.

  We are the dead: Short days ago,
  We lived, felt dawn, saw sunset glow,
  Loved and were loved: and now we lie
  In Flanders fields!

  Take up our quarrel with the foe
  To you, from failing hands, we throw
  The torch: be yours to hold it high
  If ye break faith with us who die,
  We shall not sleep, though poppies grow
  In Flanders fields.' Lieutenant Colonel John McCrae

Composed at the battlefront on May 3, 1915
during the second battle of Ypres, Belgium

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200714/0d0937b8/attachment.html>

From Jules at Zend.To  Tue Jul 14 16:40:18 2020
From: Jules at Zend.To (Jules)
Date: Tue, 14 Jul 2020 16:40:18 +0100
Subject: [ZendTo] New ZendTo Site Not loading
In-Reply-To: <WM!25eae09b40d2852949fc77faee61fa4614ac4ac9201ac0787a64d6cdd2f28a41b7d76be97c9a7c1929f1ae1d1b38dbff!@mx.jul.es>
References: <785aa2751d1d43c3813ff1ff2873b785@HSH-MAIL.HSH.local>
 <WM!25eae09b40d2852949fc77faee61fa4614ac4ac9201ac0787a64d6cdd2f28a41b7d76be97c9a7c1929f1ae1d1b38dbff!@mx.jul.es>
Message-ID: <403e2b63-2eee-5880-df42-f6babe3472d1@Zend.To>

Marlon,

Do
 ??? php -l /opt/zendto/config/preferences.php
to see if you have any syntax errors in preferences.php.

After that, if it's still not behaving, look in your Apache error log 
for a "PHP Fatal error". That will tell you where the error occurred too.

Cheers,
Jules.

On 13/07/2020 23:27, Marlon Deerr via ZendTo wrote:
>
> Hello,
>
> I?m in the process of setting up a? brand new install of ZendTo site 
> on a Ubuntu 20.04 server. ?I?ve run into an issue where I just can no 
> longer get the home page to load. After a successful install of 
> Zendto, here are the steps I performed until the issue arose
>
> 1.Created a test user successfully
>
> 2.Logged in as that test user successfully
>
> 3.Changed the ServiceTitle in the zendto.conf file without problem.
>
> a.I ?m able to access the site and see all instances where that 
> variable would display that variable.
>
> 4.Acquired the required Captcha keys from Google an inserted them 
> successfully within preferences.php
>
> a.Launch website after this successfully
>
> 5.Edited preferences.php again but this time changed all AD 
> authentication related entries
>
> a.Attempted to access webpage to see if I it work BUT now the site 
> does not load at all.
>
> I am stumped at 5a. I can?t figure out why the home page won?t load. 
> ?Apart from an Error 500 from Google Chrome, no other error is give.? 
> Is this possibly related to it having a self-signed certificate?? Any 
> guidance on this would be grated appreciated as I am at a loss.
>
> Thanks,
>
> Marlon
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'In Flanders fields the poppies blow
  Between the crosses, row on row,
  That mark our place: and in the sky
  The larks still bravely singing fly
  Scarce heard amid the guns below.

  We are the dead: Short days ago,
  We lived, felt dawn, saw sunset glow,
  Loved and were loved: and now we lie
  In Flanders fields!

  Take up our quarrel with the foe
  To you, from failing hands, we throw
  The torch: be yours to hold it high
  If ye break faith with us who die,
  We shall not sleep, though poppies grow
  In Flanders fields.' Lieutenant Colonel John McCrae

Composed at the battlefront on May 3, 1915
during the second battle of Ypres, Belgium

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200714/8a5da80a/attachment.html>

From Jules at Zend.To  Tue Jul 14 17:01:28 2020
From: Jules at Zend.To (Jules)
Date: Tue, 14 Jul 2020 17:01:28 +0100
Subject: [ZendTo] 24 hour drop-off summary
In-Reply-To: <WM!6565c3d4683aeb243828bb4cc2da049b4e071ef46f40bba5e9ffb79597d395b8285fa3c30809beebbc24ca5af88148fb!@mx.jul.es>
References: <CAD1KJM7wdKNkAb33gXeScPxuDu_mz26wFtVm8bjt+oO8-7f7uQ@mail.gmail.com>
 <WM!6565c3d4683aeb243828bb4cc2da049b4e071ef46f40bba5e9ffb79597d395b8285fa3c30809beebbc24ca5af88148fb!@mx.jul.es>
Message-ID: <a109caa9-f0bb-8d85-98f8-ce50ee86bef9@Zend.To>

Everton,

You are quite correct. Drop-offs that have been created and then deleted 
before they have been seen by any overnight run will be missing. ZendTo 
carefully deletes pretty much all record of drop-offs that have gone, so 
you haven't got any continuously growing database tables or anything 
like that. So yes, it will miss them.

I wrote the overnight-summary feature for 1 specific site with a very 
particular use case. Once written, it is far easier for everyone if that 
feature is available to all, so there is only 1 release stream.

Personally I would strongly advise against using that feature at all. It 
is very likely to wind you up in deep trouble with your nearest privacy 
lawyers, when members of your organisation discover that you are 
routinely getting this information sent to you. This kind of monitoring 
is very illegal in a large proportion of countries.

Cheers,
Jules.

On 14/07/2020 14:02, Everton Bruno Bernardi via ZendTo wrote:
> Hello there,
>
> I've just brought up a new instance of ZendTo (6.03-4) to a new Ubuntu 
> 20.04 LTS server. I noticed an undesired behavior related to the daily 
> drop-off summary:
>
> If a user sends a drop-off and deletes it the related drop off won't 
> appear in the summary - even if it was picked-up.
>
> Is it expected? I think it would be more accurate if all of the 
> drop-offs would be listed.
>
>
> Kind regards,
>
> -- 
> /Everton Bruno Bernardi/
>
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'It's in Apple's DNA that technology alone is not enough. It's
  technology married with liberal arts, married with the humanities,
  that yields us the result that makes our hearts sing.' - Steve Jobs

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200714/b77a0e7d/attachment.html>

From Jules at Zend.To  Tue Jul 14 17:04:07 2020
From: Jules at Zend.To (Jules)
Date: Tue, 14 Jul 2020 17:04:07 +0100
Subject: [ZendTo] Expire Time Incorrect
In-Reply-To: <WM!d51b52ac221d0cff6011a83a1e5295de6d6024f04ef3c38ef5d8aa40281562f79bfafe5bd331b80433e126cb8be489d9!@mx.jul.es>
References: <BN6PR1801MB1857195A295C573D911454AFD6830@BN6PR1801MB1857.namprd18.prod.outlook.com>
 <WM!13120fee741facac97f09cd93188485daeb5d83ff192787b66b95bb88c653fb0c8a74261a2969d60c60e71b3a41e3d24!@mx.jul.es>
 <c41f03dc-0658-c3c9-33c4-75885fef9367@Zend.To>
 <WM!512bec053387b578d2b0480f6c7da58b1b4d1f7e284bd6d44ccd22fc4bc2ae131dcc16747430f631eb199845eace6109!@mx.jul.es>
 <2eae023e-c1b6-7bb0-30a1-67c1188fcef3@pcfreak.de>
 <WM!d51b52ac221d0cff6011a83a1e5295de6d6024f04ef3c38ef5d8aa40281562f79bfafe5bd331b80433e126cb8be489d9!@mx.jul.es>
Message-ID: <863d9c13-4814-a68c-3c93-2098c366dcb7@Zend.To>

Peter,

I have already fixed this.
But just noticed I forgot to put it in the Change Log! :-( My bad.

Do a quick "yum update zendto", refresh your browser, and it should 
instantly go away.

Cheers,
Jules.

On 14/07/2020 10:02, Der PCFreak via ZendTo wrote:
>
> Hi Jules,
>
> I am currently facing the same problem with a Dropoff made from an 
> external user via the public site.
>
>
> It shows exactly the same days as Michael Imlay wrote (10919 days + 
> some hours).
>
> I am running
>
> ```
> Installed Packages
> Name??????? : zendto
> Arch??????? : noarch
> Version???? : 6.01
> Release???? : 2
> Size??????? : 9.5 M
> Repo??????? : installed
> From repo?? : ZendTo
> Summary???? : Web-based File Transfer and Storage System
> ```
>
> on `CentOS Linux release 7.8.2003 (Core)`.
>
>
> In the admin interface (Global Drop-off List) the `Created` date is 
> `2020-07-08 10:31:19`. This is also stated in the corresponding emails.
>
> We have a retention time of 7 days. The DropOff was sent to 2 
> recipients within our companies (if that matters somehow?).
> The size was 3.9 GB and SHa-256 Checksum was `Not calculated`.
>
> Btw. in the `Drop-Off Summary` it correctly shows `This drop-off will 
> expire in 23 hours and 31 minutes.` which is correct.
>
> Any ideas?
>
> Kind regards
>
> Peter
>
> On 10/06/2020 18:11, Jules via ZendTo wrote:
>> Michael,
>>
>> What version are you running?
>> And what are you running it on?
>>
>> Jules.
>>
>> On 10/06/2020 16:55, Michael Imlay via ZendTo wrote:
>>>
>>> Hey,
>>>
>>> I have my ZendTo configured to send out a notification started 3 
>>> days prior to removing the files. On the site it shows correct, but 
>>> the user who receives the e-mails gets something like this:
>>>
>>> *This is a reminder about a drop-off sent to you, that no one has 
>>> picked up.**
>>> *The drop-off will expire in 10911 days and 16 hours after which it 
>>> will be automatically deleted.**
>>>
>>> **
>>>
>>> *This is a reminder about a drop-off sent to you, that no one has 
>>> picked up.**
>>> *The drop-off will expire in 10912 days and 16 hours after which it 
>>> will be automatically deleted.**
>>>
>>> **
>>>
>>> *This is a reminder about a drop-off sent to you, that no one has 
>>> picked up.**
>>> *The drop-off will expire in 10913 days and 16 hours after which it 
>>> will be automatically deleted.**
>>>
>>> **
>>>
>>> Any idea why this might be happening on just the reminder e-mails?
>>>
>>> Thanks,
>>>
>>> Michael Imlay
>>>
>>> DELL LOGO
>>>
>>> Michael Imlay
>>>
>>> IT & Telecommunications Designer
>>>
>>> 129 East Government Street
>>>
>>> Pensacola, FL 32502
>>>
>>> Direct:? 850-332-2084
>>> Office:? 850-332-5687 x117
>>>
>>> Cell: ????? 850-737-9219
>>>
>>> IT at DellConsultingLLC.com <mailto:IT at DellConsultingLLC.com>
>>>
>>> This email and any files transmitted with it may contain PRIVILEGED 
>>> or CONFIDENTIAL information and may be read or used only by the 
>>> intended recipient. If you are not the intended recipient of the 
>>> email or any of its attachments, please be advised that you have 
>>> received this email in error and that any use, dissemination, 
>>> distribution, forwarding, printing, or copying of this email or any 
>>> attached files is strictly prohibited. If you have received this 
>>> email in error, please immediately purge it and all attachments and 
>>> notify the sender by reply email or contact the sender at the number 
>>> listed.
>>>
>>>
>>> _______________________________________________
>>> ZendTo mailing list
>>> ZendTo at zend.to
>>> http://jul.es/mailman/listinfo/zendto
>>
>> Jules
>>
>> -- 
>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>
>> 'It's very unlikely indeed he will ever recover consciousness, and
>>   if he does he won't be the Julian you knew.'
>>    - A hospital consultant I proved very wrong in 2007 :-)
>>
>> www.Zend.To
>> Twitter: @JulesFM
>>
>> _______________________________________________
>> ZendTo mailing list
>> ZendTo at zend.to
>> http://jul.es/mailman/listinfo/zendto
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Every morning when I wake,
  Dear Lord, a little prayer I make,
  O please do keep Thy lovely eye
  On all poor creatures born to die

  And every evening at sun-down
  I ask a blessing on the town,
  For whether we last the night or no
  I'm sure is always touch-and-go.

  We are not wholly bad or good
  Who live our lives under Milk Wood,
  And Thou, I know, wilt be the first
  To see our best side, not our worst.

  O let us see another day!
  Bless us all this night, I pray,
  And to the sun we all will bow
  And say, good-bye - but just for now!'
     - Dylan Thomas

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200714/cedf8701/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 9426 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200714/cedf8701/attachment-0001.png>

From MDeerr at hshlawyers.com  Tue Jul 14 18:45:03 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Tue, 14 Jul 2020 17:45:03 +0000
Subject: [ZendTo] Authentication Error - The username or password was
 incorrect
References: <5bbb4fb4215246b0972b060f5c691d9b@HSH-MAIL.HSH.local>
Message-ID: <WM!a36308db46adfd7479fd2ce4a18e69653cee550af1a292076bf1bab639989c97e35fe7975d56693ef9069451a9bd0778!@mx.jul.es>

Ok, so I think I finally (or almost finally) got my AD authentication settings correct.  I have installed the ldapsearch utility to confirm that I'm able to successful search the OU where my users reside, however when I attempt to log in with a valid user, ZendTo keeps erroring with:

Authentication Error
The username or password was incorrect

I checked the /var/log/zendto/zendto.log and it says the following:

"....Warning: authorization attempt for locked-out user <username1>
Then when I try logging in as another user, I see the following in the log

"...Warning: authorization failed for <username2>



I know that I have both username/password correct so I must be missing something. Anyone know what setting I may have applied incorrectly?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200714/1f8ebdc2/attachment.html>

From ebbernardi at gmail.com  Tue Jul 14 18:52:28 2020
From: ebbernardi at gmail.com (Everton Bruno Bernardi)
Date: Tue, 14 Jul 2020 14:52:28 -0300
Subject: [ZendTo] Authentication Error - The username or password was
 incorrect
In-Reply-To: <WM!d49e1b518c70e63d7f397513ba2ba81b0d660ad0dedcddb4019ed26314a250b467a6ad2012c7df47a614d53909940239!@mx.jul.es>
References: <5bbb4fb4215246b0972b060f5c691d9b@HSH-MAIL.HSH.local>
 <WM!a36308db46adfd7479fd2ce4a18e69653cee550af1a292076bf1bab639989c97e35fe7975d56693ef9069451a9bd0778!@mx.jul.es>
 <WM!d49e1b518c70e63d7f397513ba2ba81b0d660ad0dedcddb4019ed26314a250b467a6ad2012c7df47a614d53909940239!@mx.jul.es>
 <CAD1KJM6LOFcHZkLGUHe1XsT9wXiLaZekCdGqPxm+jAtQwmq8zg@mail.gmail.com>
Message-ID: <WM!c3a85fe5df1a66397fba913e4b08213b5a8a38d37f2282339d8bd40708109847726718d8befea9515af6d4cd9b9f2119!@mx.jul.es>

Hello Marlon.

Are you using SSL or TLS for LDAP communications encryption? If so, your
Domain Controller will probably have a self signed certificate and you're
gonna need to add it to the CA Certificates file used by LDAP in your Unix
distribution - The latest Ubuntu version points it
to /etc/ssl/certs/ca-certificates.crt).


Kind regards.

Everton Bernardi

On Tue, Jul 14, 2020 at 2:45 PM Marlon Deerr via ZendTo <zendto at zend.to>
wrote:

> Ok, so I think I finally (or almost finally) got my AD authentication
> settings correct.  I have installed the ldapsearch utility to confirm that
> I?m able to successful search the OU where my users reside, however when I
> attempt to log in with a valid user, ZendTo keeps erroring with:
>
>
>
> Authentication Error
>
> The username or password was incorrect
>
>
>
> I checked the /var/log/zendto/zendto.log and it says the following:
>
>
>
> ??.Warning: authorization attempt for locked-out user <username1>
>
> Then when I try logging in as another user, I see the following in the log
>
>
>
> ??Warning: authorization failed for <username2>
>
>
>
>
>
>
>
> I know that I have both username/password correct so I must be missing
> something. Anyone know what setting I may have applied incorrectly?
>
>
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
>


-- 
*Everton Bruno Bernardi <http://google.com/+EvertonBrunoBernardi>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200714/254f3e60/attachment.html>

From MDeerr at hshlawyers.com  Tue Jul 14 23:15:53 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Tue, 14 Jul 2020 22:15:53 +0000
Subject: [ZendTo] New ZendTo Site Not loading
In-Reply-To: <WM!8ea7c7ae16479fe81da0918395b55637316963abcaf8a4014a9cb8739bb0d70989ec0d7c6f97ec8de946621a1e0d6072!@mx.jul.es>
References: <785aa2751d1d43c3813ff1ff2873b785@HSH-MAIL.HSH.local>
 <WM!25eae09b40d2852949fc77faee61fa4614ac4ac9201ac0787a64d6cdd2f28a41b7d76be97c9a7c1929f1ae1d1b38dbff!@mx.jul.es>
 <403e2b63-2eee-5880-df42-f6babe3472d1@Zend.To>
 <WM!8ea7c7ae16479fe81da0918395b55637316963abcaf8a4014a9cb8739bb0d70989ec0d7c6f97ec8de946621a1e0d6072!@mx.jul.es>
 <e6ad12883fc446268ba9a05697fd0645@HSH-MAIL.HSH.local>
Message-ID: <WM!8a27559f4b92bbe3a5be72f0f21bfc896f29d09c8cb4d4e1aa353449d38b7975e60c54217a1d75b8e6c26766e7b574e3!@mx.jul.es>

Hey Jules,

I think the issue was that had commented out certain entries using #, but forgot to ensure that I ended any new entries with a comma. I had to go through each change one-by-one before I realized that but it's nice to know that I could use your suggestion below for any (possible) future syntax errors.


From: Jules [mailto:Jules at Zend.To]
Sent: Tuesday, July 14, 2020 11:40 AM
To: ZendTo Users <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] New ZendTo Site Not loading

Marlon,

Do
    php -l /opt/zendto/config/preferences.php
to see if you have any syntax errors in preferences.php.

After that, if it's still not behaving, look in your Apache error log for a "PHP Fatal error". That will tell you where the error occurred too.

Cheers,
Jules.
On 13/07/2020 23:27, Marlon Deerr via ZendTo wrote:
Hello,

I'm in the process of setting up a  brand new install of ZendTo site on a Ubuntu 20.04 server.  I've run into an issue where I just can no longer get the home page to load. After a successful install of Zendto, here are the steps I performed until the issue arose


1.       Created a test user successfully

2.       Logged in as that test user successfully

3.       Changed the ServiceTitle in the zendto.conf file without problem.

1.       I 'm able to access the site and see all instances where that variable would display that variable.

4.       Acquired the required Captcha keys from Google an inserted them successfully within preferences.php

1.       Launch website after this successfully

5.       Edited preferences.php again but this time changed all AD authentication related entries

1.       Attempted to access webpage to see if I it work BUT now the site does not load at all.

I am stumped at 5a. I can't figure out why the home page won't load.  Apart from an Error 500 from Google Chrome, no other error is give.  Is this possibly related to it having a self-signed certificate?  Any guidance on this would be grated appreciated as I am at a loss.

Thanks,
Marlon



_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto:ZendTo at zend.to>

http://jul.es/mailman/listinfo/zendto



Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'In Flanders fields the poppies blow

 Between the crosses, row on row,

 That mark our place: and in the sky

 The larks still bravely singing fly

 Scarce heard amid the guns below.



 We are the dead: Short days ago,

 We lived, felt dawn, saw sunset glow,

 Loved and were loved: and now we lie

 In Flanders fields!



 Take up our quarrel with the foe

 To you, from failing hands, we throw

 The torch: be yours to hold it high

 If ye break faith with us who die,

 We shall not sleep, though poppies grow

 In Flanders fields.' Lieutenant Colonel John McCrae



Composed at the battlefront on May 3, 1915

during the second battle of Ypres, Belgium



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200714/1adbe7d6/attachment-0001.html>

From mailinglists at pcfreak.de  Wed Jul 15 08:50:01 2020
From: mailinglists at pcfreak.de (Der PCFreak)
Date: Wed, 15 Jul 2020 09:50:01 +0200
Subject: [ZendTo] Expire Time Incorrect
In-Reply-To: <WM!8f16ebe85cf6c1cdfe6a3b2208cf7dd0aec4dbba36594dae423f87f1cdd408798a7bdb9cf3daedc5314a789dd0124d1c!@mx.jul.es>
References: <BN6PR1801MB1857195A295C573D911454AFD6830@BN6PR1801MB1857.namprd18.prod.outlook.com>
 <WM!13120fee741facac97f09cd93188485daeb5d83ff192787b66b95bb88c653fb0c8a74261a2969d60c60e71b3a41e3d24!@mx.jul.es>
 <c41f03dc-0658-c3c9-33c4-75885fef9367@Zend.To>
 <WM!512bec053387b578d2b0480f6c7da58b1b4d1f7e284bd6d44ccd22fc4bc2ae131dcc16747430f631eb199845eace6109!@mx.jul.es>
 <2eae023e-c1b6-7bb0-30a1-67c1188fcef3@pcfreak.de>
 <WM!d51b52ac221d0cff6011a83a1e5295de6d6024f04ef3c38ef5d8aa40281562f79bfafe5bd331b80433e126cb8be489d9!@mx.jul.es>
 <863d9c13-4814-a68c-3c93-2098c366dcb7@Zend.To>
 <WM!8f16ebe85cf6c1cdfe6a3b2208cf7dd0aec4dbba36594dae423f87f1cdd408798a7bdb9cf3daedc5314a789dd0124d1c!@mx.jul.es>
 <b3a331d8-7077-ca1a-63ba-a63bc13ba650@pcfreak.de>
Message-ID: <WM!5ba692860262d64f32a740a1393b37b7381ac2b8ea58e808ce166f59137b31fd2ef29b271b3518e01437b00c35d3f6c5!@mx.jul.es>

Hi Jules,

thank you, for pointing that out. Just upgraded without problems and 
great that it is now possible to edit the subject line which was
a feature request we had a lot from our users!

Thank you very much for spending your time

Regards

Peter

On 14/07/2020 18:04, Jules wrote:
> Peter,
>
> I have already fixed this.
> But just noticed I forgot to put it in the Change Log! :-( My bad.
>
> Do a quick "yum update zendto", refresh your browser, and it should 
> instantly go away.
>
> Cheers,
> Jules.
>
> On 14/07/2020 10:02, Der PCFreak via ZendTo wrote:
>>
>> Hi Jules,
>>
>> I am currently facing the same problem with a Dropoff made from an 
>> external user via the public site.
>>
>>
>> It shows exactly the same days as Michael Imlay wrote (10919 days + 
>> some hours).
>>
>> I am running
>>
>> ```
>> Installed Packages
>> Name??????? : zendto
>> Arch??????? : noarch
>> Version???? : 6.01
>> Release???? : 2
>> Size??????? : 9.5 M
>> Repo??????? : installed
>> From repo?? : ZendTo
>> Summary???? : Web-based File Transfer and Storage System
>> ```
>>
>> on `CentOS Linux release 7.8.2003 (Core)`.
>>
>>
>> In the admin interface (Global Drop-off List) the `Created` date is 
>> `2020-07-08 10:31:19`. This is also stated in the corresponding emails.
>>
>> We have a retention time of 7 days. The DropOff was sent to 2 
>> recipients within our companies (if that matters somehow?).
>> The size was 3.9 GB and SHa-256 Checksum was `Not calculated`.
>>
>> Btw. in the `Drop-Off Summary` it correctly shows `This drop-off will 
>> expire in 23 hours and 31 minutes.` which is correct.
>>
>> Any ideas?
>>
>> Kind regards
>>
>> Peter
>>
>> On 10/06/2020 18:11, Jules via ZendTo wrote:
>>> Michael,
>>>
>>> What version are you running?
>>> And what are you running it on?
>>>
>>> Jules.
>>>
>>> On 10/06/2020 16:55, Michael Imlay via ZendTo wrote:
>>>>
>>>> Hey,
>>>>
>>>> I have my ZendTo configured to send out a notification started 3 
>>>> days prior to removing the files. On the site it shows correct, but 
>>>> the user who receives the e-mails gets something like this:
>>>>
>>>> *This is a reminder about a drop-off sent to you, that no one has 
>>>> picked up.**
>>>> *The drop-off will expire in 10911 days and 16 hours after which it 
>>>> will be automatically deleted.**
>>>>
>>>> **
>>>>
>>>> *This is a reminder about a drop-off sent to you, that no one has 
>>>> picked up.**
>>>> *The drop-off will expire in 10912 days and 16 hours after which it 
>>>> will be automatically deleted.**
>>>>
>>>> **
>>>>
>>>> *This is a reminder about a drop-off sent to you, that no one has 
>>>> picked up.**
>>>> *The drop-off will expire in 10913 days and 16 hours after which it 
>>>> will be automatically deleted.**
>>>>
>>>> **
>>>>
>>>> Any idea why this might be happening on just the reminder e-mails?
>>>>
>>>> Thanks,
>>>>
>>>> Michael Imlay
>>>>
>>>> DELL LOGO
>>>>
>>>> Michael Imlay
>>>>
>>>> IT & Telecommunications Designer
>>>>
>>>> 129 East Government Street
>>>>
>>>> Pensacola, FL 32502
>>>>
>>>> Direct:? 850-332-2084
>>>> Office:? 850-332-5687 x117
>>>>
>>>> Cell: ????? 850-737-9219
>>>>
>>>> IT at DellConsultingLLC.com <mailto:IT at DellConsultingLLC.com>
>>>>
>>>> This email and any files transmitted with it may contain PRIVILEGED 
>>>> or CONFIDENTIAL information and may be read or used only by the 
>>>> intended recipient. If you are not the intended recipient of the 
>>>> email or any of its attachments, please be advised that you have 
>>>> received this email in error and that any use, dissemination, 
>>>> distribution, forwarding, printing, or copying of this email or any 
>>>> attached files is strictly prohibited. If you have received this 
>>>> email in error, please immediately purge it and all attachments and 
>>>> notify the sender by reply email or contact the sender at the 
>>>> number listed.
>>>>
>>>>
>>>> _______________________________________________
>>>> ZendTo mailing list
>>>> ZendTo at zend.to
>>>> http://jul.es/mailman/listinfo/zendto
>>>
>>> Jules
>>>
>>> -- 
>>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>>
>>> 'It's very unlikely indeed he will ever recover consciousness, and
>>>   if he does he won't be the Julian you knew.'
>>>    - A hospital consultant I proved very wrong in 2007 :-)
>>>
>>> www.Zend.To
>>> Twitter: @JulesFM
>>>
>>> _______________________________________________
>>> ZendTo mailing list
>>> ZendTo at zend.to
>>> http://jul.es/mailman/listinfo/zendto
>>
>> _______________________________________________
>> ZendTo mailing list
>> ZendTo at zend.to
>> http://jul.es/mailman/listinfo/zendto
>
> Jules
>
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
>
> 'Every morning when I wake,
>   Dear Lord, a little prayer I make,
>   O please do keep Thy lovely eye
>   On all poor creatures born to die
>
>   And every evening at sun-down
>   I ask a blessing on the town,
>   For whether we last the night or no
>   I'm sure is always touch-and-go.
>
>   We are not wholly bad or good
>   Who live our lives under Milk Wood,
>   And Thou, I know, wilt be the first
>   To see our best side, not our worst.
>
>   O let us see another day!
>   Bless us all this night, I pray,
>   And to the sun we all will bow
>   And say, good-bye - but just for now!'
>      - Dylan Thomas
>
> www.Zend.To
> Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200715/49b2801e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 9426 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200715/49b2801e/attachment-0001.png>

From Jules at Zend.To  Wed Jul 15 12:08:30 2020
From: Jules at Zend.To (Jules)
Date: Wed, 15 Jul 2020 12:08:30 +0100
Subject: [ZendTo] Authentication Error - The username or password was
 incorrect
In-Reply-To: <WM!a36308db46adfd7479fd2ce4a18e69653cee550af1a292076bf1bab639989c97e35fe7975d56693ef9069451a9bd0778!@mx.jul.es>
References: <5bbb4fb4215246b0972b060f5c691d9b@HSH-MAIL.HSH.local>
 <WM!a36308db46adfd7479fd2ce4a18e69653cee550af1a292076bf1bab639989c97e35fe7975d56693ef9069451a9bd0778!@mx.jul.es>
Message-ID: <e9b7b2e4-9981-91a5-bfc2-d8ac8c9bdbd5@Zend.To>

Marlon,

The crucial bit in the log is the "locked-out user" bit.

ZendTo has a security feature in it to stop it being used as a method of 
brute-force attacking your accounts from outside.
If the same user has several failed logins in a row, that user is locked 
out for the next 24 hours by default.

If you can login as an admin user, one of the extra admin red buttons 
shows you the locked out users and lets you reset them.

Alternatively, you can unlock all locked users from the command line with
 ??? /opt/zendto/bin/unlockuser -a

Cheers,
Jules.

On 14/07/2020 18:45, Marlon Deerr via ZendTo wrote:
>
> Ok, so I think I finally (or almost finally) got my AD authentication 
> settings correct.? I have installed the ldapsearch utility to confirm 
> that I?m able to successful search the OU where my users reside, 
> however when I attempt to log in with a valid user, ZendTo keeps 
> erroring with:
>
> Authentication Error
>
> The username or password was incorrect
>
> I checked the /var/log/zendto/zendto.log and it says the following:
>
> ??.Warning: authorization attempt for locked-out user <username1>
>
> Then when I try logging in as another user, I see the following in the 
> log
>
> ??Warning: authorization failed for <username2>
>
> I know that I have both username/password correct so I must be missing 
> something. Anyone know what setting I may have applied incorrectly?
>
>
> _______________________________________________
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200715/469eb53f/attachment.html>

From Jules at Zend.To  Wed Jul 15 12:19:58 2020
From: Jules at Zend.To (Jules)
Date: Wed, 15 Jul 2020 12:19:58 +0100
Subject: [ZendTo] Reminder email sent to wrong recipients
In-Reply-To: <WM!4dea89553e06633e843e5f96df3ed86bfb13dd7c38011a75f39c367734c60df7e123bcc3ef3491d585a5588e4e598b7a!@mx.jul.es>
References: <AM0PR04MB6082681B3AD8C20A8BE78CB0FF610@AM0PR04MB6082.eurprd04.prod.outlook.com>
 <WM!4dea89553e06633e843e5f96df3ed86bfb13dd7c38011a75f39c367734c60df7e123bcc3ef3491d585a5588e4e598b7a!@mx.jul.es>
Message-ID: <e1e2dca3-a120-68b0-59c0-dd760e768229@Zend.To>

Mark,

If you set
 ?'warnDaysBeforeDeletion' => 0,
in preferences.php, it will disable the warning emails.

I think I know exactly what is causing the bug, I just need to implement 
a tidy fix for it.

Cheers,
Jules.

On 14/07/2020 11:20, Sangster, Mark via ZendTo wrote:
>
> Hello,
>
> We also had the reminder emails send to the wrong recipients this 
> morning (sorry I can?t reply to the original thread as I just signed up).
>
> But in answer to the questions Jules asked ?
>
> # rpm -q zendto
>
> zendto-6.03-4.noarch
>
> Previous version was v5.03.
>
> The reminder emails about XYZ were sent in place of ABC/DEF.
>
> The log correctly shows the email/claimID for each reminder to be sent.
>
> XYZ was the first created.
>
> Finally .. I believe that warnDaysBeforeDeletion will prevent the 
> email reminders, can you confirm?
>
> Thanks
>
> Mark
>
> ------------------------------------------------------------------------
>
> Mark Sangster
>
> Server Infrastructure Specialist
>
> Information Technology Services | University of Aberdeen
>
> t: +44 (0)1224 27-3315 | e: mark at abdn.ac.uk <mailto:mark at abdn.ac.uk> | 
> u: http://www.abdn.ac.uk/it/ <http://www.abdn.ac.uk/it/>
>
>
>
> The University of Aberdeen is a charity registered in Scotland, No 
> SC013683.
> Tha Oilthigh Obar Dheathain na charthannas cl?raichte ann an Alba, 
> ?ir. SC013683.
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Making machines do what you want requires only two qualities:
  1) Being slightly more stubborn that the computer, &
  2) Remembering that computers are electrified rocks.' - @JediJeremy

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200715/8cd98b31/attachment.html>

From Jules at Zend.To  Wed Jul 15 13:34:14 2020
From: Jules at Zend.To (Jules)
Date: Wed, 15 Jul 2020 13:34:14 +0100
Subject: [ZendTo] Reminder email sent to wrong recipients
In-Reply-To: <WM!d5dc43789c9d088f8bfbb01aa2504defab832d0e89bc84a42e46a313626d1b5b715d65a36d76502d311086a14f357619!@mx.jul.es>
References: <CAHAhptXJcSa2Hka+4k-iHMy8hcHtr53i+mEKV3MrwNo1GnH7bA@mail.gmail.com>
 <WM!d5dc43789c9d088f8bfbb01aa2504defab832d0e89bc84a42e46a313626d1b5b715d65a36d76502d311086a14f357619!@mx.jul.es>
Message-ID: <4d4bb9f2-c16d-73e5-8bb0-889e3da0ee8f@Zend.To>

Ricky, Mark and others,

I have just fixed this bug, and will put out a new release this afternoon.
I need some food first...

I would advise all users running version 6 to upgrade as soon as possible.

Cheers,
Jules.

On 13/07/2020 17:32, Ricky Boone via ZendTo wrote:
> I'm looking into an issue that was reported to me this morning.? What 
> appears to have happened was that reminder emails for a drop-off were 
> sent, and the log indicates that multiple internal recipients were 
> sent reminders, but the emails they received were for someone else's 
> dropoff. Specifically, the log indicates they were notified about 
> dropoffs ABC and DEF, but the email they received included dropoff 
> details for XYZ.? The logs do not indicate anything related to XYZ was 
> sent to these recipients, but I do have a sample email from one of the 
> incorrect recipients that indicates they did.? The system logs 
> indicate that ZendTo was updated the day before, however the upgrade 
> script did not kick off.? Nothing in the logs indicate an issue with 
> the notification script running.? The system in question is running 
> CentOS 7.
>
> The instance uses a MariaDB backend instead of SQLite (used SQLite 
> before, ran into an unrelated corruption issue that made it difficult 
> to troubleshoot, so hard-cut over to a MariaDB backend during low 
> usage).? I confirmed the related IDs do not include the recipients in 
> question.
>
> This is the first time I've seen this, so I'm not sure it was due to 
> the upgrade step not being completed (though that should only impact 
> configuration settings, not DB schema, etc.).? I'm not sure how I 
> would be able to reproduce this yet, but I'm suspecting a value for 
> one drop-off was inadvertently reused before it was cleared and 
> updated with the correct value.? For now, I just wanted to ping the 
> mailing list to see if they've seen similar, or to at least alert 
> Jules to a possible bug that may need additional research. When I get 
> a chance today I'm going to check through some of the related scripts 
> to see if anything stands out.
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Now I am become Death, the destroyer of worlds.' - J. Robert Oppenheimer

www.Zend.To
Twitter: @JulesFM

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

From Jules at Zend.To  Wed Jul 15 15:04:40 2020
From: Jules at Zend.To (Jules)
Date: Wed, 15 Jul 2020 15:04:40 +0100
Subject: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5
Message-ID: <523fad9d-598e-431b-b360-f83820c34c74@Zend.To>

Hi all,

To follow up from the thread "Reminder email sent to wrong recipients", 
I have fixed that bug along with a few other more minor problems.

Anyone running version 6 should upgrade.

So I have just release 6.03-5, which you should be able to get with a quick
 ??? yum update
or
 ??? sudo apt update ; sudo apt upgrade
Then if you aren't already running version 6.03, run
 ??? sudo /opt/zendto/bin/upgrade

The Change Log is this:

- Fixed bug where the wrong reminder emails were being sent to users.
- Fixed formatting error in plain-text emails about a new drop-off.
- Fixed bug where changing language immediately before/after doing SAML 
login could produce blank page.
- Fixed bug where "Decline" button in GDPR cookie-consent bar was not 
being translated.
- Updated Turkish and Brazilian Portuguese translations.

Let me know of any problems, questions or suggestions!

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Intelligence is quickness to apprehend as distinct from ability,
  which is capacity to act wisely on the thing apprehended.'
  - Alfred North Whitehead

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200715/8677225c/attachment.html>

From MDeerr at hshlawyers.com  Wed Jul 15 15:13:43 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Wed, 15 Jul 2020 14:13:43 +0000
Subject: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5
In-Reply-To: <WM!ea5144e31d109651d446a3234f9a2df55952580128a90c59699ad78ef390f128761b2aadb4ed84842fcb972caf771de3!@mx.jul.es>
References: <523fad9d-598e-431b-b360-f83820c34c74@Zend.To>
 <WM!ea5144e31d109651d446a3234f9a2df55952580128a90c59699ad78ef390f128761b2aadb4ed84842fcb972caf771de3!@mx.jul.es>
 <5f35954934444b8f9102c2f3f778df41@HSH-MAIL.HSH.local>
Message-ID: <WM!a4056b4e53fd8767842192748718839db5964303022d7a675900fc6f313d5c98b7c3fa41d6628b8ac5362a4ec52ac230!@mx.jul.es>

Hello Jules,

This would be my first ever update to a newer version.  It says that that default action is to keep your current version of preferences.php, but you can see that the default would be N if  just hit enter. Are we supposed to enter Y to keep our current preferences.php then?

[cid:image001.png at 01D65A90.9E8BC980]

From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Jules via ZendTo
Sent: Wednesday, July 15, 2020 10:05 AM
To: ZendTo Users <zendto at zend.to>
Cc: Jules <Jules at Zend.To>
Subject: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5

Hi all,

To follow up from the thread "Reminder email sent to wrong recipients", I have fixed that bug along with a few other more minor problems.

Anyone running version 6 should upgrade.

So I have just release 6.03-5, which you should be able to get with a quick
    yum update
or
    sudo apt update ; sudo apt upgrade
Then if you aren't already running version 6.03, run
    sudo /opt/zendto/bin/upgrade

The Change Log is this:

- Fixed bug where the wrong reminder emails were being sent to users.
- Fixed formatting error in plain-text emails about a new drop-off.
- Fixed bug where changing language immediately before/after doing SAML login could produce blank page.
- Fixed bug where "Decline" button in GDPR cookie-consent bar was not being translated.
- Updated Turkish and Brazilian Portuguese translations.

Let me know of any problems, questions or suggestions!


Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'Intelligence is quickness to apprehend as distinct from ability,

 which is capacity to act wisely on the thing apprehended.'

 - Alfred North Whitehead



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200715/7d2a0fba/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 23046 bytes
Desc: image001.png
URL: <http://jul.es/pipermail/zendto/attachments/20200715/7d2a0fba/attachment-0001.png>

From MDeerr at hshlawyers.com  Wed Jul 15 15:16:46 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Wed, 15 Jul 2020 14:16:46 +0000
Subject: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5
In-Reply-To: <WM!1e10ee5b2f33074605d93b006b6634f6a495089afd4778800865d14eac161c63c570f44690001c0593a93a3c41094c92!@mx.jul.es>
References: <523fad9d-598e-431b-b360-f83820c34c74@Zend.To>
 <WM!ea5144e31d109651d446a3234f9a2df55952580128a90c59699ad78ef390f128761b2aadb4ed84842fcb972caf771de3!@mx.jul.es>
 <5f35954934444b8f9102c2f3f778df41@HSH-MAIL.HSH.local>
 <WM!a4056b4e53fd8767842192748718839db5964303022d7a675900fc6f313d5c98b7c3fa41d6628b8ac5362a4ec52ac230!@mx.jul.es>
 <WM!1e10ee5b2f33074605d93b006b6634f6a495089afd4778800865d14eac161c63c570f44690001c0593a93a3c41094c92!@mx.jul.es>
 <545143a62b6b446788df02fd59525fc3@HSH-MAIL.HSH.local>
Message-ID: <WM!dd4809d7fb209ac6ca627d3e15507424e5bb0edb150b12fce127eaee4f7c722e2508b12b355b36c185b245c9c61c14b6!@mx.jul.es>

Sorry Jules?.I totally misread the question. It will keep my current preferences.php if I hit enter. My bad!

From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Marlon Deerr via ZendTo
Sent: Wednesday, July 15, 2020 10:14 AM
To: 'ZendTo Users' <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5

Hello Jules,

This would be my first ever update to a newer version.  It says that that default action is to keep your current version of preferences.php, but you can see that the default would be N if  just hit enter. Are we supposed to enter Y to keep our current preferences.php then?

[cid:image001.png at 01D65A91.0B7F53E0]

From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Jules via ZendTo
Sent: Wednesday, July 15, 2020 10:05 AM
To: ZendTo Users <zendto at zend.to<mailto:zendto at zend.to>>
Cc: Jules <Jules at Zend.To<mailto:Jules at Zend.To>>
Subject: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5

Hi all,

To follow up from the thread "Reminder email sent to wrong recipients", I have fixed that bug along with a few other more minor problems.

Anyone running version 6 should upgrade.

So I have just release 6.03-5, which you should be able to get with a quick
    yum update
or
    sudo apt update ; sudo apt upgrade
Then if you aren't already running version 6.03, run
    sudo /opt/zendto/bin/upgrade

The Change Log is this:

- Fixed bug where the wrong reminder emails were being sent to users.
- Fixed formatting error in plain-text emails about a new drop-off.
- Fixed bug where changing language immediately before/after doing SAML login could produce blank page.
- Fixed bug where "Decline" button in GDPR cookie-consent bar was not being translated.
- Updated Turkish and Brazilian Portuguese translations.

Let me know of any problems, questions or suggestions!

Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'Intelligence is quickness to apprehend as distinct from ability,

 which is capacity to act wisely on the thing apprehended.'

 - Alfred North Whitehead



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200715/8789e6fc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 23046 bytes
Desc: image001.png
URL: <http://jul.es/pipermail/zendto/attachments/20200715/8789e6fc/attachment-0001.png>

From Jules at Zend.To  Wed Jul 15 15:31:28 2020
From: Jules at Zend.To (Jules)
Date: Wed, 15 Jul 2020 15:31:28 +0100
Subject: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5
In-Reply-To: <WM!dd4809d7fb209ac6ca627d3e15507424e5bb0edb150b12fce127eaee4f7c722e2508b12b355b36c185b245c9c61c14b6!@mx.jul.es>
References: <523fad9d-598e-431b-b360-f83820c34c74@Zend.To>
 <WM!ea5144e31d109651d446a3234f9a2df55952580128a90c59699ad78ef390f128761b2aadb4ed84842fcb972caf771de3!@mx.jul.es>
 <5f35954934444b8f9102c2f3f778df41@HSH-MAIL.HSH.local>
 <WM!a4056b4e53fd8767842192748718839db5964303022d7a675900fc6f313d5c98b7c3fa41d6628b8ac5362a4ec52ac230!@mx.jul.es>
 <WM!1e10ee5b2f33074605d93b006b6634f6a495089afd4778800865d14eac161c63c570f44690001c0593a93a3c41094c92!@mx.jul.es>
 <545143a62b6b446788df02fd59525fc3@HSH-MAIL.HSH.local>
 <WM!dd4809d7fb209ac6ca627d3e15507424e5bb0edb150b12fce127eaee4f7c722e2508b12b355b36c185b245c9c61c14b6!@mx.jul.es>
Message-ID: <e0e0489e-fdb8-3e7e-52ec-546de0731964@Zend.To>

Marlon,

If it asks you about preferences.php or zendto.conf, it doesn't actually 
matter *which* one you keep.
Just ensure you run my
 ??? /opt/zendto/bin/upgrade
and that will sort out the resulting confusion for you.

It actually keeps both of them, but doesn't tell you that.
(No, don't get me started about this! Grrrr......)

Your response to the question just sets which one gets what filename.
My upgrade script knows about all of this and straightens it all out for 
you.

Cheers,
Jules.

P.S. If it asks it about anything *except* obviously config files, then 
tell it to keep the new one, not your old one.

On 15/07/2020 15:16, Marlon Deerr via ZendTo wrote:
>
> Sorry Jules?.I totally misread the question. It will keep my current 
> preferences.php if I hit enter. My bad!
>
> *From:*ZendTo [mailto:zendto-bounces at zend.to] *On Behalf Of *Marlon 
> Deerr via ZendTo
> *Sent:* Wednesday, July 15, 2020 10:14 AM
> *To:* 'ZendTo Users' <zendto at zend.to>
> *Cc:* Marlon Deerr <MDeerr at hshlawyers.com>
> *Subject:* Re: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5
>
> Hello Jules,
>
> This would be my first ever update to a newer version.? It says that 
> that default action is to keep your current version of 
> preferences.php, but you can see that the default would be N if? just 
> hit enter. Are we supposed to enter Y to keep our current 
> preferences.php then?
>
> *From:*ZendTo [mailto:zendto-bounces at zend.to 
> <mailto:zendto-bounces at zend.to>] *On Behalf Of *Jules via ZendTo
> *Sent:* Wednesday, July 15, 2020 10:05 AM
> *To:* ZendTo Users <zendto at zend.to <mailto:zendto at zend.to>>
> *Cc:* Jules <Jules at Zend.To <mailto:Jules at Zend.To>>
> *Subject:* [ZendTo] ANNOUNCE: Bug-fix release 6.03-5
>
> Hi all,
>
> To follow up from the thread "Reminder email sent to wrong 
> recipients", I have fixed that bug along with a few other more minor 
> problems.
>
> Anyone running version 6 should upgrade.
>
> So I have just release 6.03-5, which you should be able to get with a 
> quick
> ??? yum update
> or
> ??? sudo apt update ; sudo apt upgrade
> Then if you aren't already running version 6.03, run
> ??? sudo /opt/zendto/bin/upgrade
>
> The Change Log is this:
>
> - Fixed bug where the wrong reminder emails were being sent to users.
> - Fixed formatting error in plain-text emails about a new drop-off.
> - Fixed bug where changing language immediately before/after doing 
> SAML login could produce blank page.
> - Fixed bug where "Decline" button in GDPR cookie-consent bar was not 
> being translated.
> - Updated Turkish and Brazilian Portuguese translations.
>
> Let me know of any problems, questions or suggestions!
>
> Jules
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> 'Intelligence is quickness to apprehend as distinct from ability,
>   which is capacity to act wisely on the thing apprehended.'
>   - Alfred North Whitehead
> www.Zend.To  <http://www.Zend.To>
> Twitter: @JulesFM
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Find a place inside where there's joy, and the joy will burn out
  the pain.' - Joseph Campbell

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200715/d3d27cd6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 23046 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200715/d3d27cd6/attachment-0001.png>

From Jules at Zend.To  Wed Jul 15 16:36:43 2020
From: Jules at Zend.To (Jules)
Date: Wed, 15 Jul 2020 16:36:43 +0100
Subject: [ZendTo] Isn't it annoying when...
Message-ID: <824eae75-1317-72f0-5c88-e0d27ae64667@Zend.To>

... you make a production release that fixes all known bugs.

Then find a bug.
Fortunately it's a *very* minor one, will only affect a few sites, and 
is dead easy to work around.

If you're a ZendTo admin and you log in via SAML-based authentication, 
you won't see the "System Statistics" button in the main menu.
The workaround for now is to add your 'authAdmins' users to your 
'authStats' users.

Cheers,

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Gaze not into the abyss, lest you become recognised as an abyss
  domain expert, and they expect you to keep gazing into the damn thing.'
                                            - @nickm_tor

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200715/82247872/attachment.html>

From MDeerr at hshlawyers.com  Wed Jul 15 16:50:52 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Wed, 15 Jul 2020 15:50:52 +0000
Subject: [ZendTo] Authentication Error - The username or password was
 incorrect
In-Reply-To: <WM!8596658a4ac6c0f2f39484749734a6bdcd881d8ab1c4ca1fc11e871bde3d0494af7561bc5fddfd9a91bbe23fa9a1fea6!@mx.jul.es>
References: <5bbb4fb4215246b0972b060f5c691d9b@HSH-MAIL.HSH.local>
 <WM!a36308db46adfd7479fd2ce4a18e69653cee550af1a292076bf1bab639989c97e35fe7975d56693ef9069451a9bd0778!@mx.jul.es>
 <e9b7b2e4-9981-91a5-bfc2-d8ac8c9bdbd5@Zend.To>
 <WM!8596658a4ac6c0f2f39484749734a6bdcd881d8ab1c4ca1fc11e871bde3d0494af7561bc5fddfd9a91bbe23fa9a1fea6!@mx.jul.es>
 <3fb2117013a6445babf526e96235aedd@HSH-MAIL.HSH.local>
Message-ID: <WM!82d33dcacc4ddee1b62dd8c18dcaac3ff0d915f311c97ff5d37725cc65a5c366a2ec8874c0db367a8bced244ef305ba3!@mx.jul.es>

OK, my user seems to be unlocked now but now I am getting the following errors below. I must be missing something else in my setup:

Warning: admin authorization failed for <username1>

And for other users I still get the following error:

Warning: authorization failed for <username2>


Note: I believe I added <username1> as an admin.

From: Jules [mailto:Jules at Zend.To]
Sent: Wednesday, July 15, 2020 7:09 AM
To: ZendTo Users <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] Authentication Error - The username or password was incorrect

Marlon,

The crucial bit in the log is the "locked-out user" bit.

ZendTo has a security feature in it to stop it being used as a method of brute-force attacking your accounts from outside.
If the same user has several failed logins in a row, that user is locked out for the next 24 hours by default.

If you can login as an admin user, one of the extra admin red buttons shows you the locked out users and lets you reset them.

Alternatively, you can unlock all locked users from the command line with
    /opt/zendto/bin/unlockuser -a

Cheers,
Jules.
On 14/07/2020 18:45, Marlon Deerr via ZendTo wrote:
Ok, so I think I finally (or almost finally) got my AD authentication settings correct.  I have installed the ldapsearch utility to confirm that I'm able to successful search the OU where my users reside, however when I attempt to log in with a valid user, ZendTo keeps erroring with:

Authentication Error
The username or password was incorrect

I checked the /var/log/zendto/zendto.log and it says the following:

"....Warning: authorization attempt for locked-out user <username1>
Then when I try logging in as another user, I see the following in the log

"...Warning: authorization failed for <username2>



I know that I have both username/password correct so I must be missing something. Anyone know what setting I may have applied incorrectly?





_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto: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<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200715/97fd4509/attachment.html>

From Massimo.Forni at turboden.it  Wed Jul 15 17:21:50 2020
From: Massimo.Forni at turboden.it (Massimo Forni)
Date: Wed, 15 Jul 2020 16:21:50 +0000
Subject: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5
In-Reply-To: <WM!ed9b9a7e13b37ba158f75e6dc724c6e43ece7bb563c7ca4231cc299d64904e7a58c98aabfe49e1027a51637af55c127e!@mx.jul.es>
References: <523fad9d-598e-431b-b360-f83820c34c74@Zend.To>
 <WM!ea5144e31d109651d446a3234f9a2df55952580128a90c59699ad78ef390f128761b2aadb4ed84842fcb972caf771de3!@mx.jul.es>
 <5f35954934444b8f9102c2f3f778df41@HSH-MAIL.HSH.local>
 <WM!a4056b4e53fd8767842192748718839db5964303022d7a675900fc6f313d5c98b7c3fa41d6628b8ac5362a4ec52ac230!@mx.jul.es>
 <WM!1e10ee5b2f33074605d93b006b6634f6a495089afd4778800865d14eac161c63c570f44690001c0593a93a3c41094c92!@mx.jul.es>
 <545143a62b6b446788df02fd59525fc3@HSH-MAIL.HSH.local>
 <WM!dd4809d7fb209ac6ca627d3e15507424e5bb0edb150b12fce127eaee4f7c722e2508b12b355b36c185b245c9c61c14b6!@mx.jul.es>
 <WM!ed9b9a7e13b37ba158f75e6dc724c6e43ece7bb563c7ca4231cc299d64904e7a58c98aabfe49e1027a51637af55c127e!@mx.jul.es>
 <e2607126ebcc438cb8f6cd17ebc8b5c8@Mailbox13.turboden.local>
Message-ID: <WM!0651285457d457b26b9fddcd728febce85d21fe71a7163e3a02f028fef3f4092fac3bc1d404130f72759d6d05cc0b8b5!@mx.jul.es>

You need to say N (keep) for the preferences and say Y (replace) to all the *.po files (language files)
After that just run the upgrade script /opt/zendto/bin/upgrade

From: ZendTo <zendto-bounces at zend.to> On Behalf Of Marlon Deerr via ZendTo
Sent: mercoled? 15 luglio 2020 16:17
To: 'ZendTo Users' <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5

Sorry Jules?.I totally misread the question. It will keep my current preferences.php if I hit enter. My bad!

From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Marlon Deerr via ZendTo
Sent: Wednesday, July 15, 2020 10:14 AM
To: 'ZendTo Users' <zendto at zend.to<mailto:zendto at zend.to>>
Cc: Marlon Deerr <MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>>
Subject: Re: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5

Hello Jules,

This would be my first ever update to a newer version.  It says that that default action is to keep your current version of preferences.php, but you can see that the default would be N if  just hit enter. Are we supposed to enter Y to keep our current preferences.php then?

[cid:image001.png at 01D65ACC.93DD4B30]

From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Jules via ZendTo
Sent: Wednesday, July 15, 2020 10:05 AM
To: ZendTo Users <zendto at zend.to<mailto:zendto at zend.to>>
Cc: Jules <Jules at Zend.To<mailto:Jules at Zend.To>>
Subject: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5

Hi all,

To follow up from the thread "Reminder email sent to wrong recipients", I have fixed that bug along with a few other more minor problems.

Anyone running version 6 should upgrade.

So I have just release 6.03-5, which you should be able to get with a quick
    yum update
or
    sudo apt update ; sudo apt upgrade
Then if you aren't already running version 6.03, run
    sudo /opt/zendto/bin/upgrade

The Change Log is this:

- Fixed bug where the wrong reminder emails were being sent to users.
- Fixed formatting error in plain-text emails about a new drop-off.
- Fixed bug where changing language immediately before/after doing SAML login could produce blank page.
- Fixed bug where "Decline" button in GDPR cookie-consent bar was not being translated.
- Updated Turkish and Brazilian Portuguese translations.

Let me know of any problems, questions or suggestions!

Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'Intelligence is quickness to apprehend as distinct from ability,

 which is capacity to act wisely on the thing apprehended.'

 - Alfred North Whitehead



www.Zend.To<https://urldefense.com/v3/__http:/www.Zend.To__;!!BYEqwblc0Q!msxyhs1Yi1-_HfXl9V6zoUc3VlDYp5BDRw9AhaUlFTusxB3yNe3LNDrpPEUTMOgVOUKazw$>

Twitter: @JulesFM

--

Massimo Forni
ICT Infrastructure Manager

Mobile: +393474110278

________________________________

Turboden S.p.A. I via Cernaia 10 I 25124 Brescia I Italy
t. +39 030 3552001 I f. +39 030 3552011
www.turboden.com<http://www.turboden.com>


Confidentiality notice: this message, together with its attachments, may contain strictly confidential and/or legally privileged information and it is destined solely to the intended addressee(s), who only may use it under his/their responsibility. Opinions, conclusions and other information contained in this message, that do not relate to the official business of this firm, shall be considered as not given or endorsed by it. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. Any use, disclosure, copying or distribution of the contents of this communication by a not-intended recipient or in violation of the purposes of this communication is strictly prohibited and may be unlawful.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200715/e7b1f04a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 23046 bytes
Desc: image001.png
URL: <http://jul.es/pipermail/zendto/attachments/20200715/e7b1f04a/attachment-0001.png>

From Jules at Zend.To  Wed Jul 15 17:35:01 2020
From: Jules at Zend.To (Jules)
Date: Wed, 15 Jul 2020 17:35:01 +0100
Subject: [ZendTo] Authentication Error - The username or password was
 incorrect
In-Reply-To: <WM!2cfe276c58174c00a9928bf2c34df7658608e338c2751e3ad3cc2719c793931fa3c0b41ef577f2b59fa5f655dab1d60c!@mx.jul.es>
References: <5bbb4fb4215246b0972b060f5c691d9b@HSH-MAIL.HSH.local>
 <WM!a36308db46adfd7479fd2ce4a18e69653cee550af1a292076bf1bab639989c97e35fe7975d56693ef9069451a9bd0778!@mx.jul.es>
 <e9b7b2e4-9981-91a5-bfc2-d8ac8c9bdbd5@Zend.To>
 <WM!8596658a4ac6c0f2f39484749734a6bdcd881d8ab1c4ca1fc11e871bde3d0494af7561bc5fddfd9a91bbe23fa9a1fea6!@mx.jul.es>
 <3fb2117013a6445babf526e96235aedd@HSH-MAIL.HSH.local>
 <WM!2cfe276c58174c00a9928bf2c34df7658608e338c2751e3ad3cc2719c793931fa3c0b41ef577f2b59fa5f655dab1d60c!@mx.jul.es>
Message-ID: <26751acd-8c1d-237b-8c41-c403ba7839e7@Zend.To>

Are you actually seeing the < and > characters?
You didn't actually type those into the /opt/zendto/bin/adduser command, 
did you?

Have a read of the AD troubleshooting steps on
 ??? zend.to/activedirectory

Do you know if you're running with a locally-signed certificate on your 
AD servers?

Assuming you have the hostname and port number (636 usually) of your? AD 
server, try
*openssl s_client -connect your-ad-server.company.com:636*

That will show you the initial SSL/TLS handshake involving all the 
certificates.
You'll need to Ctrl-C it at the end, but what it prints out should be 
very useful so you can see exactly what is using which certs.

Hope that helps,
Jules.

On 15/07/2020 16:50, Marlon Deerr wrote:
>
> OK, my user seems to be unlocked now but now I am getting the 
> following errors below. I must be missing something else in my setup:
>
> Warning: admin authorization failed for <username1>
>
> And for other users I still get the following error:
>
> Warning: authorization failed for <username2>
>
> Note: I believe I added <username1> as an admin.
>
>
> Marlon Deerr, Technology Manager
> 416-572-8795(direct) | MDeerr at hshlawyers.com 
> <mailto:MDeerr at hshlawyers.com>
> <https://www.hshlawyers.com>
> <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> 
> <https://twitter.com/hshlawyers> 
> <https://www.facebook.com/HSHPersonalInjuryLawyers/> 
> <https://www.youtube.com/user/hshlawyers> 	3500 - 20 Queen St. W., 
> Toronto, ON M5H 3R3
> Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com 
> <https://www.hshlawyers.com>
>
>
> This Howie Sacks & Henry e-mail is privileged, confidential and 
> subject to copyright. Any unauthorized use or disclosure is prohibited.
>
>
>
> *From:* Jules [mailto:Jules at Zend.To]
> *Sent:* Wednesday, July 15, 2020 7:09 AM
> *To:* ZendTo Users <zendto at zend.to>
> *Cc:* Marlon Deerr <MDeerr at hshlawyers.com>
> *Subject:* Re: [ZendTo] Authentication Error - The username or 
> password was incorrect
>
> Marlon,
>
> The crucial bit in the log is the "locked-out user" bit.
>
> ZendTo has a security feature in it to stop it being used as a method 
> of brute-force attacking your accounts from outside.
> If the same user has several failed logins in a row, that user is 
> locked out for the next 24 hours by default.
>
> If you can login as an admin user, one of the extra admin red buttons 
> shows you the locked out users and lets you reset them.
>
> Alternatively, you can unlock all locked users from the command line with
> ??? /opt/zendto/bin/unlockuser -a
>
> Cheers,
> Jules.
>
> On 14/07/2020 18:45, Marlon Deerr via ZendTo wrote:
>
>     Ok, so I think I finally (or almost finally) got my AD
>     authentication settings correct.? I have installed the ldapsearch
>     utility to confirm that I?m able to successful search the OU where
>     my users reside, however when I attempt to log in with a valid
>     user, ZendTo keeps erroring with:
>
>     Authentication Error
>
>     The username or password was incorrect
>
>     I checked the /var/log/zendto/zendto.log and it says the following:
>
>     ??.Warning: authorization attempt for locked-out user <username1>
>
>     Then when I try logging in as another user, I see the following in
>     the log
>
>     ??Warning: authorization failed for <username2>
>
>     I know that I have both username/password correct so I must be
>     missing something. Anyone know what setting I may have applied
>     incorrectly?
>
>
>
>     _______________________________________________
>
>     ZendTo mailing list
>
>     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>
>     http://jul.es/mailman/listinfo/zendto  <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  <http://www.Zend.To>
> Twitter: @JulesFM

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'There is silent poetry in the stillness of morning;
  in the calm, the cries & sighs of life sound like gentle music.'
  - @Astro_Wheels

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200715/a17e164a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagee40017.JPG
Type: image/jpeg
Size: 125353 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200715/a17e164a/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagec32181.JPG
Type: image/jpeg
Size: 7976 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200715/a17e164a/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imaged68129.JPG
Type: image/jpeg
Size: 7843 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200715/a17e164a/attachment-0007.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image72d27d.JPG
Type: image/jpeg
Size: 7268 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200715/a17e164a/attachment-0008.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image8ce258.JPG
Type: image/jpeg
Size: 7059 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200715/a17e164a/attachment-0009.jpe>

From ricky.boone at gmail.com  Thu Jul 16 23:23:11 2020
From: ricky.boone at gmail.com (Ricky Boone)
Date: Thu, 16 Jul 2020 18:23:11 -0400
Subject: [ZendTo] ANNOUNCE: Bug-fix release 6.03-5
In-Reply-To: <WM!ea5144e31d109651d446a3234f9a2df55952580128a90c59699ad78ef390f128761b2aadb4ed84842fcb972caf771de3!@mx.jul.es>
References: <523fad9d-598e-431b-b360-f83820c34c74@Zend.To>
 <WM!ea5144e31d109651d446a3234f9a2df55952580128a90c59699ad78ef390f128761b2aadb4ed84842fcb972caf771de3!@mx.jul.es>
 <CAHAhptXMwkQAHkPqJcYO6Kjxwgvrh=KOgm5VpBe0-33XcmCp4w@mail.gmail.com>
Message-ID: <WM!a07187fc324b8895c9bec88558a439099aea89dbc47225ab29c779ab2934062ad4a0b3d3a248f3eb44c45e51022939c8!@mx.jul.es>

Awesome, thanks for working on this, Jules!

On Wed, Jul 15, 2020 at 10:05 AM Jules via ZendTo <zendto at zend.to> wrote:

> Hi all,
>
> To follow up from the thread "Reminder email sent to wrong recipients", I
> have fixed that bug along with a few other more minor problems.
>
> Anyone running version 6 should upgrade.
>
> So I have just release 6.03-5, which you should be able to get with a quick
>     yum update
> or
>     sudo apt update ; sudo apt upgrade
> Then if you aren't already running version 6.03, run
>     sudo /opt/zendto/bin/upgrade
>
> The Change Log is this:
>
> - Fixed bug where the wrong reminder emails were being sent to users.
> - Fixed formatting error in plain-text emails about a new drop-off.
> - Fixed bug where changing language immediately before/after doing SAML
> login could produce blank page.
> - Fixed bug where "Decline" button in GDPR cookie-consent bar was not
> being translated.
> - Updated Turkish and Brazilian Portuguese translations.
>
> Let me know of any problems, questions or suggestions!
>
> Jules
>
> --
> Julian Field MEng CEng CITP MBCS MIEEE MACM
>
> 'Intelligence is quickness to apprehend as distinct from ability,
>  which is capacity to act wisely on the thing apprehended.'
>  - Alfred North Whitehead
> www.Zend.To
> Twitter: @JulesFM
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200716/5cda0f92/attachment.html>

From Jules at Zend.To  Fri Jul 17 16:59:30 2020
From: Jules at Zend.To (Jules)
Date: Fri, 17 Jul 2020 16:59:30 +0100
Subject: [ZendTo] =?utf-8?q?Potential_change_to_RPM_packaging_=E2=80=94_g?=
 =?utf-8?q?ood/bad_idea=3F?=
Message-ID: <79bcbb19-25f1-34f4-660c-5825859c2474@Zend.To>

Folks,

This only applies to those using the RPM/yum distribution of ZendTo.
It affects people running CentOS or RedHat, for starters.

It does not apply to people running ZendTo on Ubuntu or Debian, for example.

Currently, if you modify a *.tpl file (anything in 
/opt/zendto/templates) and then upgrade:
1. The new version goes in as *.tpl.rpmnew
2. The rpm command tells you this (but it tells you a lot of things very 
fast)
3. You have to go and fix up any customisations, so that the service 
works at all.

What I could change them to is this:
1. The new version goes in as *.tpl and the old modified one is renamed 
to *.tpl.rpmsave
2. The rpm command tells you as before
3. The service works first time, but you then need to re-apply your 
customisations.

Which approach is better?

It's going to be a very noticeable change for any site that regularly 
tweaks any of the *.tpl files.
But I suspect that is a small proportion of sites.

What do you think?

Is this change a good idea or a bad one?

Please let me know!

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'No more impressive warning can be given to those who would confine
  knowledge and rsearch to what is apparently useful, than the
  reflection that conic sections were studied for eighteen hundred
  years merely as an abstract science, without regard to any utility
  other than to satisfy the craving for knowledge on the part of
  mathematicians, and that then at the end of this long period of
  abstract study, they were found to be the necessary key with which
  to attain the knowledge of the most important laws of nature.'
  - Alfred North Whitehead

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200717/96d21b6b/attachment.html>

From ssilva at sgvwater.com  Fri Jul 17 17:05:32 2020
From: ssilva at sgvwater.com (Scott Silva)
Date: Fri, 17 Jul 2020 16:05:32 +0000
Subject: [ZendTo] 
 =?utf-8?q?Potential_change_to_RPM_packaging_=E2=80=94_g?=
 =?utf-8?q?ood/bad_idea=3F?=
In-Reply-To: <WM!624e0ef92e428c349d12870f77b9664929be46f83ecb810c26f7412cdbb899982be96c80f2f8bba82eead57facec23dc!@mx.jul.es>
References: <79bcbb19-25f1-34f4-660c-5825859c2474@Zend.To>
 <WM!624e0ef92e428c349d12870f77b9664929be46f83ecb810c26f7412cdbb899982be96c80f2f8bba82eead57facec23dc!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F42ED0C013@FONEXCH01.sgvwc.local>
Message-ID: <WM!82f6604dc5a945e99d28f15f007cbf296566a2670ae4a787881a372ffcb31695567421d08dd72fdb1d030845479fac47!@mx.jul.es>

Is there a way for your upgrade script to mention these files if it finds them?
Not necessarily fix them, but say they are there, and pause for acknowledgement to ?remind? people?


From: ZendTo <zendto-bounces at zend.to> On Behalf Of Jules via ZendTo
Sent: Friday, July 17, 2020 9:00 AM
To: ZendTo Users <zendto at zend.to>
Cc: Jules <Jules at Zend.To>
Subject: [ZendTo] Potential change to RPM packaging ? good/bad idea?

Folks,

This only applies to those using the RPM/yum distribution of ZendTo.
It affects people running CentOS or RedHat, for starters.

It does not apply to people running ZendTo on Ubuntu or Debian, for example.

Currently, if you modify a *.tpl file (anything in /opt/zendto/templates) and then upgrade:
1. The new version goes in as *.tpl.rpmnew
2. The rpm command tells you this (but it tells you a lot of things very fast)
3. You have to go and fix up any customisations, so that the service works at all.

What I could change them to is this:
1. The new version goes in as *.tpl and the old modified one is renamed to *.tpl.rpmsave
2. The rpm command tells you as before
3. The service works first time, but you then need to re-apply your customisations.

Which approach is better?

It's going to be a very noticeable change for any site that regularly tweaks any of the *.tpl files.
But I suspect that is a small proportion of sites.

What do you think?

Is this change a good idea or a bad one?

Please let me know!


Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'No more impressive warning can be given to those who would confine

 knowledge and rsearch to what is apparently useful, than the

 reflection that conic sections were studied for eighteen hundred

 years merely as an abstract science, without regard to any utility

 other than to satisfy the craving for knowledge on the part of

 mathematicians, and that then at the end of this long period of

 abstract study, they were found to be the necessary key with which

 to attain the knowledge of the most important laws of nature.'

 - Alfred North Whitehead



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200717/694a6391/attachment-0001.html>

From Jules at Zend.To  Fri Jul 17 17:41:15 2020
From: Jules at Zend.To (Jules)
Date: Fri, 17 Jul 2020 17:41:15 +0100
Subject: [ZendTo] 
 =?utf-8?q?Potential_change_to_RPM_packaging_=E2=80=94_g?=
 =?utf-8?q?ood/bad_idea=3F?=
In-Reply-To: <WM!82f6604dc5a945e99d28f15f007cbf296566a2670ae4a787881a372ffcb31695567421d08dd72fdb1d030845479fac47!@mx.jul.es>
References: <79bcbb19-25f1-34f4-660c-5825859c2474@Zend.To>
 <WM!624e0ef92e428c349d12870f77b9664929be46f83ecb810c26f7412cdbb899982be96c80f2f8bba82eead57facec23dc!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F42ED0C013@FONEXCH01.sgvwc.local>
 <WM!82f6604dc5a945e99d28f15f007cbf296566a2670ae4a787881a372ffcb31695567421d08dd72fdb1d030845479fac47!@mx.jul.es>
Message-ID: <7e5655d9-3090-09af-1a93-36122c215a6f@Zend.To>

Scott,

Yes, I could mention the presence of *.rpmnew and *.rpmsave files in 
that directory, no problem.
That would definitely be better than the current status.

Cheers,
Jules.

On 17/07/2020 17:05, Scott Silva via ZendTo wrote:
>
> Is there a way for your upgrade script to mention these files if it 
> finds them?
>
> Not necessarily fix them, but say they are there, and pause for 
> acknowledgement to ?remind? people?
>
> *From:*ZendTo <zendto-bounces at zend.to> *On Behalf Of *Jules via ZendTo
> *Sent:* Friday, July 17, 2020 9:00 AM
> *To:* ZendTo Users <zendto at zend.to>
> *Cc:* Jules <Jules at Zend.To>
> *Subject:* [ZendTo] Potential change to RPM packaging ? good/bad idea?
>
> Folks,
>
> This only applies to those using the RPM/yum distribution of ZendTo.
> It affects people running CentOS or RedHat, for starters.
>
> It does not apply to people running ZendTo on Ubuntu or Debian, for 
> example.
>
> Currently, if you modify a *.tpl file (anything in 
> /opt/zendto/templates) and then upgrade:
> 1. The new version goes in as *.tpl.rpmnew
> 2. The rpm command tells you this (but it tells you a lot of things 
> very fast)
> 3. You have to go and fix up any customisations, so that the service 
> works at all.
>
> What I could change them to is this:
> 1. The new version goes in as *.tpl and the old modified one is 
> renamed to *.tpl.rpmsave
> 2. The rpm command tells you as before
> 3. The service works first time, but you then need to re-apply your 
> customisations.
>
> Which approach is better?
>
> It's going to be a very noticeable change for any site that regularly 
> tweaks any of the *.tpl files.
> But I suspect that is a small proportion of sites.
>
> What do you think?
>
> Is this change a good idea or a bad one?
>
> Please let me know!
>
> Jules
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> 'No more impressive warning can be given to those who would confine
>   knowledge and rsearch to what is apparently useful, than the
>   reflection that conic sections were studied for eighteen hundred
>   years merely as an abstract science, without regard to any utility
>   other than to satisfy the craving for knowledge on the part of
>   mathematicians, and that then at the end of this long period of
>   abstract study, they were found to be the necessary key with which
>   to attain the knowledge of the most important laws of nature.'
>   - Alfred North Whitehead
> www.Zend.To  <http://www.Zend.To>
> Twitter: @JulesFM
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Learn from yesterday, live for today,
  look to tomorrow, rest this afternoon.' - Charles M Schulz

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200717/30b14722/attachment.html>

From Massimo.Forni at turboden.it  Fri Jul 17 18:03:01 2020
From: Massimo.Forni at turboden.it (Massimo Forni)
Date: Fri, 17 Jul 2020 17:03:01 +0000
Subject: [ZendTo] 
 =?utf-8?q?Potential_change_to_RPM_packaging_=E2=80=94_g?=
 =?utf-8?q?ood/bad_idea=3F?=
In-Reply-To: <WM!96ee5eca6016eec75bcb069460f25e3b24d6b158857af8bea969f24f37d11621cc54c6c4b9d26d380b44ff7a8ce6c2a7!@mx.jul.es>
References: <79bcbb19-25f1-34f4-660c-5825859c2474@Zend.To>,
 <WM!96ee5eca6016eec75bcb069460f25e3b24d6b158857af8bea969f24f37d11621cc54c6c4b9d26d380b44ff7a8ce6c2a7!@mx.jul.es>
 <AD7FBC45-1A7F-40CC-9122-6E13A1E043E9@turboden.it>
Message-ID: <WM!355e3d01bce60b3b2763ea1f8eff1d2c1e304efe095c8a13a9eea511a125cd51f1d511e4ec1f642370b26471d736cf18!@mx.jul.es>

+1 for me

Sent from my iPhone

On 17 Jul 2020, at 18:00, Jules via ZendTo <zendto at zend.to> wrote:

? Folks,

This only applies to those using the RPM/yum distribution of ZendTo.
It affects people running CentOS or RedHat, for starters.

It does not apply to people running ZendTo on Ubuntu or Debian, for example.

Currently, if you modify a *.tpl file (anything in /opt/zendto/templates) and then upgrade:
1. The new version goes in as *.tpl.rpmnew
2. The rpm command tells you this (but it tells you a lot of things very fast)
3. You have to go and fix up any customisations, so that the service works at all.

What I could change them to is this:
1. The new version goes in as *.tpl and the old modified one is renamed to *.tpl.rpmsave
2. The rpm command tells you as before
3. The service works first time, but you then need to re-apply your customisations.

Which approach is better?

It's going to be a very noticeable change for any site that regularly tweaks any of the *.tpl files.
But I suspect that is a small proportion of sites.

What do you think?

Is this change a good idea or a bad one?

Please let me know!

Jules

--
Julian Field MEng CEng CITP MBCS MIEEE MACM

'No more impressive warning can be given to those who would confine
 knowledge and rsearch to what is apparently useful, than the
 reflection that conic sections were studied for eighteen hundred
 years merely as an abstract science, without regard to any utility
 other than to satisfy the craving for knowledge on the part of
 mathematicians, and that then at the end of this long period of
 abstract study, they were found to be the necessary key with which
 to attain the knowledge of the most important laws of nature.'
 - Alfred North Whitehead

www.Zend.To<https://urldefense.com/v3/__http://www.Zend.To__;!!BYEqwblc0Q!lIA5Y0a4kkunwWMNiBfpobadlZZrLWjh0MYJICfsR-_5w1YdoD1qqxnmfLrIKCBdSPMNsA$>
Twitter: @JulesFM


_______________________________________________
ZendTo mailing list
ZendTo at zend.to
https://urldefense.com/v3/__http://jul.es/mailman/listinfo/zendto__;!!BYEqwblc0Q!lIA5Y0a4kkunwWMNiBfpobadlZZrLWjh0MYJICfsR-_5w1YdoD1qqxnmfLrIKCBhnCP7xA$

--

Massimo Forni
ICT Infrastructure Manager

Mobile: +393474110278

________________________________

Turboden S.p.A. I via Cernaia 10 I 25124 Brescia I Italy
t. +39 030 3552001 I f. +39 030 3552011
www.turboden.com<http://www.turboden.com>


Confidentiality notice: this message, together with its attachments, may contain strictly confidential and/or legally privileged information and it is destined solely to the intended addressee(s), who only may use it under his/their responsibility. Opinions, conclusions and other information contained in this message, that do not relate to the official business of this firm, shall be considered as not given or endorsed by it. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. Any use, disclosure, copying or distribution of the contents of this communication by a not-intended recipient or in violation of the purposes of this communication is strictly prohibited and may be unlawful.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200717/5c046064/attachment.html>

From klou at themusiclink.net  Fri Jul 17 19:32:55 2020
From: klou at themusiclink.net (Kris Lou)
Date: Fri, 17 Jul 2020 11:32:55 -0700
Subject: [ZendTo] 
	=?utf-8?q?Potential_change_to_RPM_packaging_=E2=80=94_g?=
	=?utf-8?q?ood/bad_idea=3F?=
In-Reply-To: <WM!ccf4f9e1f117f41f80ee6f30afd3476f8a6ce0fc8629a344c85d3e967c7fd14d59f4d0ffde64002f0bcd00893a0c8a8a!@mx.jul.es>
References: <79bcbb19-25f1-34f4-660c-5825859c2474@Zend.To>
 <AD7FBC45-1A7F-40CC-9122-6E13A1E043E9@turboden.it>
 <WM!355e3d01bce60b3b2763ea1f8eff1d2c1e304efe095c8a13a9eea511a125cd51f1d511e4ec1f642370b26471d736cf18!@mx.jul.es>
 <WM!96ee5eca6016eec75bcb069460f25e3b24d6b158857af8bea969f24f37d11621cc54c6c4b9d26d380b44ff7a8ce6c2a7!@mx.jul.es>
 <WM!ccf4f9e1f117f41f80ee6f30afd3476f8a6ce0fc8629a344c85d3e967c7fd14d59f4d0ffde64002f0bcd00893a0c8a8a!@mx.jul.es>
 <CAGyTNKEZC1bxRdkxbsoTf-uKkfz19C31aK=J52Fwc10HJrp9sg@mail.gmail.com>
Message-ID: <WM!2315cd058913440f26053c3b16bc7ae6209a0b0f86a825bf39c7e6db51b2cdbfcb9f4e05833c4926d18ce19b4de3b41f!@mx.jul.es>

RE: rpmnew vs rpmsave, I think it should be consistent with the
preferences.php.save (or however it's currently done).

Then the "after-upgrade adjustment workflow" for us is the same.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200717/0f17ef37/attachment-0001.html>

From Jules at Zend.To  Fri Jul 17 19:42:03 2020
From: Jules at Zend.To (Jules)
Date: Fri, 17 Jul 2020 19:42:03 +0100
Subject: [ZendTo] 
 =?utf-8?q?Potential_change_to_RPM_packaging_=E2=80=94_g?=
 =?utf-8?q?ood/bad_idea=3F?=
In-Reply-To: <WM!2315cd058913440f26053c3b16bc7ae6209a0b0f86a825bf39c7e6db51b2cdbfcb9f4e05833c4926d18ce19b4de3b41f!@mx.jul.es>
References: <79bcbb19-25f1-34f4-660c-5825859c2474@Zend.To>
 <AD7FBC45-1A7F-40CC-9122-6E13A1E043E9@turboden.it>
 <WM!355e3d01bce60b3b2763ea1f8eff1d2c1e304efe095c8a13a9eea511a125cd51f1d511e4ec1f642370b26471d736cf18!@mx.jul.es>
 <WM!96ee5eca6016eec75bcb069460f25e3b24d6b158857af8bea969f24f37d11621cc54c6c4b9d26d380b44ff7a8ce6c2a7!@mx.jul.es>
 <WM!ccf4f9e1f117f41f80ee6f30afd3476f8a6ce0fc8629a344c85d3e967c7fd14d59f4d0ffde64002f0bcd00893a0c8a8a!@mx.jul.es>
 <CAGyTNKEZC1bxRdkxbsoTf-uKkfz19C31aK=J52Fwc10HJrp9sg@mail.gmail.com>
 <WM!2315cd058913440f26053c3b16bc7ae6209a0b0f86a825bf39c7e6db51b2cdbfcb9f4e05833c4926d18ce19b4de3b41f!@mx.jul.es>
Message-ID: <354fda04-a091-bb7c-3b2f-a6faa6583318@Zend.To>

So that's a vote for "leave as is", as you should get a 
preferences.php.rpmnew at the moment.

On 17/07/2020 19:32, Kris Lou via ZendTo wrote:
> RE: rpmnew vs rpmsave, I think?it should be consistent with the 
> preferences.php.save (or however it's currently done).
>
> Then the "after-upgrade adjustment workflow" for us is the same.
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

The current UK shipping forecast:
Northwest Fair Isle, Southeast Faeroes: Southwesterly 5 to 7. Rough or very
rough, becoming rough. Squally showers. Moderate or good.

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200717/fa0b85a6/attachment.html>

From klou at themusiclink.net  Fri Jul 17 20:42:31 2020
From: klou at themusiclink.net (Kris Lou)
Date: Fri, 17 Jul 2020 12:42:31 -0700
Subject: [ZendTo] 
	=?utf-8?q?Potential_change_to_RPM_packaging_=E2=80=94_g?=
	=?utf-8?q?ood/bad_idea=3F?=
In-Reply-To: <WM!8e3a3b0cf4d79a2014e222c120f380b9a53305645f73d0db80020bc930a13aa194110fc8ec301b789d2e577dcbb454de!@mx.jul.es>
References: <79bcbb19-25f1-34f4-660c-5825859c2474@Zend.To>
 <AD7FBC45-1A7F-40CC-9122-6E13A1E043E9@turboden.it>
 <WM!355e3d01bce60b3b2763ea1f8eff1d2c1e304efe095c8a13a9eea511a125cd51f1d511e4ec1f642370b26471d736cf18!@mx.jul.es>
 <WM!96ee5eca6016eec75bcb069460f25e3b24d6b158857af8bea969f24f37d11621cc54c6c4b9d26d380b44ff7a8ce6c2a7!@mx.jul.es>
 <WM!ccf4f9e1f117f41f80ee6f30afd3476f8a6ce0fc8629a344c85d3e967c7fd14d59f4d0ffde64002f0bcd00893a0c8a8a!@mx.jul.es>
 <CAGyTNKEZC1bxRdkxbsoTf-uKkfz19C31aK=J52Fwc10HJrp9sg@mail.gmail.com>
 <354fda04-a091-bb7c-3b2f-a6faa6583318@Zend.To>
 <WM!2315cd058913440f26053c3b16bc7ae6209a0b0f86a825bf39c7e6db51b2cdbfcb9f4e05833c4926d18ce19b4de3b41f!@mx.jul.es>
 <WM!8e3a3b0cf4d79a2014e222c120f380b9a53305645f73d0db80020bc930a13aa194110fc8ec301b789d2e577dcbb454de!@mx.jul.es>
 <CAGyTNKHeWn2=0v-MEDX+KJETfxbF5GXMQTXKEL39caC3fcWieQ@mail.gmail.com>
Message-ID: <WM!c0d8adcfec1c0aae89db01e16dea41324c7791b014dfa95feac860841b848fa186422b92ad65a0b8ed3ab5ee8d12a710!@mx.jul.es>

I should've posted my disclaimer, though:  I don't change *.tpl for my
install, so the changes are not likely to affect me.  So let that affect
the weight of the opinion ...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200717/16aaa12d/attachment.html>

From MDeerr at hshlawyers.com  Fri Jul 17 22:54:09 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Fri, 17 Jul 2020 21:54:09 +0000
Subject: [ZendTo] Authentication Error - The username or password was
 incorrect
In-Reply-To: <WM!44012c2d67ca880ecf21dc5ecb37cea58f4774b542c16868afcbef4554069d936047ef6422db5fec4bbfb53961c0aa4c!@mx.jul.es>
References: <5bbb4fb4215246b0972b060f5c691d9b@HSH-MAIL.HSH.local>
 <WM!a36308db46adfd7479fd2ce4a18e69653cee550af1a292076bf1bab639989c97e35fe7975d56693ef9069451a9bd0778!@mx.jul.es>
 <e9b7b2e4-9981-91a5-bfc2-d8ac8c9bdbd5@Zend.To>
 <WM!8596658a4ac6c0f2f39484749734a6bdcd881d8ab1c4ca1fc11e871bde3d0494af7561bc5fddfd9a91bbe23fa9a1fea6!@mx.jul.es>
 <3fb2117013a6445babf526e96235aedd@HSH-MAIL.HSH.local>
 <WM!2cfe276c58174c00a9928bf2c34df7658608e338c2751e3ad3cc2719c793931fa3c0b41ef577f2b59fa5f655dab1d60c!@mx.jul.es>
 <26751acd-8c1d-237b-8c41-c403ba7839e7@Zend.To>
 <WM!44012c2d67ca880ecf21dc5ecb37cea58f4774b542c16868afcbef4554069d936047ef6422db5fec4bbfb53961c0aa4c!@mx.jul.es>
 <9db878bed4784c298a38e840516aa067@HSH-MAIL.HSH.local>
Message-ID: <WM!a6c2f730ffd9cc7d9cd6527763ebcb030ed8f57e945097f7cb30ade3ef5c8947d82e4a7183712d5cde6e0c875fe12bd5!@mx.jul.es>

Jules,

No, I didn?t type in < and > characters. I only did that to not show real usernames on my end.  So to be clear, no I did not type in those characters as part of the username when using the /opt/zendto/bin/adduser command. As for certificates, I?m not sure as our DNS server is actually managed by our MSP. With that said, when I do run the openssl command, I get the below output.

As for the log file at /var/log/zendto/zendto.log, if it says Warning: authorization failed for username, does that mean it wasn?t able to read from our AD Server. Not sure how to interpret that because before I ran the upgrade command after applying the latest patch, it seemed as though it was able to read from AD. Now I?m not sure what?s going on.


Output for openssl s_client -connect your-ad-server.company.com:636

CONNECTED(00000003)
write:errno=104
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 283 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)


From: Jules [mailto:Jules at Zend.To]
Sent: Wednesday, July 15, 2020 12:35 PM
To: Marlon Deerr <MDeerr at hshlawyers.com>; ZendTo Users <zendto at zend.to>
Subject: Re: [ZendTo] Authentication Error - The username or password was incorrect

Are you actually seeing the < and > characters?
You didn't actually type those into the /opt/zendto/bin/adduser command, did you?

Have a read of the AD troubleshooting steps on
    zend.to/activedirectory

Do you know if you're running with a locally-signed certificate on your AD servers?

Assuming you have the hostname and port number (636 usually) of your  AD server, try
openssl s_client -connect your-ad-server.company.com:636

That will show you the initial SSL/TLS handshake involving all the certificates.
You'll need to Ctrl-C it at the end, but what it prints out should be very useful so you can see exactly what is using which certs.

Hope that helps,
Jules.
On 15/07/2020 16:50, Marlon Deerr wrote:
OK, my user seems to be unlocked now but now I am getting the following errors below. I must be missing something else in my setup:

Warning: admin authorization failed for <username1>

And for other users I still get the following error:

Warning: authorization failed for <username2>


Note: I believe I added <username1> as an admin.



Marlon Deerr, Technology Manager
416-572-8795 (direct) | MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>
[cid:image002.jpg at 01D65C5C.D501A610]<https://www.hshlawyers.com>
[cid:image004.jpg at 01D65C5C.D501A610]<https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> [cid:image006.jpg at 01D65C5C.D501A610] <https://twitter.com/hshlawyers>  [cid:image008.jpg at 01D65C5C.D501A610] <https://www.facebook.com/HSHPersonalInjuryLawyers/>  [cid:image010.jpg at 01D65C5C.D501A610] <https://www.youtube.com/user/hshlawyers>

3500 - 20 Queen St. W., Toronto, ON M5H 3R3
Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com<https://www.hshlawyers.com>



This Howie Sacks & Henry e-mail is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited.



From: Jules [mailto:Jules at Zend.To]
Sent: Wednesday, July 15, 2020 7:09 AM
To: ZendTo Users <zendto at zend.to><mailto:zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com><mailto:MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] Authentication Error - The username or password was incorrect

Marlon,

The crucial bit in the log is the "locked-out user" bit.

ZendTo has a security feature in it to stop it being used as a method of brute-force attacking your accounts from outside.
If the same user has several failed logins in a row, that user is locked out for the next 24 hours by default.

If you can login as an admin user, one of the extra admin red buttons shows you the locked out users and lets you reset them.

Alternatively, you can unlock all locked users from the command line with
    /opt/zendto/bin/unlockuser -a

Cheers,
Jules.
On 14/07/2020 18:45, Marlon Deerr via ZendTo wrote:
Ok, so I think I finally (or almost finally) got my AD authentication settings correct.  I have installed the ldapsearch utility to confirm that I?m able to successful search the OU where my users reside, however when I attempt to log in with a valid user, ZendTo keeps erroring with:

Authentication Error
The username or password was incorrect

I checked the /var/log/zendto/zendto.log and it says the following:

??.Warning: authorization attempt for locked-out user <username1>
Then when I try logging in as another user, I see the following in the log

??Warning: authorization failed for <username2>



I know that I have both username/password correct so I must be missing something. Anyone know what setting I may have applied incorrectly?






_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto: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<http://www.Zend.To>

Twitter: @JulesFM



Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'There is silent poetry in the stillness of morning;

 in the calm, the cries & sighs of life sound like gentle music.'

 - @Astro_Wheels



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200717/c63546e3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 12435 bytes
Desc: image002.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200717/c63546e3/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 777 bytes
Desc: image004.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200717/c63546e3/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 768 bytes
Desc: image006.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200717/c63546e3/attachment-0007.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 756 bytes
Desc: image008.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200717/c63546e3/attachment-0008.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.jpg
Type: image/jpeg
Size: 752 bytes
Desc: image010.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200717/c63546e3/attachment-0009.jpg>

From john.thurston at alaska.gov  Tue Jul 21 00:00:02 2020
From: john.thurston at alaska.gov (John Thurston)
Date: Mon, 20 Jul 2020 15:00:02 -0800
Subject: [ZendTo] upgrade script and LDAP authentication values
References: <272118d8-0f0b-cb98-4c0e-4dd0d2ac50b4@alaska.gov>
Message-ID: <WM!ac996c1ade6bc34b86bb4b56b5cd173031fb18091de99250f657c0b73fac60ef859ae3d68b3d9dac684cf8cf5bf49efc!@mx.jul.es>

Is there some way for me to designate some values in preferences.php as 
"Just ignore me, please. Don't try to correct this." ?

With each update, the upgrade script detects my commented out values and 
does me the service of re-enabling them and supplying default values. I 
then have to go diff the files, confirm nothing has actually changed, 
and re-comment the attributes I don't want.

 >   //'authLDAPStartTLS'      => false,
 >   //'authLDAPBindDn'        => 'o=MyOrganization,uid=MyUser',
 >   //'authLDAPBindPass'      => 'SecretPassword',
 >   //'authLDAPOrganization'  => 'My Organization',
 >   //'authLDAPUsernameAttr'  => 'uid',
 >   //'authLDAPEmailAttr'     => 'mail',

I tried setting each of these to null strings, hoping that might trigger 
the code to ignore the values and also let the upgrade script leave them 
unchanged. Bzzzt. I couldn't authenticate.

I understand the difficulty in trying to detect what a customer is 
trying to do, and how to distinguish "new values" from "intentionally 
absent values". It is frustrating, though, to have to repeat the same 
manual steps, potentially missing something, with every update.

Maybe there could be a magic string to denote a line not just as a 
comment but as a "leave me as a comment" line.
Maybe triple-slash
Maybe //!/

Or is there already some way to do this that I haven't figured out?


-- 
--
Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska


From john.thurston at alaska.gov  Tue Jul 21 00:59:20 2020
From: john.thurston at alaska.gov (John Thurston)
Date: Mon, 20 Jul 2020 15:59:20 -0800
Subject: [ZendTo] Feature request re: editable subject line
References: <f8875e32-4faa-ac51-196a-6f6f7deaad26@alaska.gov>
Message-ID: <WM!0b4f1c4726b94216cf760675865fe59c90e4d0ac264a8f797b70223878c5eab682d6a0aa8f06fc1619536101d3fe78c0!@mx.jul.es>

6.0.3-1 brought us the feature:
- Users can now edit the Subject line of a new drop-off.

The editable box is available to unauthenticated users, though their 
input appears to be quietly ignored. Can we get that box marked 
un-editable for unauthenticated users so they don't think they can 
change the contents?

(I don't want unauthenticated users to be able to send arbitrary subject 
lines. I just don't want them to think they can, and then report it to 
me as a defect when their modified text doesn't appear.)


--
Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska


From Jules at Zend.To  Tue Jul 21 09:43:59 2020
From: Jules at Zend.To (Jules)
Date: Tue, 21 Jul 2020 09:43:59 +0100
Subject: [ZendTo] Feature request re: editable subject line
In-Reply-To: <WM!0b4f1c4726b94216cf760675865fe59c90e4d0ac264a8f797b70223878c5eab682d6a0aa8f06fc1619536101d3fe78c0!@mx.jul.es>
References: <f8875e32-4faa-ac51-196a-6f6f7deaad26@alaska.gov>
 <WM!0b4f1c4726b94216cf760675865fe59c90e4d0ac264a8f797b70223878c5eab682d6a0aa8f06fc1619536101d3fe78c0!@mx.jul.es>
Message-ID: <64d733b7-45dc-7cad-6bfa-aa12eca93c53@Zend.To>

John,

Well spotted, thank you.
It is now readonly unless you are logged in.
This change will be in the next release.

Cheers,
Jules.

On 21/07/2020 00:59, John Thurston via ZendTo wrote:
> 6.0.3-1 brought us the feature:
> - Users can now edit the Subject line of a new drop-off.
>
> The editable box is available to unauthenticated users, though their 
> input appears to be quietly ignored. Can we get that box marked 
> un-editable for unauthenticated users so they don't think they can 
> change the contents?
>
> (I don't want unauthenticated users to be able to send arbitrary 
> subject lines. I just don't want them to think they can, and then 
> report it to me as a defect when their modified text doesn't appear.)
>
>
> -- 
> Do things because you should, not just because you can.
>
> John Thurston??? 907-465-8591
> John.Thurston at alaska.gov
> Department of Administration
> State of Alaska
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

The current UK shipping forecast:
Shannon: Variable 3 at first in southeast, otherwise southwesterly 4 or 5,
occasionally 6 later. Moderate. Showers, rain later. Good, occasionally poor
later.

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200721/e23c1a46/attachment.html>

From MDeerr at hshlawyers.com  Tue Jul 21 13:45:36 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Tue, 21 Jul 2020 12:45:36 +0000
Subject: [ZendTo] Failed to unlock user $user as did not match
 usernameRegexp from preferences.php
References: <330ad221e5f345b3a36e5d792125630c@HSH-MAIL.HSH.local>
Message-ID: <WM!e77d92ba1db2d64e2566bde12aca80974b57b4cd5c53b32587b36194123f9181746e3a5a97665a8745fb8d589d9a7c6e!@mx.jul.es>

Hi Jules,

I was testing ZendTo. I wanted to see what the log files will report when a user is locked out after 10 unsuccessful login attempts. I noticed that the log file (I think) is incorrectly reporting that a user was not unlocked after administratively unlocking the account, when in fact the user was successfully unlocked. Here are the steps I performed.


1.       Purposely attempted to log in as a user with incorrect password 10 times

2.       Logged in as an admin user and examined the System Logs

3.       System Log file successfully identified this locked user

4.       Clicked on "Unlock User" from the main screen and selected the user to unlock and unlocked her

5.       Examined the System Logs again, but this time it said "Failed to unlock user $user as did not match usernameRegexp from preferences.php"

6.       Logged out as the administrator user

7.       Tried logged in as this "supposedly" locked user BUT the login was successful.


Does this mean that the System Log file is incorrectly reporting that the user was not unlocked, when in fact the user was unlocked?

ALSO: Feature Request (if possible)

When a user is approaching the maximum allowed failed login attempts can you include a message that


1.       Warns the user that you have x more attempts before you get locked out (where x is a number)

2.       After the user has failed to login after 10 attempts, instead of just saying "Authentication Error. The username or password was incorrect", can it not say something like "Authentication Error. You have attempted more than the allowed failed attempts to log in. Your account therefore has been locked. Please contact your administrator to have it unlocked"

While testing this feature above, I found that I was not keeping track of how many times I made a failed login and must have tried over and over again waiting for a message to let me now that I was locked out.  I think having such a message will help reduce IT Tickets from staff wondering why they can't log in. They may not even know they have been locked out.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200721/a831b394/attachment-0001.html>

From Jules at Zend.To  Tue Jul 21 14:43:04 2020
From: Jules at Zend.To (Jules)
Date: Tue, 21 Jul 2020 14:43:04 +0100
Subject: [ZendTo] Failed to unlock user $user as did not match
 usernameRegexp from preferences.php
In-Reply-To: <WM!e77d92ba1db2d64e2566bde12aca80974b57b4cd5c53b32587b36194123f9181746e3a5a97665a8745fb8d589d9a7c6e!@mx.jul.es>
References: <330ad221e5f345b3a36e5d792125630c@HSH-MAIL.HSH.local>
 <WM!e77d92ba1db2d64e2566bde12aca80974b57b4cd5c53b32587b36194123f9181746e3a5a97665a8745fb8d589d9a7c6e!@mx.jul.es>
Message-ID: <3ca20383-63b3-a467-bf24-e23ffe731f7f@Zend.To>

Marlon,

You are doing a thorough job of this, thank you!

I have fixed the bug(s) you described. It now behaves exactly as 
expected, including the logging. This will be in the next release.

As for the feature request, the current behaviour is by design.
Someone nasty (a "bad actor" in the jargon) is using your ZendTo site to 
brute-force break your password.
They keep trying different passwords, but always get the same simple 
"incorrect" response.
They don't know ZendTo very well, and don't know your configuration 
settings at all.
As a result, they can't tell if or when they should give up trying to 
break your username/password, and try some other username instead.

As soon as you display *anything* different, the attacker knows the 
lock-out limit has been reached and so they should abandon their current 
attempt and try another one.

So you *never* give away any hints as to why the login attempt failed, 
beyond a simple fixed error message.

It logs it in the ZendTo log (/var/log/zendto/zendto.log is the file 
that the "System Log" button shows you the end of), so you can check there.

Cheers,
Jules.

P.S. The "start" and "expiry" date/time selectors on the "Request a 
drop-off" form are nearly there. I just want to tidy up that page design 
layout, it's a bit of a mess and I would prefer it to use a grid or two 
and a flex box like the "new drop-off" form now does.

On 21/07/2020 13:45, Marlon Deerr via ZendTo wrote:
>
> Hi Jules,
>
> I was testing ZendTo. I wanted to see what the log files will report 
> when a user is locked out after 10 unsuccessful login attempts. I 
> noticed that the log file (I think) is incorrectly reporting that a 
> user was not unlocked after administratively unlocking the account, 
> when in fact the user was successfully unlocked. Here are the steps I 
> performed.
>
> 1.Purposely attempted to log in as a user with incorrect password 10 times
>
> 2.Logged in as an admin user and examined the System Logs
>
> 3.System Log file successfully identified this locked user
>
> 4.Clicked on ?Unlock User? from the main screen and selected the user 
> to unlock and unlocked her
>
> 5.Examined the System Logs again, but this time it said ?*Failed to 
> unlock user $user as did not match usernameRegexp from preferences.php*?
>
> 6.Logged out as the administrator user
>
> 7.Tried logged in as this ?supposedly? locked user *BUT* the login was 
> successful.
>
> Does this mean that the System Log file is incorrectly reporting that 
> the user was not unlocked, when in fact the user was unlocked?
>
> *ALSO:*Feature Request (if possible)
>
> When a user is approaching the maximum allowed failed login attempts 
> can you include a message that
>
> 1.Warns the user that you have x more attempts before you get locked 
> out (where x is a number)
>
> 2.After the user has failed to login after 10 attempts, instead of 
> just saying ?Authentication Error. The username or password was 
> incorrect?, can it not say something like ?Authentication Error. You 
> have attempted more than the allowed failed attempts to log in. Your 
> account therefore has been locked. Please contact your administrator 
> to have it unlocked?
>
> While testing this feature above, I found that I was not keeping track 
> of how many times I made a failed login and must have tried over and 
> over again waiting for a message to let me now that I was locked out. 
> ?I think having such a message will help reduce IT Tickets from staff 
> wondering why they can?t log in. They may not even know they have been 
> locked out.
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

The current UK shipping forecast:
Trafalgar: Cyclonic 6 to gale 8 at first in southeast, otherwise northerly 5
to 7, becoming variable 3 or 4 in southeast. Moderate or rough, occasionally
very rough. Thundery showers. Good, occasionally poor.

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200721/4ce11b8e/attachment.html>

From Jules at Zend.To  Tue Jul 21 14:47:45 2020
From: Jules at Zend.To (Jules)
Date: Tue, 21 Jul 2020 14:47:45 +0100
Subject: [ZendTo] Predefined Drop Offs
In-Reply-To: <WM!d0ad96999c79c93158e02dce71309d35cb34eafda26939cbdc949f37429c39a68f5373a8019fe0ff02c95cc61d3c4356!@mx.jul.es>
References: <CAKE9jaZw4eZ4JsR7gQVQna032t6c5bOJ=oV7gvAYE=9RJwp2Ew@mail.gmail.com>
 <09b6725b-f9a5-d072-e35f-70417d903046@Zend.To>
 <WM!456ff6fe50ae796f1142d9f20c87847d6b2cc0cf898db081c2f24308f181b1e54cc95fde0c7fa91397fb4f7f1311f04b!@mx.jul.es>
 <WM!63417b4327016709a5da7879eade76ad0bdf6be5eda6485bad02331d5fecdf3538af0d4dcceefe1797bfcd5ed63d4f92!@mx.jul.es>
 <CAFwmc2AZYLXfsNitGiV1=P+Ystfamdy74JGzfcT_mRczdjxRhQ@mail.gmail.com>
 <WM!d0ad96999c79c93158e02dce71309d35cb34eafda26939cbdc949f37429c39a68f5373a8019fe0ff02c95cc61d3c4356!@mx.jul.es>
Message-ID: <f58e5479-6172-b7d3-107b-5d15fe5c57cf@Zend.To>

Gregg, Luigi,

Your start and expiry date/time pickers on the "request a drop-off" page 
are nearly there.
I want to re-arrange the page a bit first, and improve the HTML in it so 
I'm using grids and flex boxes like I now do in the "new drop-off" form.

I'll release a beta once I think I've got it all right.

Cheers,
Jules.

On 12/07/2020 14:29, Luigi Capriotti wrote:
> Hi Jules,
>
> >There would also need to be Start and End Date fields, which would 
> define the period the PDO will be active for.
> this is not 100% feasible right now, isn't it.
> Acknowledging the?start date is not easily implemented with the 
> current backend library, I would envisage the availability of an 
> "advanced" PDO setup option where the end of the drop-off validity can 
> be set based on calendar/time pickers. The specified timestamp would 
> be used to calculate the validity of the drop-off in minutes.
>
> Luigi
>
> On Wed, Jul 8, 2020 at 7:55 PM Jules via ZendTo <zendto at zend.to 
> <mailto:zendto at zend.to>> wrote:
>
>     Gregg,
>
>     You can basically do all of this now.
>
>     Your "Predefined Drop Off(PDO)" is what ZendTo calls a "request
>     for a drop-off". There is a button on the main menu to do exactly
>     this.
>     You can send these to multiple recipients by putting multiple
>     email addresses in the "Request a drop-off" form, just separate
>     them with commas or spaces.
>
>     The rest of it you can do with ZendTo's automation feature, where
>     you can create a "request for a drop-off" from the command-line,
>     and hence from a script. You would need to write something to tie
>     that in to your existing coursework management system, but the
>     scripts that drive ZendTo automatically are actually nothing more
>     than a long "curl" command to do an HTTP POST operation that
>     supplies all the information in 1 hit.
>
>     The automation stuff is documented here
>     zend.to/automation <http://zend.to/automation>
>     and there is a script called "autorequest" which automates the
>     "request a drop-off" process.
>
>     Any more questions, problems, or any other way I can help, please
>     do no hesitate to get in touch.
>
>     I work for a University myself, and have written coursework
>     submission systems before. A few of our academics use our instance
>     of ZendTo to get coursework submissions from students, especially
>     when they are large submissions like videos of interviews.
>
>     Hope that helps,
>     Jules.
>
>     On 08/07/2020 18:08, Gregg Douglas via ZendTo wrote:
>>
>>     Hey Jules,
>>
>>
>>     I hope you are keeping safe and healthy.
>>
>>
>>     I would like to bounce an idea with you?
>>
>>     Take a Lecturer or Tender Officer, they need to request students
>>     to submit assignments or suppliers to submit tenders.
>>
>>     This person (Lecturer or Tender Officer) would then access ZendTO
>>     and create a ?Predefined Drop Off(PDO)?. In this PDO, one would
>>     preselect or predefine all the fields and options. The Subject,
>>     would also be predefined, but would be used as a field to group
>>     the PDOs. So, for a Lecturer they would use the Subject to define
>>     the name of the assignment that the students must submit. A
>>     Tender Officer would use the Subject to define the Tender
>>     Reference. The Short Note Field could be left as a free text
>>     block, allowing the Student or Supplier to include a note. There
>>     would also need to be Start and End Date fields, which would
>>     define the period the PDO will be active for.
>>
>>     Then, there would need to be an ?Alternative? Interface for
>>     ZendTO. In this ?Alternative? Interface a student or supplier
>>     could select the relevant active Assignment or Tender form a list
>>     of all active ones. On selecting the required item from the list,
>>     the normal process of ?Requesting a Drop Off? would follow, like
>>     confirming the email address of the student or supplier via the
>>     verification email. The link in this email would open the PDO
>>     with all the predefined fields and the student or supplier can
>>     then upload and submit the information.
>>
>>
>>     It was a thought I have for a future feature.
>>
>>
>>     Regards
>>
>>     Gregg
>>
>>
>>
>>     _______________________________________________
>>     ZendTo mailing list
>>     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>>     http://jul.es/mailman/listinfo/zendto  <http://jul.es/mailman/listinfo/zendto>
>
>     Jules
>
>     -- 
>     Julian Field MEng CEng CITP MBCS MIEEE MACM
>
>     'Probability factor of one to one. We have normality. I repeat, we
>       have normality. Anything you still can't cope with is therefore
>       your own problem.' - Trillian, The Hitch Hikers Guide to the Galaxy
>
>     www.Zend.To  <http://www.Zend.To>
>     Twitter: @JulesFM
>
>     _______________________________________________
>     ZendTo mailing list
>     ZendTo at zend.to <mailto:ZendTo at zend.to>
>     http://jul.es/mailman/listinfo/zendto
>     <http://jul.es/mailman/listinfo/zendto>
>

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

The current UK shipping forecast:
Trafalgar: Cyclonic 6 to gale 8 at first in southeast, otherwise northerly 5
to 7, becoming variable 3 or 4 in southeast. Moderate or rough, occasionally
very rough. Thundery showers. Good, occasionally poor.

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200721/9f1c0d29/attachment-0001.html>

From MDeerr at hshlawyers.com  Tue Jul 21 14:54:24 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Tue, 21 Jul 2020 13:54:24 +0000
Subject: [ZendTo] Failed to unlock user $user as did not match
 usernameRegexp from preferences.php
In-Reply-To: <WM!6db1561db190506cd8fd2183cfef804befa2ee8342c40998d4d0cac462a99b948566602374edc4daf826ab1e8f50b3f7!@mx.jul.es>
References: <330ad221e5f345b3a36e5d792125630c@HSH-MAIL.HSH.local>
 <WM!e77d92ba1db2d64e2566bde12aca80974b57b4cd5c53b32587b36194123f9181746e3a5a97665a8745fb8d589d9a7c6e!@mx.jul.es>
 <3ca20383-63b3-a467-bf24-e23ffe731f7f@Zend.To>
 <WM!6db1561db190506cd8fd2183cfef804befa2ee8342c40998d4d0cac462a99b948566602374edc4daf826ab1e8f50b3f7!@mx.jul.es>
 <5d681670907b413e8cb161fe6b8013e1@HSH-MAIL.HSH.local>
Message-ID: <WM!140e3c85520656eff95e847f56fc538c39122d4180086d030359dd69879c4f1ee1c30d828c069e6f564f2b26d9d592a0!@mx.jul.es>

Jules,

Awesome. Glad I was able to help.

As for your explanation, it makes perfect sense now. If only everyone in the world was really nice and had no knowledge of brute force attacks.

With that said however, as for not showing the message to let the user know that they have been locked out, is there a way for an email to be sent to the administrator (maybe an option that can be turned on/off by the admin) whenever someone's account has been locked. This way if I am the admin, I am full aware of who's account was locked before they even generate a ticket to me. Receiving a notification email of this can be a feature I choose to turn on or off if I don't want to be notified but will rather manually check logs on my own schedule to see what's happening on my ZendTo server.




From: Jules [mailto:Jules at Zend.To]
Sent: Tuesday, July 21, 2020 9:43 AM
To: ZendTo Users <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] Failed to unlock user $user as did not match usernameRegexp from preferences.php

Marlon,

You are doing a thorough job of this, thank you!

I have fixed the bug(s) you described. It now behaves exactly as expected, including the logging. This will be in the next release.

As for the feature request, the current behaviour is by design.
Someone nasty (a "bad actor" in the jargon) is using your ZendTo site to brute-force break your password.
They keep trying different passwords, but always get the same simple "incorrect" response.
They don't know ZendTo very well, and don't know your configuration settings at all.
As a result, they can't tell if or when they should give up trying to break your username/password, and try some other username instead.

As soon as you display *anything* different, the attacker knows the lock-out limit has been reached and so they should abandon their current attempt and try another one.

So you *never* give away any hints as to why the login attempt failed, beyond a simple fixed error message.

It logs it in the ZendTo log (/var/log/zendto/zendto.log is the file that the "System Log" button shows you the end of), so you can check there.

Cheers,
Jules.

P.S. The "start" and "expiry" date/time selectors on the "Request a drop-off" form are nearly there. I just want to tidy up that page design layout, it's a bit of a mess and I would prefer it to use a grid or two and a flex box like the "new drop-off" form now does.
On 21/07/2020 13:45, Marlon Deerr via ZendTo wrote:
Hi Jules,

I was testing ZendTo. I wanted to see what the log files will report when a user is locked out after 10 unsuccessful login attempts. I noticed that the log file (I think) is incorrectly reporting that a user was not unlocked after administratively unlocking the account, when in fact the user was successfully unlocked. Here are the steps I performed.


1.       Purposely attempted to log in as a user with incorrect password 10 times

2.       Logged in as an admin user and examined the System Logs

3.       System Log file successfully identified this locked user

4.       Clicked on "Unlock User" from the main screen and selected the user to unlock and unlocked her

5.       Examined the System Logs again, but this time it said "Failed to unlock user $user as did not match usernameRegexp from preferences.php"

6.       Logged out as the administrator user

7.       Tried logged in as this "supposedly" locked user BUT the login was successful.


Does this mean that the System Log file is incorrectly reporting that the user was not unlocked, when in fact the user was unlocked?

ALSO: Feature Request (if possible)

When a user is approaching the maximum allowed failed login attempts can you include a message that


1.       Warns the user that you have x more attempts before you get locked out (where x is a number)

2.       After the user has failed to login after 10 attempts, instead of just saying "Authentication Error. The username or password was incorrect", can it not say something like "Authentication Error. You have attempted more than the allowed failed attempts to log in. Your account therefore has been locked. Please contact your administrator to have it unlocked"

While testing this feature above, I found that I was not keeping track of how many times I made a failed login and must have tried over and over again waiting for a message to let me now that I was locked out.  I think having such a message will help reduce IT Tickets from staff wondering why they can't log in. They may not even know they have been locked out.



_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto:ZendTo at zend.to>

http://jul.es/mailman/listinfo/zendto



Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



The current UK shipping forecast:

Trafalgar: Cyclonic 6 to gale 8 at first in southeast, otherwise northerly 5

to 7, becoming variable 3 or 4 in southeast. Moderate or rough, occasionally

very rough. Thundery showers. Good, occasionally poor.



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200721/f69fb884/attachment.html>

From Massimo.Forni at turboden.it  Tue Jul 21 15:30:21 2020
From: Massimo.Forni at turboden.it (Massimo Forni)
Date: Tue, 21 Jul 2020 14:30:21 +0000
Subject: [ZendTo] Failed to unlock user $user as did not match
 usernameRegexp from preferences.php
In-Reply-To: <WM!2e0bd496ad3bed476866d7c2800a07a2aff6ecb6c76278be9905cd41ecfa7c4172a1622a2386dff482ecc2bd1d9fe8a9!@mx.jul.es>
References: <330ad221e5f345b3a36e5d792125630c@HSH-MAIL.HSH.local>
 <WM!e77d92ba1db2d64e2566bde12aca80974b57b4cd5c53b32587b36194123f9181746e3a5a97665a8745fb8d589d9a7c6e!@mx.jul.es>
 <3ca20383-63b3-a467-bf24-e23ffe731f7f@Zend.To>
 <WM!6db1561db190506cd8fd2183cfef804befa2ee8342c40998d4d0cac462a99b948566602374edc4daf826ab1e8f50b3f7!@mx.jul.es>
 <5d681670907b413e8cb161fe6b8013e1@HSH-MAIL.HSH.local>
 <WM!140e3c85520656eff95e847f56fc538c39122d4180086d030359dd69879c4f1ee1c30d828c069e6f564f2b26d9d592a0!@mx.jul.es>
 <WM!2e0bd496ad3bed476866d7c2800a07a2aff6ecb6c76278be9905cd41ecfa7c4172a1622a2386dff482ecc2bd1d9fe8a9!@mx.jul.es>
 <269df8547af34f94b8c08bc18c71850d@Mailbox13.turboden.local>
Message-ID: <WM!6e23c5de665dca4e557b793dbfcc7ea19731202ff7646496d824f9af47b44f6b49d88d87d78bea7f116d466aed1b7e46!@mx.jul.es>

+1 for this.
I've set up our elasticsearch cluster to send an email notification in case an Active Directory user lockout


From: ZendTo <zendto-bounces at zend.to> On Behalf Of Marlon Deerr via ZendTo
Sent: marted? 21 luglio 2020 15:54
To: 'Jules' <Jules at Zend.To>; ZendTo Users <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] Failed to unlock user $user as did not match usernameRegexp from preferences.php

Jules,

Awesome. Glad I was able to help.

As for your explanation, it makes perfect sense now. If only everyone in the world was really nice and had no knowledge of brute force attacks.

With that said however, as for not showing the message to let the user know that they have been locked out, is there a way for an email to be sent to the administrator (maybe an option that can be turned on/off by the admin) whenever someone's account has been locked. This way if I am the admin, I am full aware of who's account was locked before they even generate a ticket to me. Receiving a notification email of this can be a feature I choose to turn on or off if I don't want to be notified but will rather manually check logs on my own schedule to see what's happening on my ZendTo server.




From: Jules [mailto:Jules at Zend.To]
Sent: Tuesday, July 21, 2020 9:43 AM
To: ZendTo Users <zendto at zend.to<mailto:zendto at zend.to>>
Cc: Marlon Deerr <MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>>
Subject: Re: [ZendTo] Failed to unlock user $user as did not match usernameRegexp from preferences.php

Marlon,

You are doing a thorough job of this, thank you!

I have fixed the bug(s) you described. It now behaves exactly as expected, including the logging. This will be in the next release.

As for the feature request, the current behaviour is by design.
Someone nasty (a "bad actor" in the jargon) is using your ZendTo site to brute-force break your password.
They keep trying different passwords, but always get the same simple "incorrect" response.
They don't know ZendTo very well, and don't know your configuration settings at all.
As a result, they can't tell if or when they should give up trying to break your username/password, and try some other username instead.

As soon as you display *anything* different, the attacker knows the lock-out limit has been reached and so they should abandon their current attempt and try another one.

So you *never* give away any hints as to why the login attempt failed, beyond a simple fixed error message.

It logs it in the ZendTo log (/var/log/zendto/zendto.log is the file that the "System Log" button shows you the end of), so you can check there.

Cheers,
Jules.

P.S. The "start" and "expiry" date/time selectors on the "Request a drop-off" form are nearly there. I just want to tidy up that page design layout, it's a bit of a mess and I would prefer it to use a grid or two and a flex box like the "new drop-off" form now does.
On 21/07/2020 13:45, Marlon Deerr via ZendTo wrote:
Hi Jules,

I was testing ZendTo. I wanted to see what the log files will report when a user is locked out after 10 unsuccessful login attempts. I noticed that the log file (I think) is incorrectly reporting that a user was not unlocked after administratively unlocking the account, when in fact the user was successfully unlocked. Here are the steps I performed.


  1.  Purposely attempted to log in as a user with incorrect password 10 times
  2.  Logged in as an admin user and examined the System Logs
  3.  System Log file successfully identified this locked user
  4.  Clicked on "Unlock User" from the main screen and selected the user to unlock and unlocked her
  5.  Examined the System Logs again, but this time it said "Failed to unlock user $user as did not match usernameRegexp from preferences.php"
  6.  Logged out as the administrator user
  7.  Tried logged in as this "supposedly" locked user BUT the login was successful.


Does this mean that the System Log file is incorrectly reporting that the user was not unlocked, when in fact the user was unlocked?

ALSO: Feature Request (if possible)

When a user is approaching the maximum allowed failed login attempts can you include a message that


  1.  Warns the user that you have x more attempts before you get locked out (where x is a number)
  2.  After the user has failed to login after 10 attempts, instead of just saying "Authentication Error. The username or password was incorrect", can it not say something like "Authentication Error. You have attempted more than the allowed failed attempts to log in. Your account therefore has been locked. Please contact your administrator to have it unlocked"

While testing this feature above, I found that I was not keeping track of how many times I made a failed login and must have tried over and over again waiting for a message to let me now that I was locked out.  I think having such a message will help reduce IT Tickets from staff wondering why they can't log in. They may not even know they have been locked out.


_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto:ZendTo at zend.to>

http://jul.es/mailman/listinfo/zendto<https://urldefense.com/v3/__http:/jul.es/mailman/listinfo/zendto__;!!BYEqwblc0Q!jCBn-WiNh7WoO449qiyB_5KcE5QLYQi385j6eKoA6reZuwaubjVMkyXv1CMM0BbOFGHncw$>


Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



The current UK shipping forecast:

Trafalgar: Cyclonic 6 to gale 8 at first in southeast, otherwise northerly 5

to 7, becoming variable 3 or 4 in southeast. Moderate or rough, occasionally

very rough. Thundery showers. Good, occasionally poor.



www.Zend.To<https://urldefense.com/v3/__http:/www.Zend.To__;!!BYEqwblc0Q!jCBn-WiNh7WoO449qiyB_5KcE5QLYQi385j6eKoA6reZuwaubjVMkyXv1CMM0BbQRNjxEQ$>

Twitter: @JulesFM

--

Massimo Forni
ICT Infrastructure Manager

Mobile: +393474110278

________________________________

Turboden S.p.A. I via Cernaia 10 I 25124 Brescia I Italy
t. +39 030 3552001 I f. +39 030 3552011
www.turboden.com<http://www.turboden.com>


Confidentiality notice: this message, together with its attachments, may contain strictly confidential and/or legally privileged information and it is destined solely to the intended addressee(s), who only may use it under his/their responsibility. Opinions, conclusions and other information contained in this message, that do not relate to the official business of this firm, shall be considered as not given or endorsed by it. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. Any use, disclosure, copying or distribution of the contents of this communication by a not-intended recipient or in violation of the purposes of this communication is strictly prohibited and may be unlawful.

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

From Jules at Zend.To  Tue Jul 21 16:00:48 2020
From: Jules at Zend.To (Jules)
Date: Tue, 21 Jul 2020 16:00:48 +0100
Subject: [ZendTo] Failed to unlock user $user as did not match
 usernameRegexp from preferences.php
In-Reply-To: <WM!561b5eb010fbb7a85e384183333621c66d9fb679a24221c54e4fea9e99443aee465bddbfd24a06a751f3467bca733eb4!@mx.jul.es>
References: <330ad221e5f345b3a36e5d792125630c@HSH-MAIL.HSH.local>
 <WM!e77d92ba1db2d64e2566bde12aca80974b57b4cd5c53b32587b36194123f9181746e3a5a97665a8745fb8d589d9a7c6e!@mx.jul.es>
 <3ca20383-63b3-a467-bf24-e23ffe731f7f@Zend.To>
 <WM!6db1561db190506cd8fd2183cfef804befa2ee8342c40998d4d0cac462a99b948566602374edc4daf826ab1e8f50b3f7!@mx.jul.es>
 <5d681670907b413e8cb161fe6b8013e1@HSH-MAIL.HSH.local>
 <WM!561b5eb010fbb7a85e384183333621c66d9fb679a24221c54e4fea9e99443aee465bddbfd24a06a751f3467bca733eb4!@mx.jul.es>
Message-ID: <2eda6067-0bd4-37a4-ec18-bd7522512bdb@Zend.To>

Marlon,

On 21/07/2020 14:54, Marlon Deerr wrote:
>
> Jules,
>
> Awesome. Glad I was able to help.
>
> As for your explanation, it makes perfect sense now. If only everyone 
> in the world was really nice and had no knowledge of brute force attacks.
>
It's about the simplest possible form of "side channel" attack. You 
discover bits of information about the thing you are trying to break by 
watching it in some way. In this case, it's as simple as watching for 
when the error message would change. As I say, it's the simplest one.

Once you start having to be really careful, you suddenly realise you 
need things like a simple function that compares 2 strings (did their 
encryption key match the real one?), that *always* takes exactly the 
same length of time regardless of whether the strings match or not. 
Otherwise you're vulnerable to a time-based side-channel attack.

When you get into the world of chip+pin credit cards, you have be sure 
that whether the PIN matches or not, the *input* power required to run 
the chip doesn't change. Otherwise an ammeter (an electrical current 
probe) can watch and (very fast!) log the power consumption, and so you 
can make deductions about the internal decisions on the chip. Try lots 
of different input combinations and watch how the trace of current vs 
time is different for each input value you try.

There are literally thousands of examples, but they are a couple of the 
most common.
They rarely give you a direct answer or a direct way into hacking 
something, but they will provide more little nuggets of information that 
the hacker needs.

"Security by design" is fundamental. And extremely difficult!
But a very interesting subject. Try googling "side channel attack", I'm 
sure you'll find some interesting reading.


> With that said however, as for not showing the message to let the user 
> know that they have been locked out, is there a way for an email to be 
> sent to the administrator (maybe an option that can be turned on/off 
> by the admin) whenever someone?s account has been locked.
>
That's what the package "logwatch" is for. It's very good at it already, 
so I'm not going to reinvent it. :-)
Install and learn how to setup that.

Cheers,
Jules.


> This way if I am the admin, I am full aware of who?s account was 
> locked before they even generate a ticket to me. Receiving a 
> notification email of this can be a feature I choose to turn on or off 
> if I don?t want to be notified but will rather manually check logs on 
> my own schedule to see what?s happening on my ZendTo server.
>
>
> Marlon Deerr, Technology Manager
> 416-572-8795(direct) | MDeerr at hshlawyers.com 
> <mailto:MDeerr at hshlawyers.com>
> <https://www.hshlawyers.com>
> <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> 
> <https://twitter.com/hshlawyers> 
> <https://www.facebook.com/HSHPersonalInjuryLawyers/> 
> <https://www.youtube.com/user/hshlawyers> 	3500 - 20 Queen St. W., 
> Toronto, ON M5H 3R3
> Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com 
> <https://www.hshlawyers.com>
>
>
> This Howie Sacks & Henry e-mail is privileged, confidential and 
> subject to copyright. Any unauthorized use or disclosure is prohibited.
>
>
>
> *From:* Jules [mailto:Jules at Zend.To]
> *Sent:* Tuesday, July 21, 2020 9:43 AM
> *To:* ZendTo Users <zendto at zend.to>
> *Cc:* Marlon Deerr <MDeerr at hshlawyers.com>
> *Subject:* Re: [ZendTo] Failed to unlock user $user as did not match 
> usernameRegexp from preferences.php
>
> Marlon,
>
> You are doing a thorough job of this, thank you!
>
> I have fixed the bug(s) you described. It now behaves exactly as 
> expected, including the logging. This will be in the next release.
>
> As for the feature request, the current behaviour is by design.
> Someone nasty (a "bad actor" in the jargon) is using your ZendTo site 
> to brute-force break your password.
> They keep trying different passwords, but always get the same simple 
> "incorrect" response.
> They don't know ZendTo very well, and don't know your configuration 
> settings at all.
> As a result, they can't tell if or when they should give up trying to 
> break your username/password, and try some other username instead.
>
> As soon as you display *anything* different, the attacker knows the 
> lock-out limit has been reached and so they should abandon their 
> current attempt and try another one.
>
> So you *never* give away any hints as to why the login attempt failed, 
> beyond a simple fixed error message.
>
> It logs it in the ZendTo log (/var/log/zendto/zendto.log is the file 
> that the "System Log" button shows you the end of), so you can check 
> there.
>
> Cheers,
> Jules.
>
> P.S. The "start" and "expiry" date/time selectors on the "Request a 
> drop-off" form are nearly there. I just want to tidy up that page 
> design layout, it's a bit of a mess and I would prefer it to use a 
> grid or two and a flex box like the "new drop-off" form now does.
>
> On 21/07/2020 13:45, Marlon Deerr via ZendTo wrote:
>
>     Hi Jules,
>
>     I was testing ZendTo. I wanted to see what the log files will
>     report when a user is locked out after 10 unsuccessful login
>     attempts. I noticed that the log file (I think) is incorrectly
>     reporting that a user was not unlocked after administratively
>     unlocking the account, when in fact the user was successfully
>     unlocked. Here are the steps I performed.
>
>     1.Purposely attempted to log in as a user with incorrect password
>     10 times
>
>     2.Logged in as an admin user and examined the System Logs
>
>     3.System Log file successfully identified this locked user
>
>     4.Clicked on ?Unlock User? from the main screen and selected the
>     user to unlock and unlocked her
>
>     5.Examined the System Logs again, but this time it said ?*Failed
>     to unlock user $user as did not match usernameRegexp from
>     preferences.php*?
>
>     6.Logged out as the administrator user
>
>     7.Tried logged in as this ?supposedly? locked user *BUT* the login
>     was successful.
>
>     Does this mean that the System Log file is incorrectly reporting
>     that the user was not unlocked, when in fact the user was unlocked?
>
>     *ALSO:*Feature Request (if possible)
>
>     When a user is approaching the maximum allowed failed login
>     attempts can you include a message that
>
>     1.Warns the user that you have x more attempts before you get
>     locked out (where x is a number)
>
>     2.After the user has failed to login after 10 attempts, instead of
>     just saying ?Authentication Error. The username or password was
>     incorrect?, can it not say something like ?Authentication Error.
>     You have attempted more than the allowed failed attempts to log
>     in. Your account therefore has been locked. Please contact your
>     administrator to have it unlocked?
>
>     While testing this feature above, I found that I was not keeping
>     track of how many times I made a failed login and must have tried
>     over and over again waiting for a message to let me now that I was
>     locked out. ?I think having such a message will help reduce IT
>     Tickets from staff wondering why they can?t log in. They may not
>     even know they have been locked out.
>
>
>
>     _______________________________________________
>
>     ZendTo mailing list
>
>     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>
>     http://jul.es/mailman/listinfo/zendto  <http://jul.es/mailman/listinfo/zendto>
>
>
>
> Jules
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> The current UK shipping forecast:
> Trafalgar: Cyclonic 6 to gale 8 at first in southeast, otherwise northerly 5
> to 7, becoming variable 3 or 4 in southeast. Moderate or rough, occasionally
> very rough. Thundery showers. Good, occasionally poor.
> www.Zend.To  <http://www.Zend.To>
> Twitter: @JulesFM

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Think globally, act locally.' - Friends of the Earth

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200721/9a0a063a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagecae09c.JPG
Type: image/jpeg
Size: 125353 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200721/9a0a063a/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imageb64590.JPG
Type: image/jpeg
Size: 7976 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200721/9a0a063a/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image0e8bb5.JPG
Type: image/jpeg
Size: 7843 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200721/9a0a063a/attachment-0007.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image8ef134.JPG
Type: image/jpeg
Size: 7268 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200721/9a0a063a/attachment-0008.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagec0f457.JPG
Type: image/jpeg
Size: 7059 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200721/9a0a063a/attachment-0009.jpe>

From klou at themusiclink.net  Tue Jul 21 17:49:55 2020
From: klou at themusiclink.net (Kris Lou)
Date: Tue, 21 Jul 2020 09:49:55 -0700
Subject: [ZendTo] Suggestion?: Edit Address book from "Home" page
References: <CAGyTNKF1VgNijLoHRe=kGPdSCVhMQnocYdMM7C0yTB8PCngm+Q@mail.gmail.com>
Message-ID: <WM!510c17cfbf1734a999796e8a9b1d8ab194de0b134149c1b051476af899ae483b38f5002e7dc0ef9b647e561c6c67e8ae!@mx.jul.es>

Jules,

I ran into an "issue" that's incredibly low priority, but the only way to
access and edit the Address Book is from the Dropoff page.  (I had some
typos that were nice to fix.)

Is it worth making that accessible from the initial login page?

Thanks,

Kris Lou
klou at themusiclink.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200721/7300dd2f/attachment.html>

From Jules at Zend.To  Tue Jul 21 18:49:42 2020
From: Jules at Zend.To (Jules)
Date: Tue, 21 Jul 2020 18:49:42 +0100
Subject: [ZendTo] Suggestion?: Edit Address book from "Home" page
In-Reply-To: <WM!510c17cfbf1734a999796e8a9b1d8ab194de0b134149c1b051476af899ae483b38f5002e7dc0ef9b647e561c6c67e8ae!@mx.jul.es>
References: <CAGyTNKF1VgNijLoHRe=kGPdSCVhMQnocYdMM7C0yTB8PCngm+Q@mail.gmail.com>
 <WM!510c17cfbf1734a999796e8a9b1d8ab194de0b134149c1b051476af899ae483b38f5002e7dc0ef9b647e561c6c67e8ae!@mx.jul.es>
Message-ID: <f2096b9f-bfdd-716b-1b5b-8a28430024c7@Zend.To>

Kris,

I've thought about that one (briefly) too. The amount of work required 
to implement an address book editor is simply not worth the gain.
You can delete address book entries from both the "new drop-off" and 
"request a drop-off" pages.
You can even add new ones (without sending anything anywhere) by 
entering them in the "request a drop-off" page and unticking the "Send 
email" checkbox.

I'm going to have to be *awfully* bored before I start trying to write 
an editor.

Sorry,
Jules.

On 21/07/2020 17:49, Kris Lou via ZendTo wrote:
> Jules,
>
> I ran into an "issue" that's incredibly low priority, but the only way 
> to access and edit the Address Book is from the Dropoff page.? (I had 
> some typos that were nice to fix.)
>
> Is it worth making that accessible from the initial login page?
>
> Thanks,
>
> Kris Lou
> klou at themusiclink.net <mailto:klou at themusiclink.net>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Making machines do what you want requires only two qualities:
  1) Being slightly more stubborn that the computer, &
  2) Remembering that computers are electrified rocks.' - @JediJeremy

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200721/0204fdb9/attachment.html>

From klou at themusiclink.net  Tue Jul 21 18:53:55 2020
From: klou at themusiclink.net (Kris Lou)
Date: Tue, 21 Jul 2020 10:53:55 -0700
Subject: [ZendTo] Suggestion?: Edit Address book from "Home" page
In-Reply-To: <WM!65d970b7e41cdc28ce513330869d743aa110e8880a7b3eb554dde1fa057e831b620f880754c5cefe60c1c1cfd1a4b8a5!@mx.jul.es>
References: <CAGyTNKF1VgNijLoHRe=kGPdSCVhMQnocYdMM7C0yTB8PCngm+Q@mail.gmail.com>
 <f2096b9f-bfdd-716b-1b5b-8a28430024c7@Zend.To>
 <WM!510c17cfbf1734a999796e8a9b1d8ab194de0b134149c1b051476af899ae483b38f5002e7dc0ef9b647e561c6c67e8ae!@mx.jul.es>
 <WM!65d970b7e41cdc28ce513330869d743aa110e8880a7b3eb554dde1fa057e831b620f880754c5cefe60c1c1cfd1a4b8a5!@mx.jul.es>
 <CAGyTNKHV9ahZr-tX4HiMgjsHhhJKK6PEsXHpakAUNcm+FBdWyQ@mail.gmail.com>
Message-ID: <WM!ca4c756e6b8668737feac4071f70a2c689e99170feb40b521e038fd86fdc25b734d3044d8183dfebb646520fdad2a61d!@mx.jul.es>

> I've thought about that one (briefly) too. The amount of work required to
> implement an address book editor is simply not worth the gain.
> You can delete address book entries from both the "new drop-off" and
> "request a drop-off" pages.
> You can even add new ones (without sending anything anywhere) by entering
> them in the "request a drop-off" page and unticking the "Send email"
> checkbox.
>
>
Absolutely more than fair.  It was a more of a "maybe I should mention it"
kind of thing.

Thanks,
-Kris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200721/b4b82883/attachment.html>

From MDeerr at hshlawyers.com  Tue Jul 21 20:55:11 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Tue, 21 Jul 2020 19:55:11 +0000
Subject: [ZendTo] Authentication Error - The username or password was
 incorrect
In-Reply-To: <WM!8dfced315f7584d8a63807730b2547811edc9215423e180d3c3c04a7e66c504886cd24aaf39fe1363f5361445a5650dc!@mx.jul.es>
References: <5bbb4fb4215246b0972b060f5c691d9b@HSH-MAIL.HSH.local>
 <9db878bed4784c298a38e840516aa067@HSH-MAIL.HSH.local>
 <WM!b31c576e9da1091c079373617098d4f5be165aa432658bc2ca9e0d15fc7739e2a2ce5150a9a0be6ed363f194ce8ec8ab!@mx.jul.es>
 <8633ea36-d98e-eec3-280c-30d37cdedcee@Zend.To>
 <WM!36554503182ace1df2afaaff5f2e82f27591fa50d1f1befd6a7c03b7c776856cdfdb28a8102e5aedca1e3f341635a740!@mx.jul.es>
 <36da1928b55b441c9ba5f1e3fe185f88@HSH-MAIL.HSH.local>
 <WM!f0e79ea6f129bacb925a5a4d0228a3c867e28d502c471a621d8b9bac2457d8742017f4112a12ba759596619ec06b0424!@mx.jul.es>
 <e3508cb1-9e20-2007-3dcb-2c7a0e97446b@Zend.To>
 <WM!9eb58ea76f65561c0e3398715a95feb4b5ddb3606b9ab86af5dc8be794991c68e2849f792af39795fa6052fc2f17157e!@mx.jul.es>
 <473b8aaef8384f248b7c6099939a7dcd@HSH-MAIL.HSH.local>
 <WM!b5b92cd801734e61eb6e0dbd3c89c0c8045e7f0f3ada72c21308719fc69d25c264cdbd39fed66fb7740ee5f02cee7ce9!@mx.jul.es>
 <f3141ccc-0742-4f9e-5705-d0bf150a8155@Zend.To>
 <WM!8dfced315f7584d8a63807730b2547811edc9215423e180d3c3c04a7e66c504886cd24aaf39fe1363f5361445a5650dc!@mx.jul.es>
 <8459aa5af5314062959201fecf68ea23@HSH-MAIL.HSH.local>
Message-ID: <WM!a40791ce30fb6c23a92762c136c8ae2c68ff9d52f3d33d0b5427b6b7ee91c5be21a1c4c6c3916c4e9bb51f99c21e1ee7!@mx.jul.es>

Hey Jules,

Here is a portion of what was displayed after my attempt to re-send the dropoff. It failed (obviously), but I?m not sure why it is.

2020-07-21 16:51:21 CLIENT -> SERVER: STARTTLS
2020-07-21 16:51:21 SERVER -> CLIENT: 220 2.0.0 SMTP server ready
SMTP Error: Could not connect to SMTP host.
2020-07-21 16:51:21 CLIENT -> SERVER: QUIT
2020-07-21 16:51:21 SERVER -> CLIENT:
2020-07-21 16:51:21 SMTP ERROR: QUIT command failed:
SMTP connect() failed. Sta


What I have done to troubleshoot


1.       Tried setting the SMTP port within preferences to 25, 465 & 587 ? failed on each re-send

2.       Opened a PowerShell prompt opened a telnet session to our mail server (on port 25) ? success

3.       Sent a simple email from myself to myself ? success (my Outlook client received it right away)

4.       Sent another simple test email but this time from another email address to myself - success

This tells me that technically I can connect to the server and send emails. Not sure why ZendTo is failing to connect.

From: Jules [mailto:Jules at Zend.To]
Sent: Tuesday, July 21, 2020 7:41 AM
To: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] Authentication Error - The username or password was incorrect


On 21/07/2020 12:32, Marlon Deerr wrote:
You did the trick Jules. Removing ?ldaps://? from hostname of the authLDAPSServers1 value worked. I thought that it was supposed to be there so I never even thought to remove that.
Yay! You need to add the ldaps:// when you are encrypting all the traffic to your AD server. Which you're not. In which case it just wants the hostname and nothing else.



Now I just need to work on getting SMTP working. I was working on one problem at a time.
There's a slightly curious but effective way of debugging this setup...
Send yourself (or a test account) a drop-off.
Through your ZendTo Outbox, view the drop-off.
Edit preferences.php to set
  'SMTPdebug'    => true,
(it's normally set to false, it will be near the bottom of the SMTP settings in preferences.php).
Click on the "Resend Dropoff" button on the web page.
You will see the entire SMTP conversation happen on the web page output.
It often only stays there for a few seconds, so you might want to be ready with whatever keys you need to take a screenshot!

Fix the problems and get the "Resend Dropoff" debug output looking right. You should see some "OK" type messages.

Then reset
  'SMTPdebug'    => false,
before trying anything else, such as creating a new drop-off.
Having that 'SMTPdebug' set to true will break the new drop-off process.

It's usually fairly straightforward to fix. Feel free to send me a screenshot or two if you can't see what's wrong (I've had 30 years experience running enterprise email systems, so what's easy/obvious to me may well not be to you. Sorry about that!).

Cheers,
Jules.





Thanks so much for your assistance.



Marlon Deerr, Technology Manager
416-572-8795 (direct) | MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>
[cid:image002.jpg at 01D65F60.66955490]<https://www.hshlawyers.com>
[cid:image004.jpg at 01D65F60.66955490]<https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> [cid:image006.jpg at 01D65F60.66955490] <https://twitter.com/hshlawyers>  [cid:image008.jpg at 01D65F60.66955490] <https://www.facebook.com/HSHPersonalInjuryLawyers/>  [cid:image010.jpg at 01D65F60.66955490] <https://www.youtube.com/user/hshlawyers>

3500 - 20 Queen St. W., Toronto, ON M5H 3R3
Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com<https://www.hshlawyers.com>



This Howie Sacks & Henry e-mail is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited.



From: Jules [mailto:Jules at Zend.To]
Sent: Tuesday, July 21, 2020 4:02 AM
To: Marlon Deerr <MDeerr at hshlawyers.com><mailto:MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] Authentication Error - The username or password was incorrect

Marlon,

Try changing this setting to the one below:
  'authLDAPServers1'          => array('hsh-dc.hsh.local'),
What I've done is remove the "ldaps://"<ldaps://> from the hostname of the authLDAPServers1 value.

If that doesn't fix it, can you send me the exact ldapsearch command you used that worked?

Cheers,
Jules.


On 20/07/2020 20:52, Marlon Deerr wrote:
Hello Jules,

Thank you for following up on this issue I?m experiencing. To answer your question, yes, I meant to refer to my AD server not DNS.  As for the ldapsearch utility, yes I am able to successfully show my details when I insert the correct values in the command.  Also, as requested, I have copy/pasted the LDAP section of my preferences.php file for you to take a look at.

Hopefully, you see something I?m missing.





Marlon Deerr, Technology Manager
416-572-8795 (direct) | MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>
[cid:image011.jpg at 01D65F60.66955490]<https://www.hshlawyers.com>
[cid:image012.jpg at 01D65F60.66955490]<https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> [cid:image013.jpg at 01D65F60.66955490] <https://twitter.com/hshlawyers>  [cid:image014.jpg at 01D65F60.66955490] <https://www.facebook.com/HSHPersonalInjuryLawyers/>  [cid:image015.jpg at 01D65F60.66955490] <https://www.youtube.com/user/hshlawyers>

3500 - 20 Queen St. W., Toronto, ON M5H 3R3
Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com<https://www.hshlawyers.com>



This Howie Sacks & Henry e-mail is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited.



From: Jules [mailto:Jules at Zend.To]
Sent: Saturday, July 18, 2020 8:03 AM
To: Marlon Deerr <MDeerr at hshlawyers.com><mailto:MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] Authentication Error - The username or password was incorrect

Marlon,
On 17/07/2020 22:54, Marlon Deerr wrote:
Jules,

No, I didn?t type in < and > characters. I only did that to not show real usernames on my end.  So to be clear, no I did not type in those characters as part of the username when using the /opt/zendto/bin/adduser command. As for certificates, I?m not sure as our DNS server
I assume you mean your AD server, not your DNS server. DNS should have no impact on this at all.




is actually managed by our MSP. With that said, when I do run the openssl command, I get the below output.
That looks like they're not running any encryption on your AD traffic. Okay, but Microsoft are going to mandate encryption on AD traffic very soon. But in the mean time, you should be okay using it unencrypted.

On zend.to/activedirectory, read section 2 and there is an ldapsearch command. Replacing the necessary bits of that, can you get it to show you your details?

If you can send me your AD settings from preferences.php (all the LDAP settings whose names end in 1, 2 or 3), I can take a look and suggest an ldapsearch command that should work if your settings are correct.





As for the log file at /var/log/zendto/zendto.log, if it says Warning: authorization failed for username, does that mean it wasn?t able to read from our AD Server. Not sure how to interpret that because before I ran the upgrade command after applying the latest patch, it seemed as though it was able to read from AD. Now I?m not sure what?s going on.
It probably did manage to connect to your AD server, but couldn't get any further.






Output for openssl s_client -connect your-ad-server.company.com:636

From this output, it looks like you're running AD unencrypted.

Cheers,
Jules.




CONNECTED(00000003)
write:errno=104
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 283 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)




Marlon Deerr, Technology Manager
416-572-8795 (direct) | MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>
[cid:image011.jpg at 01D65F60.66955490]<https://www.hshlawyers.com>
[cid:image012.jpg at 01D65F60.66955490]<https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> [cid:image013.jpg at 01D65F60.66955490] <https://twitter.com/hshlawyers>  [cid:image014.jpg at 01D65F60.66955490] <https://www.facebook.com/HSHPersonalInjuryLawyers/>  [cid:image015.jpg at 01D65F60.66955490] <https://www.youtube.com/user/hshlawyers>

3500 - 20 Queen St. W., Toronto, ON M5H 3R3
Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com<https://www.hshlawyers.com>



This Howie Sacks & Henry e-mail is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited.



From: Jules [mailto:Jules at Zend.To]
Sent: Wednesday, July 15, 2020 12:35 PM
To: Marlon Deerr <MDeerr at hshlawyers.com><mailto:MDeerr at hshlawyers.com>; ZendTo Users <zendto at zend.to><mailto:zendto at zend.to>
Subject: Re: [ZendTo] Authentication Error - The username or password was incorrect

Are you actually seeing the < and > characters?
You didn't actually type those into the /opt/zendto/bin/adduser command, did you?

Have a read of the AD troubleshooting steps on
    zend.to/activedirectory

Do you know if you're running with a locally-signed certificate on your AD servers?

Assuming you have the hostname and port number (636 usually) of your  AD server, try
openssl s_client -connect your-ad-server.company.com:636

That will show you the initial SSL/TLS handshake involving all the certificates.
You'll need to Ctrl-C it at the end, but what it prints out should be very useful so you can see exactly what is using which certs.

Hope that helps,
Jules.
On 15/07/2020 16:50, Marlon Deerr wrote:
OK, my user seems to be unlocked now but now I am getting the following errors below. I must be missing something else in my setup:

Warning: admin authorization failed for <username1>

And for other users I still get the following error:

Warning: authorization failed for <username2>


Note: I believe I added <username1> as an admin.



Marlon Deerr, Technology Manager
416-572-8795 (direct) | MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>
[cid:image011.jpg at 01D65F60.66955490]<https://www.hshlawyers.com>
[cid:image012.jpg at 01D65F60.66955490]<https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> [cid:image013.jpg at 01D65F60.66955490] <https://twitter.com/hshlawyers>  [cid:image014.jpg at 01D65F60.66955490] <https://www.facebook.com/HSHPersonalInjuryLawyers/>  [cid:image015.jpg at 01D65F60.66955490] <https://www.youtube.com/user/hshlawyers>

3500 - 20 Queen St. W., Toronto, ON M5H 3R3
Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com<https://www.hshlawyers.com>



This Howie Sacks & Henry e-mail is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited.



From: Jules [mailto:Jules at Zend.To]
Sent: Wednesday, July 15, 2020 7:09 AM
To: ZendTo Users <zendto at zend.to><mailto:zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com><mailto:MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] Authentication Error - The username or password was incorrect

Marlon,

The crucial bit in the log is the "locked-out user" bit.

ZendTo has a security feature in it to stop it being used as a method of brute-force attacking your accounts from outside.
If the same user has several failed logins in a row, that user is locked out for the next 24 hours by default.

If you can login as an admin user, one of the extra admin red buttons shows you the locked out users and lets you reset them.

Alternatively, you can unlock all locked users from the command line with
    /opt/zendto/bin/unlockuser -a

Cheers,
Jules.
On 14/07/2020 18:45, Marlon Deerr via ZendTo wrote:
Ok, so I think I finally (or almost finally) got my AD authentication settings correct.  I have installed the ldapsearch utility to confirm that I?m able to successful search the OU where my users reside, however when I attempt to log in with a valid user, ZendTo keeps erroring with:

Authentication Error
The username or password was incorrect

I checked the /var/log/zendto/zendto.log and it says the following:

??.Warning: authorization attempt for locked-out user <username1>
Then when I try logging in as another user, I see the following in the log

??Warning: authorization failed for <username2>



I know that I have both username/password correct so I must be missing something. Anyone know what setting I may have applied incorrectly?









_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto: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<http://www.Zend.To>

Twitter: @JulesFM






Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'There is silent poetry in the stillness of morning;

 in the calm, the cries & sighs of life sound like gentle music.'

 - @Astro_Wheels



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM





Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



The current UK shipping forecast:

South Utsire, Forties: Southwesterly veering westerly 3 or 4. Mainly moderate.

Rain at first. Moderate or poor, becoming good.



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM




Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'Every morning when I wake,

 Dear Lord, a little prayer I make,

 O please do keep Thy lovely eye

 On all poor creatures born to die



 And every evening at sun-down

 I ask a blessing on the town,

 For whether we last the night or no

 I'm sure is always touch-and-go.



 We are not wholly bad or good

 Who live our lives under Milk Wood,

 And Thou, I know, wilt be the first

 To see our best side, not our worst.



 O let us see another day!

 Bless us all this night, I pray,

 And to the sun we all will bow

 And say, good-bye - but just for now!'

    - Dylan Thomas



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM



Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'All programs have a desire to be useful' - Tron, 1982



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200721/4de0bfc2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 12435 bytes
Desc: image002.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200721/4de0bfc2/attachment-0010.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 777 bytes
Desc: image004.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200721/4de0bfc2/attachment-0011.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 768 bytes
Desc: image006.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200721/4de0bfc2/attachment-0012.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 756 bytes
Desc: image008.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200721/4de0bfc2/attachment-0013.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.jpg
Type: image/jpeg
Size: 752 bytes
Desc: image010.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200721/4de0bfc2/attachment-0014.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.jpg
Type: image/jpeg
Size: 12435 bytes
Desc: image011.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200721/4de0bfc2/attachment-0015.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.jpg
Type: image/jpeg
Size: 777 bytes
Desc: image012.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200721/4de0bfc2/attachment-0016.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.jpg
Type: image/jpeg
Size: 768 bytes
Desc: image013.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200721/4de0bfc2/attachment-0017.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.jpg
Type: image/jpeg
Size: 756 bytes
Desc: image014.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200721/4de0bfc2/attachment-0018.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image015.jpg
Type: image/jpeg
Size: 752 bytes
Desc: image015.jpg
URL: <http://jul.es/pipermail/zendto/attachments/20200721/4de0bfc2/attachment-0019.jpg>

From MDeerr at hshlawyers.com  Tue Jul 21 23:45:22 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Tue, 21 Jul 2020 22:45:22 +0000
Subject: [ZendTo] Incorrect drop-off notice within debug message
References: <b53c4f1a72ff4c4db6c0ee7642dab2ad@HSH-MAIL.HSH.local>
Message-ID: <WM!2ea2845ba8b2debac32746974332fa4df966b69c2789f8c1935f319f8d43901732734949cde54767e2b38a4a98edf78b!@mx.jul.es>

Jules,

Not sure if this is just my install, but I noticed the following.  Maybe other users can confirm if it happens with them.  While troubleshooting my SMTP settings with the various SMTP ports, I attempted to re-send drop-off and it failed BUT the message still said that "The drop-off was successfully re-sent to its recipients.



Error received with debug mode on


Mail Error


SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting

The drop-off was successfully re-sent to its recipients.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200721/a813c2c5/attachment.html>

From Jules at Zend.To  Wed Jul 22 09:50:47 2020
From: Jules at Zend.To (Jules)
Date: Wed, 22 Jul 2020 09:50:47 +0100
Subject: [ZendTo] Authentication Error - The username or password was
 incorrect
In-Reply-To: <WM!11370fd31152423eaca59e89a406c04ecc88cd65b6cbcefed9fd92f7517ac1e1377a53b47411da75c27005e443580e90!@mx.jul.es>
References: <5bbb4fb4215246b0972b060f5c691d9b@HSH-MAIL.HSH.local>
 <36da1928b55b441c9ba5f1e3fe185f88@HSH-MAIL.HSH.local>
 <WM!f0e79ea6f129bacb925a5a4d0228a3c867e28d502c471a621d8b9bac2457d8742017f4112a12ba759596619ec06b0424!@mx.jul.es>
 <e3508cb1-9e20-2007-3dcb-2c7a0e97446b@Zend.To>
 <WM!9eb58ea76f65561c0e3398715a95feb4b5ddb3606b9ab86af5dc8be794991c68e2849f792af39795fa6052fc2f17157e!@mx.jul.es>
 <473b8aaef8384f248b7c6099939a7dcd@HSH-MAIL.HSH.local>
 <WM!b5b92cd801734e61eb6e0dbd3c89c0c8045e7f0f3ada72c21308719fc69d25c264cdbd39fed66fb7740ee5f02cee7ce9!@mx.jul.es>
 <f3141ccc-0742-4f9e-5705-d0bf150a8155@Zend.To>
 <WM!8dfced315f7584d8a63807730b2547811edc9215423e180d3c3c04a7e66c504886cd24aaf39fe1363f5361445a5650dc!@mx.jul.es>
 <8459aa5af5314062959201fecf68ea23@HSH-MAIL.HSH.local>
 <WM!11370fd31152423eaca59e89a406c04ecc88cd65b6cbcefed9fd92f7517ac1e1377a53b47411da75c27005e443580e90!@mx.jul.es>
Message-ID: <029648fe-2963-8cd9-f170-f353c3845705@Zend.To>

Marlon,

On 21/07/2020 20:55, Marlon Deerr wrote:
>
> Hey Jules,
>
> Here is a portion of what was displayed after my attempt to re-send 
> the dropoff. It failed (obviously), but I?m not sure why it is.
>
> 2020-07-21 16:51:21 CLIENT -> SERVER: STARTTLS
>
> 2020-07-21 16:51:21 SERVER -> CLIENT: 220 2.0.0 SMTP server ready
>
> SMTP Error: Could not connect to SMTP host.
>
> 2020-07-21 16:51:21 CLIENT -> SERVER: QUIT
>
> 2020-07-21 16:51:21 SERVER -> CLIENT:
>
> 2020-07-21 16:51:21 SMTP ERROR: QUIT command failed:
>
> SMTP connect() failed. Sta
>
You are doing TLS encryption over the connection (well, trying to). The 
TLS handshake is failing.
Set the port number to 25 (as you did with your telnet session), and 
switch off any encryption and switch off the username/password as well, 
all in preferences.php.

Basically set it as simply as you can, using no more than what you gave 
the telnet session.

> *_What I have done to troubleshoot_*
>
> *__*
>
> 1.Tried setting the SMTP port within preferences to 25, 465 & 587 ? 
> failed on each re-send
>
> 2.Opened a PowerShell prompt opened a telnet session to our mail 
> server (on port 25) ? success
>
> 3.Sent a simple email from myself to myself ? success (my Outlook 
> client received it right away)
>
> 4.Sent another simple test email but this time from another email 
> address to myself - success
>
Check that you can send an email from yourself to someone outside your 
organization, too.

> This tells me that technically I can connect to the server and send 
> emails. Not sure why ZendTo is failing to connect.
>
>
> Marlon Deerr, Technology Manager
> 416-572-8795(direct) | MDeerr at hshlawyers.com 
> <mailto:MDeerr at hshlawyers.com>
> <https://www.hshlawyers.com>
> <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> 
> <https://twitter.com/hshlawyers> 
> <https://www.facebook.com/HSHPersonalInjuryLawyers/> 
> <https://www.youtube.com/user/hshlawyers> 	3500 - 20 Queen St. W., 
> Toronto, ON M5H 3R3
> Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com 
> <https://www.hshlawyers.com>
>
>
> This Howie Sacks & Henry e-mail is privileged, confidential and 
> subject to copyright. Any unauthorized use or disclosure is prohibited.
>
>
>
> *From:* Jules [mailto:Jules at Zend.To]
> *Sent:* Tuesday, July 21, 2020 7:41 AM
> *To:* Marlon Deerr <MDeerr at hshlawyers.com>
> *Subject:* Re: [ZendTo] Authentication Error - The username or 
> password was incorrect
>
> On 21/07/2020 12:32, Marlon Deerr wrote:
>
>     You did the trick Jules. Removing ?ldaps://? <ldaps://?> from
>     hostname of the authLDAPSServers1 value worked. I thought that it
>     was supposed to be there so I never even thought to remove that.
>
> Yay! You need to add the ldaps:// <ldaps://> when you are encrypting 
> all the traffic to your AD server. Which you're not. In which case it 
> just wants the hostname and nothing else.
>
>
>     Now I just need to work on getting SMTP working. I was working on
>     one problem at a time.
>
> There's a slightly curious but effective way of debugging this setup...
> Send yourself (or a test account) a drop-off.
> Through your ZendTo Outbox, view the drop-off.
> Edit preferences.php to set
> ? 'SMTPdebug' => true,
> (it's normally set to false, it will be near the bottom of the SMTP 
> settings in preferences.php).
> Click on the "Resend Dropoff" button on the web page.
> You will see the entire SMTP conversation happen on the web page output.
> It often only stays there for a few seconds, so you might want to be 
> ready with whatever keys you need to take a screenshot!
>
> Fix the problems and get the "Resend Dropoff" debug output looking 
> right. You should see some "OK" type messages.
>
> Then reset
> ? 'SMTPdebug' => false,
> before trying anything else, such as creating a new drop-off.
> Having that 'SMTPdebug'set to true will break the new drop-off process.
>
> It's usually fairly straightforward to fix. Feel free to send me a 
> screenshot or two if you can't see what's wrong (I've had 30 years 
> experience running enterprise email systems, so what's easy/obvious to 
> me may well not be to you. Sorry about that!).
>
> Cheers,
> Jules.
>
>
>
>
>     Thanks so much for your assistance.
>
>     *Marlon Deerr*, *Technology Manager*
>     416-572-8795(direct)| MDeerr at hshlawyers.com
>     <mailto:MDeerr at hshlawyers.com>
>     <https://www.hshlawyers.com>
>
>     <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/>
>     <https://twitter.com/hshlawyers>
>     <https://www.facebook.com/HSHPersonalInjuryLawyers/>
>     <https://www.youtube.com/user/hshlawyers>
>
>     	
>
>     3500 - 20 Queen St. W., Toronto, ON M5H 3R3
>     Fax: 416-361-0083 | Toll Free: 877-474-5997| www.hshlawyers.com
>     <https://www.hshlawyers.com>
>
>     This Howie Sacks & Henry e-mail is privileged, confidential and
>     subject to copyright. Any unauthorized use or disclosure is
>     prohibited.
>
>     *From:* Jules [mailto:Jules at Zend.To <mailto:Jules at Zend.To>]
>     *Sent:* Tuesday, July 21, 2020 4:02 AM
>     *To:* Marlon Deerr <MDeerr at hshlawyers.com>
>     <mailto:MDeerr at hshlawyers.com>
>     *Subject:* Re: [ZendTo] Authentication Error - The username or
>     password was incorrect
>
>     Marlon,
>
>     Try changing this setting to the one below:
>     'authLDAPServers1'????????? => array('hsh-dc.hsh.local'),
>     What I've done is remove the "ldaps://" <ldaps://> from the
>     hostname of the authLDAPServers1 value.
>
>     If that doesn't fix it, can you send me the exact ldapsearch
>     command you used that worked?
>
>     Cheers,
>     Jules.
>
>
>     On 20/07/2020 20:52, Marlon Deerr wrote:
>
>         Hello Jules,
>
>         Thank you for following up on this issue I?m experiencing. To
>         answer your question, yes, I meant to refer to my AD server
>         not DNS.? As for the ldapsearch utility, yes I am able to
>         successfully show my details when I insert the correct values
>         in the command.? Also, as requested, I have copy/pasted the
>         LDAP section of my preferences.php file for you to take a look at.
>
>         Hopefully, you see something I?m missing.
>
>         *Marlon Deerr*, *Technology Manager*
>         416-572-8795(direct)| MDeerr at hshlawyers.com
>         <mailto:MDeerr at hshlawyers.com>
>         <https://www.hshlawyers.com>
>
>         <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/>
>         <https://twitter.com/hshlawyers>
>         <https://www.facebook.com/HSHPersonalInjuryLawyers/>
>         <https://www.youtube.com/user/hshlawyers>
>
>         	
>
>         3500 - 20 Queen St. W., Toronto, ON M5H 3R3
>         Fax: 416-361-0083 | Toll Free: 877-474-5997|
>         www.hshlawyers.com <https://www.hshlawyers.com>
>
>         This Howie Sacks & Henry e-mail is privileged, confidential
>         and subject to copyright. Any unauthorized use or disclosure
>         is prohibited.
>
>         *From:* Jules [mailto:Jules at Zend.To <mailto:Jules at Zend.To>]
>         *Sent:* Saturday, July 18, 2020 8:03 AM
>         *To:* Marlon Deerr <MDeerr at hshlawyers.com>
>         <mailto:MDeerr at hshlawyers.com>
>         *Subject:* Re: [ZendTo] Authentication Error - The username or
>         password was incorrect
>
>         Marlon,
>
>         On 17/07/2020 22:54, Marlon Deerr wrote:
>
>             Jules,
>
>             No, I didn?t type in < and > characters. I only did that
>             to not show real usernames on my end.? So to be clear, no
>             I did not type in those characters as part of the username
>             when using the /opt/zendto/bin/adduser command. As for
>             certificates, I?m not sure as our DNS server
>
>         I assume you mean your AD server, not your DNS server. DNS
>         should have no impact on this at all.
>
>
>
>
>             is actually managed by our MSP. With that said, when I do
>             run the openssl command, I get the below output.
>
>         That looks like they're not running any encryption on your AD
>         traffic. Okay, but Microsoft are going to mandate encryption
>         on AD traffic very soon. But in the mean time, you should be
>         okay using it unencrypted.
>
>         On zend.to/activedirectory, read section 2 and there is an
>         ldapsearch command. Replacing the necessary bits of that, can
>         you get it to show you your details?
>
>         If you can send me your AD settings from preferences.php (all
>         the LDAP settings whose names end in 1, 2 or 3), I can take a
>         look and suggest an ldapsearch command that should work if
>         your settings are correct.
>
>
>
>
>             As for the log file at /var/log/zendto/zendto.log, if it
>             says Warning: authorization failed for username, does that
>             mean it wasn?t able to read from our AD Server. Not sure
>             how to interpret that because before I ran the upgrade
>             command after applying the latest patch, it seemed as
>             though it was able to read from AD. Now I?m not sure
>             what?s going on.
>
>         It probably did manage to connect to your AD server, but
>         couldn't get any further.
>
>
>
>
>             _Output for _*_openssl s_client -connect
>             your-ad-server.company.com:636_*
>
>         From this output, it looks like you're running AD unencrypted.
>
>         Cheers,
>         Jules.
>
>
>
>
>             CONNECTED(00000003)
>
>             write:errno=104
>
>             ---
>
>             no peer certificate available
>
>             ---
>
>             No client certificate CA names sent
>
>             ---
>
>             SSL handshake has read 0 bytes and written 283 bytes
>
>             Verification: OK
>
>             ---
>
>             New, (NONE), Cipher is (NONE)
>
>             Secure Renegotiation IS NOT supported
>
>             Compression: NONE
>
>             Expansion: NONE
>
>             No ALPN negotiated
>
>             Early data was not sent
>
>             Verify return code: 0 (ok)
>
>             *Marlon Deerr*, *Technology Manager*
>             416-572-8795(direct)| MDeerr at hshlawyers.com
>             <mailto:MDeerr at hshlawyers.com>
>             <https://www.hshlawyers.com>
>
>             <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/>
>             <https://twitter.com/hshlawyers>
>             <https://www.facebook.com/HSHPersonalInjuryLawyers/>
>             <https://www.youtube.com/user/hshlawyers>
>
>             	
>
>             3500 - 20 Queen St. W., Toronto, ON M5H 3R3
>             Fax: 416-361-0083 | Toll Free: 877-474-5997|
>             www.hshlawyers.com <https://www.hshlawyers.com>
>
>             This Howie Sacks & Henry e-mail is privileged,
>             confidential and subject to copyright. Any unauthorized
>             use or disclosure is prohibited.
>
>             *From:* Jules [mailto:Jules at Zend.To <mailto:Jules at Zend.To>]
>             *Sent:* Wednesday, July 15, 2020 12:35 PM
>             *To:* Marlon Deerr <MDeerr at hshlawyers.com>
>             <mailto:MDeerr at hshlawyers.com>; ZendTo Users
>             <zendto at zend.to> <mailto:zendto at zend.to>
>             *Subject:* Re: [ZendTo] Authentication Error - The
>             username or password was incorrect
>
>             Are you actually seeing the < and > characters?
>             You didn't actually type those into the
>             /opt/zendto/bin/adduser command, did you?
>
>             Have a read of the AD troubleshooting steps on
>             zend.to/activedirectory
>
>             Do you know if you're running with a locally-signed
>             certificate on your AD servers?
>
>             Assuming you have the hostname and port number (636
>             usually) of your? AD server, try
>             *openssl s_client -connect your-ad-server.company.com:636*
>
>             That will show you the initial SSL/TLS handshake involving
>             all the certificates.
>             You'll need to Ctrl-C it at the end, but what it prints
>             out should be very useful so you can see exactly what is
>             using which certs.
>
>             Hope that helps,
>             Jules.
>
>             On 15/07/2020 16:50, Marlon Deerr wrote:
>
>                 OK, my user seems to be unlocked now but now I am
>                 getting the following errors below. I must be missing
>                 something else in my setup:
>
>                 Warning: admin authorization failed for <username1>
>
>                 And for other users I still get the following error:
>
>                 Warning: authorization failed for <username2>
>
>                 Note: I believe I added <username1> as an admin.
>
>                 *Marlon Deerr*, *Technology Manager*
>                 416-572-8795(direct)| MDeerr at hshlawyers.com
>                 <mailto:MDeerr at hshlawyers.com>
>                 <https://www.hshlawyers.com>
>
>                 <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/>
>                 <https://twitter.com/hshlawyers>
>                 <https://www.facebook.com/HSHPersonalInjuryLawyers/>
>                 <https://www.youtube.com/user/hshlawyers>
>
>                 	
>
>                 3500 - 20 Queen St. W., Toronto, ON M5H 3R3
>                 Fax: 416-361-0083 | Toll Free: 877-474-5997|
>                 www.hshlawyers.com <https://www.hshlawyers.com>
>
>                 This Howie Sacks & Henry e-mail is privileged,
>                 confidential and subject to copyright. Any
>                 unauthorized use or disclosure is prohibited.
>
>                 *From:* Jules [mailto:Jules at Zend.To
>                 <mailto:Jules at Zend.To>]
>                 *Sent:* Wednesday, July 15, 2020 7:09 AM
>                 *To:* ZendTo Users <zendto at zend.to>
>                 <mailto:zendto at zend.to>
>                 *Cc:* Marlon Deerr <MDeerr at hshlawyers.com>
>                 <mailto:MDeerr at hshlawyers.com>
>                 *Subject:* Re: [ZendTo] Authentication Error - The
>                 username or password was incorrect
>
>                 Marlon,
>
>                 The crucial bit in the log is the "locked-out user" bit.
>
>                 ZendTo has a security feature in it to stop it being
>                 used as a method of brute-force attacking your
>                 accounts from outside.
>                 If the same user has several failed logins in a row,
>                 that user is locked out for the next 24 hours by default.
>
>                 If you can login as an admin user, one of the extra
>                 admin red buttons shows you the locked out users and
>                 lets you reset them.
>
>                 Alternatively, you can unlock all locked users from
>                 the command line with
>                 ??? /opt/zendto/bin/unlockuser -a
>
>                 Cheers,
>                 Jules.
>
>                 On 14/07/2020 18:45, Marlon Deerr via ZendTo wrote:
>
>                     Ok, so I think I finally (or almost finally) got
>                     my AD authentication settings correct.? I have
>                     installed the ldapsearch utility to confirm that
>                     I?m able to successful search the OU where my
>                     users reside, however when I attempt to log in
>                     with a valid user, ZendTo keeps erroring with:
>
>                     Authentication Error
>
>                     The username or password was incorrect
>
>                     I checked the /var/log/zendto/zendto.log and it
>                     says the following:
>
>                     ??.Warning: authorization attempt for locked-out
>                     user <username1>
>
>                     Then when I try logging in as another user, I see
>                     the following in the log
>
>                     ??Warning: authorization failed for <username2>
>
>                     I know that I have both username/password correct
>                     so I must be missing something. Anyone know what
>                     setting I may have applied incorrectly?
>
>
>
>
>
>
>
>                     _______________________________________________
>
>                     ZendTo mailing list
>
>                     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>
>                     http://jul.es/mailman/listinfo/zendto  <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  <http://www.Zend.To>
>
>                 Twitter: @JulesFM
>
>
>
>
>
>
>             Jules
>
>               
>
>             -- 
>
>             Julian Field MEng CEng CITP MBCS MIEEE MACM
>
>               
>
>             'There is silent poetry in the stillness of morning;
>
>               in the calm, the cries & sighs of life sound like gentle music.'
>
>               - @Astro_Wheels
>
>               
>
>             www.Zend.To  <http://www.Zend.To>
>
>             Twitter: @JulesFM
>
>
>
>
>
>         Jules
>
>           
>
>         -- 
>
>         Julian Field MEng CEng CITP MBCS MIEEE MACM
>
>           
>
>         The current UK shipping forecast:
>
>         South Utsire, Forties: Southwesterly veering westerly 3 or 4. Mainly moderate.
>
>         Rain at first. Moderate or poor, becoming good.
>
>           
>
>         www.Zend.To  <http://www.Zend.To>
>
>         Twitter: @JulesFM
>
>
>
>
>     Jules
>
>       
>
>     -- 
>
>     Julian Field MEng CEng CITP MBCS MIEEE MACM
>
>       
>
>     'Every morning when I wake,
>
>       Dear Lord, a little prayer I make,
>
>       O please do keep Thy lovely eye
>
>       On all poor creatures born to die
>
>       
>
>       And every evening at sun-down
>
>       I ask a blessing on the town,
>
>       For whether we last the night or no
>
>       I'm sure is always touch-and-go.
>
>       
>
>       We are not wholly bad or good
>
>       Who live our lives under Milk Wood,
>
>       And Thou, I know, wilt be the first
>
>       To see our best side, not our worst.
>
>       
>
>       O let us see another day!
>
>       Bless us all this night, I pray,
>
>       And to the sun we all will bow
>
>       And say, good-bye - but just for now!'
>
>      ??? - Dylan Thomas
>
>       
>
>     www.Zend.To  <http://www.Zend.To>
>
>     Twitter: @JulesFM
>
>
>
> Jules
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> 'All programs have a desire to be useful' - Tron, 1982
> www.Zend.To  <http://www.Zend.To>
> Twitter: @JulesFM

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Intelligence is quickness to apprehend as distinct from ability,
  which is capacity to act wisely on the thing apprehended.'
  - Alfred North Whitehead

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagee5148c.JPG
Type: image/jpeg
Size: 125353 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image68fc40.JPG
Type: image/jpeg
Size: 7976 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image1bceaa.JPG
Type: image/jpeg
Size: 7843 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0007.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image9de8c6.JPG
Type: image/jpeg
Size: 7268 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0008.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image163859.JPG
Type: image/jpeg
Size: 7059 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0009.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 12435 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0010.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 777 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0011.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 768 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0012.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 756 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0013.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.jpg
Type: image/jpeg
Size: 752 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0014.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.jpg
Type: image/jpeg
Size: 12435 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0015.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.jpg
Type: image/jpeg
Size: 777 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0016.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.jpg
Type: image/jpeg
Size: 768 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0017.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.jpg
Type: image/jpeg
Size: 756 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0018.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image015.jpg
Type: image/jpeg
Size: 752 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/acd18e71/attachment-0019.jpg>

From Jules at Zend.To  Wed Jul 22 09:51:57 2020
From: Jules at Zend.To (Jules)
Date: Wed, 22 Jul 2020 09:51:57 +0100
Subject: [ZendTo] Incorrect drop-off notice within debug message
In-Reply-To: <WM!736e6f486c85152ea5a6fa8f9dc28a10647a42b91703e4698b28e4aa2b44a955cf710a31f4d34ed01970bbe8b37e6db9!@mx.jul.es>
References: <b53c4f1a72ff4c4db6c0ee7642dab2ad@HSH-MAIL.HSH.local>
 <WM!736e6f486c85152ea5a6fa8f9dc28a10647a42b91703e4698b28e4aa2b44a955cf710a31f4d34ed01970bbe8b37e6db9!@mx.jul.es>
Message-ID: <b8a18512-4c72-c998-f653-e99b0c3ad2c5@Zend.To>

I wouldn't read much into the error messages returned when the smtp 
debug flag is on.

On 21/07/2020 23:45, Marlon Deerr wrote:
>
> Jules,
>
> Not sure if this is just my install, but I noticed the following.? 
> Maybe other users can confirm if it happens with them.? While 
> troubleshooting my SMTP settings with the various SMTP ports, I 
> attempted to re-send drop-off and it failed BUT the message still said 
> that ?The drop-off was successfully re-sent to its recipients.
>
> *_Error received with debug mode on_*
>
>
> 	
>
> Mail Error
>
>
> 	
>
> SMTP connect() failed. 
> https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
>
> The drop-off was successfully re-sent to its recipients.
>
>
> Marlon Deerr, Technology Manager
> 416-572-8795(direct) | MDeerr at hshlawyers.com 
> <mailto:MDeerr at hshlawyers.com>
> <https://www.hshlawyers.com>
> <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> 
> <https://twitter.com/hshlawyers> 
> <https://www.facebook.com/HSHPersonalInjuryLawyers/> 
> <https://www.youtube.com/user/hshlawyers> 	3500 - 20 Queen St. W., 
> Toronto, ON M5H 3R3
> Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com 
> <https://www.hshlawyers.com>
>
>
> This Howie Sacks & Henry e-mail is privileged, confidential and 
> subject to copyright. Any unauthorized use or disclosure is prohibited.
>
>
>

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Do not go gentle into that good night,
  Old age should burn and rave at close of day;
  Rage, rage against the dying of the light.
  
  Though wise men at their end know dark is right,
  Because their words had forked no lightning they
  Do not go gentle into that good night.
  
  Good men, the last wave by, crying how bright
  Their frail deeds might have danced in a green bay,
  Rage, rage against the dying of the light.
  
  Wild men who caught and sang the sun in flight,
  And learn, too late, they grieved it on its way,
  Do not go gentle into that good night.
  
  Grave men, near death, who see with blinding sight
  Blind eyes could blaze like meteors and be gay,
  Rage, rage against the dying of the light.
  
  And you, my father, there on the sad height,
  Curse, bless, me now with your fierce tears, I pray.
  Do not go gentle into that good night.
  Rage, rage against the dying of the light.'
                           - Dylan Thomas

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200722/e5ed8403/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagec436cb.JPG
Type: image/jpeg
Size: 125353 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/e5ed8403/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image8b1214.JPG
Type: image/jpeg
Size: 7976 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/e5ed8403/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image6e0d2f.JPG
Type: image/jpeg
Size: 7843 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/e5ed8403/attachment-0007.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image6a6ade.JPG
Type: image/jpeg
Size: 7268 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/e5ed8403/attachment-0008.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imageb94379.JPG
Type: image/jpeg
Size: 7059 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/e5ed8403/attachment-0009.jpe>

From Jules at Zend.To  Wed Jul 22 09:54:55 2020
From: Jules at Zend.To (Jules)
Date: Wed, 22 Jul 2020 09:54:55 +0100
Subject: [ZendTo] Authentication Error - The username or password was
 incorrect
In-Reply-To: <WM!11370fd31152423eaca59e89a406c04ecc88cd65b6cbcefed9fd92f7517ac1e1377a53b47411da75c27005e443580e90!@mx.jul.es>
References: <5bbb4fb4215246b0972b060f5c691d9b@HSH-MAIL.HSH.local>
 <36da1928b55b441c9ba5f1e3fe185f88@HSH-MAIL.HSH.local>
 <WM!f0e79ea6f129bacb925a5a4d0228a3c867e28d502c471a621d8b9bac2457d8742017f4112a12ba759596619ec06b0424!@mx.jul.es>
 <e3508cb1-9e20-2007-3dcb-2c7a0e97446b@Zend.To>
 <WM!9eb58ea76f65561c0e3398715a95feb4b5ddb3606b9ab86af5dc8be794991c68e2849f792af39795fa6052fc2f17157e!@mx.jul.es>
 <473b8aaef8384f248b7c6099939a7dcd@HSH-MAIL.HSH.local>
 <WM!b5b92cd801734e61eb6e0dbd3c89c0c8045e7f0f3ada72c21308719fc69d25c264cdbd39fed66fb7740ee5f02cee7ce9!@mx.jul.es>
 <f3141ccc-0742-4f9e-5705-d0bf150a8155@Zend.To>
 <WM!8dfced315f7584d8a63807730b2547811edc9215423e180d3c3c04a7e66c504886cd24aaf39fe1363f5361445a5650dc!@mx.jul.es>
 <8459aa5af5314062959201fecf68ea23@HSH-MAIL.HSH.local>
 <WM!11370fd31152423eaca59e89a406c04ecc88cd65b6cbcefed9fd92f7517ac1e1377a53b47411da75c27005e443580e90!@mx.jul.es>
Message-ID: <bb03f9ca-9bfe-8fe3-af75-9e12d31e5047@Zend.To>

Also, google "phpmailer Could not connect to SMTP host" and you will 
find lots of helpful articles.

BTW for 99% of users the Installer gets it all right first time. :-)

On 21/07/2020 20:55, Marlon Deerr wrote:
>
> Hey Jules,
>
> Here is a portion of what was displayed after my attempt to re-send 
> the dropoff. It failed (obviously), but I?m not sure why it is.
>
> 2020-07-21 16:51:21 CLIENT -> SERVER: STARTTLS
>
> 2020-07-21 16:51:21 SERVER -> CLIENT: 220 2.0.0 SMTP server ready
>
> SMTP Error: Could not connect to SMTP host.
>
> 2020-07-21 16:51:21 CLIENT -> SERVER: QUIT
>
> 2020-07-21 16:51:21 SERVER -> CLIENT:
>
> 2020-07-21 16:51:21 SMTP ERROR: QUIT command failed:
>
> SMTP connect() failed. Sta
>
> *_What I have done to troubleshoot_*
>
> *__*
>
> 1.Tried setting the SMTP port within preferences to 25, 465 & 587 ? 
> failed on each re-send
>
> 2.Opened a PowerShell prompt opened a telnet session to our mail 
> server (on port 25) ? success
>
> 3.Sent a simple email from myself to myself ? success (my Outlook 
> client received it right away)
>
> 4.Sent another simple test email but this time from another email 
> address to myself - success
>
> This tells me that technically I can connect to the server and send 
> emails. Not sure why ZendTo is failing to connect.
>
>
> Marlon Deerr, Technology Manager
> 416-572-8795(direct) | MDeerr at hshlawyers.com 
> <mailto:MDeerr at hshlawyers.com>
> <https://www.hshlawyers.com>
> <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> 
> <https://twitter.com/hshlawyers> 
> <https://www.facebook.com/HSHPersonalInjuryLawyers/> 
> <https://www.youtube.com/user/hshlawyers> 	3500 - 20 Queen St. W., 
> Toronto, ON M5H 3R3
> Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com 
> <https://www.hshlawyers.com>
>
>
> This Howie Sacks & Henry e-mail is privileged, confidential and 
> subject to copyright. Any unauthorized use or disclosure is prohibited.
>
>
>
> *From:* Jules [mailto:Jules at Zend.To]
> *Sent:* Tuesday, July 21, 2020 7:41 AM
> *To:* Marlon Deerr <MDeerr at hshlawyers.com>
> *Subject:* Re: [ZendTo] Authentication Error - The username or 
> password was incorrect
>
> On 21/07/2020 12:32, Marlon Deerr wrote:
>
>     You did the trick Jules. Removing ?ldaps://? <ldaps://?> from
>     hostname of the authLDAPSServers1 value worked. I thought that it
>     was supposed to be there so I never even thought to remove that.
>
> Yay! You need to add the ldaps:// <ldaps://> when you are encrypting 
> all the traffic to your AD server. Which you're not. In which case it 
> just wants the hostname and nothing else.
>
>
>     Now I just need to work on getting SMTP working. I was working on
>     one problem at a time.
>
> There's a slightly curious but effective way of debugging this setup...
> Send yourself (or a test account) a drop-off.
> Through your ZendTo Outbox, view the drop-off.
> Edit preferences.php to set
> ? 'SMTPdebug' => true,
> (it's normally set to false, it will be near the bottom of the SMTP 
> settings in preferences.php).
> Click on the "Resend Dropoff" button on the web page.
> You will see the entire SMTP conversation happen on the web page output.
> It often only stays there for a few seconds, so you might want to be 
> ready with whatever keys you need to take a screenshot!
>
> Fix the problems and get the "Resend Dropoff" debug output looking 
> right. You should see some "OK" type messages.
>
> Then reset
> ? 'SMTPdebug' => false,
> before trying anything else, such as creating a new drop-off.
> Having that 'SMTPdebug'set to true will break the new drop-off process.
>
> It's usually fairly straightforward to fix. Feel free to send me a 
> screenshot or two if you can't see what's wrong (I've had 30 years 
> experience running enterprise email systems, so what's easy/obvious to 
> me may well not be to you. Sorry about that!).
>
> Cheers,
> Jules.
>
>
>
>
>     Thanks so much for your assistance.
>
>     *Marlon Deerr*, *Technology Manager*
>     416-572-8795(direct)| MDeerr at hshlawyers.com
>     <mailto:MDeerr at hshlawyers.com>
>     <https://www.hshlawyers.com>
>
>     <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/>
>     <https://twitter.com/hshlawyers>
>     <https://www.facebook.com/HSHPersonalInjuryLawyers/>
>     <https://www.youtube.com/user/hshlawyers>
>
>     	
>
>     3500 - 20 Queen St. W., Toronto, ON M5H 3R3
>     Fax: 416-361-0083 | Toll Free: 877-474-5997| www.hshlawyers.com
>     <https://www.hshlawyers.com>
>
>     This Howie Sacks & Henry e-mail is privileged, confidential and
>     subject to copyright. Any unauthorized use or disclosure is
>     prohibited.
>
>     *From:* Jules [mailto:Jules at Zend.To <mailto:Jules at Zend.To>]
>     *Sent:* Tuesday, July 21, 2020 4:02 AM
>     *To:* Marlon Deerr <MDeerr at hshlawyers.com>
>     <mailto:MDeerr at hshlawyers.com>
>     *Subject:* Re: [ZendTo] Authentication Error - The username or
>     password was incorrect
>
>     Marlon,
>
>     Try changing this setting to the one below:
>     'authLDAPServers1'????????? => array('hsh-dc.hsh.local'),
>     What I've done is remove the "ldaps://" <ldaps://> from the
>     hostname of the authLDAPServers1 value.
>
>     If that doesn't fix it, can you send me the exact ldapsearch
>     command you used that worked?
>
>     Cheers,
>     Jules.
>
>
>     On 20/07/2020 20:52, Marlon Deerr wrote:
>
>         Hello Jules,
>
>         Thank you for following up on this issue I?m experiencing. To
>         answer your question, yes, I meant to refer to my AD server
>         not DNS.? As for the ldapsearch utility, yes I am able to
>         successfully show my details when I insert the correct values
>         in the command.? Also, as requested, I have copy/pasted the
>         LDAP section of my preferences.php file for you to take a look at.
>
>         Hopefully, you see something I?m missing.
>
>         *Marlon Deerr*, *Technology Manager*
>         416-572-8795(direct)| MDeerr at hshlawyers.com
>         <mailto:MDeerr at hshlawyers.com>
>         <https://www.hshlawyers.com>
>
>         <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/>
>         <https://twitter.com/hshlawyers>
>         <https://www.facebook.com/HSHPersonalInjuryLawyers/>
>         <https://www.youtube.com/user/hshlawyers>
>
>         	
>
>         3500 - 20 Queen St. W., Toronto, ON M5H 3R3
>         Fax: 416-361-0083 | Toll Free: 877-474-5997|
>         www.hshlawyers.com <https://www.hshlawyers.com>
>
>         This Howie Sacks & Henry e-mail is privileged, confidential
>         and subject to copyright. Any unauthorized use or disclosure
>         is prohibited.
>
>         *From:* Jules [mailto:Jules at Zend.To <mailto:Jules at Zend.To>]
>         *Sent:* Saturday, July 18, 2020 8:03 AM
>         *To:* Marlon Deerr <MDeerr at hshlawyers.com>
>         <mailto:MDeerr at hshlawyers.com>
>         *Subject:* Re: [ZendTo] Authentication Error - The username or
>         password was incorrect
>
>         Marlon,
>
>         On 17/07/2020 22:54, Marlon Deerr wrote:
>
>             Jules,
>
>             No, I didn?t type in < and > characters. I only did that
>             to not show real usernames on my end.? So to be clear, no
>             I did not type in those characters as part of the username
>             when using the /opt/zendto/bin/adduser command. As for
>             certificates, I?m not sure as our DNS server
>
>         I assume you mean your AD server, not your DNS server. DNS
>         should have no impact on this at all.
>
>
>
>
>             is actually managed by our MSP. With that said, when I do
>             run the openssl command, I get the below output.
>
>         That looks like they're not running any encryption on your AD
>         traffic. Okay, but Microsoft are going to mandate encryption
>         on AD traffic very soon. But in the mean time, you should be
>         okay using it unencrypted.
>
>         On zend.to/activedirectory, read section 2 and there is an
>         ldapsearch command. Replacing the necessary bits of that, can
>         you get it to show you your details?
>
>         If you can send me your AD settings from preferences.php (all
>         the LDAP settings whose names end in 1, 2 or 3), I can take a
>         look and suggest an ldapsearch command that should work if
>         your settings are correct.
>
>
>
>
>             As for the log file at /var/log/zendto/zendto.log, if it
>             says Warning: authorization failed for username, does that
>             mean it wasn?t able to read from our AD Server. Not sure
>             how to interpret that because before I ran the upgrade
>             command after applying the latest patch, it seemed as
>             though it was able to read from AD. Now I?m not sure
>             what?s going on.
>
>         It probably did manage to connect to your AD server, but
>         couldn't get any further.
>
>
>
>
>             _Output for _*_openssl s_client -connect
>             your-ad-server.company.com:636_*
>
>         From this output, it looks like you're running AD unencrypted.
>
>         Cheers,
>         Jules.
>
>
>
>
>             CONNECTED(00000003)
>
>             write:errno=104
>
>             ---
>
>             no peer certificate available
>
>             ---
>
>             No client certificate CA names sent
>
>             ---
>
>             SSL handshake has read 0 bytes and written 283 bytes
>
>             Verification: OK
>
>             ---
>
>             New, (NONE), Cipher is (NONE)
>
>             Secure Renegotiation IS NOT supported
>
>             Compression: NONE
>
>             Expansion: NONE
>
>             No ALPN negotiated
>
>             Early data was not sent
>
>             Verify return code: 0 (ok)
>
>             *Marlon Deerr*, *Technology Manager*
>             416-572-8795(direct)| MDeerr at hshlawyers.com
>             <mailto:MDeerr at hshlawyers.com>
>             <https://www.hshlawyers.com>
>
>             <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/>
>             <https://twitter.com/hshlawyers>
>             <https://www.facebook.com/HSHPersonalInjuryLawyers/>
>             <https://www.youtube.com/user/hshlawyers>
>
>             	
>
>             3500 - 20 Queen St. W., Toronto, ON M5H 3R3
>             Fax: 416-361-0083 | Toll Free: 877-474-5997|
>             www.hshlawyers.com <https://www.hshlawyers.com>
>
>             This Howie Sacks & Henry e-mail is privileged,
>             confidential and subject to copyright. Any unauthorized
>             use or disclosure is prohibited.
>
>             *From:* Jules [mailto:Jules at Zend.To <mailto:Jules at Zend.To>]
>             *Sent:* Wednesday, July 15, 2020 12:35 PM
>             *To:* Marlon Deerr <MDeerr at hshlawyers.com>
>             <mailto:MDeerr at hshlawyers.com>; ZendTo Users
>             <zendto at zend.to> <mailto:zendto at zend.to>
>             *Subject:* Re: [ZendTo] Authentication Error - The
>             username or password was incorrect
>
>             Are you actually seeing the < and > characters?
>             You didn't actually type those into the
>             /opt/zendto/bin/adduser command, did you?
>
>             Have a read of the AD troubleshooting steps on
>             zend.to/activedirectory
>
>             Do you know if you're running with a locally-signed
>             certificate on your AD servers?
>
>             Assuming you have the hostname and port number (636
>             usually) of your? AD server, try
>             *openssl s_client -connect your-ad-server.company.com:636*
>
>             That will show you the initial SSL/TLS handshake involving
>             all the certificates.
>             You'll need to Ctrl-C it at the end, but what it prints
>             out should be very useful so you can see exactly what is
>             using which certs.
>
>             Hope that helps,
>             Jules.
>
>             On 15/07/2020 16:50, Marlon Deerr wrote:
>
>                 OK, my user seems to be unlocked now but now I am
>                 getting the following errors below. I must be missing
>                 something else in my setup:
>
>                 Warning: admin authorization failed for <username1>
>
>                 And for other users I still get the following error:
>
>                 Warning: authorization failed for <username2>
>
>                 Note: I believe I added <username1> as an admin.
>
>                 *Marlon Deerr*, *Technology Manager*
>                 416-572-8795(direct)| MDeerr at hshlawyers.com
>                 <mailto:MDeerr at hshlawyers.com>
>                 <https://www.hshlawyers.com>
>
>                 <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/>
>                 <https://twitter.com/hshlawyers>
>                 <https://www.facebook.com/HSHPersonalInjuryLawyers/>
>                 <https://www.youtube.com/user/hshlawyers>
>
>                 	
>
>                 3500 - 20 Queen St. W., Toronto, ON M5H 3R3
>                 Fax: 416-361-0083 | Toll Free: 877-474-5997|
>                 www.hshlawyers.com <https://www.hshlawyers.com>
>
>                 This Howie Sacks & Henry e-mail is privileged,
>                 confidential and subject to copyright. Any
>                 unauthorized use or disclosure is prohibited.
>
>                 *From:* Jules [mailto:Jules at Zend.To
>                 <mailto:Jules at Zend.To>]
>                 *Sent:* Wednesday, July 15, 2020 7:09 AM
>                 *To:* ZendTo Users <zendto at zend.to>
>                 <mailto:zendto at zend.to>
>                 *Cc:* Marlon Deerr <MDeerr at hshlawyers.com>
>                 <mailto:MDeerr at hshlawyers.com>
>                 *Subject:* Re: [ZendTo] Authentication Error - The
>                 username or password was incorrect
>
>                 Marlon,
>
>                 The crucial bit in the log is the "locked-out user" bit.
>
>                 ZendTo has a security feature in it to stop it being
>                 used as a method of brute-force attacking your
>                 accounts from outside.
>                 If the same user has several failed logins in a row,
>                 that user is locked out for the next 24 hours by default.
>
>                 If you can login as an admin user, one of the extra
>                 admin red buttons shows you the locked out users and
>                 lets you reset them.
>
>                 Alternatively, you can unlock all locked users from
>                 the command line with
>                 ??? /opt/zendto/bin/unlockuser -a
>
>                 Cheers,
>                 Jules.
>
>                 On 14/07/2020 18:45, Marlon Deerr via ZendTo wrote:
>
>                     Ok, so I think I finally (or almost finally) got
>                     my AD authentication settings correct.? I have
>                     installed the ldapsearch utility to confirm that
>                     I?m able to successful search the OU where my
>                     users reside, however when I attempt to log in
>                     with a valid user, ZendTo keeps erroring with:
>
>                     Authentication Error
>
>                     The username or password was incorrect
>
>                     I checked the /var/log/zendto/zendto.log and it
>                     says the following:
>
>                     ??.Warning: authorization attempt for locked-out
>                     user <username1>
>
>                     Then when I try logging in as another user, I see
>                     the following in the log
>
>                     ??Warning: authorization failed for <username2>
>
>                     I know that I have both username/password correct
>                     so I must be missing something. Anyone know what
>                     setting I may have applied incorrectly?
>
>
>
>
>
>
>
>                     _______________________________________________
>
>                     ZendTo mailing list
>
>                     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>
>                     http://jul.es/mailman/listinfo/zendto  <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  <http://www.Zend.To>
>
>                 Twitter: @JulesFM
>
>
>
>
>
>
>             Jules
>
>               
>
>             -- 
>
>             Julian Field MEng CEng CITP MBCS MIEEE MACM
>
>               
>
>             'There is silent poetry in the stillness of morning;
>
>               in the calm, the cries & sighs of life sound like gentle music.'
>
>               - @Astro_Wheels
>
>               
>
>             www.Zend.To  <http://www.Zend.To>
>
>             Twitter: @JulesFM
>
>
>
>
>
>         Jules
>
>           
>
>         -- 
>
>         Julian Field MEng CEng CITP MBCS MIEEE MACM
>
>           
>
>         The current UK shipping forecast:
>
>         South Utsire, Forties: Southwesterly veering westerly 3 or 4. Mainly moderate.
>
>         Rain at first. Moderate or poor, becoming good.
>
>           
>
>         www.Zend.To  <http://www.Zend.To>
>
>         Twitter: @JulesFM
>
>
>
>
>     Jules
>
>       
>
>     -- 
>
>     Julian Field MEng CEng CITP MBCS MIEEE MACM
>
>       
>
>     'Every morning when I wake,
>
>       Dear Lord, a little prayer I make,
>
>       O please do keep Thy lovely eye
>
>       On all poor creatures born to die
>
>       
>
>       And every evening at sun-down
>
>       I ask a blessing on the town,
>
>       For whether we last the night or no
>
>       I'm sure is always touch-and-go.
>
>       
>
>       We are not wholly bad or good
>
>       Who live our lives under Milk Wood,
>
>       And Thou, I know, wilt be the first
>
>       To see our best side, not our worst.
>
>       
>
>       O let us see another day!
>
>       Bless us all this night, I pray,
>
>       And to the sun we all will bow
>
>       And say, good-bye - but just for now!'
>
>      ??? - Dylan Thomas
>
>       
>
>     www.Zend.To  <http://www.Zend.To>
>
>     Twitter: @JulesFM
>
>
>
> Jules
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> 'All programs have a desire to be useful' - Tron, 1982
> www.Zend.To  <http://www.Zend.To>
> Twitter: @JulesFM

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'There is one thing stronger than all the armies in the world;
  and that is an idea whose time has come.'

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagee5148c.JPG
Type: image/jpeg
Size: 125353 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image68fc40.JPG
Type: image/jpeg
Size: 7976 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image1bceaa.JPG
Type: image/jpeg
Size: 7843 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0007.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image9de8c6.JPG
Type: image/jpeg
Size: 7268 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0008.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image163859.JPG
Type: image/jpeg
Size: 7059 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0009.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 12435 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0010.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 777 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0011.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 768 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0012.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 756 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0013.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.jpg
Type: image/jpeg
Size: 752 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0014.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.jpg
Type: image/jpeg
Size: 12435 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0015.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.jpg
Type: image/jpeg
Size: 777 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0016.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.jpg
Type: image/jpeg
Size: 768 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0017.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.jpg
Type: image/jpeg
Size: 756 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0018.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image015.jpg
Type: image/jpeg
Size: 752 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200722/7e25eede/attachment-0019.jpg>

From MDeerr at hshlawyers.com  Wed Jul 22 13:33:59 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Wed, 22 Jul 2020 12:33:59 +0000
Subject: [ZendTo] Drop-Off Summaries & Drop-Off Notices still have "ZendTo"
 in body
References: <7e051aa87b26444698a861f306e2cf1b@HSH-MAIL.HSH.local>
Message-ID: <WM!316afd3bef486872c280d4d250e24119db81607f6373999ef785c2c77cd608ceb316627204e7c1805d01a044ad35d6ba!@mx.jul.es>

Hello Jules,

While testing ZendTo, I noticed that whenever I receive a Drop-Off notice or a nightly 24 hour summary, the body of those emails are showing "ZendTo" in the upper right corner. This however is not the case within the ZendTo sight as all ZendTo references seemed to have been replaced with what it set the ServiceTitle variable to within zendto.conf.

Is there another variable I am missing somewhere?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200722/be41dc2d/attachment.html>

From Jules at Zend.To  Wed Jul 22 14:43:15 2020
From: Jules at Zend.To (Jules)
Date: Wed, 22 Jul 2020 14:43:15 +0100
Subject: [ZendTo] Drop-Off Summaries & Drop-Off Notices still have
 "ZendTo" in body
In-Reply-To: <WM!316afd3bef486872c280d4d250e24119db81607f6373999ef785c2c77cd608ceb316627204e7c1805d01a044ad35d6ba!@mx.jul.es>
References: <7e051aa87b26444698a861f306e2cf1b@HSH-MAIL.HSH.local>
 <WM!316afd3bef486872c280d4d250e24119db81607f6373999ef785c2c77cd608ceb316627204e7c1805d01a044ad35d6ba!@mx.jul.es>
Message-ID: <c7b58ee2-db83-6dc3-cc4a-1118cb7ea5f3@Zend.To>

Marlon,

In short, "yes". ;-)

Look in zendto.conf and read the comments above "ServiceEmailLogoFile".

The logo used in emails has to be an image (a lot of email clients are 
*VERY* bad at rendering HTML, particularly Microsoft ones).

Drop your logo (or a screenshot of what appears for your ServiceTitle on 
the website) into
 ??? /opt/zendto/www/images/email/email-logo.png
and then it will use that instead.

Changes to that file will be kept when you apt/yum upgrade.

Cheers,
Jules.

On 22/07/2020 13:33, Marlon Deerr via ZendTo wrote:
>
> Hello Jules,
>
> While testing ZendTo, I noticed that whenever I receive a Drop-Off 
> notice or a nightly 24 hour summary, the body of those emails are 
> showing ?ZendTo? in the upper right corner. This however is not the 
> case within the ZendTo sight as all ZendTo references seemed to have 
> been replaced with what it set the ServiceTitle variable to within 
> zendto.conf.
>
> Is there another variable I am missing somewhere?
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Now I am become Death, the destroyer of worlds.' - J. Robert Oppenheimer

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200722/b4326cb5/attachment.html>

From Jules at Zend.To  Wed Jul 22 14:58:49 2020
From: Jules at Zend.To (Jules)
Date: Wed, 22 Jul 2020 14:58:49 +0100
Subject: [ZendTo] upgrade script and LDAP authentication values
In-Reply-To: <WM!ac996c1ade6bc34b86bb4b56b5cd173031fb18091de99250f657c0b73fac60ef859ae3d68b3d9dac684cf8cf5bf49efc!@mx.jul.es>
References: <272118d8-0f0b-cb98-4c0e-4dd0d2ac50b4@alaska.gov>
 <WM!ac996c1ade6bc34b86bb4b56b5cd173031fb18091de99250f657c0b73fac60ef859ae3d68b3d9dac684cf8cf5bf49efc!@mx.jul.es>
Message-ID: <a588cc8d-fd77-a7e1-1c76-9106f3f9f384@Zend.To>

John,

The upgrade script doesn't know much about comments, except that they 
are the block of lines immediately before a setting in preferences.php 
(and zendto.conf, with a different syntax).
It certainly can't actually parse them to see what you may have 
commented out.

The upgrade script also has no prior knowledge of what settings should 
be there, and what shouldn't. There is no "list of all the possible 
settings". It learns all that for itself, by reading your old 
preferences.php and the newly supplied one.

What's happening is that you are commenting out the only definition of 
'authLDAPStartTLS', for example, so it thinks this is a new setting that 
has just appeared in the very latest preferences.php (and it wasn't set 
in your previous one), so it adds it as a new setting.

But the 1 and only setting for (for example) 'authLDAPStartTLS' won't 
have any effect unless you also have set
 ??? 'authenticator' => 'LDAP',
so I don't quite see what you achieve by commenting them out. It will 
only use the authenticator settings for your chosen authenticator. All 
the others will simply have no effect.

Sorry about the 'authLDAP' naming clash between the LDAP and AD 
authenticators, that's for historic reasons from when I first forked the 
project from udel's "Dropbox" a long time ago in a galaxy far away. And 
yes, they sadly called it Dropbox, nothing to do with the "other" 
Dropbox. So I can't change that now.
The difference is that all the AD settings end with a number (1,2,3) 
whereas the LDAP settings don't.

Leaving the LDAP settings in place will have no effect *at all* on the 
AD authenticator.

Does that help explain the situation?

Cheers,
Jules.

On 21/07/2020 00:00, John Thurston via ZendTo wrote:
> Is there some way for me to designate some values in preferences.php 
> as "Just ignore me, please. Don't try to correct this." ?
>
> With each update, the upgrade script detects my commented out values 
> and does me the service of re-enabling them and supplying default 
> values. I then have to go diff the files, confirm nothing has actually 
> changed, and re-comment the attributes I don't want.
>
> >?? //'authLDAPStartTLS'????? => false,
> >?? //'authLDAPBindDn'??????? => 'o=MyOrganization,uid=MyUser',
> >?? //'authLDAPBindPass'????? => 'SecretPassword',
> >?? //'authLDAPOrganization'? => 'My Organization',
> >?? //'authLDAPUsernameAttr'? => 'uid',
> >?? //'authLDAPEmailAttr'???? => 'mail',
>
> I tried setting each of these to null strings, hoping that might 
> trigger the code to ignore the values and also let the upgrade script 
> leave them unchanged. Bzzzt. I couldn't authenticate.
>
> I understand the difficulty in trying to detect what a customer is 
> trying to do, and how to distinguish "new values" from "intentionally 
> absent values". It is frustrating, though, to have to repeat the same 
> manual steps, potentially missing something, with every update.
>
> Maybe there could be a magic string to denote a line not just as a 
> comment but as a "leave me as a comment" line.
> Maybe triple-slash
> Maybe //!/
>
> Or is there already some way to do this that I haven't figured out?
>
>

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Ensanguining the skies
  How heavily it dies
  Into the west away;
  Past touch and sight and sound
  Not further to be found,
  How hopeless under ground
    Falls the remorseful day.' - A.E.Houseman

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200722/a6872872/attachment.html>

From john.thurston at alaska.gov  Wed Jul 22 17:59:30 2020
From: john.thurston at alaska.gov (John Thurston)
Date: Wed, 22 Jul 2020 08:59:30 -0800
Subject: [ZendTo] upgrade script and LDAP authentication values
In-Reply-To: <WM!07bd423778926c0cd4bd4027dab96413ab12583173910b46d4ffedd4bcb6a8e95253bfa48002f2cf0e397bb402584633!@mx.jul.es>
References: <272118d8-0f0b-cb98-4c0e-4dd0d2ac50b4@alaska.gov>
 <WM!ac996c1ade6bc34b86bb4b56b5cd173031fb18091de99250f657c0b73fac60ef859ae3d68b3d9dac684cf8cf5bf49efc!@mx.jul.es>
 <a588cc8d-fd77-a7e1-1c76-9106f3f9f384@Zend.To>
 <WM!07bd423778926c0cd4bd4027dab96413ab12583173910b46d4ffedd4bcb6a8e95253bfa48002f2cf0e397bb402584633!@mx.jul.es>
 <995dde30-62c0-1f71-4038-2a607e3f880b@alaska.gov>
Message-ID: <WM!dad1407ddef8dae6dd3532dd5fd68662f4f817d8edbd320c4eb4a9a04ca173a7785714e3a8db12f33024d723ec3f6584!@mx.jul.es>

But I _am_ using the LDAP authenticator, and I have those values 
commented out because I don't want them.

The way I see it, the application defines those values as 'not required' 
while the upgrade-script defines those values as 'must be present'. My 
business case is caught in the crack between those two parsing rules. It 
looks like I have options:

A) create and maintain a service account in my directory so these values 
can be defined and the upgrade script will work as expected

B) switch to AD authentication and also implement option (A)

C) write my own post-upgrade script to re-comment these values

I'm definitely leaning towards (C) as that is simple, direct, and easy 
to add to our in-house documentation.

--
Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska

On 7/22/2020 5:58 AM, Jules wrote:
> John,
> 
> The upgrade script doesn't know much about comments, except that they 
> are the block of lines immediately before a setting in preferences.php 
> (and zendto.conf, with a different syntax).
> It certainly can't actually parse them to see what you may have 
> commented out.
> 
> The upgrade script also has no prior knowledge of what settings should 
> be there, and what shouldn't. There is no "list of all the possible 
> settings". It learns all that for itself, by reading your old 
> preferences.php and the newly supplied one.
> 
> What's happening is that you are commenting out the only definition of 
> 'authLDAPStartTLS', for example, so it thinks this is a new setting that 
> has just appeared in the very latest preferences.php (and it wasn't set 
> in your previous one), so it adds it as a new setting.
> 
> But the 1 and only setting for (for example) 'authLDAPStartTLS' won't 
> have any effect unless you also have set
>  ??? 'authenticator' => 'LDAP',
> so I don't quite see what you achieve by commenting them out. It will 
> only use the authenticator settings for your chosen authenticator. All 
> the others will simply have no effect.
> 
> Sorry about the 'authLDAP' naming clash between the LDAP and AD 
> authenticators, that's for historic reasons from when I first forked the 
> project from udel's "Dropbox" a long time ago in a galaxy far away. And 
> yes, they sadly called it Dropbox, nothing to do with the "other" 
> Dropbox. So I can't change that now.
> The difference is that all the AD settings end with a number (1,2,3) 
> whereas the LDAP settings don't.
> 
> Leaving the LDAP settings in place will have no effect *at all* on the 
> AD authenticator.
> 
> Does that help explain the situation?
> 
> Cheers,
> Jules.
> 
> On 21/07/2020 00:00, John Thurston via ZendTo wrote:
>> Is there some way for me to designate some values in preferences.php 
>> as "Just ignore me, please. Don't try to correct this." ?
>>
>> With each update, the upgrade script detects my commented out values 
>> and does me the service of re-enabling them and supplying default 
>> values. I then have to go diff the files, confirm nothing has actually 
>> changed, and re-comment the attributes I don't want.
>>
>> >?? //'authLDAPStartTLS'????? => false,
>> >?? //'authLDAPBindDn'??????? => 'o=MyOrganization,uid=MyUser',
>> >?? //'authLDAPBindPass'????? => 'SecretPassword',
>> >?? //'authLDAPOrganization'? => 'My Organization',
>> >?? //'authLDAPUsernameAttr'? => 'uid',
>> >?? //'authLDAPEmailAttr'???? => 'mail',
>>
>> I tried setting each of these to null strings, hoping that might 
>> trigger the code to ignore the values and also let the upgrade script 
>> leave them unchanged. Bzzzt. I couldn't authenticate.
>>
>> I understand the difficulty in trying to detect what a customer is 
>> trying to do, and how to distinguish "new values" from "intentionally 
>> absent values". It is frustrating, though, to have to repeat the same 
>> manual steps, potentially missing something, with every update.
>>
>> Maybe there could be a magic string to denote a line not just as a 
>> comment but as a "leave me as a comment" line.
>> Maybe triple-slash
>> Maybe //!/
>>
>> Or is there already some way to do this that I haven't figured out?
>>
>>
> 
> Jules
> 
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> 
> 'Ensanguining the skies
>   How heavily it dies
>   Into the west away;
>   Past touch and sight and sound
>   Not further to be found,
>   How hopeless under ground
>     Falls the remorseful day.' - A.E.Houseman
> 
> www.Zend.To
> Twitter: @JulesFM
> 


From Jules at Zend.To  Wed Jul 22 18:08:00 2020
From: Jules at Zend.To (Jules)
Date: Wed, 22 Jul 2020 18:08:00 +0100
Subject: [ZendTo] upgrade script and LDAP authentication values
In-Reply-To: <WM!dad1407ddef8dae6dd3532dd5fd68662f4f817d8edbd320c4eb4a9a04ca173a7785714e3a8db12f33024d723ec3f6584!@mx.jul.es>
References: <272118d8-0f0b-cb98-4c0e-4dd0d2ac50b4@alaska.gov>
 <WM!ac996c1ade6bc34b86bb4b56b5cd173031fb18091de99250f657c0b73fac60ef859ae3d68b3d9dac684cf8cf5bf49efc!@mx.jul.es>
 <a588cc8d-fd77-a7e1-1c76-9106f3f9f384@Zend.To>
 <WM!07bd423778926c0cd4bd4027dab96413ab12583173910b46d4ffedd4bcb6a8e95253bfa48002f2cf0e397bb402584633!@mx.jul.es>
 <995dde30-62c0-1f71-4038-2a607e3f880b@alaska.gov>
 <WM!dad1407ddef8dae6dd3532dd5fd68662f4f817d8edbd320c4eb4a9a04ca173a7785714e3a8db12f33024d723ec3f6584!@mx.jul.es>
Message-ID: <e205bf37-dd8d-009e-760b-b962c7233f06@Zend.To>

John,

On 22/07/2020 17:59, John Thurston via ZendTo wrote:
> But I _am_ using the LDAP authenticator, and I have those values 
> commented out because I don't want them.
But if you are using the LDAP authenticator, surely you have to define 
those values for the authenticator to work at all.
I don't quite see how you are using the LDAP authenticator successfully 
with no settings for it whatsoever.

Jules.


>
> The way I see it, the application defines those values as 'not 
> required' while the upgrade-script defines those values as 'must be 
> present'. My business case is caught in the crack between those two 
> parsing rules. It looks like I have options:
>
> A) create and maintain a service account in my directory so these 
> values can be defined and the upgrade script will work as expected
>
> B) switch to AD authentication and also implement option (A)
>
> C) write my own post-upgrade script to re-comment these values
>
> I'm definitely leaning towards (C) as that is simple, direct, and easy 
> to add to our in-house documentation.
>
> -- 
> Do things because you should, not just because you can.
>
> John Thurston??? 907-465-8591
> John.Thurston at alaska.gov
> Department of Administration
> State of Alaska
>
> On 7/22/2020 5:58 AM, Jules wrote:
>> John,
>>
>> The upgrade script doesn't know much about comments, except that they 
>> are the block of lines immediately before a setting in 
>> preferences.php (and zendto.conf, with a different syntax).
>> It certainly can't actually parse them to see what you may have 
>> commented out.
>>
>> The upgrade script also has no prior knowledge of what settings 
>> should be there, and what shouldn't. There is no "list of all the 
>> possible settings". It learns all that for itself, by reading your 
>> old preferences.php and the newly supplied one.
>>
>> What's happening is that you are commenting out the only definition 
>> of 'authLDAPStartTLS', for example, so it thinks this is a new 
>> setting that has just appeared in the very latest preferences.php 
>> (and it wasn't set in your previous one), so it adds it as a new 
>> setting.
>>
>> But the 1 and only setting for (for example) 'authLDAPStartTLS' won't 
>> have any effect unless you also have set
>> ???? 'authenticator' => 'LDAP',
>> so I don't quite see what you achieve by commenting them out. It will 
>> only use the authenticator settings for your chosen authenticator. 
>> All the others will simply have no effect.
>>
>> Sorry about the 'authLDAP' naming clash between the LDAP and AD 
>> authenticators, that's for historic reasons from when I first forked 
>> the project from udel's "Dropbox" a long time ago in a galaxy far 
>> away. And yes, they sadly called it Dropbox, nothing to do with the 
>> "other" Dropbox. So I can't change that now.
>> The difference is that all the AD settings end with a number (1,2,3) 
>> whereas the LDAP settings don't.
>>
>> Leaving the LDAP settings in place will have no effect *at all* on 
>> the AD authenticator.
>>
>> Does that help explain the situation?
>>
>> Cheers,
>> Jules.
>>
>> On 21/07/2020 00:00, John Thurston via ZendTo wrote:
>>> Is there some way for me to designate some values in preferences.php 
>>> as "Just ignore me, please. Don't try to correct this." ?
>>>
>>> With each update, the upgrade script detects my commented out values 
>>> and does me the service of re-enabling them and supplying default 
>>> values. I then have to go diff the files, confirm nothing has 
>>> actually changed, and re-comment the attributes I don't want.
>>>
>>> >?? //'authLDAPStartTLS'????? => false,
>>> >?? //'authLDAPBindDn'??????? => 'o=MyOrganization,uid=MyUser',
>>> >?? //'authLDAPBindPass'????? => 'SecretPassword',
>>> >?? //'authLDAPOrganization'? => 'My Organization',
>>> >?? //'authLDAPUsernameAttr'? => 'uid',
>>> >?? //'authLDAPEmailAttr'???? => 'mail',
>>>
>>> I tried setting each of these to null strings, hoping that might 
>>> trigger the code to ignore the values and also let the upgrade 
>>> script leave them unchanged. Bzzzt. I couldn't authenticate.
>>>
>>> I understand the difficulty in trying to detect what a customer is 
>>> trying to do, and how to distinguish "new values" from 
>>> "intentionally absent values". It is frustrating, though, to have to 
>>> repeat the same manual steps, potentially missing something, with 
>>> every update.
>>>
>>> Maybe there could be a magic string to denote a line not just as a 
>>> comment but as a "leave me as a comment" line.
>>> Maybe triple-slash
>>> Maybe //!/
>>>
>>> Or is there already some way to do this that I haven't figured out?
>>>
>>>
>>
>> Jules
>>
>> -- 
>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>
>> 'Ensanguining the skies
>> ? How heavily it dies
>> ? Into the west away;
>> ? Past touch and sight and sound
>> ? Not further to be found,
>> ? How hopeless under ground
>> ??? Falls the remorseful day.' - A.E.Houseman
>>
>> www.Zend.To
>> Twitter: @JulesFM
>>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'When I read Shakespeare I am struck with wonder
  That such trivial people should muse and thunder
  In such lovely language.' - D.H. Lawrence

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200722/b3198803/attachment.html>

From Jules at Zend.To  Wed Jul 22 18:11:00 2020
From: Jules at Zend.To (Jules)
Date: Wed, 22 Jul 2020 18:11:00 +0100
Subject: [ZendTo] 
 =?utf-8?q?Potential_change_to_RPM_packaging_=E2=80=94_g?=
 =?utf-8?q?ood/bad_idea=3F?=
In-Reply-To: <7e5655d9-3090-09af-1a93-36122c215a6f@Zend.To>
References: <79bcbb19-25f1-34f4-660c-5825859c2474@Zend.To>
 <WM!624e0ef92e428c349d12870f77b9664929be46f83ecb810c26f7412cdbb899982be96c80f2f8bba82eead57facec23dc!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F42ED0C013@FONEXCH01.sgvwc.local>
 <WM!82f6604dc5a945e99d28f15f007cbf296566a2670ae4a787881a372ffcb31695567421d08dd72fdb1d030845479fac47!@mx.jul.es>
 <7e5655d9-3090-09af-1a93-36122c215a6f@Zend.To>
Message-ID: <1a8c11f1-98a4-6710-b510-b5b84c126462@Zend.To>

Scott,

I have added that to the upgrade script in the new beta release.

Cheers,
Jules.

On 17/07/2020 17:41, Jules via ZendTo wrote:
> Scott,
>
> Yes, I could mention the presence of *.rpmnew and *.rpmsave files in 
> that directory, no problem.
> That would definitely be better than the current status.
>
> Cheers,
> Jules.
>
> On 17/07/2020 17:05, Scott Silva via ZendTo wrote:
>>
>> Is there a way for your upgrade script to mention these files if it 
>> finds them?
>>
>> Not necessarily fix them, but say they are there, and pause for 
>> acknowledgement to ?remind? people?
>>
>> *From:*ZendTo <zendto-bounces at zend.to> *On Behalf Of *Jules via ZendTo
>> *Sent:* Friday, July 17, 2020 9:00 AM
>> *To:* ZendTo Users <zendto at zend.to>
>> *Cc:* Jules <Jules at Zend.To>
>> *Subject:* [ZendTo] Potential change to RPM packaging ? good/bad idea?
>>
>> Folks,
>>
>> This only applies to those using the RPM/yum distribution of ZendTo.
>> It affects people running CentOS or RedHat, for starters.
>>
>> It does not apply to people running ZendTo on Ubuntu or Debian, for 
>> example.
>>
>> Currently, if you modify a *.tpl file (anything in 
>> /opt/zendto/templates) and then upgrade:
>> 1. The new version goes in as *.tpl.rpmnew
>> 2. The rpm command tells you this (but it tells you a lot of things 
>> very fast)
>> 3. You have to go and fix up any customisations, so that the service 
>> works at all.
>>
>> What I could change them to is this:
>> 1. The new version goes in as *.tpl and the old modified one is 
>> renamed to *.tpl.rpmsave
>> 2. The rpm command tells you as before
>> 3. The service works first time, but you then need to re-apply your 
>> customisations.
>>
>> Which approach is better?
>>
>> It's going to be a very noticeable change for any site that regularly 
>> tweaks any of the *.tpl files.
>> But I suspect that is a small proportion of sites.
>>
>> What do you think?
>>
>> Is this change a good idea or a bad one?
>>
>> Please let me know!
>>
>> Jules
>> -- 
>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>> 'No more impressive warning can be given to those who would confine
>>   knowledge and rsearch to what is apparently useful, than the
>>   reflection that conic sections were studied for eighteen hundred
>>   years merely as an abstract science, without regard to any utility
>>   other than to satisfy the craving for knowledge on the part of
>>   mathematicians, and that then at the end of this long period of
>>   abstract study, they were found to be the necessary key with which
>>   to attain the knowledge of the most important laws of nature.'
>>   - Alfred North Whitehead
>> www.Zend.To  <http://www.Zend.To>
>> Twitter: @JulesFM
>>
>> _______________________________________________
>> ZendTo mailing list
>> ZendTo at zend.to
>> http://jul.es/mailman/listinfo/zendto
>
> Jules
>
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
>
> 'Learn from yesterday, live for today,
>   look to tomorrow, rest this afternoon.' - Charles M Schulz
>
> www.Zend.To
> Twitter: @JulesFM
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'The past is supposed to be a place of reference, not a place of
residence! There is a reason why your car has a big windshield and
a small rearview mirror. You are supposed to keep your eyes on where
you are going, and just occasionally check out where you have been.'
   - Willie Jolley

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200722/970a361c/attachment-0001.html>

From Jules at Zend.To  Wed Jul 22 18:19:20 2020
From: Jules at Zend.To (Jules)
Date: Wed, 22 Jul 2020 18:19:20 +0100
Subject: [ZendTo] Beta release 6.04-1 has overhauled "Request a drop-off"
 page
Message-ID: <b13e6a1a-fc65-4274-50fb-8f4df4a6f911@Zend.To>

Folks,

I have just released a new beta 6.04-1.
The main feature of this is I have overhauled the "Request a drop-off" 
page, and added date/time pickers so you can set precise start and end 
times for the request to be valid.

If you have a "Content-Security-Policy" header defined in your Apache 
config, that will need updating to allow "data:" URLs for images.
Fortunately I have written a tool to do that for you, and it is now run 
as part of "upgrade".

For more details, and how to download it, please see the beta page at
 ??? https://zend.to/beta

*PLEASE* can you test the "request a drop-off" page on your favourite 
browsers, and tell me if it all looks okay, or if it doesn't. I've tried 
about 11 different browsers on 3 platforms, but that's only a sample.

The full Change Log for this beta is:
- Overhauled the "request a drop-off" page.
- Added new feature to requests: you can now set a start and end 
date+time. Outside those times, the request won't work.
- Fixed bug where admins logging in via SAML would not see statistics 
button in main menu. Alternative workaround is to list 'authAdmins' 
users in 'authStats' as well.
- Changed 'Content-Security-Policy' header definition in Apache config. 
Exact change is to replace "img-src *" with "img-src data: *", then 
restart Apache. Otherwise the date/time picker in the "Request a 
Drop-off" form will not display correctly.
- Subject in new drop-off form can now only be edited if you are logged in.
- Fixed bug in unlock-user to get all the reporting correct, and fix and 
improve logging. Thanks Marlon!
- Improved "upgrade" command so it warns you if you have *.rpmnew or 
*.dpkg-dist files in your templates dir that you need to move into place 
by hand, as you had modified the previous versions.
- Improved "upgrade" command so it checks you have a 
'Content-Security-Policy' header definition in your Apache config for 
the https ZendTo site. And if so, adds "data:" to the list of valid 
sources of images. Otherwise the date+time pickers in the "request a 
drop-off" page will look messed up. If it doesn't find the header 
definition at all, it suggests the change you need to make.

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200722/44efe4a0/attachment.html>

From john.thurston at alaska.gov  Wed Jul 22 19:01:05 2020
From: john.thurston at alaska.gov (John Thurston)
Date: Wed, 22 Jul 2020 10:01:05 -0800
Subject: [ZendTo] upgrade script and LDAP authentication values
In-Reply-To: <WM!f8fcbe3111ea07307b4c3a04aebdd081cecd533a9a634f41e84f33b99db72808100fd15bc5fe6253e2c2291bfe574469!@mx.jul.es>
References: <272118d8-0f0b-cb98-4c0e-4dd0d2ac50b4@alaska.gov>
 <WM!ac996c1ade6bc34b86bb4b56b5cd173031fb18091de99250f657c0b73fac60ef859ae3d68b3d9dac684cf8cf5bf49efc!@mx.jul.es>
 <a588cc8d-fd77-a7e1-1c76-9106f3f9f384@Zend.To>
 <WM!07bd423778926c0cd4bd4027dab96413ab12583173910b46d4ffedd4bcb6a8e95253bfa48002f2cf0e397bb402584633!@mx.jul.es>
 <995dde30-62c0-1f71-4038-2a607e3f880b@alaska.gov>
 <WM!dad1407ddef8dae6dd3532dd5fd68662f4f817d8edbd320c4eb4a9a04ca173a7785714e3a8db12f33024d723ec3f6584!@mx.jul.es>
 <e205bf37-dd8d-009e-760b-b962c7233f06@Zend.To>
 <WM!f8fcbe3111ea07307b4c3a04aebdd081cecd533a9a634f41e84f33b99db72808100fd15bc5fe6253e2c2291bfe574469!@mx.jul.es>
 <98424f19-ca65-9623-c177-4c06193acd9d@alaska.gov>
Message-ID: <WM!34fa42006b29171c9f84bd048128d9dfce9a2be5c16c1f0e780607d3f4e22dd9891abe01a16b4ef2388b462e6ae47689!@mx.jul.es>


On 7/22/2020 9:08 AM, Jules wrote:
> But if you are using the LDAP authenticator, surely you have to define 
> those values for the authenticator to work at all.
> I don't quite see how you are using the LDAP authenticator successfully 
> with no settings for it whatsoever.

Because our internal directory has all of our users in one OU (which is 
defined as the BaseDN, so no directory searching is required). No 
search, hence no authenticated service account, hence those values are 
commented out.


The relevant output (slightly sanitized) of uncommented lines from 
preferences.cfg

>   'authenticator'         => 'LDAP',
> 
>   'authIMAPServer' => 'mail.soton.ac.uk',
>   'authIMAPDomain' => 'soton.ac.uk',
>   'authIMAPOrganization' => 'University of Southampton',
>   'authIMAPAdmins' => array(),
> 
>   'authLDAPBaseDN'        => 'OU=ourusers,o=state.ak.us',
>   'authLDAPServers'       => array('ldap1.state.ak.us','ldap2.state.ak.us'),
>   'authLDAPAccountSuffix' => '@alaska.gov',
>   'authLDAPUseSSL'        => true,
>   'authLDAPFullName'      => 'givenName sn',
> 
>   'authLDAPServers1'          => array('ad1.ecs.soton.ac.uk','ad2.ecs.soton.ac.uk'),
>   'authLDAPBaseDN1'           => 'OU=users,DC=ecs,DC=soton,DC=ac,DC=uk',
>   'authLDAPAccountSuffix1'    => '@ecs.soton.ac.uk',
>   'authLDAPUseSSL1'           => false,
>   'authLDAPUseTLS1'           => false,
>   'authLDAPBindUser1'         => 'SecretUsername1',
>   'authLDAPBindPass1'         => 'SecretPassword1',
>   'authLDAPOrganization1'     => 'ECS, University of Southampton',
>   'authLDAPUsernameAttribute1' => 'sAMAccountName',
>   'authLDAPServers2'          => array('ad1.soton.ac.uk','ad2.soton.ac.uk'),
>   'authLDAPBaseDN2'           => 'DC=soton,DC=ac,DC=uk',
>   'authLDAPAccountSuffix2'    => '@soton.ac.uk',
>   'authLDAPUseSSL2'           => false,
>   'authLDAPUseTLS2'           => false,
>   'authLDAPBindUser2'         => 'SecretUsername2',
>   'authLDAPBindPass2'         => 'SecretPassword2',
>   'authLDAPOrganization2'     => 'University of Southampton',
>   'authLDAPUsernameAttribute2' => '',
>   'authLDAPServers3'          => array('ad1.example.com','ad2.example.com'),
>   'authLDAPBaseDN3'           => 'DC=example,DC=com',
>   'authLDAPAccountSuffix3'    => '@example.com',
>   'authLDAPUseSSL3'           => false,
>   'authLDAPUseTLS3'           => false,
>   'authLDAPBindUser3'         => 'SecretUsername3',
>   'authLDAPBindPass3'         => 'SecretPassword3',
>   'authLDAPOrganization3'     => 'Example Inc.',
>   'authLDAPUsernameAttribute3' => '',
> 
>   'authMultiAuthenticators' => array('AD', 'Local'),



--
Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska


From MDeerr at hshlawyers.com  Wed Jul 22 20:45:30 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Wed, 22 Jul 2020 19:45:30 +0000
Subject: [ZendTo] Failed Drop Off: you cannot drop-off directories;
 only files
References: <cd4fd50be4ef4d44942ab7de8690a375@HSH-MAIL.HSH.local>
Message-ID: <WM!c9201f86a1d25ae0eb68747b4029e66784547aa880388d96ecc7d5f5ee4227202ae3446c803ad658d31366c9b5843c66!@mx.jul.es>

Anyone know why I am getting this.  I am trying to drop-off a PDF document. I used both the drag'n drop option and also the file browsing option to select the file itself but in both cases, it fails.

I've tried several different files without success.




[cid:image001.png at 01D6603E.E4F79D00]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200722/f7227da0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11934 bytes
Desc: image001.png
URL: <http://jul.es/pipermail/zendto/attachments/20200722/f7227da0/attachment-0001.png>

From Jules at Zend.To  Thu Jul 23 12:51:18 2020
From: Jules at Zend.To (Jules)
Date: Thu, 23 Jul 2020 12:51:18 +0100
Subject: [ZendTo] upgrade script and LDAP authentication values
In-Reply-To: <WM!34fa42006b29171c9f84bd048128d9dfce9a2be5c16c1f0e780607d3f4e22dd9891abe01a16b4ef2388b462e6ae47689!@mx.jul.es>
References: <272118d8-0f0b-cb98-4c0e-4dd0d2ac50b4@alaska.gov>
 <WM!ac996c1ade6bc34b86bb4b56b5cd173031fb18091de99250f657c0b73fac60ef859ae3d68b3d9dac684cf8cf5bf49efc!@mx.jul.es>
 <a588cc8d-fd77-a7e1-1c76-9106f3f9f384@Zend.To>
 <WM!07bd423778926c0cd4bd4027dab96413ab12583173910b46d4ffedd4bcb6a8e95253bfa48002f2cf0e397bb402584633!@mx.jul.es>
 <995dde30-62c0-1f71-4038-2a607e3f880b@alaska.gov>
 <WM!dad1407ddef8dae6dd3532dd5fd68662f4f817d8edbd320c4eb4a9a04ca173a7785714e3a8db12f33024d723ec3f6584!@mx.jul.es>
 <e205bf37-dd8d-009e-760b-b962c7233f06@Zend.To>
 <WM!f8fcbe3111ea07307b4c3a04aebdd081cecd533a9a634f41e84f33b99db72808100fd15bc5fe6253e2c2291bfe574469!@mx.jul.es>
 <98424f19-ca65-9623-c177-4c06193acd9d@alaska.gov>
 <WM!34fa42006b29171c9f84bd048128d9dfce9a2be5c16c1f0e780607d3f4e22dd9891abe01a16b4ef2388b462e6ae47689!@mx.jul.es>
Message-ID: <33659d2e-b725-aed1-fb6b-be9a14fea535@Zend.To>

John,

Please don't comment out settings you don't want to specify (such as the 
service account credentials, etc). Just leave them set to an empty 
string. Then 'upgrade' will be happy.

Cheers,
Jules.

On 22/07/2020 19:01, John Thurston via ZendTo wrote:
>
> On 7/22/2020 9:08 AM, Jules wrote:
>> But if you are using the LDAP authenticator, surely you have to 
>> define those values for the authenticator to work at all.
>> I don't quite see how you are using the LDAP authenticator 
>> successfully with no settings for it whatsoever.
>
> Because our internal directory has all of our users in one OU (which 
> is defined as the BaseDN, so no directory searching is required). No 
> search, hence no authenticated service account, hence those values are 
> commented out.
>
>
> The relevant output (slightly sanitized) of uncommented lines from 
> preferences.cfg
>
>> ? 'authenticator'???????? => 'LDAP',
>>
>> ? 'authIMAPServer' => 'mail.soton.ac.uk',
>> ? 'authIMAPDomain' => 'soton.ac.uk',
>> ? 'authIMAPOrganization' => 'University of Southampton',
>> ? 'authIMAPAdmins' => array(),
>>
>> ? 'authLDAPBaseDN'??????? => 'OU=ourusers,o=state.ak.us',
>> ? 'authLDAPServers'?????? => 
>> array('ldap1.state.ak.us','ldap2.state.ak.us'),
>> ? 'authLDAPAccountSuffix' => '@alaska.gov',
>> ? 'authLDAPUseSSL'??????? => true,
>> ? 'authLDAPFullName'????? => 'givenName sn',
>>
>> ? 'authLDAPServers1'????????? => 
>> array('ad1.ecs.soton.ac.uk','ad2.ecs.soton.ac.uk'),
>> ? 'authLDAPBaseDN1'?????????? => 'OU=users,DC=ecs,DC=soton,DC=ac,DC=uk',
>> ? 'authLDAPAccountSuffix1'??? => '@ecs.soton.ac.uk',
>> ? 'authLDAPUseSSL1'?????????? => false,
>> ? 'authLDAPUseTLS1'?????????? => false,
>> ? 'authLDAPBindUser1'???????? => 'SecretUsername1',
>> ? 'authLDAPBindPass1'???????? => 'SecretPassword1',
>> ? 'authLDAPOrganization1'???? => 'ECS, University of Southampton',
>> ? 'authLDAPUsernameAttribute1' => 'sAMAccountName',
>> ? 'authLDAPServers2'????????? => 
>> array('ad1.soton.ac.uk','ad2.soton.ac.uk'),
>> ? 'authLDAPBaseDN2'?????????? => 'DC=soton,DC=ac,DC=uk',
>> ? 'authLDAPAccountSuffix2'??? => '@soton.ac.uk',
>> ? 'authLDAPUseSSL2'?????????? => false,
>> ? 'authLDAPUseTLS2'?????????? => false,
>> ? 'authLDAPBindUser2'???????? => 'SecretUsername2',
>> ? 'authLDAPBindPass2'???????? => 'SecretPassword2',
>> ? 'authLDAPOrganization2'???? => 'University of Southampton',
>> ? 'authLDAPUsernameAttribute2' => '',
>> ? 'authLDAPServers3'????????? => 
>> array('ad1.example.com','ad2.example.com'),
>> ? 'authLDAPBaseDN3'?????????? => 'DC=example,DC=com',
>> ? 'authLDAPAccountSuffix3'??? => '@example.com',
>> ? 'authLDAPUseSSL3'?????????? => false,
>> ? 'authLDAPUseTLS3'?????????? => false,
>> ? 'authLDAPBindUser3'???????? => 'SecretUsername3',
>> ? 'authLDAPBindPass3'???????? => 'SecretPassword3',
>> ? 'authLDAPOrganization3'???? => 'Example Inc.',
>> ? 'authLDAPUsernameAttribute3' => '',
>>
>> ? 'authMultiAuthenticators' => array('AD', 'Local'),
>
>
>
> -- 
> Do things because you should, not just because you can.
>
> John Thurston??? 907-465-8591
> John.Thurston at alaska.gov
> Department of Administration
> State of Alaska
>
> _______________________________________________
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/233306d8/attachment.html>

From Jules at Zend.To  Thu Jul 23 12:55:50 2020
From: Jules at Zend.To (Jules)
Date: Thu, 23 Jul 2020 12:55:50 +0100
Subject: [ZendTo] Failed Drop Off: you cannot drop-off directories;
 only files
In-Reply-To: <WM!c9201f86a1d25ae0eb68747b4029e66784547aa880388d96ecc7d5f5ee4227202ae3446c803ad658d31366c9b5843c66!@mx.jul.es>
References: <cd4fd50be4ef4d44942ab7de8690a375@HSH-MAIL.HSH.local>
 <WM!c9201f86a1d25ae0eb68747b4029e66784547aa880388d96ecc7d5f5ee4227202ae3446c803ad658d31366c9b5843c66!@mx.jul.es>
Message-ID: <4d57b7d2-4e81-03ff-9330-28e3492bf6cc@Zend.To>

Does it work if you do the exact same steps with a different file?

Cheers,
Jules.

On 22/07/2020 20:45, Marlon Deerr via ZendTo wrote:
>
> Anyone know why I am getting this.? I am trying to drop-off a PDF 
> document. I used both the drag?n drop option and also the file 
> browsing option to select the file itself but in both cases, it fails.
>
> I?ve tried several different files without success.
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

How to stop time: kiss.
How to travel in time: read.
How to escape time: music.
How to feel time: write.
How to release time: breathe.

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/f0bf8a78/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11934 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/f0bf8a78/attachment-0001.png>

From MDeerr at hshlawyers.com  Thu Jul 23 13:46:53 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Thu, 23 Jul 2020 12:46:53 +0000
Subject: [ZendTo] Failed Drop Off: you cannot drop-off directories;
 only files
In-Reply-To: <WM!26536391b088bd68450eacd62122de075498b7cf3e3301616317837fe77a7905c90c0fee071d152b62f3846d265f23b7!@mx.jul.es>
References: <cd4fd50be4ef4d44942ab7de8690a375@HSH-MAIL.HSH.local>
 <WM!c9201f86a1d25ae0eb68747b4029e66784547aa880388d96ecc7d5f5ee4227202ae3446c803ad658d31366c9b5843c66!@mx.jul.es>
 <4d57b7d2-4e81-03ff-9330-28e3492bf6cc@Zend.To>
 <WM!26536391b088bd68450eacd62122de075498b7cf3e3301616317837fe77a7905c90c0fee071d152b62f3846d265f23b7!@mx.jul.es>
 <11dba1c801a14ee6b0e08177f15b0dd1@HSH-MAIL.HSH.local>
Message-ID: <WM!8f0404a5b6019912ad633ba5f1429cac8ace830a4259aacbe9be2855b53f485b298f6371a7659c5ff8f752720cab4764!@mx.jul.es>

Yes, it was happening even when I tried a different file. The funny thing is, I tried again a little later and then it worked AND this was with the same file I was trying to drop off. The only variable I believed changed was the web browser I was using.  Tested again this morning and all seems to be fine now. I am not at the computer I was using previously so I'll need to circle back and perform some more tests on that computer to see if I can recreate the problem.

I'm curious though...your logs record the when and from what IP the drop-off was made. For a future version, any chance you can also capture the browser (and its version)  that was used at the time of drop-off?

From: Jules [mailto:Jules at Zend.To]
Sent: Thursday, July 23, 2020 7:56 AM
To: ZendTo Users <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] Failed Drop Off: you cannot drop-off directories; only files

Does it work if you do the exact same steps with a different file?

Cheers,
Jules.
On 22/07/2020 20:45, Marlon Deerr via ZendTo wrote:
Anyone know why I am getting this.  I am trying to drop-off a PDF document. I used both the drag'n drop option and also the file browsing option to select the file itself but in both cases, it fails.

I've tried several different files without success.




[cid:image001.png at 01D660CD.D0129810]



_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto:ZendTo at zend.to>

http://jul.es/mailman/listinfo/zendto



Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



How to stop time: kiss.

How to travel in time: read.

How to escape time: music.

How to feel time: write.

How to release time: breathe.



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/33a62f04/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11934 bytes
Desc: image001.png
URL: <http://jul.es/pipermail/zendto/attachments/20200723/33a62f04/attachment.png>

From MDeerr at hshlawyers.com  Thu Jul 23 13:50:12 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Thu, 23 Jul 2020 12:50:12 +0000
Subject: [ZendTo] Uploading - Scanning,
 Checksumming... message remains after drop-off
References: <1dfdbc698e964835a7bf664208fc2baa@HSH-MAIL.HSH.local>
Message-ID: <WM!6d65508a11b7ab9ed96d95ae5651fd2160adeefd9ed86ce9e52a6d52fbe2a41db953d398f7064efe2ba2e3e135353e1a!@mx.jul.es>


I'm noticing the following message remaining at times when I perform a drop-off. I'm thinking this "may" be browser related. It is somewhat misleading as the drop-off is actually completed but with the message remaining on the screen, it can confuse a sender. They may think the process was not complete and then re-attempt another drop-off, not realizing that the recipient already received the notice of the drop-off.

I'll continue to test this theory out but I know for sure I have received this more than once on different web browsers.

Anyone else experiencing this?


[cid:image001.png at 01D660CE.46AF6E80]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/35dd327d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14963 bytes
Desc: image001.png
URL: <http://jul.es/pipermail/zendto/attachments/20200723/35dd327d/attachment-0001.png>

From zend.to at neilzone.co.uk  Thu Jul 23 13:51:29 2020
From: zend.to at neilzone.co.uk (zend.to at neilzone.co.uk)
Date: Thu, 23 Jul 2020 13:51:29 +0100
Subject: [ZendTo] Uploading - Scanning,
 Checksumming... message remains after drop-off
In-Reply-To: <WM!2bc674383c7efb3330fb6d16b3eafb9490d2e3a139e01abb3372fd4d6eaa14d547a0445dfb95a3b434572b844b2303e3!@mx.jul.es>
References: <1dfdbc698e964835a7bf664208fc2baa@HSH-MAIL.HSH.local>
 <WM!6d65508a11b7ab9ed96d95ae5651fd2160adeefd9ed86ce9e52a6d52fbe2a41db953d398f7064efe2ba2e3e135353e1a!@mx.jul.es>
 <WM!2bc674383c7efb3330fb6d16b3eafb9490d2e3a139e01abb3372fd4d6eaa14d547a0445dfb95a3b434572b844b2303e3!@mx.jul.es>
 <4D8F1ADD-F03B-4838-B3D4-C7FCC5FF71D7@neilzone.co.uk>
Message-ID: <WM!d0cd981e8490a51f2121298d3dd2716c729e47560936bf3d6a36aa3cab0ef7d45d3dc00f8d7bf8e5d5d17c51776a8508!@mx.jul.es>



> On 23 Jul 2020, at 13:50, Marlon Deerr via ZendTo <zendto at zend.to> wrote:
> 
> I?ll continue to test this theory out but I know for sure I have received this more than once on different web browsers.


Is there anything in your zendto log or apache2 log?


Neil

__________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/1e478333/attachment.html>

From Jules at Zend.To  Thu Jul 23 13:54:11 2020
From: Jules at Zend.To (Jules)
Date: Thu, 23 Jul 2020 13:54:11 +0100
Subject: [ZendTo] Failed Drop Off: you cannot drop-off directories;
 only files
In-Reply-To: <WM!47f1b92dfc4a01b3850337d7d3d20c68ce6b9647b3ce569a241faaa3fb67e464b5c1f5fe341298e45cc74b59707d3636!@mx.jul.es>
References: <cd4fd50be4ef4d44942ab7de8690a375@HSH-MAIL.HSH.local>
 <WM!c9201f86a1d25ae0eb68747b4029e66784547aa880388d96ecc7d5f5ee4227202ae3446c803ad658d31366c9b5843c66!@mx.jul.es>
 <4d57b7d2-4e81-03ff-9330-28e3492bf6cc@Zend.To>
 <WM!26536391b088bd68450eacd62122de075498b7cf3e3301616317837fe77a7905c90c0fee071d152b62f3846d265f23b7!@mx.jul.es>
 <11dba1c801a14ee6b0e08177f15b0dd1@HSH-MAIL.HSH.local>
 <WM!47f1b92dfc4a01b3850337d7d3d20c68ce6b9647b3ce569a241faaa3fb67e464b5c1f5fe341298e45cc74b59707d3636!@mx.jul.es>
Message-ID: <7c0b5556-d424-4254-e236-4e5af809d075@Zend.To>

Marlon,

How much RAM does your ZendTo server have?

Were you trying to encrypt that drop-off? The encryption needs a fair 
bit of RAM (extra 1GB or so).

If you are running with a total of less than about 3GB RAM on the 
server, I would try increasing it to at least that.

And yes, capturing the browser information sounds like a good idea. 
There will be a corresponding entry in your Apache logs, but adding it 
to the ZendTo log as well would save a lot of cross-checking.

Cheers,
Jules.

On 23/07/2020 13:46, Marlon Deerr wrote:
>
> Yes, it was happening even when I tried a different file. The funny 
> thing is, I tried again a little later and then it worked AND this was 
> with the same file I was trying to drop off. The only variable I 
> believed changed was the web browser I was using.? Tested again this 
> morning and all seems to be fine now. I am not at the computer I was 
> using previously so I?ll need to circle back and perform some more 
> tests on that computer to see if I can recreate the problem.
>
> I?m curious though?your logs record the when and from what IP the 
> drop-off was made. For a future version, any chance you can also 
> capture the browser (and its version) ?that was used at the time of 
> drop-off?
>
>
> Marlon Deerr, Technology Manager
> 416-572-8795(direct) | MDeerr at hshlawyers.com 
> <mailto:MDeerr at hshlawyers.com>
> <https://www.hshlawyers.com>
> <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> 
> <https://twitter.com/hshlawyers> 
> <https://www.facebook.com/HSHPersonalInjuryLawyers/> 
> <https://www.youtube.com/user/hshlawyers> 	3500 - 20 Queen St. W., 
> Toronto, ON M5H 3R3
> Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com 
> <https://www.hshlawyers.com>
>
>
> This Howie Sacks & Henry e-mail is privileged, confidential and 
> subject to copyright. Any unauthorized use or disclosure is prohibited.
>
>
>
> *From:* Jules [mailto:Jules at Zend.To]
> *Sent:* Thursday, July 23, 2020 7:56 AM
> *To:* ZendTo Users <zendto at zend.to>
> *Cc:* Marlon Deerr <MDeerr at hshlawyers.com>
> *Subject:* Re: [ZendTo] Failed Drop Off: you cannot drop-off 
> directories; only files
>
> Does it work if you do the exact same steps with a different file?
>
> Cheers,
> Jules.
>
> On 22/07/2020 20:45, Marlon Deerr via ZendTo wrote:
>
>     Anyone know why I am getting this.? I am trying to drop-off a PDF
>     document. I used both the drag?n drop option and also the file
>     browsing option to select the file itself but in both cases, it fails.
>
>     I?ve tried several different files without success.
>
>
>
>     _______________________________________________
>
>     ZendTo mailing list
>
>     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>
>     http://jul.es/mailman/listinfo/zendto  <http://jul.es/mailman/listinfo/zendto>
>
>
>
> Jules
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> How to stop time: kiss.
> How to travel in time: read.
> How to escape time: music.
> How to feel time: write.
> How to release time: breathe.
> www.Zend.To  <http://www.Zend.To>
> Twitter: @JulesFM

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Probability factor of one to one. We have normality. I repeat, we
  have normality. Anything you still can't cope with is therefore
  your own problem.' - Trillian, The Hitch Hikers Guide to the Galaxy

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/3fc33bb5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image9c8470.JPG
Type: image/jpeg
Size: 125353 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/3fc33bb5/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image97cc5a.JPG
Type: image/jpeg
Size: 7976 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/3fc33bb5/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image272c88.JPG
Type: image/jpeg
Size: 7843 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/3fc33bb5/attachment-0007.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagef7130e.JPG
Type: image/jpeg
Size: 7268 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/3fc33bb5/attachment-0008.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image397d97.JPG
Type: image/jpeg
Size: 7059 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/3fc33bb5/attachment-0009.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11934 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/3fc33bb5/attachment-0001.png>

From Jordack at yahoo.com  Thu Jul 23 13:58:06 2020
From: Jordack at yahoo.com (Travis McDugald)
Date: Thu, 23 Jul 2020 08:58:06 -0400
Subject: [ZendTo] Failed Drop Off: you cannot drop-off directories;
 only files
In-Reply-To: <WM!0d3efc2c7433d90ec6d7cb630bcabd97ab2adae88cc895fa889e61d971deb4f9cdc41d8ae0e68f077244564ee5261495!@mx.jul.es>
References: <WM!0d3efc2c7433d90ec6d7cb630bcabd97ab2adae88cc895fa889e61d971deb4f9cdc41d8ae0e68f077244564ee5261495!@mx.jul.es>
 <E0FAE88D-E8A3-4C04-9099-C3060DA56155@yahoo.com>
Message-ID: <WM!d9e3e3793f447d204ddf2a15270697bcbb36b33bc51afe798818dfa2c6c02f42db9c75fc14a05917cbcbd9481757b9af!@mx.jul.es>

We just ran into a similar issue.

Check the free space on the server.  Ours gave the error after running out of space.

Sent from my iPad

> On Jul 23, 2020, at 8:47 AM, Marlon Deerr via ZendTo <zendto at zend.to> wrote:
> 
> ?
> Yes, it was happening even when I tried a different file. The funny thing is, I tried again a little later and then it worked AND this was with the same file I was trying to drop off. The only variable I believed changed was the web browser I was using.  Tested again this morning and all seems to be fine now. I am not at the computer I was using previously so I?ll need to circle back and perform some more tests on that computer to see if I can recreate the problem.
>  
> I?m curious though?your logs record the when and from what IP the drop-off was made. For a future version, any chance you can also capture the browser (and its version)  that was used at the time of drop-off?
>  
> From: Jules [mailto:Jules at Zend.To] 
> Sent: Thursday, July 23, 2020 7:56 AM
> To: ZendTo Users <zendto at zend.to>
> Cc: Marlon Deerr <MDeerr at hshlawyers.com>
> Subject: Re: [ZendTo] Failed Drop Off: you cannot drop-off directories; only files
>  
> Does it work if you do the exact same steps with a different file?
> 
> Cheers,
> Jules.
> 
> On 22/07/2020 20:45, Marlon Deerr via ZendTo wrote:
> Anyone know why I am getting this.  I am trying to drop-off a PDF document. I used both the drag?n drop option and also the file browsing option to select the file itself but in both cases, it fails.
>  
> I?ve tried several different files without success.
>  
>  
>  
>  
> <image001.png>
> 
> 
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
> 
> 
> Jules
>  
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
>  
> How to stop time: kiss.
> How to travel in time: read.
> How to escape time: music.
> How to feel time: write.
> How to release time: breathe.
>  
> www.Zend.To
> Twitter: @JulesFM
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/1169ffbd/attachment.html>

From Jules at Zend.To  Thu Jul 23 14:04:06 2020
From: Jules at Zend.To (Jules)
Date: Thu, 23 Jul 2020 14:04:06 +0100
Subject: [ZendTo] Uploading - Scanning,
 Checksumming... message remains after drop-off
In-Reply-To: <WM!6d65508a11b7ab9ed96d95ae5651fd2160adeefd9ed86ce9e52a6d52fbe2a41db953d398f7064efe2ba2e3e135353e1a!@mx.jul.es>
References: <1dfdbc698e964835a7bf664208fc2baa@HSH-MAIL.HSH.local>
 <WM!6d65508a11b7ab9ed96d95ae5651fd2160adeefd9ed86ce9e52a6d52fbe2a41db953d398f7064efe2ba2e3e135353e1a!@mx.jul.es>
Message-ID: <2e002e00-92a1-4cbf-d069-b0738a4e56b7@Zend.To>

Marlon,

This leads me to think that PHP is getting killed. So in some cases it 
will return an error (your PDF problem), but more likely it will just 
die without returning anything (such as your example below).

Temporarily, add a file called "info.php" to /opt/zendto/www and in it 
put this exact code (apart from the ?SNIP--- lines)
? SNIP ?
<?PHP
phpinfo();
?>
? SNIP ?

Then go to your ZendTo site, with "info.php" on the end of the URL 
instead of anything else.

That will print *loads* of information about your PHP environment.
Check particularly the value of "memory_limit". It should be at least 300M.

Remember to delete the /opt/zendto/www/info.php file again as soon as 
you've finished with it. It would give an attacker an awful lot of 
useful information about your site!

Otherwise, check in your Apache error logs (in either /var/log/apache2 
or /var/log/httpd) for any errors (looking for "PHP Fatal" is often 
quite productive). Apache should have logged why your PHP was killed.

Hope that helps,
Jules.

On 23/07/2020 13:50, Marlon Deerr via ZendTo wrote:
>
> I?m noticing the following message remaining at times when I perform a 
> drop-off. I?m thinking this ?may? be browser related. It is somewhat 
> misleading as the drop-off is actually completed but with the message 
> remaining on the screen, it can confuse a sender. They may think the 
> process was not complete and then re-attempt another drop-off, not 
> realizing that the recipient already received the notice of the drop-off.
>
> I?ll continue to test this theory out but I know for sure I have 
> received this more than once on different web browsers.
>
> Anyone else experiencing this?
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Find a place inside where there's joy, and the joy will burn out
  the pain.' - Joseph Campbell

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/679ae52a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14963 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/679ae52a/attachment-0001.png>

From chris.venter1 at gmail.com  Thu Jul 23 14:30:15 2020
From: chris.venter1 at gmail.com (Chris Venter)
Date: Thu, 23 Jul 2020 14:30:15 +0100
Subject: [ZendTo] Failed Drop Off: you cannot drop-off directories;
 only files
In-Reply-To: <WM!0d0ab6d12bdf36cf69359e56dd4fff93dbcbde07e8a92f2a6058f06a799d0bacfab23c6bf90fc04ca6e5c626a3af65fa!@mx.jul.es>
References: <E0FAE88D-E8A3-4C04-9099-C3060DA56155@yahoo.com>
 <WM!d9e3e3793f447d204ddf2a15270697bcbb36b33bc51afe798818dfa2c6c02f42db9c75fc14a05917cbcbd9481757b9af!@mx.jul.es>
 <WM!0d3efc2c7433d90ec6d7cb630bcabd97ab2adae88cc895fa889e61d971deb4f9cdc41d8ae0e68f077244564ee5261495!@mx.jul.es>
 <WM!0d0ab6d12bdf36cf69359e56dd4fff93dbcbde07e8a92f2a6058f06a799d0bacfab23c6bf90fc04ca6e5c626a3af65fa!@mx.jul.es>
 <CAPgmoWY0K7CJ8ppHvhEuTq0zOnDDNMhC7sYd-qT-Yc9Q1WOj5Q@mail.gmail.com>
Message-ID: <WM!bb03a6b125e3732e63ce31213784e70f9cc229ea2835575c69c6292494fe39d0f14b470fe8bf9d58f53ef3159755a4e9!@mx.jul.es>

I can confirm this happens when out of space on the server same has
happened to us in the past,

On Thu, 23 Jul 2020 at 14:19, Travis McDugald via ZendTo <zendto at zend.to>
wrote:

> We just ran into a similar issue.
>
> Check the free space on the server.  Ours gave the error after running out
> of space.
>
> Sent from my iPad
>
> On Jul 23, 2020, at 8:47 AM, Marlon Deerr via ZendTo <zendto at zend.to>
> wrote:
>
> ?
>
> Yes, it was happening even when I tried a different file. The funny thing
> is, I tried again a little later and then it worked AND this was with the
> same file I was trying to drop off. The only variable I believed changed
> was the web browser I was using.  Tested again this morning and all seems
> to be fine now. I am not at the computer I was using previously so I?ll
> need to circle back and perform some more tests on that computer to see if
> I can recreate the problem.
>
>
>
> I?m curious though?your logs record the when and from what IP the drop-off
> was made. For a future version, any chance you can also capture the browser
> (and its version)  that was used at the time of drop-off?
>
>
>
> *From:* Jules [mailto:Jules at Zend.To]
> *Sent:* Thursday, July 23, 2020 7:56 AM
> *To:* ZendTo Users <zendto at zend.to>
> *Cc:* Marlon Deerr <MDeerr at hshlawyers.com>
> *Subject:* Re: [ZendTo] Failed Drop Off: you cannot drop-off directories;
> only files
>
>
>
> Does it work if you do the exact same steps with a different file?
>
> Cheers,
> Jules.
>
> On 22/07/2020 20:45, Marlon Deerr via ZendTo wrote:
>
> Anyone know why I am getting this.  I am trying to drop-off a PDF
> document. I used both the drag?n drop option and also the file browsing
> option to select the file itself but in both cases, it fails.
>
>
>
> I?ve tried several different files without success.
>
>
>
>
>
>
>
>
>
> <image001.png>
>
>
>
> _______________________________________________
>
> ZendTo mailing list
>
> ZendTo at zend.to
>
> http://jul.es/mailman/listinfo/zendto
>
>
>
> Jules
>
>
>
> --
>
> Julian Field MEng CEng CITP MBCS MIEEE MACM
>
>
>
> How to stop time: kiss.
>
> How to travel in time: read.
>
> How to escape time: music.
>
> How to feel time: write.
>
> How to release time: breathe.
>
>
>
> www.Zend.To
>
> Twitter: @JulesFM
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/79872477/attachment.html>

From MDeerr at hshlawyers.com  Thu Jul 23 14:34:16 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Thu, 23 Jul 2020 13:34:16 +0000
Subject: [ZendTo] Failed Drop Off: you cannot drop-off directories;
 only files
In-Reply-To: <WM!a8f4b999f0463ce7f4771e87eae53b7a0661453b524e69cf7f411d0faab4b59928ac0802b8d755c916a5eb586ae5d764!@mx.jul.es>
References: <E0FAE88D-E8A3-4C04-9099-C3060DA56155@yahoo.com>
 <WM!d9e3e3793f447d204ddf2a15270697bcbb36b33bc51afe798818dfa2c6c02f42db9c75fc14a05917cbcbd9481757b9af!@mx.jul.es>
 <WM!0d3efc2c7433d90ec6d7cb630bcabd97ab2adae88cc895fa889e61d971deb4f9cdc41d8ae0e68f077244564ee5261495!@mx.jul.es>
 <WM!0d0ab6d12bdf36cf69359e56dd4fff93dbcbde07e8a92f2a6058f06a799d0bacfab23c6bf90fc04ca6e5c626a3af65fa!@mx.jul.es>
 <CAPgmoWY0K7CJ8ppHvhEuTq0zOnDDNMhC7sYd-qT-Yc9Q1WOj5Q@mail.gmail.com>
 <WM!bb03a6b125e3732e63ce31213784e70f9cc229ea2835575c69c6292494fe39d0f14b470fe8bf9d58f53ef3159755a4e9!@mx.jul.es>
 <WM!a8f4b999f0463ce7f4771e87eae53b7a0661453b524e69cf7f411d0faab4b59928ac0802b8d755c916a5eb586ae5d764!@mx.jul.es>
 <eef994dd6de140299dbeec950b167e4e@HSH-MAIL.HSH.local>
Message-ID: <WM!acffabe2bd28923e78b7df2edfb94776466f0a8cdd3fa4f1d5d342731aba14c9237f4a6695e403aaf73e126db15dee80!@mx.jul.es>

Interesting?.I know for sure I am not out of space on my server as I have allocated a lot and users haven?t even begun using the service. Memory is also not an issue as well.  I allocated 16GB. I know that?s overkill. Just haven?t gotten around to reducing that.



From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Chris Venter via ZendTo
Sent: Thursday, July 23, 2020 9:30 AM
To: ZendTo Users <zendto at zend.to>
Cc: Chris Venter <chris.venter1 at gmail.com>
Subject: Re: [ZendTo] Failed Drop Off: you cannot drop-off directories; only files

I can confirm this happens when out of space on the server same has happened to us in the past,

On Thu, 23 Jul 2020 at 14:19, Travis McDugald via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> wrote:
We just ran into a similar issue.

Check the free space on the server.  Ours gave the error after running out of space.
Sent from my iPad


On Jul 23, 2020, at 8:47 AM, Marlon Deerr via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> wrote:
?
Yes, it was happening even when I tried a different file. The funny thing is, I tried again a little later and then it worked AND this was with the same file I was trying to drop off. The only variable I believed changed was the web browser I was using.  Tested again this morning and all seems to be fine now. I am not at the computer I was using previously so I?ll need to circle back and perform some more tests on that computer to see if I can recreate the problem.

I?m curious though?your logs record the when and from what IP the drop-off was made. For a future version, any chance you can also capture the browser (and its version)  that was used at the time of drop-off?

From: Jules [mailto:Jules at Zend.To<mailto:Jules at Zend.To>]
Sent: Thursday, July 23, 2020 7:56 AM
To: ZendTo Users <zendto at zend.to<mailto:zendto at zend.to>>
Cc: Marlon Deerr <MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>>
Subject: Re: [ZendTo] Failed Drop Off: you cannot drop-off directories; only files

Does it work if you do the exact same steps with a different file?

Cheers,
Jules.
On 22/07/2020 20:45, Marlon Deerr via ZendTo wrote:
Anyone know why I am getting this.  I am trying to drop-off a PDF document. I used both the drag?n drop option and also the file browsing option to select the file itself but in both cases, it fails.

I?ve tried several different files without success.




<image001.png>


_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto:ZendTo at zend.to>

http://jul.es/mailman/listinfo/zendto


Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



How to stop time: kiss.

How to travel in time: read.

How to escape time: music.

How to feel time: write.

How to release time: breathe.



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
_______________________________________________
ZendTo mailing list
ZendTo at zend.to<mailto:ZendTo at zend.to>
http://jul.es/mailman/listinfo/zendto
_______________________________________________
ZendTo mailing list
ZendTo at zend.to<mailto:ZendTo at zend.to>
http://jul.es/mailman/listinfo/zendto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/b5a16ccf/attachment-0001.html>

From Jules at Zend.To  Thu Jul 23 14:35:39 2020
From: Jules at Zend.To (Jules)
Date: Thu, 23 Jul 2020 14:35:39 +0100
Subject: [ZendTo] Failed Drop Off: you cannot drop-off directories;
 only files
In-Reply-To: <WM!acffabe2bd28923e78b7df2edfb94776466f0a8cdd3fa4f1d5d342731aba14c9237f4a6695e403aaf73e126db15dee80!@mx.jul.es>
References: <E0FAE88D-E8A3-4C04-9099-C3060DA56155@yahoo.com>
 <WM!d9e3e3793f447d204ddf2a15270697bcbb36b33bc51afe798818dfa2c6c02f42db9c75fc14a05917cbcbd9481757b9af!@mx.jul.es>
 <WM!0d3efc2c7433d90ec6d7cb630bcabd97ab2adae88cc895fa889e61d971deb4f9cdc41d8ae0e68f077244564ee5261495!@mx.jul.es>
 <WM!0d0ab6d12bdf36cf69359e56dd4fff93dbcbde07e8a92f2a6058f06a799d0bacfab23c6bf90fc04ca6e5c626a3af65fa!@mx.jul.es>
 <CAPgmoWY0K7CJ8ppHvhEuTq0zOnDDNMhC7sYd-qT-Yc9Q1WOj5Q@mail.gmail.com>
 <WM!bb03a6b125e3732e63ce31213784e70f9cc229ea2835575c69c6292494fe39d0f14b470fe8bf9d58f53ef3159755a4e9!@mx.jul.es>
 <WM!a8f4b999f0463ce7f4771e87eae53b7a0661453b524e69cf7f411d0faab4b59928ac0802b8d755c916a5eb586ae5d764!@mx.jul.es>
 <eef994dd6de140299dbeec950b167e4e@HSH-MAIL.HSH.local>
 <WM!acffabe2bd28923e78b7df2edfb94776466f0a8cdd3fa4f1d5d342731aba14c9237f4a6695e403aaf73e126db15dee80!@mx.jul.es>
Message-ID: <3cebd347-483d-d1e9-fc6d-f4fed99c91e7@Zend.To>

But is that space in the right place?

Please do the command "df -h" and send us the output.

Cheers,
Jules.

On 23/07/2020 14:34, Marlon Deerr via ZendTo wrote:
>
> Interesting?.I know for sure I am not out of space on my server as I 
> have allocated a lot and users haven?t even begun using the service. 
> Memory is also not an issue as well.? I allocated 16GB. I know that?s 
> overkill. Just haven?t gotten around to reducing that.
>
> *From:*ZendTo [mailto:zendto-bounces at zend.to] *On Behalf Of *Chris 
> Venter via ZendTo
> *Sent:* Thursday, July 23, 2020 9:30 AM
> *To:* ZendTo Users <zendto at zend.to>
> *Cc:* Chris Venter <chris.venter1 at gmail.com>
> *Subject:* Re: [ZendTo] Failed Drop Off: you cannot drop-off 
> directories; only files
>
> I can confirm this happens when out of space on the server same has 
> happened to us in the past,
>
> On Thu, 23 Jul 2020 at 14:19, Travis McDugald via ZendTo 
> <zendto at zend.to <mailto:zendto at zend.to>> wrote:
>
>     We just ran into a similar issue.
>
>     Check the free space on the server.? Ours gave the error after
>     running out of space.
>
>     Sent from my iPad
>
>
>
>         On Jul 23, 2020, at 8:47 AM, Marlon Deerr via ZendTo
>         <zendto at zend.to <mailto:zendto at zend.to>> wrote:
>
>         ?
>
>         Yes, it was happening even when I tried a different file. The
>         funny thing is, I tried again a little later and then it
>         worked AND this was with the same file I was trying to drop
>         off. The only variable I believed changed was the web browser
>         I was using.? Tested again this morning and all seems to be
>         fine now. I am not at the computer I was using previously so
>         I?ll need to circle back and perform some more tests on that
>         computer to see if I can recreate the problem.
>
>         I?m curious though?your logs record the when and from what IP
>         the drop-off was made. For a future version, any chance you
>         can also capture the browser (and its version) ?that was used
>         at the time of drop-off?
>
>         *From:* Jules [mailto:Jules at Zend.To <mailto:Jules at Zend.To>]
>         *Sent:* Thursday, July 23, 2020 7:56 AM
>         *To:* ZendTo Users <zendto at zend.to <mailto:zendto at zend.to>>
>         *Cc:* Marlon Deerr <MDeerr at hshlawyers.com
>         <mailto:MDeerr at hshlawyers.com>>
>         *Subject:* Re: [ZendTo] Failed Drop Off: you cannot drop-off
>         directories; only files
>
>         Does it work if you do the exact same steps with a different file?
>
>         Cheers,
>         Jules.
>
>         On 22/07/2020 20:45, Marlon Deerr via ZendTo wrote:
>
>             Anyone know why I am getting this.? I am trying to
>             drop-off a PDF document. I used both the drag?n drop
>             option and also the file browsing option to select the
>             file itself but in both cases, it fails.
>
>             I?ve tried several different files without success.
>
>             <image001.png>
>
>             _______________________________________________
>
>             ZendTo mailing list
>
>             ZendTo at zend.to  <mailto:ZendTo at zend.to>
>
>             http://jul.es/mailman/listinfo/zendto  <http://jul.es/mailman/listinfo/zendto>
>
>         Jules
>
>           
>
>         -- 
>
>         Julian Field MEng CEng CITP MBCS MIEEE MACM
>
>           
>
>         How to stop time: kiss.
>
>         How to travel in time: read.
>
>         How to escape time: music.
>
>         How to feel time: write.
>
>         How to release time: breathe.
>
>           
>
>         www.Zend.To  <http://www.Zend.To>
>
>         Twitter: @JulesFM
>
>         _______________________________________________
>         ZendTo mailing list
>         ZendTo at zend.to <mailto:ZendTo at zend.to>
>         http://jul.es/mailman/listinfo/zendto
>         <http://jul.es/mailman/listinfo/zendto>
>
>     _______________________________________________
>     ZendTo mailing list
>     ZendTo at zend.to <mailto:ZendTo at zend.to>
>     http://jul.es/mailman/listinfo/zendto
>     <http://jul.es/mailman/listinfo/zendto>
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Every morning when I wake,
  Dear Lord, a little prayer I make,
  O please do keep Thy lovely eye
  On all poor creatures born to die

  And every evening at sun-down
  I ask a blessing on the town,
  For whether we last the night or no
  I'm sure is always touch-and-go.

  We are not wholly bad or good
  Who live our lives under Milk Wood,
  And Thou, I know, wilt be the first
  To see our best side, not our worst.

  O let us see another day!
  Bless us all this night, I pray,
  And to the sun we all will bow
  And say, good-bye - but just for now!'
     - Dylan Thomas

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/1f124ebd/attachment.html>

From mailinglists at pcfreak.de  Thu Jul 23 15:25:29 2020
From: mailinglists at pcfreak.de (Der PCFreak)
Date: Thu, 23 Jul 2020 16:25:29 +0200
Subject: [ZendTo] Uploading - Scanning,
 Checksumming... message remains after drop-off
In-Reply-To: <WM!2bc674383c7efb3330fb6d16b3eafb9490d2e3a139e01abb3372fd4d6eaa14d547a0445dfb95a3b434572b844b2303e3!@mx.jul.es>
References: <1dfdbc698e964835a7bf664208fc2baa@HSH-MAIL.HSH.local>
 <WM!6d65508a11b7ab9ed96d95ae5651fd2160adeefd9ed86ce9e52a6d52fbe2a41db953d398f7064efe2ba2e3e135353e1a!@mx.jul.es>
 <WM!2bc674383c7efb3330fb6d16b3eafb9490d2e3a139e01abb3372fd4d6eaa14d547a0445dfb95a3b434572b844b2303e3!@mx.jul.es>
 <638026ba-624b-d3be-2a8f-fa249dffddc1@pcfreak.de>
Message-ID: <WM!60435a379657aca346a15ca338e4637e3cffcb283ef4201b1f88eba46787d6ddf8efc3d15aeafb48d24886a0b1ce7c87!@mx.jul.es>

Hi Marlon,


I had similar issues. The problem in my case was, that the local 
Anti-Virus transparently went between the client and my ZendTo server. 
It immediately picked up the file(s) completely and tried to scan them 
all locally and then did the request to ZendTo which totally messed up 
everything. In my case we created and exclusion for the internal IP and 
the internal fqdn of the ZendTo system from the Antivirus-Webprotection 
which was Sophos in our case. Then it worked as expected.

Maybe you have a similar problem and maybe you find this info useful. If 
not just ignore my mail.

Regards

Peter

On 23/07/2020 14:50, Marlon Deerr via ZendTo wrote:
>
> I?m noticing the following message remaining at times when I perform a 
> drop-off. I?m thinking this ?may? be browser related. It is somewhat 
> misleading as the drop-off is actually completed but with the message 
> remaining on the screen, it can confuse a sender. They may think the 
> process was not complete and then re-attempt another drop-off, not 
> realizing that the recipient already received the notice of the drop-off.
>
> I?ll continue to test this theory out but I know for sure I have 
> received this more than once on different web browsers.
>
> Anyone else experiencing this?
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/6db4d764/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14963 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/6db4d764/attachment-0001.png>

From mailinglists at pcfreak.de  Thu Jul 23 15:28:00 2020
From: mailinglists at pcfreak.de (Der PCFreak)
Date: Thu, 23 Jul 2020 16:28:00 +0200
Subject: [ZendTo] Failed Drop Off: you cannot drop-off directories;
 only files
In-Reply-To: <WM!8f66d755c12426217a16c5ac8dde8dd5602f024d1ef5530e12c23104bd22b8d374805ed4dcdd328a2513a43f5eca5bb0!@mx.jul.es>
References: <cd4fd50be4ef4d44942ab7de8690a375@HSH-MAIL.HSH.local>
 <WM!c9201f86a1d25ae0eb68747b4029e66784547aa880388d96ecc7d5f5ee4227202ae3446c803ad658d31366c9b5843c66!@mx.jul.es>
 <WM!8f66d755c12426217a16c5ac8dde8dd5602f024d1ef5530e12c23104bd22b8d374805ed4dcdd328a2513a43f5eca5bb0!@mx.jul.es>
 <6516a623-8e91-7d43-b825-58a460692425@pcfreak.de>
Message-ID: <WM!2af67efdc902a25e865df6bdb95c3484531e5ba8e0a46753d58f5e62752f7f948b482c629e5257d6a99521d07fb37285!@mx.jul.es>

Hi,

just out of curiosity, try to disable the local Anti-virus, 
webprotection, whatever and retry.
You wrote, switching browser brought success. This can be the case AV is 
the cause but it lags full integration to the browser you had success with.

Kind regards

Peter

On 22/07/2020 21:45, Marlon Deerr via ZendTo wrote:
>
> Anyone know why I am getting this.? I am trying to drop-off a PDF 
> document. I used both the drag?n drop option and also the file 
> browsing option to select the file itself but in both cases, it fails.
>
> I?ve tried several different files without success.
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/48354b48/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11934 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/48354b48/attachment.png>

From Jules at Zend.To  Thu Jul 23 15:56:21 2020
From: Jules at Zend.To (Jules)
Date: Thu, 23 Jul 2020 15:56:21 +0100
Subject: [ZendTo] Calling all translators !!
Message-ID: <c85befa7-a607-e841-98d9-ff74e8ae04c1@Zend.To>

Folks,

In the new beta, there are some new (and a few updated) phrases that 
need translating.

Please can you take a look at the ones in your language that are marked 
"fuzzy" as well as the new phrases. Some of the "fuzzy" matches are now 
definitely wrong.

Many thanks indeed!

Cheers,

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Think globally, act locally.' - Friends of the Earth

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/96c31986/attachment.html>

From MDeerr at hshlawyers.com  Thu Jul 23 16:03:10 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Thu, 23 Jul 2020 15:03:10 +0000
Subject: [ZendTo] Failed Drop Off: you cannot drop-off directories;
 only files
In-Reply-To: <WM!a7b90706608aafb16c8295cc2a7b4ee2b26beaa72ebe441716bc439d9b160070af655d59772e4b361fcfdd73994306a5!@mx.jul.es>
References: <E0FAE88D-E8A3-4C04-9099-C3060DA56155@yahoo.com>
 <WM!d9e3e3793f447d204ddf2a15270697bcbb36b33bc51afe798818dfa2c6c02f42db9c75fc14a05917cbcbd9481757b9af!@mx.jul.es>
 <WM!0d3efc2c7433d90ec6d7cb630bcabd97ab2adae88cc895fa889e61d971deb4f9cdc41d8ae0e68f077244564ee5261495!@mx.jul.es>
 <WM!0d0ab6d12bdf36cf69359e56dd4fff93dbcbde07e8a92f2a6058f06a799d0bacfab23c6bf90fc04ca6e5c626a3af65fa!@mx.jul.es>
 <CAPgmoWY0K7CJ8ppHvhEuTq0zOnDDNMhC7sYd-qT-Yc9Q1WOj5Q@mail.gmail.com>
 <WM!bb03a6b125e3732e63ce31213784e70f9cc229ea2835575c69c6292494fe39d0f14b470fe8bf9d58f53ef3159755a4e9!@mx.jul.es>
 <WM!a8f4b999f0463ce7f4771e87eae53b7a0661453b524e69cf7f411d0faab4b59928ac0802b8d755c916a5eb586ae5d764!@mx.jul.es>
 <eef994dd6de140299dbeec950b167e4e@HSH-MAIL.HSH.local>
 <WM!acffabe2bd28923e78b7df2edfb94776466f0a8cdd3fa4f1d5d342731aba14c9237f4a6695e403aaf73e126db15dee80!@mx.jul.es>
 <3cebd347-483d-d1e9-fc6d-f4fed99c91e7@Zend.To>
 <WM!a7b90706608aafb16c8295cc2a7b4ee2b26beaa72ebe441716bc439d9b160070af655d59772e4b361fcfdd73994306a5!@mx.jul.es>
 <b81ed3be94154c7098740480ee96b107@HSH-MAIL.HSH.local>
Message-ID: <WM!e2e3d0a29c9f06a94e81c80b88b12cb80b067747b75b6e46133726910ac2cc5456beee61e70ffe88b38810428e260d93!@mx.jul.es>

Here is my output for ?df ?h?

[cid:image001.png at 01D660E0.DA353830]

From: Jules [mailto:Jules at Zend.To]
Sent: Thursday, July 23, 2020 9:36 AM
To: ZendTo Users <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] Failed Drop Off: you cannot drop-off directories; only files

But is that space in the right place?

Please do the command "df -h" and send us the output.

Cheers,
Jules.
On 23/07/2020 14:34, Marlon Deerr via ZendTo wrote:
Interesting?.I know for sure I am not out of space on my server as I have allocated a lot and users haven?t even begun using the service. Memory is also not an issue as well.  I allocated 16GB. I know that?s overkill. Just haven?t gotten around to reducing that.



From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Chris Venter via ZendTo
Sent: Thursday, July 23, 2020 9:30 AM
To: ZendTo Users <zendto at zend.to><mailto:zendto at zend.to>
Cc: Chris Venter <chris.venter1 at gmail.com><mailto:chris.venter1 at gmail.com>
Subject: Re: [ZendTo] Failed Drop Off: you cannot drop-off directories; only files

I can confirm this happens when out of space on the server same has happened to us in the past,

On Thu, 23 Jul 2020 at 14:19, Travis McDugald via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> wrote:
We just ran into a similar issue.

Check the free space on the server.  Ours gave the error after running out of space.
Sent from my iPad



On Jul 23, 2020, at 8:47 AM, Marlon Deerr via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> wrote:
?
Yes, it was happening even when I tried a different file. The funny thing is, I tried again a little later and then it worked AND this was with the same file I was trying to drop off. The only variable I believed changed was the web browser I was using.  Tested again this morning and all seems to be fine now. I am not at the computer I was using previously so I?ll need to circle back and perform some more tests on that computer to see if I can recreate the problem.

I?m curious though?your logs record the when and from what IP the drop-off was made. For a future version, any chance you can also capture the browser (and its version)  that was used at the time of drop-off?

From: Jules [mailto:Jules at Zend.To<mailto:Jules at Zend.To>]
Sent: Thursday, July 23, 2020 7:56 AM
To: ZendTo Users <zendto at zend.to<mailto:zendto at zend.to>>
Cc: Marlon Deerr <MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>>
Subject: Re: [ZendTo] Failed Drop Off: you cannot drop-off directories; only files

Does it work if you do the exact same steps with a different file?

Cheers,
Jules.
On 22/07/2020 20:45, Marlon Deerr via ZendTo wrote:
Anyone know why I am getting this.  I am trying to drop-off a PDF document. I used both the drag?n drop option and also the file browsing option to select the file itself but in both cases, it fails.

I?ve tried several different files without success.




<image001.png>


_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto:ZendTo at zend.to>

http://jul.es/mailman/listinfo/zendto


Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



How to stop time: kiss.

How to travel in time: read.

How to escape time: music.

How to feel time: write.

How to release time: breathe.



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
_______________________________________________
ZendTo mailing list
ZendTo at zend.to<mailto:ZendTo at zend.to>
http://jul.es/mailman/listinfo/zendto
_______________________________________________
ZendTo mailing list
ZendTo at zend.to<mailto:ZendTo at zend.to>
http://jul.es/mailman/listinfo/zendto



_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto:ZendTo at zend.to>

http://jul.es/mailman/listinfo/zendto



Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'Every morning when I wake,

 Dear Lord, a little prayer I make,

 O please do keep Thy lovely eye

 On all poor creatures born to die



 And every evening at sun-down

 I ask a blessing on the town,

 For whether we last the night or no

 I'm sure is always touch-and-go.



 We are not wholly bad or good

 Who live our lives under Milk Wood,

 And Thou, I know, wilt be the first

 To see our best side, not our worst.



 O let us see another day!

 Bless us all this night, I pray,

 And to the sun we all will bow

 And say, good-bye - but just for now!'

    - Dylan Thomas



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/fe1f3a80/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 25572 bytes
Desc: image001.png
URL: <http://jul.es/pipermail/zendto/attachments/20200723/fe1f3a80/attachment-0001.png>

From Jules at Zend.To  Thu Jul 23 16:25:47 2020
From: Jules at Zend.To (Jules)
Date: Thu, 23 Jul 2020 16:25:47 +0100
Subject: [ZendTo] Failed Drop Off: you cannot drop-off directories;
 only files
In-Reply-To: <WM!646d994954c374d95affeccc75ded583da8a9362d660fc30eb1c448f52f211fd5f6129b864decc772a71817bd5040aaa!@mx.jul.es>
References: <E0FAE88D-E8A3-4C04-9099-C3060DA56155@yahoo.com>
 <WM!0d0ab6d12bdf36cf69359e56dd4fff93dbcbde07e8a92f2a6058f06a799d0bacfab23c6bf90fc04ca6e5c626a3af65fa!@mx.jul.es>
 <CAPgmoWY0K7CJ8ppHvhEuTq0zOnDDNMhC7sYd-qT-Yc9Q1WOj5Q@mail.gmail.com>
 <WM!bb03a6b125e3732e63ce31213784e70f9cc229ea2835575c69c6292494fe39d0f14b470fe8bf9d58f53ef3159755a4e9!@mx.jul.es>
 <WM!a8f4b999f0463ce7f4771e87eae53b7a0661453b524e69cf7f411d0faab4b59928ac0802b8d755c916a5eb586ae5d764!@mx.jul.es>
 <eef994dd6de140299dbeec950b167e4e@HSH-MAIL.HSH.local>
 <WM!acffabe2bd28923e78b7df2edfb94776466f0a8cdd3fa4f1d5d342731aba14c9237f4a6695e403aaf73e126db15dee80!@mx.jul.es>
 <3cebd347-483d-d1e9-fc6d-f4fed99c91e7@Zend.To>
 <WM!a7b90706608aafb16c8295cc2a7b4ee2b26beaa72ebe441716bc439d9b160070af655d59772e4b361fcfdd73994306a5!@mx.jul.es>
 <b81ed3be94154c7098740480ee96b107@HSH-MAIL.HSH.local>
 <WM!646d994954c374d95affeccc75ded583da8a9362d660fc30eb1c448f52f211fd5f6129b864decc772a71817bd5040aaa!@mx.jul.es>
Message-ID: <ee0e5b1d-ed04-fdef-e28c-2f954b9a1212@Zend.To>

Well you certainly aren't running out of disk space in / or /var/zendto.

Go through your Apache logs for the exact time at which it failed. There 
should be a clue there.

On 23/07/2020 16:03, Marlon Deerr wrote:
>
> Here is my output for ?df ?h?
>
>
> Marlon Deerr, Technology Manager
> 416-572-8795(direct) | MDeerr at hshlawyers.com 
> <mailto:MDeerr at hshlawyers.com>
> <https://www.hshlawyers.com>
> <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> 
> <https://twitter.com/hshlawyers> 
> <https://www.facebook.com/HSHPersonalInjuryLawyers/> 
> <https://www.youtube.com/user/hshlawyers> 	3500 - 20 Queen St. W., 
> Toronto, ON M5H 3R3
> Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com 
> <https://www.hshlawyers.com>
>
>
> This Howie Sacks & Henry e-mail is privileged, confidential and 
> subject to copyright. Any unauthorized use or disclosure is prohibited.
>
>
>
> *From:*Jules [mailto:Jules at Zend.To]
> *Sent:* Thursday, July 23, 2020 9:36 AM
> *To:* ZendTo Users <zendto at zend.to>
> *Cc:* Marlon Deerr <MDeerr at hshlawyers.com>
> *Subject:* Re: [ZendTo] Failed Drop Off: you cannot drop-off 
> directories; only files
>
> But is that space in the right place?
>
> Please do the command "df -h" and send us the output.
>
> Cheers,
> Jules.
>
> On 23/07/2020 14:34, Marlon Deerr via ZendTo wrote:
>
>     Interesting?.I know for sure I am not out of space on my server as
>     I have allocated a lot and users haven?t even begun using the
>     service. Memory is also not an issue as well.? I allocated 16GB. I
>     know that?s overkill. Just haven?t gotten around to reducing that.
>
>     *From:*ZendTo [mailto:zendto-bounces at zend.to
>     <mailto:zendto-bounces at zend.to>] *On Behalf Of *Chris Venter via
>     ZendTo
>     *Sent:* Thursday, July 23, 2020 9:30 AM
>     *To:* ZendTo Users <zendto at zend.to> <mailto:zendto at zend.to>
>     *Cc:* Chris Venter <chris.venter1 at gmail.com>
>     <mailto:chris.venter1 at gmail.com>
>     *Subject:* Re: [ZendTo] Failed Drop Off: you cannot drop-off
>     directories; only files
>
>     I can confirm this happens when out of space on the server same
>     has happened to us in the past,
>
>     On Thu, 23 Jul 2020 at 14:19, Travis McDugald via ZendTo
>     <zendto at zend.to <mailto:zendto at zend.to>> wrote:
>
>         We just ran into a similar issue.
>
>         Check the free space on the server.? Ours gave the error after
>         running out of space.
>
>         Sent from my iPad
>
>
>
>
>             On Jul 23, 2020, at 8:47 AM, Marlon Deerr via ZendTo
>             <zendto at zend.to <mailto:zendto at zend.to>> wrote:
>
>             ?
>
>             Yes, it was happening even when I tried a different file.
>             The funny thing is, I tried again a little later and then
>             it worked AND this was with the same file I was trying to
>             drop off. The only variable I believed changed was the web
>             browser I was using.? Tested again this morning and all
>             seems to be fine now. I am not at the computer I was using
>             previously so I?ll need to circle back and perform some
>             more tests on that computer to see if I can recreate the
>             problem.
>
>             I?m curious though?your logs record the when and from what
>             IP the drop-off was made. For a future version, any chance
>             you can also capture the browser (and its version) ?that
>             was used at the time of drop-off?
>
>             *From:* Jules [mailto:Jules at Zend.To <mailto:Jules at Zend.To>]
>             *Sent:* Thursday, July 23, 2020 7:56 AM
>             *To:* ZendTo Users <zendto at zend.to <mailto:zendto at zend.to>>
>             *Cc:* Marlon Deerr <MDeerr at hshlawyers.com
>             <mailto:MDeerr at hshlawyers.com>>
>             *Subject:* Re: [ZendTo] Failed Drop Off: you cannot
>             drop-off directories; only files
>
>             Does it work if you do the exact same steps with a
>             different file?
>
>             Cheers,
>             Jules.
>
>             On 22/07/2020 20:45, Marlon Deerr via ZendTo wrote:
>
>                 Anyone know why I am getting this.? I am trying to
>                 drop-off a PDF document. I used both the drag?n drop
>                 option and also the file browsing option to select the
>                 file itself but in both cases, it fails.
>
>                 I?ve tried several different files without success.
>
>                 <image001.png>
>
>                 _______________________________________________
>
>                 ZendTo mailing list
>
>                 ZendTo at zend.to  <mailto:ZendTo at zend.to>
>
>                 http://jul.es/mailman/listinfo/zendto  <http://jul.es/mailman/listinfo/zendto>
>
>             Jules
>
>               
>
>             -- 
>
>             Julian Field MEng CEng CITP MBCS MIEEE MACM
>
>               
>
>             How to stop time: kiss.
>
>             How to travel in time: read.
>
>             How to escape time: music.
>
>             How to feel time: write.
>
>             How to release time: breathe.
>
>               
>
>             www.Zend.To  <http://www.Zend.To>
>
>             Twitter: @JulesFM
>
>             _______________________________________________
>             ZendTo mailing list
>             ZendTo at zend.to <mailto:ZendTo at zend.to>
>             http://jul.es/mailman/listinfo/zendto
>             <http://jul.es/mailman/listinfo/zendto>
>
>         _______________________________________________
>         ZendTo mailing list
>         ZendTo at zend.to <mailto:ZendTo at zend.to>
>         http://jul.es/mailman/listinfo/zendto
>         <http://jul.es/mailman/listinfo/zendto>
>
>
>
>     _______________________________________________
>
>     ZendTo mailing list
>
>     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>
>     http://jul.es/mailman/listinfo/zendto  <http://jul.es/mailman/listinfo/zendto>
>
>
>
> Jules
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> 'Every morning when I wake,
>   Dear Lord, a little prayer I make,
>   O please do keep Thy lovely eye
>   On all poor creatures born to die
>   And every evening at sun-down
>   I ask a blessing on the town,
>   For whether we last the night or no
>   I'm sure is always touch-and-go.
>   We are not wholly bad or good
>   Who live our lives under Milk Wood,
>   And Thou, I know, wilt be the first
>   To see our best side, not our worst.
>   O let us see another day!
>   Bless us all this night, I pray,
>   And to the sun we all will bow
>   And say, good-bye - but just for now!'
>  ??? - Dylan Thomas
> www.Zend.To  <http://www.Zend.To>
> Twitter: @JulesFM

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'To see a World in a Grain of Sand
  And a Heaven in a Wild Flower
  Hold Infinity in the palm of your hand
  And Eternity in an hour' - William Blake

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200723/eb4953b6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 25572 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/eb4953b6/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imageeaa572.JPG
Type: image/jpeg
Size: 125353 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/eb4953b6/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image3b00e7.JPG
Type: image/jpeg
Size: 7976 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/eb4953b6/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagec0b5e0.JPG
Type: image/jpeg
Size: 7843 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/eb4953b6/attachment-0007.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image6a718b.JPG
Type: image/jpeg
Size: 7268 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/eb4953b6/attachment-0008.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagea4f251.JPG
Type: image/jpeg
Size: 7059 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200723/eb4953b6/attachment-0009.jpe>

From john.thurston at alaska.gov  Thu Jul 23 17:54:45 2020
From: john.thurston at alaska.gov (John Thurston)
Date: Thu, 23 Jul 2020 08:54:45 -0800
Subject: [ZendTo] upgrade script and LDAP authentication values
In-Reply-To: <WM!54cd4f7c2464771ca0bfd4cb5d1b2cb06b8a61003475b8e5bccffde075da4796e97198dc61900f918002f38c0095ea0c!@mx.jul.es>
References: <272118d8-0f0b-cb98-4c0e-4dd0d2ac50b4@alaska.gov>
 <WM!ac996c1ade6bc34b86bb4b56b5cd173031fb18091de99250f657c0b73fac60ef859ae3d68b3d9dac684cf8cf5bf49efc!@mx.jul.es>
 <a588cc8d-fd77-a7e1-1c76-9106f3f9f384@Zend.To>
 <WM!07bd423778926c0cd4bd4027dab96413ab12583173910b46d4ffedd4bcb6a8e95253bfa48002f2cf0e397bb402584633!@mx.jul.es>
 <995dde30-62c0-1f71-4038-2a607e3f880b@alaska.gov>
 <WM!dad1407ddef8dae6dd3532dd5fd68662f4f817d8edbd320c4eb4a9a04ca173a7785714e3a8db12f33024d723ec3f6584!@mx.jul.es>
 <e205bf37-dd8d-009e-760b-b962c7233f06@Zend.To>
 <WM!f8fcbe3111ea07307b4c3a04aebdd081cecd533a9a634f41e84f33b99db72808100fd15bc5fe6253e2c2291bfe574469!@mx.jul.es>
 <98424f19-ca65-9623-c177-4c06193acd9d@alaska.gov>
 <WM!34fa42006b29171c9f84bd048128d9dfce9a2be5c16c1f0e780607d3f4e22dd9891abe01a16b4ef2388b462e6ae47689!@mx.jul.es>
 <33659d2e-b725-aed1-fb6b-be9a14fea535@Zend.To>
 <WM!54cd4f7c2464771ca0bfd4cb5d1b2cb06b8a61003475b8e5bccffde075da4796e97198dc61900f918002f38c0095ea0c!@mx.jul.es>
 <502c4975-a276-138d-13ce-e297450d401a@alaska.gov>
Message-ID: <WM!2612535d3274ab75de47001c2fafa283d5094730243720e1accc5ab3d4466881bb619f7ffd750588f87b9ef8b5d8e0c9!@mx.jul.es>


On 7/23/2020 3:51 AM, Jules wrote:
> John,
> 
> Please don't comment out settings you don't want to specify (such as the 
> service account credentials, etc). Just leave them set to an empty 
> string. Then 'upgrade' will be happy.

As mentioned in my original note, "I tried setting each of these to null 
strings, hoping that might trigger the code to ignore the values and 
also let the upgrade script leave them unchanged. Bzzzt. I couldn't 
authenticate. "

But taking your advice, I tried it again...and got the same result. So 
went to my ldap logs to see what queries were being performed, and dug 
in the code to see how the settings are being used. The crux of the 
problem is an empty string does not result in the same behavior as an 
undefined value.

The LDAP authenticator works perfectly for us with those settings 
_undefined_. But, if defined, the value of 'authLDAPUsernameAttr' and 
'authLDAPEmailAttr' must _not be empty strings_. If they are undefined, 
the code in NSSLDAPAuthenticator.php assumes reasonable values for those 
two settings:

   protected $_ldapUNA = 'uid';
   protected $_ldapEMA = 'mail';

which happened to align perfectly well with our directory.



I will uncomment those attributes in preferences. That will make the 
upgrade script happy.

I will leave the default values for those two attributes, and set the 
other string values to empty. That will make authentication work.

And with those steps, I think my future version upgrades will be much 
easier!


I will also report a bug:
The upgrade script requires the presence of at least two attributes in 
preferences.php, which the LDAP authentication code treats as optional.


--
Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska


From Jules at Zend.To  Fri Jul 24 10:26:12 2020
From: Jules at Zend.To (Jules)
Date: Fri, 24 Jul 2020 10:26:12 +0100
Subject: [ZendTo] upgrade script and LDAP authentication values
In-Reply-To: <WM!2612535d3274ab75de47001c2fafa283d5094730243720e1accc5ab3d4466881bb619f7ffd750588f87b9ef8b5d8e0c9!@mx.jul.es>
References: <272118d8-0f0b-cb98-4c0e-4dd0d2ac50b4@alaska.gov>
 <WM!07bd423778926c0cd4bd4027dab96413ab12583173910b46d4ffedd4bcb6a8e95253bfa48002f2cf0e397bb402584633!@mx.jul.es>
 <995dde30-62c0-1f71-4038-2a607e3f880b@alaska.gov>
 <WM!dad1407ddef8dae6dd3532dd5fd68662f4f817d8edbd320c4eb4a9a04ca173a7785714e3a8db12f33024d723ec3f6584!@mx.jul.es>
 <e205bf37-dd8d-009e-760b-b962c7233f06@Zend.To>
 <WM!f8fcbe3111ea07307b4c3a04aebdd081cecd533a9a634f41e84f33b99db72808100fd15bc5fe6253e2c2291bfe574469!@mx.jul.es>
 <98424f19-ca65-9623-c177-4c06193acd9d@alaska.gov>
 <WM!34fa42006b29171c9f84bd048128d9dfce9a2be5c16c1f0e780607d3f4e22dd9891abe01a16b4ef2388b462e6ae47689!@mx.jul.es>
 <33659d2e-b725-aed1-fb6b-be9a14fea535@Zend.To>
 <WM!54cd4f7c2464771ca0bfd4cb5d1b2cb06b8a61003475b8e5bccffde075da4796e97198dc61900f918002f38c0095ea0c!@mx.jul.es>
 <502c4975-a276-138d-13ce-e297450d401a@alaska.gov>
 <WM!2612535d3274ab75de47001c2fafa283d5094730243720e1accc5ab3d4466881bb619f7ffd750588f87b9ef8b5d8e0c9!@mx.jul.es>
Message-ID: <8bdd4d93-8fcb-2568-71fa-4c36acfee366@Zend.To>

John,

I have just fixed that bug. It will be included in the next release.
Setting those attributes to '' now has the same effect as not setting 
them at all.
So now you don't need to fight with 'upgrade' any more (hopefully!).

Cheers,
Jules.

On 23/07/2020 17:54, John Thurston via ZendTo wrote:
>
> On 7/23/2020 3:51 AM, Jules wrote:
>> John,
>>
>> Please don't comment out settings you don't want to specify (such as 
>> the service account credentials, etc). Just leave them set to an 
>> empty string. Then 'upgrade' will be happy.
>
> As mentioned in my original note, "I tried setting each of these to 
> null strings, hoping that might trigger the code to ignore the values 
> and also let the upgrade script leave them unchanged. Bzzzt. I 
> couldn't authenticate. "
>
> But taking your advice, I tried it again...and got the same result. So 
> went to my ldap logs to see what queries were being performed, and dug 
> in the code to see how the settings are being used. The crux of the 
> problem is an empty string does not result in the same behavior as an 
> undefined value.
>
> The LDAP authenticator works perfectly for us with those settings 
> _undefined_. But, if defined, the value of 'authLDAPUsernameAttr' and 
> 'authLDAPEmailAttr' must _not be empty strings_. If they are 
> undefined, the code in NSSLDAPAuthenticator.php assumes reasonable 
> values for those two settings:
>
> ? protected $_ldapUNA = 'uid';
> ? protected $_ldapEMA = 'mail';
>
> which happened to align perfectly well with our directory.
>
>
>
> I will uncomment those attributes in preferences. That will make the 
> upgrade script happy.
>
> I will leave the default values for those two attributes, and set the 
> other string values to empty. That will make authentication work.
>
> And with those steps, I think my future version upgrades will be much 
> easier!
>
>
> I will also report a bug:
> The upgrade script requires the presence of at least two attributes in 
> preferences.php, which the LDAP authentication code treats as optional.
>
>
> -- 
> Do things because you should, not just because you can.
>
> John Thurston??? 907-465-8591
> John.Thurston at alaska.gov
> Department of Administration
> State of Alaska
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'A committee is a group of the unwilling, chosen from the unfit,
  to do the unnecessary.' - Anon

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/43c2c5e4/attachment.html>

From gkandalaft at sdis91.fr  Fri Jul 24 10:29:04 2020
From: gkandalaft at sdis91.fr (Kandalaft George)
Date: Fri, 24 Jul 2020 09:29:04 +0000
Subject: [ZendTo] Calling all translators !!
In-Reply-To: <WM!618ab4bc5d08019dd5bb5e263bb010c0a4e25d3bd501677314800aeb4118522f8cd0ebb722bb43e1fef83ac1ab3af230!@mx.jul.es>
References: <c85befa7-a607-e841-98d9-ff74e8ae04c1@Zend.To>
 <WM!618ab4bc5d08019dd5bb5e263bb010c0a4e25d3bd501677314800aeb4118522f8cd0ebb722bb43e1fef83ac1ab3af230!@mx.jul.es>
 <8c648746ecea4d2aab582783f9d18b49@sdis91.fr>
Message-ID: <WM!cf7a5e306587463376359466b0e00c079238ae269b8fe56057c6104fba78f4183c0cacdd1696d6d49aaeb7fdff16472e!@mx.jul.es>

Hello Jules

Here is the French translation

George

From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Jules via ZendTo
Sent: Thursday, July 23, 2020 4:56 PM
To: ZendTo Users
Cc: Jules
Subject: [ZendTo] Calling all translators !!

Folks,

In the new beta, there are some new (and a few updated) phrases that need translating.

Please can you take a look at the ones in your language that are marked "fuzzy" as well as the new phrases. Some of the "fuzzy" matches are now definitely wrong.

Many thanks indeed!

Cheers,


Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'Think globally, act locally.' - Friends of the Earth



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/08068e9f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zendto.po
Type: application/octet-stream
Size: 80163 bytes
Desc: zendto.po
URL: <http://jul.es/pipermail/zendto/attachments/20200724/08068e9f/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zendto.mo
Type: application/octet-stream
Size: 78548 bytes
Desc: zendto.mo
URL: <http://jul.es/pipermail/zendto/attachments/20200724/08068e9f/attachment-0003.obj>

From MDeerr at hshlawyers.com  Fri Jul 24 17:54:52 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Fri, 24 Jul 2020 16:54:52 +0000
Subject: [ZendTo] Free SSL Certificate Authority Recommendations for ZendTo
References: <5d0a8c92c702482aadaae619b2ce3d33@HSH-MAIL.HSH.local>
Message-ID: <WM!0dedb597f6f2f3f2b6efe06990bd6507d466d466f1d50351ffd814bca31d16150f8814bd5dd6d6e83253079fb735625e!@mx.jul.es>

Hello All,

I want to get a new ZendTo install up and running to demo to management.  I want it fully functioning, even with an SSL Certificate. While I demo it and have it running for staff to test, I would prefer to not run into any SSL related issues. I'm not looking to have any self-signed stuff either. I would prefer to setup an official, yet free SSL Cert and once management is convinced that this is a service we should keep running long term, then I can go out an invest in a commercial grade SSL Cert we actually pay for.

With that said, has anyone setup ZendTo with an SSL Certificate offered by a CA. If so, which one(s) would you recommend?

Thanks,
Marlon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/f4fa4947/attachment.html>

From KLE at msktd.com  Fri Jul 24 18:01:17 2020
From: KLE at msktd.com (Ken Etter)
Date: Fri, 24 Jul 2020 13:01:17 -0400
Subject: [ZendTo] Free SSL Certificate Authority Recommendations for
 ZendTo
In-Reply-To: <WM!ecfeb6dcc149bb3f0b72cfd3e7c55b1671cc51ce7211d6b6ee9b1233dcc378ac687492fa3b78b8ff09816397d3a321ea!@mx.jul.es>
References: <5d0a8c92c702482aadaae619b2ce3d33@HSH-MAIL.HSH.local>
 <WM!0dedb597f6f2f3f2b6efe06990bd6507d466d466f1d50351ffd814bca31d16150f8814bd5dd6d6e83253079fb735625e!@mx.jul.es>
 <WM!ecfeb6dcc149bb3f0b72cfd3e7c55b1671cc51ce7211d6b6ee9b1233dcc378ac687492fa3b78b8ff09816397d3a321ea!@mx.jul.es>
 <5F1B13DD0200001300146749@mail.msktd.com>
Message-ID: <WM!ed7745f76b7f9b21660c61cdf2eedec98c39b1dfd9bbff2d368bb96c543486778ed7ca0e29a0cca6e9cdb27e15af4423!@mx.jul.es>

I know you're asking about free ones, so this isn't directly answering
your question.  But just thought I would throw it out there as an idea. 
I use a Digicert Wildcard cert.  That enables me to cover all the
servers in my domain.  So I have never had to consider free ones because
I can just pull another for any servers I want to stand up.  The
viability of this solution probably depends upon the number of servers
you need to provide with certs.

Ken
>>> Marlon Deerr via ZendTo <zendto at zend.to> 7/24/2020 12:54 PM >>>
Hello All,
 
I want to get a new ZendTo install up and running to demo to
management.  I want it fully functioning, even with an SSL Certificate.
While I demo it and have it running for staff to test, I would prefer to
not run into any SSL related issues.I?m not looking to have any
self-signed stuff either. I would prefer to setup an official, yet free
SSL Cert and once management is convinced that this is a service we
should keep running long term, then I can go out an invest in a
commercial grade SSL Cert we actually pay for.
 
With that said, has anyone setup ZendTo with an SSL Certificate offered
by a CA. If so, which one(s) would you recommend?
 
Thanks,
Marlon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/444a8496/attachment.html>

From Massimo.Forni at turboden.it  Fri Jul 24 18:01:53 2020
From: Massimo.Forni at turboden.it (Massimo Forni)
Date: Fri, 24 Jul 2020 17:01:53 +0000
Subject: [ZendTo] Free SSL Certificate Authority Recommendations for
 ZendTo
In-Reply-To: <WM!f759f9f0da79bc36bb460495d60ea46c935b4dac559afb35cd1ad8f8706a5c7eaa105a2cb912887a5df378f8e96ba199!@mx.jul.es>
References: <5d0a8c92c702482aadaae619b2ce3d33@HSH-MAIL.HSH.local>
 <WM!0dedb597f6f2f3f2b6efe06990bd6507d466d466f1d50351ffd814bca31d16150f8814bd5dd6d6e83253079fb735625e!@mx.jul.es>,
 <WM!f759f9f0da79bc36bb460495d60ea46c935b4dac559afb35cd1ad8f8706a5c7eaa105a2cb912887a5df378f8e96ba199!@mx.jul.es>
 <F8886EE0-1DD1-46B4-BBA4-0D3C4F9D2905@turboden.it>
Message-ID: <WM!49c42d7b9faa0d0b55ceb320316f94e379986e350f79b31985b92412856a17babc750e7fb7adb61c6de3aca94d9bb7df!@mx.jul.es>

https://letsencrypt.org/


Sent from my iPhone

On 24 Jul 2020, at 18:55, Marlon Deerr via ZendTo <zendto at zend.to> wrote:

?
Hello All,

I want to get a new ZendTo install up and running to demo to management.  I want it fully functioning, even with an SSL Certificate. While I demo it and have it running for staff to test, I would prefer to not run into any SSL related issues. I?m not looking to have any self-signed stuff either. I would prefer to setup an official, yet free SSL Cert and once management is convinced that this is a service we should keep running long term, then I can go out an invest in a commercial grade SSL Cert we actually pay for.

With that said, has anyone setup ZendTo with an SSL Certificate offered by a CA. If so, which one(s) would you recommend?

Thanks,
Marlon
_______________________________________________
ZendTo mailing list
ZendTo at zend.to
https://urldefense.com/v3/__http://jul.es/mailman/listinfo/zendto__;!!BYEqwblc0Q!nIlcimAL0nnUDvPFKfZ5vXqKgle8Thlr2XeaJv2r-o6EqDToV7AHyBdFY25mJ4KJ6yBdww$

--

Massimo Forni
ICT Infrastructure Manager

Mobile: +393474110278

________________________________

Turboden S.p.A. I via Cernaia 10 I 25124 Brescia I Italy
t. +39 030 3552001 I f. +39 030 3552011
www.turboden.com<http://www.turboden.com>


Confidentiality notice: this message, together with its attachments, may contain strictly confidential and/or legally privileged information and it is destined solely to the intended addressee(s), who only may use it under his/their responsibility. Opinions, conclusions and other information contained in this message, that do not relate to the official business of this firm, shall be considered as not given or endorsed by it. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. Any use, disclosure, copying or distribution of the contents of this communication by a not-intended recipient or in violation of the purposes of this communication is strictly prohibited and may be unlawful.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/1f92c7c1/attachment-0001.html>

From ssilva at sgvwater.com  Fri Jul 24 18:07:56 2020
From: ssilva at sgvwater.com (Scott Silva)
Date: Fri, 24 Jul 2020 17:07:56 +0000
Subject: [ZendTo] Free SSL Certificate Authority Recommendations for
 ZendTo
In-Reply-To: <WM!ecfeb6dcc149bb3f0b72cfd3e7c55b1671cc51ce7211d6b6ee9b1233dcc378ac687492fa3b78b8ff09816397d3a321ea!@mx.jul.es>
References: <5d0a8c92c702482aadaae619b2ce3d33@HSH-MAIL.HSH.local>
 <WM!0dedb597f6f2f3f2b6efe06990bd6507d466d466f1d50351ffd814bca31d16150f8814bd5dd6d6e83253079fb735625e!@mx.jul.es>
 <WM!ecfeb6dcc149bb3f0b72cfd3e7c55b1671cc51ce7211d6b6ee9b1233dcc378ac687492fa3b78b8ff09816397d3a321ea!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F42ED2C166@FONEXCH01.sgvwc.local>
Message-ID: <WM!77445822ea7969009a973fcb01cacaba4f07f97bffd827540b2cad2064d50fb0175e6c1093634455288ffd439e7d6354!@mx.jul.es>

Mine runs on Lets Encrypt certs.
I use the "getssl" scripts and use symlinks to link Zendto to the certs.



From: ZendTo <zendto-bounces at zend.to> On Behalf Of Marlon Deerr via ZendTo
Sent: Friday, July 24, 2020 9:56 AM
To: ZendTo Users <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: [ZendTo] Free SSL Certificate Authority Recommendations for ZendTo

Hello All,

I want to get a new ZendTo install up and running to demo to management.  I want it fully functioning, even with an SSL Certificate. While I demo it and have it running for staff to test, I would prefer to not run into any SSL related issues. I'm not looking to have any self-signed stuff either. I would prefer to setup an official, yet free SSL Cert and once management is convinced that this is a service we should keep running long term, then I can go out an invest in a commercial grade SSL Cert we actually pay for.

With that said, has anyone setup ZendTo with an SSL Certificate offered by a CA. If so, which one(s) would you recommend?

Thanks,
Marlon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/fc606814/attachment.html>

From nresults at comcast.net  Fri Jul 24 18:07:45 2020
From: nresults at comcast.net (Net Results)
Date: Fri, 24 Jul 2020 13:07:45 -0400
Subject: [ZendTo] Free SSL Certificate Authority Recommendations for
 ZendTo
In-Reply-To: <WM!0ea47706fb5e594aa655b614823bdd3549066c76ddf730682d7288bbfa5f19a82bccce90bd12e95d5e9a405f3b271a38!@mx.jul.es>
References: <WM!0ea47706fb5e594aa655b614823bdd3549066c76ddf730682d7288bbfa5f19a82bccce90bd12e95d5e9a405f3b271a38!@mx.jul.es>
 <9C22A86F-ACCB-4B2F-9E5E-6EE1F98A4BC7@comcast.net>
Message-ID: <WM!aa7194caf13b01cf9566a58073ecb761b61943f4102bb84b9f8396838478ac2c32cc7790b90918db79c077d27a588062!@mx.jul.es>

I use Digicert for my domains.

The wildcard certificate works perfectly with Zento.

Remember to disable http access to avoid mixed mode errors.

Sent from a fancy digital device...

> On Jul 24, 2020, at 1:00 PM, Marlon Deerr via ZendTo <zendto at zend.to> wrote:
> 
> ?
> Hello All,
>  
> I want to get a new ZendTo install up and running to demo to management.  I want it fully functioning, even with an SSL Certificate. While I demo it and have it running for staff to test, I would prefer to not run into any SSL related issues. I?m not looking to have any self-signed stuff either. I would prefer to setup an official, yet free SSL Cert and once management is convinced that this is a service we should keep running long term, then I can go out an invest in a commercial grade SSL Cert we actually pay for.
>  
> With that said, has anyone setup ZendTo with an SSL Certificate offered by a CA. If so, which one(s) would you recommend?
>  
> Thanks,
> Marlon
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/ab06ad13/attachment.html>

From zend.to at neilzone.co.uk  Fri Jul 24 18:08:30 2020
From: zend.to at neilzone.co.uk (zend.to at neilzone.co.uk)
Date: Fri, 24 Jul 2020 18:08:30 +0100
Subject: [ZendTo] Free SSL Certificate Authority Recommendations for
 ZendTo
In-Reply-To: <WM!f759f9f0da79bc36bb460495d60ea46c935b4dac559afb35cd1ad8f8706a5c7eaa105a2cb912887a5df378f8e96ba199!@mx.jul.es>
References: <5d0a8c92c702482aadaae619b2ce3d33@HSH-MAIL.HSH.local>
 <WM!0dedb597f6f2f3f2b6efe06990bd6507d466d466f1d50351ffd814bca31d16150f8814bd5dd6d6e83253079fb735625e!@mx.jul.es>
 <WM!f759f9f0da79bc36bb460495d60ea46c935b4dac559afb35cd1ad8f8706a5c7eaa105a2cb912887a5df378f8e96ba199!@mx.jul.es>
 <BBA785F2-0A0D-48DA-960B-BC89D42A2D2E@neilzone.co.uk>
Message-ID: <WM!56fb9e4eb748ed699ce1d2c94410d768694266973feea330ead208c32fde630c53e7edcfb56cf65bebaf7dd44456be5f!@mx.jul.es>



> On 24 Jul 2020, at 17:54, Marlon Deerr via ZendTo <zendto at zend.to> wrote:
> 
> With that said, has anyone setup ZendTo with an SSL Certificate offered by a CA. If so, which one(s) would you recommend?

Let?s Encrypt?



Neil

__________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/02fa3610/attachment.html>

From klou at themusiclink.net  Fri Jul 24 18:19:05 2020
From: klou at themusiclink.net (Kris Lou)
Date: Fri, 24 Jul 2020 10:19:05 -0700
Subject: [ZendTo] Free SSL Certificate Authority Recommendations for
 ZendTo
In-Reply-To: <WM!95f0e9d70aba53d6de6fcb267d74e1a0e14757eb97fcdb4cecde2f9bee8f11d14f16e1666b205ca3838fe7038eee7f80!@mx.jul.es>
References: <5d0a8c92c702482aadaae619b2ce3d33@HSH-MAIL.HSH.local>
 <WM!0dedb597f6f2f3f2b6efe06990bd6507d466d466f1d50351ffd814bca31d16150f8814bd5dd6d6e83253079fb735625e!@mx.jul.es>
 <F8886EE0-1DD1-46B4-BBA4-0D3C4F9D2905@turboden.it>
 <WM!49c42d7b9faa0d0b55ceb320316f94e379986e350f79b31985b92412856a17babc750e7fb7adb61c6de3aca94d9bb7df!@mx.jul.es>
 <WM!f759f9f0da79bc36bb460495d60ea46c935b4dac559afb35cd1ad8f8706a5c7eaa105a2cb912887a5df378f8e96ba199!@mx.jul.es>
 <WM!95f0e9d70aba53d6de6fcb267d74e1a0e14757eb97fcdb4cecde2f9bee8f11d14f16e1666b205ca3838fe7038eee7f80!@mx.jul.es>
 <CAGyTNKEjCvR+Y+twg0O9XweTm85wSKWbUgnVazw7vz6hs24-gQ@mail.gmail.com>
Message-ID: <WM!e5d256b515511c8e4f6d4d4a1dff1c7b2c34fe376604f6b4d5fa502fc18629e077406ce639de6c02e2306f5553acc7dd!@mx.jul.es>

I use Let's Encrypt, with Dehydrated (it's on github) to manage/renew it.
Then I have osync jobs (as a Dehydrated post-renew hook) which distribute
the certs where they need to go.


On Fri, Jul 24, 2020 at 10:02 AM Massimo Forni via ZendTo <zendto at zend.to>
wrote:

> https://letsencrypt.org/
>
>
> Sent from my iPhone
>
> On 24 Jul 2020, at 18:55, Marlon Deerr via ZendTo <zendto at zend.to> wrote:
>
> ?
>
> Hello All,
>
>
>
> I want to get a new ZendTo install up and running to demo to management.
> I want it fully functioning, even with an SSL Certificate. While I demo it
> and have it running for staff to test, I would prefer to not run into any
> SSL related issues. *I?m not looking to have any self-signed *stuff
> either. I would prefer to setup an official, yet free SSL Cert and once
> management is convinced that this is a service we should keep running long
> term, then I can go out an invest in a commercial grade SSL Cert we
> actually pay for.
>
>
>
> With that said, has anyone setup ZendTo with an SSL Certificate offered by
> a CA. If so, which one(s) would you recommend?
>
>
>
> Thanks,
>
> Marlon
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
>
> https://urldefense.com/v3/__http://jul.es/mailman/listinfo/zendto__;!!BYEqwblc0Q!nIlcimAL0nnUDvPFKfZ5vXqKgle8Thlr2XeaJv2r-o6EqDToV7AHyBdFY25mJ4KJ6yBdww$
>
> --
>
> *Massimo Forni*
> ICT Infrastructure Manager
>
> Mobile: +393474110278
> ------------------------------
>
> *Turboden S.p.A.* *I* via Cernaia 10 *I* 25124 Brescia *I* Italy
> t. +39 030 3552001 *I* f. +39 030 3552011
> www.turboden.com
>
>
> *Confidentiality notice*: this message, together with its attachments,
> may contain strictly confidential and/or legally privileged information and
> it is destined solely to the intended addressee(s), who only may use it
> under his/their responsibility. Opinions, conclusions and other information
> contained in this message, that do not relate to the official business of
> this firm, shall be considered as not given or endorsed by it. If you have
> received this communication in error, please notify us immediately by
> responding to this email and then delete it from your system. Any use,
> disclosure, copying or distribution of the contents of this communication
> by a not-intended recipient or in violation of the purposes of this
> communication is strictly prohibited and may be unlawful.
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/d5989ddb/attachment-0001.html>

From john.thurston at alaska.gov  Fri Jul 24 19:15:37 2020
From: john.thurston at alaska.gov (John Thurston)
Date: Fri, 24 Jul 2020 10:15:37 -0800
Subject: [ZendTo] Free SSL Certificate Authority Recommendations for
 ZendTo
In-Reply-To: <WM!f759f9f0da79bc36bb460495d60ea46c935b4dac559afb35cd1ad8f8706a5c7eaa105a2cb912887a5df378f8e96ba199!@mx.jul.es>
References: <5d0a8c92c702482aadaae619b2ce3d33@HSH-MAIL.HSH.local>
 <WM!0dedb597f6f2f3f2b6efe06990bd6507d466d466f1d50351ffd814bca31d16150f8814bd5dd6d6e83253079fb735625e!@mx.jul.es>
 <WM!f759f9f0da79bc36bb460495d60ea46c935b4dac559afb35cd1ad8f8706a5c7eaa105a2cb912887a5df378f8e96ba199!@mx.jul.es>
 <9ea1bc35-5681-0447-ea08-c8433602e83c@alaska.gov>
Message-ID: <WM!890d2bc48318797d682bae9f69161206ee984d9dcf66da682aa6385c6aff2b0a98c818b0cbc12e990e34c2d2f4217c35!@mx.jul.es>


On 7/24/2020 8:54 AM, Marlon Deerr via ZendTo wrote:
> With that said, has anyone setup ZendTo with an SSL Certificate offered 
> by a CA. If so, which one(s) would you recommend?

Let's Encrypt

--
Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska



From MDeerr at hshlawyers.com  Fri Jul 24 22:33:04 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Fri, 24 Jul 2020 21:33:04 +0000
Subject: [ZendTo] ZendTo port forwarding - how have you set it up?
References: <74119d20676a4b0cae11941cb371c611@HSH-MAIL.HSH.local>
Message-ID: <WM!64c5abad0910da010ce67d07525986988fd09aa4a14428e2d782fbcc4b23b5f17b23465accdcd07d8b738e6daa805aa7!@mx.jul.es>

What port are you all using for your ZendTo install sitting behind your firewall?

I've created a DNS A record pointing to the public IP of our WAN (a set of SonicWall Appliances), however it currently has 443 already in use for secure remote admin access to it.  Internally, I have my ZendTo install working fine now with an SSL Cert. For those in a similar situation, how are you port forwarding (or on what port are you port forwarding) to your internal ZendTo install?

My first guess is that some of you may say, change your WAN SSL port to 4443 and reserve 443 for ZendTo.  Just curious what you are all doing with your install.

Thanks,
Marlon



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/22c7e8e8/attachment.html>

From MDeerr at hshlawyers.com  Fri Jul 24 22:33:50 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Fri, 24 Jul 2020 21:33:50 +0000
Subject: [ZendTo] Free SSL Certificate Authority Recommendations for
 ZendTo
In-Reply-To: <WM!4a9d33362897768b30c5f57d3eb594d74bf1bdb7f36eda46aa6c2f7265dde32820fad8fa1c753cd1d835bec5482c4e20!@mx.jul.es>
References: <5d0a8c92c702482aadaae619b2ce3d33@HSH-MAIL.HSH.local>
 <WM!0dedb597f6f2f3f2b6efe06990bd6507d466d466f1d50351ffd814bca31d16150f8814bd5dd6d6e83253079fb735625e!@mx.jul.es>
 <WM!ecfeb6dcc149bb3f0b72cfd3e7c55b1671cc51ce7211d6b6ee9b1233dcc378ac687492fa3b78b8ff09816397d3a321ea!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F42ED2C166@FONEXCH01.sgvwc.local>
 <WM!77445822ea7969009a973fcb01cacaba4f07f97bffd827540b2cad2064d50fb0175e6c1093634455288ffd439e7d6354!@mx.jul.es>
 <WM!4a9d33362897768b30c5f57d3eb594d74bf1bdb7f36eda46aa6c2f7265dde32820fad8fa1c753cd1d835bec5482c4e20!@mx.jul.es>
 <ed69cc0c80e546b6a4e4fc88bcdf5fb9@HSH-MAIL.HSH.local>
Message-ID: <WM!7d2d56d0b711b9c5e1a8b9766833152c1f9d219226ae725b52895d51db84f81fc4d9cd34364f0e95d8378afb0acbd605!@mx.jul.es>

Seems like a good bunch of you are using Letsencrypt. I was thinking of doing the same but found ZeroSSL and thought I would give that a try. Was pretty simple.

Many thanks to all of you who took the time to respond.


From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Scott Silva via ZendTo
Sent: Friday, July 24, 2020 1:08 PM
To: 'ZendTo Users' <zendto at zend.to>
Cc: Scott Silva <ssilva at sgvwater.com>
Subject: Re: [ZendTo] Free SSL Certificate Authority Recommendations for ZendTo

Mine runs on Lets Encrypt certs.
I use the "getssl" scripts and use symlinks to link Zendto to the certs.



From: ZendTo <zendto-bounces at zend.to<mailto:zendto-bounces at zend.to>> On Behalf Of Marlon Deerr via ZendTo
Sent: Friday, July 24, 2020 9:56 AM
To: ZendTo Users <zendto at zend.to<mailto:zendto at zend.to>>
Cc: Marlon Deerr <MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>>
Subject: [ZendTo] Free SSL Certificate Authority Recommendations for ZendTo

Hello All,

I want to get a new ZendTo install up and running to demo to management.  I want it fully functioning, even with an SSL Certificate. While I demo it and have it running for staff to test, I would prefer to not run into any SSL related issues. I'm not looking to have any self-signed stuff either. I would prefer to setup an official, yet free SSL Cert and once management is convinced that this is a service we should keep running long term, then I can go out an invest in a commercial grade SSL Cert we actually pay for.

With that said, has anyone setup ZendTo with an SSL Certificate offered by a CA. If so, which one(s) would you recommend?

Thanks,
Marlon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/84fbf7aa/attachment-0001.html>

From ssilva at sgvwater.com  Fri Jul 24 22:47:59 2020
From: ssilva at sgvwater.com (Scott Silva)
Date: Fri, 24 Jul 2020 21:47:59 +0000
Subject: [ZendTo] ZendTo port forwarding - how have you set it up?
In-Reply-To: <WM!f205ae553b7c7fff94323ec7939c6bb14d6d9317562c6eb8ab60d817b2667c44eef363a98888bb17047d2bddbdfa8a13!@mx.jul.es>
References: <74119d20676a4b0cae11941cb371c611@HSH-MAIL.HSH.local>
 <WM!64c5abad0910da010ce67d07525986988fd09aa4a14428e2d782fbcc4b23b5f17b23465accdcd07d8b738e6daa805aa7!@mx.jul.es>
 <WM!f205ae553b7c7fff94323ec7939c6bb14d6d9317562c6eb8ab60d817b2667c44eef363a98888bb17047d2bddbdfa8a13!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F42ED2C741@FONEXCH01.sgvwc.local>
Message-ID: <WM!4ac98b70702f6b8cd44135638fb0b8b8c80c5396037d53f3124b16d2dcf5cc1c4d08c440286c53331f733c48b05e8807!@mx.jul.es>

We have ip blocks at our main locations. I just nat the dmz server to a free outside address...


From: ZendTo <zendto-bounces at zend.to> On Behalf Of Marlon Deerr via ZendTo
Sent: Friday, July 24, 2020 2:34 PM
To: ZendTo Users <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: [ZendTo] ZendTo port forwarding - how have you set it up?

What port are you all using for your ZendTo install sitting behind your firewall?

I've created a DNS A record pointing to the public IP of our WAN (a set of SonicWall Appliances), however it currently has 443 already in use for secure remote admin access to it.  Internally, I have my ZendTo install working fine now with an SSL Cert. For those in a similar situation, how are you port forwarding (or on what port are you port forwarding) to your internal ZendTo install?

My first guess is that some of you may say, change your WAN SSL port to 4443 and reserve 443 for ZendTo.  Just curious what you are all doing with your install.

Thanks,
Marlon



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/7c2e28c4/attachment.html>

From MDeerr at hshlawyers.com  Fri Jul 24 23:20:34 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Fri, 24 Jul 2020 22:20:34 +0000
Subject: [ZendTo] ZendTo port forwarding - how have you set it up?
In-Reply-To: <WM!0567f5eaeeec01a072766a061db5d530ac76f6529c298da22b14d0c233c36029d4612dabb125955ac596fd0cb49b2d82!@mx.jul.es>
References: <74119d20676a4b0cae11941cb371c611@HSH-MAIL.HSH.local>
 <WM!64c5abad0910da010ce67d07525986988fd09aa4a14428e2d782fbcc4b23b5f17b23465accdcd07d8b738e6daa805aa7!@mx.jul.es>
 <WM!f205ae553b7c7fff94323ec7939c6bb14d6d9317562c6eb8ab60d817b2667c44eef363a98888bb17047d2bddbdfa8a13!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F42ED2C741@FONEXCH01.sgvwc.local>
 <WM!4ac98b70702f6b8cd44135638fb0b8b8c80c5396037d53f3124b16d2dcf5cc1c4d08c440286c53331f733c48b05e8807!@mx.jul.es>
 <WM!0567f5eaeeec01a072766a061db5d530ac76f6529c298da22b14d0c233c36029d4612dabb125955ac596fd0cb49b2d82!@mx.jul.es>
 <7013f0e49e45472cafef34ba56b3ce3b@HSH-MAIL.HSH.local>
Message-ID: <WM!58361f481d3cd6d37f20fff1747c66c7a68c7318e19624cab7105e1f3399af7ee0713dacc3334c41683d9092b31d44dd!@mx.jul.es>

Thanks for your reply Scott. Unfortunately for me, we are currently housed with our MSP's datacenter so I don't have a block of IP's to work with. I have to perform some form of NATing or Port Forwarding.


From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Scott Silva via ZendTo
Sent: Friday, July 24, 2020 5:48 PM
To: 'ZendTo Users' <zendto at zend.to>
Cc: Scott Silva <ssilva at sgvwater.com>
Subject: Re: [ZendTo] ZendTo port forwarding - how have you set it up?

We have ip blocks at our main locations. I just nat the dmz server to a free outside address...


From: ZendTo <zendto-bounces at zend.to<mailto:zendto-bounces at zend.to>> On Behalf Of Marlon Deerr via ZendTo
Sent: Friday, July 24, 2020 2:34 PM
To: ZendTo Users <zendto at zend.to<mailto:zendto at zend.to>>
Cc: Marlon Deerr <MDeerr at hshlawyers.com<mailto:MDeerr at hshlawyers.com>>
Subject: [ZendTo] ZendTo port forwarding - how have you set it up?

What port are you all using for your ZendTo install sitting behind your firewall?

I've created a DNS A record pointing to the public IP of our WAN (a set of SonicWall Appliances), however it currently has 443 already in use for secure remote admin access to it.  Internally, I have my ZendTo install working fine now with an SSL Cert. For those in a similar situation, how are you port forwarding (or on what port are you port forwarding) to your internal ZendTo install?

My first guess is that some of you may say, change your WAN SSL port to 4443 and reserve 443 for ZendTo.  Just curious what you are all doing with your install.

Thanks,
Marlon



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200724/df151e44/attachment.html>

From zend.to at neilzone.co.uk  Sat Jul 25 12:35:26 2020
From: zend.to at neilzone.co.uk (zend.to at neilzone.co.uk)
Date: Sat, 25 Jul 2020 12:35:26 +0100
Subject: [ZendTo] ZendTo port forwarding - how have you set it up?
In-Reply-To: <WM!c74364253d7014919e5750c97b52340a41b0e74ebb92e6ce5e2cc9beb0a6eedd9b19e5389200a4a585717afb699df573!@mx.jul.es>
References: <74119d20676a4b0cae11941cb371c611@HSH-MAIL.HSH.local>
 <WM!64c5abad0910da010ce67d07525986988fd09aa4a14428e2d782fbcc4b23b5f17b23465accdcd07d8b738e6daa805aa7!@mx.jul.es>
 <WM!f205ae553b7c7fff94323ec7939c6bb14d6d9317562c6eb8ab60d817b2667c44eef363a98888bb17047d2bddbdfa8a13!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F42ED2C741@FONEXCH01.sgvwc.local>
 <WM!4ac98b70702f6b8cd44135638fb0b8b8c80c5396037d53f3124b16d2dcf5cc1c4d08c440286c53331f733c48b05e8807!@mx.jul.es>
 <WM!0567f5eaeeec01a072766a061db5d530ac76f6529c298da22b14d0c233c36029d4612dabb125955ac596fd0cb49b2d82!@mx.jul.es>
 <7013f0e49e45472cafef34ba56b3ce3b@HSH-MAIL.HSH.local>
 <WM!58361f481d3cd6d37f20fff1747c66c7a68c7318e19624cab7105e1f3399af7ee0713dacc3334c41683d9092b31d44dd!@mx.jul.es>
 <WM!c74364253d7014919e5750c97b52340a41b0e74ebb92e6ce5e2cc9beb0a6eedd9b19e5389200a4a585717afb699df573!@mx.jul.es>
 <B920CB94-A9B7-417D-944D-8DC0CBA5D3B3@neilzone.co.uk>
Message-ID: <WM!c0c08156c14e1d97257d9c57dc4285ff24c3ad7d6b2b07490bdf620f6e2aa585c95412cbf78f54aacca17bc3bed98533!@mx.jul.es>



> On 24 Jul 2020, at 23:20, Marlon Deerr via ZendTo <zendto at zend.to> wrote:
> 
>  Unfortunately for me, we are currently housed with our MSP?s datacenter so I don?t have a block of IP?s to work with. I have to perform some form of NATing or Port Forwarding.

You might consider if it would make your (and your users' / their clients?) lives easier if you move the SonicWall remote admin to a different port, freeing up 443, and then using that for zend.to and other bits.

Otherwise, you?ll need to ensure people remember to specify the port number in the URL in time (if they type it manually, I guess).

Best wishes

Neil

__________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200725/08be2b8b/attachment-0001.html>

From MDeerr at hshlawyers.com  Wed Jul 29 03:30:58 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Wed, 29 Jul 2020 02:30:58 +0000
Subject: [ZendTo] ZendTo admin funtions not available when I log in from the
 WAN
References: <1595989858786.1070@hshlawyers.com>
Message-ID: <WM!41e4d8fd6d6d896f6f88a51a317d2c019f0ab702990ebf8b43be638e4d0c39dfc21ce8257d32d6c014532c09e7705616!@mx.jul.es>

Hello All,


I have my ZendTo site now working from outside my LAN, however whenever I log in as an admin user coming in from the WAN, I am not given any of the admin related functions, however when I log in as an admin from inside our LAN, I have all admin functions available to me.


Am I missing a setting somewhere?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200729/9bdd60fb/attachment.html>

From zend.to at neilzone.co.uk  Wed Jul 29 07:19:02 2020
From: zend.to at neilzone.co.uk (zend.to at neilzone.co.uk)
Date: Wed, 29 Jul 2020 07:19:02 +0100
Subject: [ZendTo] ZendTo admin funtions not available when I log in from
 the WAN
In-Reply-To: <WM!b2f454016d6d80cd477881f523e0872fa34f44e4cc6d3048cdb75cf70aab505533642777c455606200f56d314f48211a!@mx.jul.es>
References: <1595989858786.1070@hshlawyers.com>
 <WM!41e4d8fd6d6d896f6f88a51a317d2c019f0ab702990ebf8b43be638e4d0c39dfc21ce8257d32d6c014532c09e7705616!@mx.jul.es>
 <WM!b2f454016d6d80cd477881f523e0872fa34f44e4cc6d3048cdb75cf70aab505533642777c455606200f56d314f48211a!@mx.jul.es>
 <FD81FF5B-2AE3-4296-A20B-F6BF147DFA9C@neilzone.co.uk>
Message-ID: <WM!d2ee363ca0e39eaf41c17f4aa55dcc04575ee4fbc81d4860c972b7e1c6fbfd7d21aecba99bdb7f2dd688856597e3eeac!@mx.jul.es>



> On 29 Jul 2020, at 03:30, Marlon Deerr via ZendTo <zendto at zend.to> wrote:
> 
> I have my ZendTo site now working from outside my LAN, however whenever I log in as an admin user coming in from the WAN, I am not given any of the admin related functions, however when I log in as an admin from inside our LAN, I have all admin functions available to me.


Look for the following in preferences.php:

 // Are admin logins restricted to connections from the 'localIPSubnets'
  // networks?
  // Yes by default. This stops attempted remote logins to admin
  // accounts, so your admin accounts cannot be used maliciously by
  // outsiders.
  'adminLoginsMustBeLocal' => TRUE,

Try changing it to FALSE, if you are absolutely sure you want this functionality.

Best wishes

Neil

__________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200729/9ae95e25/attachment.html>

From Jules at Zend.To  Wed Jul 29 09:53:40 2020
From: Jules at Zend.To (Jules)
Date: Wed, 29 Jul 2020 09:53:40 +0100
Subject: [ZendTo] ZendTo admin funtions not available when I log in from
 the WAN
In-Reply-To: <WM!41e4d8fd6d6d896f6f88a51a317d2c019f0ab702990ebf8b43be638e4d0c39dfc21ce8257d32d6c014532c09e7705616!@mx.jul.es>
References: <1595989858786.1070@hshlawyers.com>
 <WM!41e4d8fd6d6d896f6f88a51a317d2c019f0ab702990ebf8b43be638e4d0c39dfc21ce8257d32d6c014532c09e7705616!@mx.jul.es>
Message-ID: <5b451503-1c87-3d20-fd1d-c83d9f10e420@Zend.To>

Marlon,

There is a setting in preferences.php called
 ? 'adminLoginsMustBeLocal' => TRUE,
which is probably set to TRUE by default. Change it to FALSE and refresh 
the page in your browser.

It should be the setting immediately below "authAdmins".

Cheers,
Jules.


On 29/07/2020 03:30, Marlon Deerr via ZendTo wrote:
>
> Hello All,
>
>
> I have my ZendTo site now working from outside my LAN, however 
> whenever I log in as an admin user coming in from the WAN, I am not 
> given any of the admin related functions, however when I log in as an 
> admin from inside our LAN, I have?all admin functions available to me.
>
>
> Am I missing a setting somewhere?
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

How to stop time: kiss.
How to travel in time: read.
How to escape time: music.
How to feel time: write.
How to release time: breathe.

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8908969b/attachment.html>

From MDeerr at hshlawyers.com  Wed Jul 29 14:07:16 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Wed, 29 Jul 2020 13:07:16 +0000
Subject: [ZendTo] ZendTo admin funtions not available when I log in from
 the WAN
In-Reply-To: <WM!54fedabe74f2c43e43d5f6c84d1be9bc2de09d0f5c404424be797e77bae08f0231c9e66179af39f39ed63e2b0ee485e5!@mx.jul.es>
References: <1595989858786.1070@hshlawyers.com>
 <WM!41e4d8fd6d6d896f6f88a51a317d2c019f0ab702990ebf8b43be638e4d0c39dfc21ce8257d32d6c014532c09e7705616!@mx.jul.es>
 <5b451503-1c87-3d20-fd1d-c83d9f10e420@Zend.To>
 <WM!54fedabe74f2c43e43d5f6c84d1be9bc2de09d0f5c404424be797e77bae08f0231c9e66179af39f39ed63e2b0ee485e5!@mx.jul.es>
 <694e25ff4a2d4f06aa3caf79fd8a1a73@HSH-MAIL.HSH.local>
Message-ID: <WM!3ccc6a9b472a1b4c3228a0f3e1e3e61df867721a0786ff30bc1dabb6ca12cced45f77beba0ce265c266fbcf27d861844!@mx.jul.es>

Thanks Jules. All good now.

From: Jules [mailto:Jules at Zend.To]
Sent: Wednesday, July 29, 2020 4:54 AM
To: ZendTo Users <zendto at zend.to>
Cc: Marlon Deerr <MDeerr at hshlawyers.com>
Subject: Re: [ZendTo] ZendTo admin funtions not available when I log in from the WAN

Marlon,

There is a setting in preferences.php called
  'adminLoginsMustBeLocal' => TRUE,
which is probably set to TRUE by default. Change it to FALSE and refresh the page in your browser.

It should be the setting immediately below "authAdmins".

Cheers,
Jules.

On 29/07/2020 03:30, Marlon Deerr via ZendTo wrote:

Hello All,



I have my ZendTo site now working from outside my LAN, however whenever I log in as an admin user coming in from the WAN, I am not given any of the admin related functions, however when I log in as an admin from inside our LAN, I have all admin functions available to me.



Am I missing a setting somewhere?



_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto:ZendTo at zend.to>

http://jul.es/mailman/listinfo/zendto



Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



How to stop time: kiss.

How to travel in time: read.

How to escape time: music.

How to feel time: write.

How to release time: breathe.



www.Zend.To<http://www.Zend.To>

Twitter: @JulesFM
-->
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200729/0cef0d3b/attachment-0001.html>

From MDeerr at hshlawyers.com  Wed Jul 29 15:03:17 2020
From: MDeerr at hshlawyers.com (Marlon Deerr)
Date: Wed, 29 Jul 2020 14:03:17 +0000
Subject: [ZendTo] Uploading - Scanning,
 Checksumming... message remains after drop-off
In-Reply-To: <WM!3078277bb18d1b9f1b6e896b88cd4f6a318f1918c6790490f103ef03cec30e9a6ee0c374f5aff1eee0e39907aa5b5a10!@mx.jul.es>
References: <1dfdbc698e964835a7bf664208fc2baa@HSH-MAIL.HSH.local>
 <WM!6d65508a11b7ab9ed96d95ae5651fd2160adeefd9ed86ce9e52a6d52fbe2a41db953d398f7064efe2ba2e3e135353e1a!@mx.jul.es>
 <WM!2bc674383c7efb3330fb6d16b3eafb9490d2e3a139e01abb3372fd4d6eaa14d547a0445dfb95a3b434572b844b2303e3!@mx.jul.es>
 <638026ba-624b-d3be-2a8f-fa249dffddc1@pcfreak.de>
 <WM!60435a379657aca346a15ca338e4637e3cffcb283ef4201b1f88eba46787d6ddf8efc3d15aeafb48d24886a0b1ce7c87!@mx.jul.es>
 <WM!3078277bb18d1b9f1b6e896b88cd4f6a318f1918c6790490f103ef03cec30e9a6ee0c374f5aff1eee0e39907aa5b5a10!@mx.jul.es>
 <99ce2040f4754183b7e1ae43f53ddebc@HSH-MAIL.HSH.local>
Message-ID: <WM!286af37f67ee4ced5c3b82768ec9e03e1c5b1d40ca78668c37a60f62fa78f24effd929f91d6c8204362ae11d433af426!@mx.jul.es>

@Der PCFreak - Interesting?.so when your Sophos was intercepting and scanning, were the ZendTo uploads still completing or where they failing? In my case, the upload still went through and the notice went out to all recipients of the uploads. All works fine except for the Uploading? imaging remaining on the screen.

I?ll look to see if this is related to our AntiVirus as well. Thanks for your reply.

From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Der PCFreak via ZendTo
Sent: Thursday, July 23, 2020 10:25 AM
To: zendto at zend.to
Cc: Der PCFreak <mailinglists at pcfreak.de>
Subject: Re: [ZendTo] Uploading - Scanning, Checksumming... message remains after drop-off


Hi Marlon,



I had similar issues. The problem in my case was, that the local Anti-Virus transparently went between the client and my ZendTo server. It immediately picked up the file(s) completely and tried to scan them all locally and then did the request to ZendTo which totally messed up everything. In my case we created and exclusion for the internal IP and the internal fqdn of the ZendTo system from the Antivirus-Webprotection which was Sophos in our case. Then it worked as expected.

Maybe you have a similar problem and maybe you find this info useful. If not just ignore my mail.

Regards

Peter
On 23/07/2020 14:50, Marlon Deerr via ZendTo wrote:

I?m noticing the following message remaining at times when I perform a drop-off. I?m thinking this ?may? be browser related. It is somewhat misleading as the drop-off is actually completed but with the message remaining on the screen, it can confuse a sender. They may think the process was not complete and then re-attempt another drop-off, not realizing that the recipient already received the notice of the drop-off.

I?ll continue to test this theory out but I know for sure I have received this more than once on different web browsers.

Anyone else experiencing this?


[cid:image001.png at 01D6658F.7B3248B0]



_______________________________________________

ZendTo mailing list

ZendTo at zend.to<mailto:ZendTo at zend.to>

http://jul.es/mailman/listinfo/zendto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200729/10b13984/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14963 bytes
Desc: image001.png
URL: <http://jul.es/pipermail/zendto/attachments/20200729/10b13984/attachment-0001.png>

From Jules at Zend.To  Wed Jul 29 15:17:46 2020
From: Jules at Zend.To (Jules)
Date: Wed, 29 Jul 2020 15:17:46 +0100
Subject: [ZendTo] Uploading - Scanning,
 Checksumming... message remains after drop-off
In-Reply-To: <WM!286af37f67ee4ced5c3b82768ec9e03e1c5b1d40ca78668c37a60f62fa78f24effd929f91d6c8204362ae11d433af426!@mx.jul.es>
References: <1dfdbc698e964835a7bf664208fc2baa@HSH-MAIL.HSH.local>
 <WM!6d65508a11b7ab9ed96d95ae5651fd2160adeefd9ed86ce9e52a6d52fbe2a41db953d398f7064efe2ba2e3e135353e1a!@mx.jul.es>
 <WM!2bc674383c7efb3330fb6d16b3eafb9490d2e3a139e01abb3372fd4d6eaa14d547a0445dfb95a3b434572b844b2303e3!@mx.jul.es>
 <638026ba-624b-d3be-2a8f-fa249dffddc1@pcfreak.de>
 <WM!60435a379657aca346a15ca338e4637e3cffcb283ef4201b1f88eba46787d6ddf8efc3d15aeafb48d24886a0b1ce7c87!@mx.jul.es>
 <WM!3078277bb18d1b9f1b6e896b88cd4f6a318f1918c6790490f103ef03cec30e9a6ee0c374f5aff1eee0e39907aa5b5a10!@mx.jul.es>
 <99ce2040f4754183b7e1ae43f53ddebc@HSH-MAIL.HSH.local>
 <WM!286af37f67ee4ced5c3b82768ec9e03e1c5b1d40ca78668c37a60f62fa78f24effd929f91d6c8204362ae11d433af426!@mx.jul.es>
Message-ID: <cffe1a4b-9a85-5a12-5709-c047c8fbf47c@Zend.To>

If you get that happening, please take a look in the JavaScript Console 
in your web browser.
There might well be clues in the output there. And also in your 
/var/log/zendto/zendto.log file.

Cheers,
Jules.

On 29/07/2020 15:03, Marlon Deerr via ZendTo wrote:
>
> @Der PCFreak - Interesting?.so when your Sophos was intercepting and 
> scanning, were the ZendTo uploads still completing or where they 
> failing? In my case, the upload still went through and the notice went 
> out to all recipients of the uploads. All works fine except for the 
> Uploading? imaging remaining on the screen.
>
> I?ll look to see if this is related to our AntiVirus as well. Thanks 
> for your reply.
>
> *From:* ZendTo [mailto:zendto-bounces at zend.to] *On Behalf Of *Der 
> PCFreak via ZendTo
> *Sent:* Thursday, July 23, 2020 10:25 AM
> *To:* zendto at zend.to
> *Cc:* Der PCFreak <mailinglists at pcfreak.de>
> *Subject:* Re: [ZendTo] Uploading - Scanning, Checksumming... message 
> remains after drop-off
>
> Hi Marlon,
>
> I had similar issues. The problem in my case was, that the local 
> Anti-Virus transparently went between the client and my ZendTo server. 
> It immediately picked up the file(s) completely and tried to scan them 
> all locally and then did the request to ZendTo which totally messed up 
> everything. In my case we created and exclusion for the internal IP 
> and the internal fqdn of the ZendTo system from the 
> Antivirus-Webprotection which was Sophos in our case. Then it worked 
> as expected.
>
> Maybe you have a similar problem and maybe you find this info useful. 
> If not just ignore my mail.
>
> Regards
>
> Peter
>
> On 23/07/2020 14:50, Marlon Deerr via ZendTo wrote:
>
>     I?m noticing the following message remaining at times when I
>     perform a drop-off. I?m thinking this ?may? be browser related. It
>     is somewhat misleading as the drop-off is actually completed but
>     with the message remaining on the screen, it can confuse a sender.
>     They may think the process was not complete and then re-attempt
>     another drop-off, not realizing that the recipient already
>     received the notice of the drop-off.
>
>     I?ll continue to test this theory out but I know for sure I have
>     received this more than once on different web browsers.
>
>     Anyone else experiencing this?
>
>
>
>     _______________________________________________
>
>     ZendTo mailing list
>
>     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>
>     http://jul.es/mailman/listinfo/zendto  <http://jul.es/mailman/listinfo/zendto>
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Making machines do what you want requires only two qualities:
  1) Being slightly more stubborn that the computer, &
  2) Remembering that computers are electrified rocks.' - @JediJeremy

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200729/751ad6ea/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14963 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/751ad6ea/attachment-0001.png>

From mailinglists at pcfreak.de  Wed Jul 29 16:10:51 2020
From: mailinglists at pcfreak.de (Der PCFreak)
Date: Wed, 29 Jul 2020 17:10:51 +0200
Subject: [ZendTo] Uploading - Scanning,
 Checksumming... message remains after drop-off
In-Reply-To: <99ce2040f4754183b7e1ae43f53ddebc@HSH-MAIL.HSH.local>
References: <1dfdbc698e964835a7bf664208fc2baa@HSH-MAIL.HSH.local>
 <WM!6d65508a11b7ab9ed96d95ae5651fd2160adeefd9ed86ce9e52a6d52fbe2a41db953d398f7064efe2ba2e3e135353e1a!@mx.jul.es>
 <WM!2bc674383c7efb3330fb6d16b3eafb9490d2e3a139e01abb3372fd4d6eaa14d547a0445dfb95a3b434572b844b2303e3!@mx.jul.es>
 <638026ba-624b-d3be-2a8f-fa249dffddc1@pcfreak.de>
 <WM!60435a379657aca346a15ca338e4637e3cffcb283ef4201b1f88eba46787d6ddf8efc3d15aeafb48d24886a0b1ce7c87!@mx.jul.es>
 <WM!3078277bb18d1b9f1b6e896b88cd4f6a318f1918c6790490f103ef03cec30e9a6ee0c374f5aff1eee0e39907aa5b5a10!@mx.jul.es>
 <99ce2040f4754183b7e1ae43f53ddebc@HSH-MAIL.HSH.local>
 <cae18f5e-afb0-6950-5f2f-72a63b93c2c9@pcfreak.de>
Message-ID: <WM!2c486f544a55e4aa75b5f4c05424126befa990df52efdef433279c23c322e1215ae5581c468b9a703b7e7c21e618cc2f!@mx.jul.es>

@Marlon

I can?t remember exactly but I think I remember how I could detect it. I 
logged into my Linux box (Zendto server) and did a

|watch -n0 ls -lh /var/zendto/incoming|

to find out, that even the browser said upload completed the AV was 
still trying to upload which caused the problems.

I hope you find your problem.

On 29/07/2020 16:03, Marlon Deerr wrote:

> @Der PCFreak - Interesting?.so when your Sophos was intercepting and 
> scanning, were the ZendTo uploads still completing or where they 
> failing? In my case, the upload still went through and the notice went 
> out to all recipients of the uploads. All works fine except for the 
> Uploading? imaging remaining on the screen.
>
> I?ll look to see if this is related to our AntiVirus as well. Thanks 
> for your reply.
>
>
> Marlon Deerr, Technology Manager
> 416-572-8795(direct) | MDeerr at hshlawyers.com 
> <mailto:MDeerr at hshlawyers.com>
> <https://www.hshlawyers.com>
> <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> 
> <https://twitter.com/hshlawyers> 
> <https://www.facebook.com/HSHPersonalInjuryLawyers/> 
> <https://www.youtube.com/user/hshlawyers> 	3500 - 20 Queen St. W., 
> Toronto, ON M5H 3R3
> Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com 
> <https://www.hshlawyers.com>
>
>
> This Howie Sacks & Henry e-mail is privileged, confidential and 
> subject to copyright. Any unauthorized use or disclosure is prohibited.
>
>
>
> *From:* ZendTo [mailto:zendto-bounces at zend.to] *On Behalf Of *Der 
> PCFreak via ZendTo
> *Sent:* Thursday, July 23, 2020 10:25 AM
> *To:* zendto at zend.to
> *Cc:* Der PCFreak <mailinglists at pcfreak.de>
> *Subject:* Re: [ZendTo] Uploading - Scanning, Checksumming... message 
> remains after drop-off
>
> Hi Marlon,
>
> I had similar issues. The problem in my case was, that the local 
> Anti-Virus transparently went between the client and my ZendTo server. 
> It immediately picked up the file(s) completely and tried to scan them 
> all locally and then did the request to ZendTo which totally messed up 
> everything. In my case we created and exclusion for the internal IP 
> and the internal fqdn of the ZendTo system from the 
> Antivirus-Webprotection which was Sophos in our case. Then it worked 
> as expected.
>
> Maybe you have a similar problem and maybe you find this info useful. 
> If not just ignore my mail.
>
> Regards
>
> Peter
>
> On 23/07/2020 14:50, Marlon Deerr via ZendTo wrote:
>
>     I?m noticing the following message remaining at times when I
>     perform a drop-off. I?m thinking this ?may? be browser related. It
>     is somewhat misleading as the drop-off is actually completed but
>     with the message remaining on the screen, it can confuse a sender.
>     They may think the process was not complete and then re-attempt
>     another drop-off, not realizing that the recipient already
>     received the notice of the drop-off.
>
>     I?ll continue to test this theory out but I know for sure I have
>     received this more than once on different web browsers.
>
>     Anyone else experiencing this?
>
>
>
>     _______________________________________________
>
>     ZendTo mailing list
>
>     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>
>     http://jul.es/mailman/listinfo/zendto
>
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8af5bfc0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagec6e406.JPG
Type: image/jpeg
Size: 125353 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8af5bfc0/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image5b670f.JPG
Type: image/jpeg
Size: 7976 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8af5bfc0/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image034fe2.JPG
Type: image/jpeg
Size: 7843 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8af5bfc0/attachment-0007.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagef680c6.JPG
Type: image/jpeg
Size: 7268 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8af5bfc0/attachment-0008.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image17b998.JPG
Type: image/jpeg
Size: 7059 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8af5bfc0/attachment-0009.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14963 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8af5bfc0/attachment-0001.png>

From Jules at Zend.To  Wed Jul 29 16:43:11 2020
From: Jules at Zend.To (Jules)
Date: Wed, 29 Jul 2020 16:43:11 +0100
Subject: [ZendTo] Uploading - Scanning,
 Checksumming... message remains after drop-off
In-Reply-To: <WM!2c486f544a55e4aa75b5f4c05424126befa990df52efdef433279c23c322e1215ae5581c468b9a703b7e7c21e618cc2f!@mx.jul.es>
References: <1dfdbc698e964835a7bf664208fc2baa@HSH-MAIL.HSH.local>
 <WM!6d65508a11b7ab9ed96d95ae5651fd2160adeefd9ed86ce9e52a6d52fbe2a41db953d398f7064efe2ba2e3e135353e1a!@mx.jul.es>
 <WM!2bc674383c7efb3330fb6d16b3eafb9490d2e3a139e01abb3372fd4d6eaa14d547a0445dfb95a3b434572b844b2303e3!@mx.jul.es>
 <638026ba-624b-d3be-2a8f-fa249dffddc1@pcfreak.de>
 <WM!60435a379657aca346a15ca338e4637e3cffcb283ef4201b1f88eba46787d6ddf8efc3d15aeafb48d24886a0b1ce7c87!@mx.jul.es>
 <WM!3078277bb18d1b9f1b6e896b88cd4f6a318f1918c6790490f103ef03cec30e9a6ee0c374f5aff1eee0e39907aa5b5a10!@mx.jul.es>
 <99ce2040f4754183b7e1ae43f53ddebc@HSH-MAIL.HSH.local>
 <cae18f5e-afb0-6950-5f2f-72a63b93c2c9@pcfreak.de>
 <WM!2c486f544a55e4aa75b5f4c05424126befa990df52efdef433279c23c322e1215ae5581c468b9a703b7e7c21e618cc2f!@mx.jul.es>
Message-ID: <db22cce5-c96d-bf7d-6834-3efc52e52567@Zend.To>

Assuming you're running a nice recent version, one suggestion which may 
appear slightly odd:
reduce the 'uploadChunkSize' in preferences.php.

If ZendTo decides it needs to upload the file in more than 1 chunk, then 
your Sophos AV won't see the whole file, so probably won't be able to 
check much on it. So it *may* be more inclined to let it through, and 
more quickly.

Just a thought. It may not help at all. But you never know...

Cheers,
Jules.

On 29/07/2020 16:10, Der PCFreak via ZendTo wrote:
>
> @Marlon
>
> I can?t remember exactly but I think I remember how I could detect it. 
> I logged into my Linux box (Zendto server) and did a
>
> |watch -n0 ls -lh /var/zendto/incoming|
>
> to find out, that even the browser said upload completed the AV was 
> still trying to upload which caused the problems.
>
> I hope you find your problem.
>
> On 29/07/2020 16:03, Marlon Deerr wrote:
>
>> @Der PCFreak - Interesting?.so when your Sophos was intercepting and 
>> scanning, were the ZendTo uploads still completing or where they 
>> failing? In my case, the upload still went through and the notice 
>> went out to all recipients of the uploads. All works fine except for 
>> the Uploading? imaging remaining on the screen.
>>
>> I?ll look to see if this is related to our AntiVirus as well. Thanks 
>> for your reply.
>>
>>
>> Marlon Deerr, Technology Manager
>> 416-572-8795(direct) | MDeerr at hshlawyers.com 
>> <mailto:MDeerr at hshlawyers.com>
>> <https://www.hshlawyers.com>
>> <https://www.linkedin.com/company/howie-sacks-&-henry-llp---personal-injury-law/> 
>> <https://twitter.com/hshlawyers> 
>> <https://www.facebook.com/HSHPersonalInjuryLawyers/> 
>> <https://www.youtube.com/user/hshlawyers> 	3500 - 20 Queen St. W., 
>> Toronto, ON M5H 3R3
>> Fax: 416-361-0083 | Toll Free: 877-474-5997 | www.hshlawyers.com 
>> <https://www.hshlawyers.com>
>>
>>
>> This Howie Sacks & Henry e-mail is privileged, confidential and 
>> subject to copyright. Any unauthorized use or disclosure is prohibited.
>>
>>
>>
>> *From:* ZendTo [mailto:zendto-bounces at zend.to] *On Behalf Of *Der 
>> PCFreak via ZendTo
>> *Sent:* Thursday, July 23, 2020 10:25 AM
>> *To:* zendto at zend.to
>> *Cc:* Der PCFreak <mailinglists at pcfreak.de>
>> *Subject:* Re: [ZendTo] Uploading - Scanning, Checksumming... message 
>> remains after drop-off
>>
>> Hi Marlon,
>>
>> I had similar issues. The problem in my case was, that the local 
>> Anti-Virus transparently went between the client and my ZendTo 
>> server. It immediately picked up the file(s) completely and tried to 
>> scan them all locally and then did the request to ZendTo which 
>> totally messed up everything. In my case we created and exclusion for 
>> the internal IP and the internal fqdn of the ZendTo system from the 
>> Antivirus-Webprotection which was Sophos in our case. Then it worked 
>> as expected.
>>
>> Maybe you have a similar problem and maybe you find this info useful. 
>> If not just ignore my mail.
>>
>> Regards
>>
>> Peter
>>
>> On 23/07/2020 14:50, Marlon Deerr via ZendTo wrote:
>>
>>     I?m noticing the following message remaining at times when I
>>     perform a drop-off. I?m thinking this ?may? be browser related.
>>     It is somewhat misleading as the drop-off is actually completed
>>     but with the message remaining on the screen, it can confuse a
>>     sender. They may think the process was not complete and then
>>     re-attempt another drop-off, not realizing that the recipient
>>     already received the notice of the drop-off.
>>
>>     I?ll continue to test this theory out but I know for sure I have
>>     received this more than once on different web browsers.
>>
>>     Anyone else experiencing this?
>>
>>
>>
>>     _______________________________________________
>>
>>     ZendTo mailing list
>>
>>     ZendTo at zend.to  <mailto:ZendTo at zend.to>
>>
>>     http://jul.es/mailman/listinfo/zendto  <http://jul.es/mailman/listinfo/zendto>
>>
> ?
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Infosec: A profession that turns normal people into whiskey drinking,
  swearing, paranoid, disheartened curmudgeons with no hope for the
  future of computers or humanity.' - Urban Dictionary

www.Zend.To
Twitter: @JulesFM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8383050c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagec6e406.JPG
Type: image/jpeg
Size: 125353 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8383050c/attachment-0005.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image5b670f.JPG
Type: image/jpeg
Size: 7976 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8383050c/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image034fe2.JPG
Type: image/jpeg
Size: 7843 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8383050c/attachment-0007.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagef680c6.JPG
Type: image/jpeg
Size: 7268 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8383050c/attachment-0008.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image17b998.JPG
Type: image/jpeg
Size: 7059 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8383050c/attachment-0009.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14963 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20200729/8383050c/attachment-0001.png>