From zend.to at neilzone.co.uk  Fri Apr  5 16:29:04 2019
From: zend.to at neilzone.co.uk (zend.to at neilzone.co.uk)
Date: Fri, 5 Apr 2019 16:29:04 +0100
Subject: [ZendTo] Scripted use of zend.to
References: <EBB29FBB-BF92-4E2F-A3AF-78A783922490@neilzone.co.uk>
Message-ID: <WM!72e88bf2b345d7839993faba3a2831e2a4e18a38bf8f5e791838c004074466a2f37b2142de35524249105c000319044a!@mx.jul.es>

I have had a quick look through recent archives, and I can?t see anything on this, but apologies if it has been covered already.

Does anyone have an example of using zend.to in a scripted manner, rather than through the web browser?

I can think of a number of occasions where it would be useful to be able to generate a zend.to drop-off request (to have someone drop a file off for me) without me needing to log in to the UI and do it. I suspect it can be done quite readily with curl, but I wonder if someone has already tackled this and would be willing to share the output?

Best wishes

Neil



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

From douglagm at gmail.com  Sat Apr  6 09:35:57 2019
From: douglagm at gmail.com (Gregg Douglas)
Date: Sat, 6 Apr 2019 10:35:57 +0200
Subject: [ZendTo] Scripted use of zend.to
In-Reply-To: <WM!61cfd11b7cafd522d20af3a1989a7a4be9c4169930bfb9537945451ec922f13f1dbece2201a9e04d334b334046c03f855fbdc4bb745fa8767bdcb3f09916ed13!@mx.jul.es>
References: <EBB29FBB-BF92-4E2F-A3AF-78A783922490@neilzone.co.uk>
 <WM!72e88bf2b345d7839993faba3a2831e2a4e18a38bf8f5e791838c004074466a2f37b2142de35524249105c000319044a!@mx.jul.es>
 <WM!61cfd11b7cafd522d20af3a1989a7a4be9c4169930bfb9537945451ec922f13f1dbece2201a9e04d334b334046c03f855fbdc4bb745fa8767bdcb3f09916ed13!@mx.jul.es>
 <CAKE9jaY_G2hLT0ReCcCGsHSgaUG6bU_bOfvGdd1ixDo0cPJEJQ@mail.gmail.com>
Message-ID: <WM!a300a1b4bb66d25e535f209b81e2d1a4aa4cb5ed7180ab064b1f190d197af9831b46989e599f9f18a5ac3313be7264aa!@mx.jul.es>

An API would be an awesome addition...

On Fri, Apr 5, 2019 at 5:29 PM Neil via ZendTo <zendto at zend.to> wrote:

> I have had a quick look through recent archives, and I can?t see anything
> on this, but apologies if it has been covered already.
>
> Does anyone have an example of using zend.to in a scripted manner, rather
> than through the web browser?
>
> I can think of a number of occasions where it would be useful to be able
> to generate a zend.to drop-off request (to have someone drop a file off
> for me) without me needing to log in to the UI and do it. I suspect it can
> be done quite readily with curl, but I wonder if someone has already
> tackled this and would be willing to share the output?
>
> Best wishes
>
> Neil
>
>
>
> _______________________________________________
> 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/20190406/9f63c272/attachment.html>

From kbe2 at lehigh.edu  Thu Apr 11 22:26:28 2019
From: kbe2 at lehigh.edu (Keith Erekson)
Date: Thu, 11 Apr 2019 17:26:28 -0400
Subject: [ZendTo] Scripted use of zend.to
In-Reply-To: <WM!cb366a4cd40d02d1e3dbaba8aecd6998c3656bc8d7a9f7e54101f7a1ee2f43ba7c8f2ede649979cd954e18715cc0e1fc254cdd5c288e9e6407d02bb387b8ea93!@mx.jul.es>
References: <EBB29FBB-BF92-4E2F-A3AF-78A783922490@neilzone.co.uk>
 <WM!72e88bf2b345d7839993faba3a2831e2a4e18a38bf8f5e791838c004074466a2f37b2142de35524249105c000319044a!@mx.jul.es>
 <WM!cb366a4cd40d02d1e3dbaba8aecd6998c3656bc8d7a9f7e54101f7a1ee2f43ba7c8f2ede649979cd954e18715cc0e1fc254cdd5c288e9e6407d02bb387b8ea93!@mx.jul.es>
 <89516a74-7fd1-cd4d-0809-45790403a96f@lehigh.edu>
Message-ID: <WM!6645ad4d44a0c03253152ebc24368a8a8e4df0a923c7fb7756e8cd9589e2dfdafb6737aed17a3becd26281a8d0f357f6!@mx.jul.es>

The previous implementation of this project, back when it was the "UD
Dropbox" had some sort of "custom upload form" functionality.

I don't remember exactly what they called it, and 30 seconds of Googling
hasn't turned up a download location for their code, but it's
essentially a stripped-down UI that lets you (the admin) hard-code the
recipient info, so people can't screw up the file transfer.

This feature was dropped from ZendTo, but we've been forward-porting it
for years, as some of our departments depend on it for various reasons.

Using it requires some modifications to ZendTo, to allow uploads without
the CAPTCHA verification. (By which I mean: we have been too lazy to
implement the CAPTCHA in our custom dropoff interface; it was
implemented before ZendTo had a CAPTCHA.)

It wouldn't be possible to use this directly from a script (e.g., curl
-X POST ...), as it still uses JavaScript, but you could possibly use it
as a starting point to add a similar API interface.

If there's interest, I can post some sanitized git diffs and/or some
documentation about how it works.

~Keith

On 4/5/19 11:29 AM, Neil via ZendTo wrote:
> I have had a quick look through recent archives, and I can?t see
> anything on this, but apologies if it has been covered already.
>
> Does anyone have an example of using zend.to in a scripted manner,
> rather than through the web browser?
>
> I can think of a number of occasions where it would be useful to be
> able to generate a zend.to drop-off request (to have someone drop a
> file off for me) without me needing to log in to the UI and do it. I
> suspect it can be done quite readily with curl, but I wonder if
> someone has already tackled this and would be willing to share the output?
>
> Best wishes
>
> Neil
>
>
>
>
> _______________________________________________
> 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/20190411/89428fdc/attachment.html>

From john.thurston at alaska.gov  Thu Apr 11 22:45:23 2019
From: john.thurston at alaska.gov (John Thurston)
Date: Thu, 11 Apr 2019 13:45:23 -0800
Subject: [ZendTo] NSSDROPBOX_DATA_DIR and logrotate
References: <0029a60a-5ac3-e547-67fc-ddc78e93dfc6@alaska.gov>
Message-ID: <WM!101ac07959aca9e5c98376e488d62d12c0b1e53eae67123ccf614c655e7094ae6e6a2570c5ea97c93a461013e15fb4e8!@mx.jul.es>

I'm not exactly sure when this problem started, but the log rotation 
process is failing.

The file:
   /etc/logrotate.d/zendto
references the files:
   /var/log/zendto/zendto.log
   /var/zendto/zendto.log

But that isn't where my logs are. My config in:
   preferences.php
has the following:
   define('NSSDROPBOX_DATA_DIR','/var/zendto-storage/zendto/');


I can go edit /etc/logrotate.d/zendto and hope it persists through the 
next update.

Is there some other way I should correct this?



-- 
    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 zend.to at neilzone.co.uk  Fri Apr 12 08:21:26 2019
From: zend.to at neilzone.co.uk (zend.to at neilzone.co.uk)
Date: Fri, 12 Apr 2019 08:21:26 +0100
Subject: [ZendTo] Scripted use of zend.to
In-Reply-To: <WM!ac343dcf3df6fd70b160d502055fa96c12a7999639fbd8e6d181dac80909f8846cd2c3eea8a28fc9f6f7b99fb00e1b1c4922de9ce5e87a2369f81abdda0ecad1!@mx.jul.es>
References: <EBB29FBB-BF92-4E2F-A3AF-78A783922490@neilzone.co.uk>
 <WM!72e88bf2b345d7839993faba3a2831e2a4e18a38bf8f5e791838c004074466a2f37b2142de35524249105c000319044a!@mx.jul.es>
 <WM!cb366a4cd40d02d1e3dbaba8aecd6998c3656bc8d7a9f7e54101f7a1ee2f43ba7c8f2ede649979cd954e18715cc0e1fc254cdd5c288e9e6407d02bb387b8ea93!@mx.jul.es>
 <89516a74-7fd1-cd4d-0809-45790403a96f@lehigh.edu>
 <WM!6645ad4d44a0c03253152ebc24368a8a8e4df0a923c7fb7756e8cd9589e2dfdafb6737aed17a3becd26281a8d0f357f6!@mx.jul.es>
 <WM!ac343dcf3df6fd70b160d502055fa96c12a7999639fbd8e6d181dac80909f8846cd2c3eea8a28fc9f6f7b99fb00e1b1c4922de9ce5e87a2369f81abdda0ecad1!@mx.jul.es>
 <4DCD579A-2F7C-437A-AABF-88DBE450169C@neilzone.co.uk>
Message-ID: <WM!f8347720f7bb71dff980b7538a09e8b59490bc421be4552936580c45c5f28908afbb1fb72db26ab87a0c9347ddad533c!@mx.jul.es>



> On 11 Apr 2019, at 22:26, Keith Erekson via ZendTo <zendto at zend.to> wrote:

Hello Keith

> If there's interest, I can post some sanitized git diffs and/or some documentation about how it works.


I would be interested in seeing it, if, for no other reason, than to see how others have extended zend.to.

If it?s no hassle, that would be great. Thank you!

Best wishes

Neil



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

From KLE at msktd.com  Fri Apr 12 21:41:47 2019
From: KLE at msktd.com (Ken Etter)
Date: Fri, 12 Apr 2019 16:41:47 -0400
Subject: [ZendTo] API for login?
References: <5CB0F80B0200001300133E82@mail.msktd.com>
Message-ID: <WM!96ac6513ce83ba47a4c2af0e424b2b9ce0f690867a2072d8e3167585c59952ffa7337c2c17847a14871746e866f07739!@mx.jul.es>

We have some internal web sites that I have tied into our network so that users are automatically logged in if they are logged into our network.  Just had someone ask if there was a way to do that with ZendTo.  Right now I have ZendTo setup to do LDAP authentication.  Is there any way to automate the login process?

Ken Etter, System Administrator
Architectural Group
260.432.9337 | msktd.com




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190412/7b74e64e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE.png
Type: image/png
Size: 18080 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20190412/7b74e64e/attachment-0001.png>

From klou at themusiclink.net  Tue Apr 16 18:00:20 2019
From: klou at themusiclink.net (Kris Lou)
Date: Tue, 16 Apr 2019 10:00:20 -0700
Subject: [ZendTo] zendto.multi-domain.com, shared backend
References: <CAGyTNKEV83J3gD7U5qyQ5Ei=kVyh-76LWdkMSMVbA78eko2=2Q@mail.gmail.com>
Message-ID: <WM!cfbd515bba6a3a60a5f1695fa4663db1abf6332fd9e5dc76682fc57a1226d6f907113e7552d0d98990519d7697af8377!@mx.jul.es>

All,

Previously, I ran dual copies of the /opt/zendto directories and pointed
the data and library directories to the same location.  Apache webroots
were pointing to different locations, and those had respective config files.

I've since merged the two (and adjusted text accordingly), and both domains
point to a single installation, but I can apparently only dropoff when
accessing via one domain -- the one that matches "serverRoot" in
preferences.php.  Otherwise, it complains of "Note that you cannot drop-off
directories, only files."

Is there any way to whitelist this 2nd root URL?  Adding a 2nd value to
serverRoot?

Not the end of the world if I can't, but thought I'd ask.

Thanks,

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

From kevin.miller at juneau.org  Wed Apr 17 23:51:35 2019
From: kevin.miller at juneau.org (Kevin Miller)
Date: Wed, 17 Apr 2019 22:51:35 +0000
Subject: [ZendTo] Migrating to new server
References: <5abce6f339d44f7fbd7885e890549297@City-Exch-DB2.cbj.local>
Message-ID: <WM!7cc603c45af744deb7c7bbdbcca55bdeec3cf7d50ed1d93095c24202718a9694edf6f4e641d2d5bb770ac46eb16282f9!@mx.jul.es>

Old server:
	Debian Jessie (8)
	Zendto 4.28

New server:
	Debian Stretch (9)
	Zendto 5.17-6

I built a brand new server and with a minimal amount of fuss was able to get it configured thanks to Jules' handy update scripts.  Now however I want to move the existing uploads to the new server from the old one.  I found some old messages in this list which said to copy ALL the directories under /var/zendto/drop-offs and /var/zendto/incoming.  Easy enough.  Also saw a post by Jules mentioning to stop the cron.d jobs so things don't get out of whack during cleanup.

I don't know how to migrate the sql stuff however.  As nearly as I can tell, both servers are using SQLite.  Mysql does not exist on my new server (php7.3-mysql is installed however).  It is installed on the old server but not being used.  At least there aren't any tables with names like "zendto" or anything.

If I had to hazard a guess I'd suppose that there may well have been schema changes from 4.28 to the current version, 5.17-6.  

So beyond moving the files over, what's the optimal way to get the database information moved?  Or is it even possible?

Thanks.

...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357




From kevin.miller at juneau.org  Fri Apr 19 20:08:25 2019
From: kevin.miller at juneau.org (Kevin Miller)
Date: Fri, 19 Apr 2019 19:08:25 +0000
Subject: [ZendTo] Migrating to new server
In-Reply-To: <WM!69595300dd5db5bffe8a1c18afb2dc817025c77f72de6bc0e7b490db138512b7d12bcab5d76f648093444ef3042a97a6ee9e413cd9169a40a3a24fa9f705ae77!@mx.jul.es>
References: <5abce6f339d44f7fbd7885e890549297@City-Exch-DB2.cbj.local>
 <WM!7cc603c45af744deb7c7bbdbcca55bdeec3cf7d50ed1d93095c24202718a9694edf6f4e641d2d5bb770ac46eb16282f9!@mx.jul.es>
 <WM!69595300dd5db5bffe8a1c18afb2dc817025c77f72de6bc0e7b490db138512b7d12bcab5d76f648093444ef3042a97a6ee9e413cd9169a40a3a24fa9f705ae77!@mx.jul.es>
 <322e2651593b4601890b75f5cec8c504@City-Exch-DB2.cbj.local>
Message-ID: <WM!d6ce1551267897a4b8eb0c186f8ac768525ba26f8278c87c02080c56b461792cf4e67d74200ad91d44279219093778f6!@mx.jul.es>

Well, this turned out easier than I expected.

I install sqlite3 on my old and new zendto servers. Then ran the following command:
  sqlite3 zendto.sqlite .dump > zendto.sqlite.txt

This gave me a text dump of the databases.  From there I was able to look at the schema on both servers. with:
  cat zendto.sqlite.txt | grep -v INDEX | grep -v INSERT

That pretty much cleaned out most of the cruft that was irrelevant.  Note I only had a dozen or so messages to worry about.  On a very active server you may have a bit more work to do to get to just the schema.  Or probably there's a sqlite command to just dump the schema.

Anyway, the schema was the same on both so I just copied the files/dirs in /var/zendto/drop-offs to the new serer, then copied the old database to the new one and restarted apache.

Prior to copying all the files over, I created a test upload so I'd have an active dropoff to verify I could still get it on the new box.  After copying everything over, there was no problem going in and retrieving the dropoff that I'd originally made on the old server from the new server.

The only thing that didn't seem to come over was the statistics when I tried to view them, but I can live with that.

Hope this helps someone down the line.  It was definitely worth the upgrade - nice new security and encryption features, etc.

...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357

-----Original Message-----
From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Kevin Miller via ZendTo
Sent: Wednesday, April 17, 2019 2:52 PM
To: 'ZendTo Users'
Cc: Kevin Miller
Subject: [ZendTo] Migrating to new server

Old server:
	Debian Jessie (8)
	Zendto 4.28

New server:
	Debian Stretch (9)
	Zendto 5.17-6

I built a brand new server and with a minimal amount of fuss was able to get it configured thanks to Jules' handy update scripts.  Now however I want to move the existing uploads to the new server from the old one.  I found some old messages in this list which said to copy ALL the directories under /var/zendto/drop-offs and /var/zendto/incoming.  Easy enough.  Also saw a post by Jules mentioning to stop the cron.d jobs so things don't get out of whack during cleanup.

I don't know how to migrate the sql stuff however.  As nearly as I can tell, both servers are using SQLite.  Mysql does not exist on my new server (php7.3-mysql is installed however).  It is installed on the old server but not being used.  At least there aren't any tables with names like "zendto" or anything.

If I had to hazard a guess I'd suppose that there may well have been schema changes from 4.28 to the current version, 5.17-6.  

So beyond moving the files over, what's the optimal way to get the database information moved?  Or is it even possible?

Thanks.

...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357



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


From Jules at Zend.To  Sun Apr 21 10:27:36 2019
From: Jules at Zend.To (Jules)
Date: Sun, 21 Apr 2019 10:27:36 +0100
Subject: [ZendTo] Migrating to new server
In-Reply-To: <WM!d6ce1551267897a4b8eb0c186f8ac768525ba26f8278c87c02080c56b461792cf4e67d74200ad91d44279219093778f6!@mx.jul.es>
References: <5abce6f339d44f7fbd7885e890549297@City-Exch-DB2.cbj.local>
 <WM!7cc603c45af744deb7c7bbdbcca55bdeec3cf7d50ed1d93095c24202718a9694edf6f4e641d2d5bb770ac46eb16282f9!@mx.jul.es>
 <WM!69595300dd5db5bffe8a1c18afb2dc817025c77f72de6bc0e7b490db138512b7d12bcab5d76f648093444ef3042a97a6ee9e413cd9169a40a3a24fa9f705ae77!@mx.jul.es>
 <322e2651593b4601890b75f5cec8c504@City-Exch-DB2.cbj.local>
 <WM!d6ce1551267897a4b8eb0c186f8ac768525ba26f8278c87c02080c56b461792cf4e67d74200ad91d44279219093778f6!@mx.jul.es>
Message-ID: <179d14e4-6d98-e0c2-1da2-8b7cb59a30d2@Zend.To>

On 19/04/2019 8:08 pm, Kevin Miller via ZendTo wrote:
> Well, this turned out easier than I expected.
>
> I install sqlite3 on my old and new zendto servers. Then ran the following command:
>    sqlite3 zendto.sqlite .dump > zendto.sqlite.txt
>
> This gave me a text dump of the databases.  From there I was able to look at the schema on both servers. with:
>    cat zendto.sqlite.txt | grep -v INDEX | grep -v INSERT
>
> That pretty much cleaned out most of the cruft that was irrelevant.  Note I only had a dozen or so messages to worry about.  On a very active server you may have a bit more work to do to get to just the schema.  Or probably there's a sqlite command to just dump the schema.
Funnily enough, it's simply
 ??? .schema
:-)

>
> Anyway, the schema was the same on both so I just copied the files/dirs in /var/zendto/drop-offs to the new serer, then copied the old database to the new one and restarted apache.
And if the schema isn't the same, the overnight cleanup cron job will 
fix the missing bits of the schema for you.
So if after moving everything over, it doesn't work, just leave it for 
the day and try again in the morning.

>
> Prior to copying all the files over, I created a test upload so I'd have an active dropoff to verify I could still get it on the new box.  After copying everything over, there was no problem going in and retrieving the dropoff that I'd originally made on the old server from the new server.
>
> The only thing that didn't seem to come over was the statistics when I tried to view them, but I can live with that.
Provided you copy of the rrd data file, you should be able to do this. I 
certainly have done. The location of the RRD file is near the top of 
preferences.php.

> Hope this helps someone down the line.  It was definitely worth the upgrade - nice new security and encryption features, etc.
The key step here is to *not* try to do an in-place upgrade. As you have 
demonstrated, build a new server, get it all working exactly how you 
want it, and only then migrate the existing drop-offs and database across.

Well done!

Cheers,
Jules.
>
> ...Kevin
> --
> Kevin Miller
> Network/email Administrator, CBJ MIS Dept.
> 155 South Seward Street
> Juneau, Alaska 99801
> Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357
>
> -----Original Message-----
> From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Kevin Miller via ZendTo
> Sent: Wednesday, April 17, 2019 2:52 PM
> To: 'ZendTo Users'
> Cc: Kevin Miller
> Subject: [ZendTo] Migrating to new server
>
> Old server:
> 	Debian Jessie (8)
> 	Zendto 4.28
>
> New server:
> 	Debian Stretch (9)
> 	Zendto 5.17-6
>
> I built a brand new server and with a minimal amount of fuss was able to get it configured thanks to Jules' handy update scripts.  Now however I want to move the existing uploads to the new server from the old one.  I found some old messages in this list which said to copy ALL the directories under /var/zendto/drop-offs and /var/zendto/incoming.  Easy enough.  Also saw a post by Jules mentioning to stop the cron.d jobs so things don't get out of whack during cleanup.
>
> I don't know how to migrate the sql stuff however.  As nearly as I can tell, both servers are using SQLite.  Mysql does not exist on my new server (php7.3-mysql is installed however).  It is installed on the old server but not being used.  At least there aren't any tables with names like "zendto" or anything.
>
> If I had to hazard a guess I'd suppose that there may well have been schema changes from 4.28 to the current version, 5.17-6.
>
> So beyond moving the files over, what's the optimal way to get the database information moved?  Or is it even possible?
>
> Thanks.
>
> ...Kevin
> --
> Kevin Miller
> Network/email Administrator, CBJ MIS Dept.
> 155 South Seward Street
> Juneau, Alaska 99801
> Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357
>
>
>
> _______________________________________________
> 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

'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/20190421/6321e2bc/attachment-0001.html>

From Jules at Zend.To  Sun Apr 21 10:52:33 2019
From: Jules at Zend.To (Jules)
Date: Sun, 21 Apr 2019 10:52:33 +0100
Subject: [ZendTo] zendto.multi-domain.com, shared backend
In-Reply-To: <WM!cfbd515bba6a3a60a5f1695fa4663db1abf6332fd9e5dc76682fc57a1226d6f907113e7552d0d98990519d7697af8377!@mx.jul.es>
References: <CAGyTNKEV83J3gD7U5qyQ5Ei=kVyh-76LWdkMSMVbA78eko2=2Q@mail.gmail.com>
 <WM!cfbd515bba6a3a60a5f1695fa4663db1abf6332fd9e5dc76682fc57a1226d6f907113e7552d0d98990519d7697af8377!@mx.jul.es>
Message-ID: <c5952581-17f2-0d6a-96b4-605efea8abf1@Zend.To>

Kris,

I would be very surprised if this worked. In the database tables, there 
are auto-incrementing counters that give out unique numbers for things 
(if you wander the db schema, you'll find "dID" for example). If you 
merge 2 copies into the same db, those numbers are going to clash and 
all sorts of nasty things.

I would just force new drop-offs onto the new setup and let the old 
setup expire in a month or whatever.

Cheers,
Jules.

On 16/04/2019 6:00 pm, Kris Lou via ZendTo wrote:
> All,
>
> Previously, I ran dual copies of the /opt/zendto directories and 
> pointed the data and library directories to the same location.? Apache 
> webroots were pointing to different locations, and those had 
> respective config files.
>
> I've since merged the two (and adjusted text accordingly), and both 
> domains point to a single installation, but I can apparently only 
> dropoff when accessing via one domain -- the one that matches 
> "serverRoot" in preferences.php.? Otherwise, it complains of "Note 
> that you cannot drop-off directories, only files."
>
> Is there any way to whitelist this 2nd root URL?? Adding a 2nd value 
> to serverRoot?
>
> Not the end of the world if I can't, but thought I'd ask.
>
> 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

'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/20190421/6998a952/attachment.html>

From Jules at Zend.To  Sun Apr 21 10:57:19 2019
From: Jules at Zend.To (Jules)
Date: Sun, 21 Apr 2019 10:57:19 +0100
Subject: [ZendTo] API for login?
In-Reply-To: <WM!96ac6513ce83ba47a4c2af0e424b2b9ce0f690867a2072d8e3167585c59952ffa7337c2c17847a14871746e866f07739!@mx.jul.es>
References: <5CB0F80B0200001300133E82@mail.msktd.com>
 <WM!96ac6513ce83ba47a4c2af0e424b2b9ce0f690867a2072d8e3167585c59952ffa7337c2c17847a14871746e866f07739!@mx.jul.es>
Message-ID: <e45a1fcb-3888-f8a7-4d25-0b65d86a9715@Zend.To>

Not currently, no. Sorry. This is another thing I need to write...

On 12/04/2019 9:41 pm, Ken Etter via ZendTo wrote:
> We have some internal web sites that I have tied into our network so 
> that users are automatically logged in if they are logged into our 
> network.? Just had someone ask if there was a way to do that with 
> ZendTo.? Right now I have ZendTo setup to do LDAP authentication.? Is 
> there any way to automate the login process?
>
> *Ken Etter*, System Administrator
> Architectural Group
> 260.432.9337|msktd.com <http://msktd.com/>
>
> <http://msktd.com/>
>
>
>
> _______________________________________________
> 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/20190421/2305aa00/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE.png
Type: image/png
Size: 18080 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20190421/2305aa00/attachment-0001.png>

From Jules at Zend.To  Sun Apr 21 11:02:39 2019
From: Jules at Zend.To (Jules)
Date: Sun, 21 Apr 2019 11:02:39 +0100
Subject: [ZendTo] Scripted use of zend.to
In-Reply-To: <WM!6645ad4d44a0c03253152ebc24368a8a8e4df0a923c7fb7756e8cd9589e2dfdafb6737aed17a3becd26281a8d0f357f6!@mx.jul.es>
References: <EBB29FBB-BF92-4E2F-A3AF-78A783922490@neilzone.co.uk>
 <WM!72e88bf2b345d7839993faba3a2831e2a4e18a38bf8f5e791838c004074466a2f37b2142de35524249105c000319044a!@mx.jul.es>
 <WM!cb366a4cd40d02d1e3dbaba8aecd6998c3656bc8d7a9f7e54101f7a1ee2f43ba7c8f2ede649979cd954e18715cc0e1fc254cdd5c288e9e6407d02bb387b8ea93!@mx.jul.es>
 <89516a74-7fd1-cd4d-0809-45790403a96f@lehigh.edu>
 <WM!6645ad4d44a0c03253152ebc24368a8a8e4df0a923c7fb7756e8cd9589e2dfdafb6737aed17a3becd26281a8d0f357f6!@mx.jul.es>
Message-ID: <72faae87-37c2-1810-c1be-62ec07b11fb3@Zend.To>

Keith,

I would very much like to see this, if you could be so kind!

How do you limit who/where can use the automated version?
I was thinking that you could automate the "Send a Request for a 
Drop-off" process but leave the actual file upload process alone. Then 
you can put much tighter controls on who/what can automatically create a 
request, and you don't have to tweak the remote user's upload experience 
at all.

Thanks!
Jules.

On 11/04/2019 10:26 pm, Keith Erekson via ZendTo wrote:
>
> The previous implementation of this project, back when it was the "UD 
> Dropbox" had some sort of "custom upload form" functionality.
>
> I don't remember exactly what they called it, and 30 seconds of 
> Googling hasn't turned up a download location for their code, but it's 
> essentially a stripped-down UI that lets you (the admin) hard-code the 
> recipient info, so people can't screw up the file transfer.
>
> This feature was dropped from ZendTo, but we've been forward-porting 
> it for years, as some of our departments depend on it for various reasons.
>
> Using it requires some modifications to ZendTo, to allow uploads 
> without the CAPTCHA verification. (By which I mean: we have been too 
> lazy to implement the CAPTCHA in our custom dropoff interface; it was 
> implemented before ZendTo had a CAPTCHA.)
>
> It wouldn't be possible to use this directly from a script (e.g., curl 
> -X POST ...), as it still uses JavaScript, but you could possibly use 
> it as a starting point to add a similar API interface.
>
> If there's interest, I can post some sanitized git diffs and/or some 
> documentation about how it works.
>
> ~Keith
>
> On 4/5/19 11:29 AM, Neil via ZendTo wrote:
>> I have had a quick look through recent archives, and I can?t see 
>> anything on this, but apologies if it has been covered already.
>>
>> Does anyone have an example of using zend.to in a scripted manner, 
>> rather than through the web browser?
>>
>> I can think of a number of occasions where it would be useful to be 
>> able to generate a zend.to drop-off request (to have someone drop a 
>> file off for me) without me needing to log in to the UI and do it. I 
>> suspect it can be done quite readily with curl, but I wonder if 
>> someone has already tackled this and would be willing to share the 
>> output?
>>
>> Best wishes
>>
>> Neil
>>
>>
>>
>>
>> _______________________________________________
>> 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

The current UK shipping forecast:
Biscay: Variable, mainly northeast, 3 or 4, occasionally 5 later. Moderate.
Showers. Good.

www.Zend.To
Twitter: @JulesFM

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

From Jules at Zend.To  Sun Apr 21 11:08:19 2019
From: Jules at Zend.To (Jules)
Date: Sun, 21 Apr 2019 11:08:19 +0100
Subject: [ZendTo] NSSDROPBOX_DATA_DIR and logrotate
In-Reply-To: <WM!101ac07959aca9e5c98376e488d62d12c0b1e53eae67123ccf614c655e7094ae6e6a2570c5ea97c93a461013e15fb4e8!@mx.jul.es>
References: <0029a60a-5ac3-e547-67fc-ddc78e93dfc6@alaska.gov>
 <WM!101ac07959aca9e5c98376e488d62d12c0b1e53eae67123ccf614c655e7094ae6e6a2570c5ea97c93a461013e15fb4e8!@mx.jul.es>
Message-ID: <3fdada91-14e6-53eb-9f6c-4c5b61fe8360@Zend.To>

John,

Sadly I don't think there's any way for logrotate to be able to execute 
code in order to work out the location of the log files it needs to 
rotate. An easy alternative solution would just be
 ??? ln -sn /var/zendto-storage/zendto /var/zendto
Then any references to /var/zendto which I can't fix automatically (of 
which the logrotate.d file is a fine example) will still work.

But yes, your change to /etc/logrotate.d/zendto should survive updates.

Cheers,
Jules.

On 11/04/2019 10:45 pm, John Thurston via ZendTo wrote:
> I'm not exactly sure when this problem started, but the log rotation 
> process is failing.
>
> The file:
> ? /etc/logrotate.d/zendto
> references the files:
> ? /var/log/zendto/zendto.log
> ? /var/zendto/zendto.log
>
> But that isn't where my logs are. My config in:
> ? preferences.php
> has the following:
> ? define('NSSDROPBOX_DATA_DIR','/var/zendto-storage/zendto/');
>
>
> I can go edit /etc/logrotate.d/zendto and hope it persists through the 
> next update.
>
> Is there some other way I should correct this?
>
>
>

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/20190421/a87d47cc/attachment.html>

From Jules at Zend.To  Sun Apr 21 12:04:22 2019
From: Jules at Zend.To (Jules)
Date: Sun, 21 Apr 2019 12:04:22 +0100
Subject: [ZendTo] Possible CSS problem with logo in 5.17
In-Reply-To: <WM!9c07e8a091440e5297d7fe60533efe71aa7f306efd444d5aa916c07347430c2fdf3d1e57bdf0b391c11095ddd5fb22a7!@mx.jul.es>
References: <72021174-b85a-f62a-78e5-92fa9cb9e4a1@alaska.gov>
 <WM!601aa15929bdeea29ad985192f134949b64c158e8f19715b26ede15fb5acf855d89ce87182681bd05fd1efc2eb20ff31!@mx.jul.es>
 <WM!69ddbd46c492c10ace9d9b472ee360d5b5aae89f8636aba653a1794ed8e2e9269242eee7e7675294c86615d9145898cdcbd25d3cd93fbe170b83bb8cc6bac7ef!@mx.jul.es>
 <20752f01-40b2-b4ba-eb8a-0ab75c6e6abe@alaska.gov>
 <WM!1a4a7cb50ac70b60ac73fe0bdcc7fcae032b0af70be5fdb99cd3579b3c299c0212d77733ac56f63ae4d6f0a2dbf19f5f!@mx.jul.es>
 <WM!f99ff47a45eb5205efd595fae1c433bc6e5df00c8a77130545b194d67fe5890570d8c0516f7a4ef5a913cf476457abf9f1ad0eb28621a9eff5210264b064ffa9!@mx.jul.es>
 <9e9b4afe-1e65-2aa5-7f68-472712223a5b@alaska.gov>
 <WM!9c07e8a091440e5297d7fe60533efe71aa7f306efd444d5aa916c07347430c2fdf3d1e57bdf0b391c11095ddd5fb22a7!@mx.jul.es>
Message-ID: <d8d13b3f-3c89-32b4-0486-01efe5b31133@Zend.To>

John,

I will have to have another play with this. The CSS rules interact 
really badly with overflow, overflow-x and overflow-y and I did it the 
way I was advised to. Clearly it behaves better with an image than it 
does with text.

What I needed to do was make it clip in 1 direction but allow overflow 
in the other.

I'll put it on the list of fixes to be looked at.

Cheers,
Jules.

On 28/03/2019 9:07 pm, John Thurston via ZendTo wrote:
>
> On 3/28/2019 12:49 PM, John Thurston via ZendTo wrote:
>> I think the simplest way to solve my problem (so all the edits are to 
>> a single file) will be to modify swish2.css to
>> ?? Change "overflow-y: hidden;" in #logo
>> and to
>> ?? Add "overflow-y: inherit;" to #logoxclip
>
> K. I looked in swish2.css and found the admonition to leave it alone, 
> so I've made the following additions to /opt/zendto/www/css/local.css
>
>
> #logo {
> ??????? overflow-y: hidden;
> }
>
> #logoxclip {
> ??????? overflow-y: inherit;
> }
>
>
>
> And that crazy little scroll bar is gone.
>
> -- 
> ?? 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

'Named must your fear be before banish it you can.' - Yoda

www.Zend.To
Twitter: @JulesFM

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

From Jules at Zend.To  Sun Apr 21 12:13:12 2019
From: Jules at Zend.To (Jules)
Date: Sun, 21 Apr 2019 12:13:12 +0100
Subject: [ZendTo] Authenticator after update
In-Reply-To: <WM!999efad5bf8cb0c5e95a2ee98c9d3844b82302ce3480728f644c309b61d24a9d7977014dd74124289da4bba1927a20a1!@mx.jul.es>
References: <e232dd06-f1d1-da6f-6084-8808659b08db@alaska.gov>
 <WM!16d95f4a4e68b5a3c9b18eca328410920b3a965833dd40daeb468f9a82d57a78b6a66a497efeb762ecbd9380511f7155a0880585e292a4d52ccdfa7bfc0ad153!@mx.jul.es>
 <5C9CBC8302000013001335A0@mail.msktd.com>
 <WM!25ebe10779e4b2f8cbbdf814c4010d34a2559cd2960398e2357a75510782e7267c76f37714479db8d29f9363bf591bdb!@mx.jul.es>
 <WM!ab33ddb78db808d51ad4b1cfe23cb5bab8d67e21e10ce84626246605edef8532130eb880da67e4697519a194210d3dd1ea33d2a2d00147c7d9712b2080410a21!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F4204A073F@FONEXCH01.sgvwc.local>
 <WM!61d5e9188fb917f2f52e3cad113e4373e21081615ec558dc95dea5c797fb8b16938ffa836eea654856f1cf635ca0b8f6!@mx.jul.es>
 <WM!ceeb6dc5e97371edb35ebbe6d31c4c4d8d2d136b823c1329914e331ad99d926b8fb47999e8830908a99efc1599b3302b898167b9668fa7ad370e3f696de48067!@mx.jul.es>
 <1d7de9d0-991f-62f3-7406-d11939f561dc@alaska.gov>
 <WM!999efad5bf8cb0c5e95a2ee98c9d3844b82302ce3480728f644c309b61d24a9d7977014dd74124289da4bba1927a20a1!@mx.jul.es>
Message-ID: <b1739317-11a8-2ae1-98bd-3dcf5025cc5a@Zend.To>

John,

Sorry, I suspect that you are one of the few sites using LDAP, but not AD.
:-(

What happens if you explicitly set them (to quite possibly empty 
strings), rather than comment them out?

The updater doesn't understand PHP itself, it looks for settings and 
comments. It can't tell the difference between a commented-out setting 
and any other sort of comment.

Let me know how you get on. If I need to change some of the behaviour to 
treat an "empty" value as if it weren't set at all, I can do that no 
problem.

Cheers,
Jules.

On 28/03/2019 4:26 pm, John Thurston via ZendTo wrote:
> Are you using all of the available "authLDAP" config values?
>
> In my case, the updater re-enables configuration values I have 
> explicitly commented out. Things like:
> 'authLDAPBindDn'
> 'authLDAPBindPass'
> 'authLDAPOrganization'
> 'authLDAPUsernameAttr'
> 'authLDAPEmailAttr'
> 'authLDAPMemberKey'
> 'authLDAPMemberRole'
>
> When they get re-enabled, authentication fails because none of the 
> values are applicable or correct.
>
> -- 
> ?? 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 3/28/2019 7:02 AM, Scott Silva via ZendTo wrote:
>> I just ran the new upgrade script on an update from 5.15 to 5.17 and 
>> everything seems to be going smoothly in my testing. And I am using 
>> LDAP auth against an AD system.
>>
>
> _______________________________________________
> 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:
East Sole, Lundy, Fastnet: Variable 3 or 4, becoming southeasterly 4 or 5
later. Moderate. Fog patches. Moderate or good, occasionally very poor.

www.Zend.To
Twitter: @JulesFM

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

From Jules at Zend.To  Sun Apr 21 12:22:30 2019
From: Jules at Zend.To (Jules)
Date: Sun, 21 Apr 2019 12:22:30 +0100
Subject: [ZendTo] Feature requests - Global Drop-off List
In-Reply-To: <WM!28188fe001a22bb6ccf2a7b74b506b22ae4d8458cd11e247643900e3c5d5dc8051d275b36fc56594e7857e57ff79ecff!@mx.jul.es>
References: <eb696566-d2e7-d0a4-aab8-8b8fc9026312@alaska.gov>
 <WM!28188fe001a22bb6ccf2a7b74b506b22ae4d8458cd11e247643900e3c5d5dc8051d275b36fc56594e7857e57ff79ecff!@mx.jul.es>
Message-ID: <9c01915d-62b9-20fb-9ef1-c3ab0e33e874@Zend.To>

John,

On 28/03/2019 5:33 pm, John Thurston via ZendTo wrote:
> The part of ZendTo with which I interact most often is the 'Global 
> Drop-off List". It would be wonderful to have some more information 
> there. I'm thinking specifically of
> ? Indicators for "encrypted" and "picked-up"
Added to the list. Should be fairly easy to do with luck.

>
> It would also be helpful if there were a way to 'open in new tab' from 
> that screen. If I sort by size and want to examine the 8 largest 
> dropoffs, I have to open the list, sort the list, identify the claimID 
> I want, open it, examine it, ... then I must repeat all the steps from 
> the beginning. If I could ctrl-click on a claimID and open it in a new 
> tab, I would save a whole bunch of clicks.
How about I just tweak the template a bit so that all of that type of 
"list of drop-offs" page opens up a new tab instead?
Is there any reason or situation where the current behaviour would be 
*better* than opening the drop-off in a new tab?
Changing all of them is trivial.

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'There is always one moment in childhood when the door opens and
  lets the future in.' - Graham Greene

www.Zend.To
Twitter: @JulesFM

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

From Jules at Zend.To  Sun Apr 21 12:32:12 2019
From: Jules at Zend.To (Jules)
Date: Sun, 21 Apr 2019 12:32:12 +0100
Subject: [ZendTo] Ideas wanted: "Forget me" button
In-Reply-To: <WM!1c04c3a622dbe66df5148aa28e069a1af6f15239251ac98e291ef4cdae6b14958a8db5f59069c39e04774e13980ea45d!@mx.jul.es>
References: <9E8FF5130DE9CD4D895AF10041C1085B040B000AAC@BTIEXCH04.BTec.ad.banctec.com>
 <WM!1c04c3a622dbe66df5148aa28e069a1af6f15239251ac98e291ef4cdae6b14958a8db5f59069c39e04774e13980ea45d!@mx.jul.es>
Message-ID: <bf8c6a95-0e2c-b5fc-5c36-563a56c7a359@Zend.To>

Guy,

Thanks for those ideas.

The auto-complete drop-down is provided by a Jquery thing, so I don't 
know how easy that will be to modify.

And good point about deleting someone from *all* the address books 
they're in.

Cheers,
Jules.

On 13/03/2019 4:38 pm, Bertrand, Guy via ZendTo wrote:
> Hi Jules,
>
> Are you looking to delete all "remembered users" with one button??  Or just to delete one user?  If it deletes all names, it would be an inconvenience to have to re-type all names when needed.
>
> Since you do not want to write an entire address book editor in the s/w, how about just adding an X beside a remembered name?
>
> Example:
> When a user starts typing a name into the recipients box, the matching entries are returned in the order of most-recently-used at the top.  As they are displayed, add an field to the right of each name with an X.  To delete just that entry, press the X at the right of the name.  That way, you maintain your existing list, and have deleted just that name, without a full address book editor.
>
> However, I think I need to discuss a caveat.  I'm no expert of the GDPR, but if a user/person requests that their name "be forgotten", doesn't also imply that it is from the whole system, not just one user's cache of names??  Example, if we are 2 users who have sent files to the same external user, and I delete the name from my list, it will still remain in the second user's list.
>
> I need another coffee.
>
> Cheers and keep up the good work!!
>
> Regards,
>
> Guy
>
> Guy Bertrand, M.Ing
> Directeur informatique / IT Manager
> EXELA TECHNOLOGIES
> b: +1.514.392.4999 | m: +1.514.265.9754
> 1155, boulevard Robert-Bourassa, suite 500 | Montr?al (Qu?bec) CANADA H3B 3A7
> www.ExelaTech.com | EXELA LinkedIn
>
>
> _______________________________________________
> 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:
Wight, Portland: East 3 or 4. Slight or moderate. Fair. Moderate or good.

www.Zend.To
Twitter: @JulesFM

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

From Jules at Zend.To  Sun Apr 21 12:40:53 2019
From: Jules at Zend.To (Jules)
Date: Sun, 21 Apr 2019 12:40:53 +0100
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!04ac29d9b1cb683f7de0e78e84e4e2f34923d59c81d707d8829575b8c92b00a79e43ddd45ef21721380bef949edd6a9c!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <WM!04ac29d9b1cb683f7de0e78e84e4e2f34923d59c81d707d8829575b8c92b00a79e43ddd45ef21721380bef949edd6a9c!@mx.jul.es>
Message-ID: <68797d56-996b-b3fe-122c-5d076cd94553@Zend.To>

Peter,

You effectively just want to allow senders to customise the "[ZENDTO]" 
subject line tag in each drop-off, correct?

Does anyone else need to do this too?

Cheers,
Jules.

On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
> Hi Jules, hi all.
>
> I have a strange request from our ZendTo users. They asked if it would 
> be possible to add a custom field when sending a DropOff
> that results in a custom text in all ZendTo email concerning this 
> specific DropOff.
>
> Example current:
>
> [ZENDTO] One of the recipients has picked up your drop-off!
>
> Example requested:
>
> [ZENDTO] CUSTOM_STRING One of the recipients has picked up your drop-off!
>
> I asked a little bit about the purpose of their request and they told 
> me that project teams sort their email by subject and
> consequently keep the project name (CUSTOM_STRING) in every subject of 
> their emails concerning that specific project.
> So later they could sort by project name (CUSTOM_STRING) within 
> Outlook to be able to verify when they sent a specific DropOff.
>
> Question:
> Is it possible to implement such a feature?
>
> I know that I could handcraft it but I don't want to make big changes 
> to the source and always have to keep track of them when upgrading.
>
> I am currently not on the latest version of ZendTo, so if such a 
> feature is maybe already present in the latest version, feel free
> to tell me.
>
> Thanks in advance.
>
> Peter
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Once is happenstance, twice is coincidence, three times is enemy
  action.' - Ian Fleming

www.Zend.To
Twitter: @JulesFM

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

From Jordack at yahoo.com  Sun Apr 21 14:13:43 2019
From: Jordack at yahoo.com (Travis McDugald)
Date: Sun, 21 Apr 2019 09:13:43 -0400
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!79697c98063608f12637d627205225e506bd16c422cf2e658b71dc91c96e4d93d6992b06c09415a55ed033135a0e0804eb61b1e883ecc1b85f1b57981f916e16!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <WM!04ac29d9b1cb683f7de0e78e84e4e2f34923d59c81d707d8829575b8c92b00a79e43ddd45ef21721380bef949edd6a9c!@mx.jul.es>
 <68797d56-996b-b3fe-122c-5d076cd94553@Zend.To>
 <WM!79697c98063608f12637d627205225e506bd16c422cf2e658b71dc91c96e4d93d6992b06c09415a55ed033135a0e0804eb61b1e883ecc1b85f1b57981f916e16!@mx.jul.es>
 <5F237D6D-5E93-4097-ACD0-F64A2485F135@yahoo.com>
Message-ID: <WM!70ecf74f9e7d0b8945733332927203aaee6acd5c28f43499004c3696c297dd37eb1ba48282437d0b6734377ab4e96d6d!@mx.jul.es>

While no one has asked for this yet, I do see it?s usefulness.
I do use custom strings in email subjects for some projects as well.  Helps with sorting, searching, and filtering.

Side note: great job on everything Jules, thank you.

Sent from my iPad

> On Apr 21, 2019, at 7:40 AM, Jules via ZendTo <zendto at zend.to> wrote:
> 
> Peter,
> 
> You effectively just want to allow senders to customise the "[ZENDTO]" subject line tag in each drop-off, correct?
> 
> Does anyone else need to do this too?
> 
> Cheers,
> Jules.
> 
>> On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
>> Hi Jules, hi all. 
>> 
>> I have a strange request from our ZendTo users. They asked if it would be possible to add a custom field when sending a DropOff 
>> that results in a custom text in all ZendTo email concerning this specific DropOff. 
>> 
>> Example current: 
>> 
>> [ZENDTO] One of the recipients has picked up your drop-off! 
>> 
>> Example requested: 
>> 
>> [ZENDTO] CUSTOM_STRING One of the recipients has picked up your drop-off! 
>> 
>> I asked a little bit about the purpose of their request and they told me that project teams sort their email by subject and 
>> consequently keep the project name (CUSTOM_STRING) in every subject of their emails concerning that specific project. 
>> So later they could sort by project name (CUSTOM_STRING) within Outlook to be able to verify when they sent a specific DropOff. 
>> 
>> Question: 
>> Is it possible to implement such a feature? 
>> 
>> I know that I could handcraft it but I don't want to make big changes to the source and always have to keep track of them when upgrading. 
>> 
>> I am currently not on the latest version of ZendTo, so if such a feature is maybe already present in the latest version, feel free 
>> to tell me. 
>> 
>> Thanks in advance. 
>> 
>> Peter 
>> 
>> 
>> _______________________________________________ 
>> ZendTo mailing list 
>> ZendTo at zend.to 
>> http://jul.es/mailman/listinfo/zendto 
> 
> Jules
> 
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
> 
> 'Once is happenstance, twice is coincidence, three times is enemy
>  action.' - Ian Fleming
> 
> 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/20190421/021f061a/attachment.html>

From mailinglists at pcfreak.de  Sun Apr 21 14:29:37 2019
From: mailinglists at pcfreak.de (Mailing Lists)
Date: Sun, 21 Apr 2019 15:29:37 +0200
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!a19dcdb9c2fb31a686ce792da4aa12c43d3ba00e35a4a16664a231c772ba25bdf2971934cb3c63b3b06a4fec57930a2506d42cd5112dbe4ad05a20e79c8bf783!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <WM!04ac29d9b1cb683f7de0e78e84e4e2f34923d59c81d707d8829575b8c92b00a79e43ddd45ef21721380bef949edd6a9c!@mx.jul.es>
 <68797d56-996b-b3fe-122c-5d076cd94553@Zend.To>
 <WM!79697c98063608f12637d627205225e506bd16c422cf2e658b71dc91c96e4d93d6992b06c09415a55ed033135a0e0804eb61b1e883ecc1b85f1b57981f916e16!@mx.jul.es>
 <5F237D6D-5E93-4097-ACD0-F64A2485F135@yahoo.com>
 <WM!70ecf74f9e7d0b8945733332927203aaee6acd5c28f43499004c3696c297dd37eb1ba48282437d0b6734377ab4e96d6d!@mx.jul.es>
 <WM!a19dcdb9c2fb31a686ce792da4aa12c43d3ba00e35a4a16664a231c772ba25bdf2971934cb3c63b3b06a4fec57930a2506d42cd5112dbe4ad05a20e79c8bf783!@mx.jul.es>
 <E2766566-A872-4994-AE6C-2B8354C2B2A3@pcfreak.de>
Message-ID: <WM!2259e31bcbec5992430418f002c490bbc3dd01ed4b2c0329743d8fc779d9efef6d0061ecc3c40991a151f8b11ffe7010!@mx.jul.es>

Hi Jules,

yes it would be enough to allow 20 editable characters.

via Smartphone

> Am 21.04.2019 um 15:13 schrieb Travis McDugald via ZendTo <zendto at zend.to>:
> 
> While no one has asked for this yet, I do see it?s usefulness.
> I do use custom strings in email subjects for some projects as well.  Helps with sorting, searching, and filtering.
> 
> Side note: great job on everything Jules, thank you.
> 
> Sent from my iPad
> 
>> On Apr 21, 2019, at 7:40 AM, Jules via ZendTo <zendto at zend.to> wrote:
>> 
>> Peter,
>> 
>> You effectively just want to allow senders to customise the "[ZENDTO]" subject line tag in each drop-off, correct?
>> 
>> Does anyone else need to do this too?
>> 
>> Cheers,
>> Jules.
>> 
>>> On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
>>> Hi Jules, hi all. 
>>> 
>>> I have a strange request from our ZendTo users. They asked if it would be possible to add a custom field when sending a DropOff 
>>> that results in a custom text in all ZendTo email concerning this specific DropOff. 
>>> 
>>> Example current: 
>>> 
>>> [ZENDTO] One of the recipients has picked up your drop-off! 
>>> 
>>> Example requested: 
>>> 
>>> [ZENDTO] CUSTOM_STRING One of the recipients has picked up your drop-off! 
>>> 
>>> I asked a little bit about the purpose of their request and they told me that project teams sort their email by subject and 
>>> consequently keep the project name (CUSTOM_STRING) in every subject of their emails concerning that specific project. 
>>> So later they could sort by project name (CUSTOM_STRING) within Outlook to be able to verify when they sent a specific DropOff. 
>>> 
>>> Question: 
>>> Is it possible to implement such a feature? 
>>> 
>>> I know that I could handcraft it but I don't want to make big changes to the source and always have to keep track of them when upgrading. 
>>> 
>>> I am currently not on the latest version of ZendTo, so if such a feature is maybe already present in the latest version, feel free 
>>> to tell me. 
>>> 
>>> Thanks in advance. 
>>> 
>>> Peter 
>>> 
>>> 
>>> _______________________________________________ 
>>> ZendTo mailing list 
>>> ZendTo at zend.to 
>>> http://jul.es/mailman/listinfo/zendto 
>> 
>> Jules
>> 
>> -- 
>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>> 
>> 'Once is happenstance, twice is coincidence, three times is enemy
>>  action.' - Ian Fleming
>> 
>> 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/20190421/0e0c29b6/attachment-0001.html>

From zend.to at neilzone.co.uk  Sun Apr 21 17:22:19 2019
From: zend.to at neilzone.co.uk (zend.to at neilzone.co.uk)
Date: Sun, 21 Apr 2019 17:22:19 +0100
Subject: [ZendTo] Scripted use of zend.to
In-Reply-To: <WM!205351bbfb7468e7dabdbe0dded91cad484ccd5ede5b910ce734dd81b2fccf03c9c331d8d5e359e081804f7e7a411f5ec5397865bd1a870066581cf64baa83ff!@mx.jul.es>
References: <EBB29FBB-BF92-4E2F-A3AF-78A783922490@neilzone.co.uk>
 <WM!72e88bf2b345d7839993faba3a2831e2a4e18a38bf8f5e791838c004074466a2f37b2142de35524249105c000319044a!@mx.jul.es>
 <WM!cb366a4cd40d02d1e3dbaba8aecd6998c3656bc8d7a9f7e54101f7a1ee2f43ba7c8f2ede649979cd954e18715cc0e1fc254cdd5c288e9e6407d02bb387b8ea93!@mx.jul.es>
 <89516a74-7fd1-cd4d-0809-45790403a96f@lehigh.edu>
 <WM!6645ad4d44a0c03253152ebc24368a8a8e4df0a923c7fb7756e8cd9589e2dfdafb6737aed17a3becd26281a8d0f357f6!@mx.jul.es>
 <72faae87-37c2-1810-c1be-62ec07b11fb3@Zend.To>
 <WM!205351bbfb7468e7dabdbe0dded91cad484ccd5ede5b910ce734dd81b2fccf03c9c331d8d5e359e081804f7e7a411f5ec5397865bd1a870066581cf64baa83ff!@mx.jul.es>
 <3AD7FA96-0F75-4FB7-A263-E32AF5F80B40@neilzone.co.uk>
Message-ID: <WM!966e3ea92f67732d6fe00ba1e9f87dfe12cbce97e9a8368a76ae05d940ddac5dff81f63caadae9bd4ed4b65b96d3aad0!@mx.jul.es>



> On 21 Apr 2019, at 11:02, Jules via ZendTo <zendto at zend.to> wrote:
> 
> I was thinking that you could automate the "Send a Request for a Drop-off" process but leave the actual file upload process alone. 


For what it might be worth, that is consistent with what I personally was trying to achieve: a simple, scriptable, mechanism for asking for a drop-off, bit not tinkering with the actual upload / drop-off itself.

(I tried buying some music from your Amazon wishlist, in case you find a chance to work on this, but managed only to buy it for myself! If you were to add some other bits, where I?m less likely to mess the process up?)

Best wishes

Neil

__________

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

From Jules at Zend.To  Mon Apr 22 17:22:37 2019
From: Jules at Zend.To (Jules)
Date: Mon, 22 Apr 2019 17:22:37 +0100
Subject: [ZendTo] Possible CSS problem with logo in 5.17
In-Reply-To: <WM!9c07e8a091440e5297d7fe60533efe71aa7f306efd444d5aa916c07347430c2fdf3d1e57bdf0b391c11095ddd5fb22a7!@mx.jul.es>
References: <72021174-b85a-f62a-78e5-92fa9cb9e4a1@alaska.gov>
 <WM!601aa15929bdeea29ad985192f134949b64c158e8f19715b26ede15fb5acf855d89ce87182681bd05fd1efc2eb20ff31!@mx.jul.es>
 <WM!69ddbd46c492c10ace9d9b472ee360d5b5aae89f8636aba653a1794ed8e2e9269242eee7e7675294c86615d9145898cdcbd25d3cd93fbe170b83bb8cc6bac7ef!@mx.jul.es>
 <20752f01-40b2-b4ba-eb8a-0ab75c6e6abe@alaska.gov>
 <WM!1a4a7cb50ac70b60ac73fe0bdcc7fcae032b0af70be5fdb99cd3579b3c299c0212d77733ac56f63ae4d6f0a2dbf19f5f!@mx.jul.es>
 <WM!f99ff47a45eb5205efd595fae1c433bc6e5df00c8a77130545b194d67fe5890570d8c0516f7a4ef5a913cf476457abf9f1ad0eb28621a9eff5210264b064ffa9!@mx.jul.es>
 <9e9b4afe-1e65-2aa5-7f68-472712223a5b@alaska.gov>
 <WM!9c07e8a091440e5297d7fe60533efe71aa7f306efd444d5aa916c07347430c2fdf3d1e57bdf0b391c11095ddd5fb22a7!@mx.jul.es>
Message-ID: <feadc027-e767-3398-bf45-20c5f81f7bcb@Zend.To>

I think I've found a better solution.
Comment out those changes in local.css, then edit swish2.css and comment 
out this line-height setting (shown in context):

#logo {
 ??????? float: right;
 ??????? height: 60px;
*??????? /* line-height: 60px; */*
 ??????? padding-left: 25px;
 ??????? padding-right: 20px;
 ??????? text-decoration: none;
 ??????? font-weight: bold;
 ??????? color: #a5abb0;
 ??????? font-size: 3.5em;
 ??????? text-shadow: 1px 1px 0px #fbfbfb;
 ??????? max-width: 270px;
 ??????? overflow-y: visible;
}

Be very careful to ensure your browser does actually re-read the CSS 
(most cache it far too aggressively) and you will hopefully find that 
fixes it.
I have tried it on a Mac with Safari / Chrome / Firefox and on Windows 
10 with IE / Edge / Edgium / Chrome / Firefox.

The only place it doesn't work nicely is Edge if you use an image.
Otherwise it appears to work in all the above with either text or an image.

So it's an improvement on the previous version. :-)

Cheers,
Jules.

On 28/03/2019 9:07 pm, John Thurston via ZendTo wrote:
>
> On 3/28/2019 12:49 PM, John Thurston via ZendTo wrote:
>> I think the simplest way to solve my problem (so all the edits are to 
>> a single file) will be to modify swish2.css to
>> ?? Change "overflow-y: hidden;" in #logo
>> and to
>> ?? Add "overflow-y: inherit;" to #logoxclip
>
> K. I looked in swish2.css and found the admonition to leave it alone, 
> so I've made the following additions to /opt/zendto/www/css/local.css
>
>
> #logo {
> ??????? overflow-y: hidden;
> }
>
> #logoxclip {
> ??????? overflow-y: inherit;
> }
>
>
>
> And that crazy little scroll bar is gone.
>
> -- 
> ?? 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

'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/20190422/49c7011d/attachment.html>

From kevin.miller at juneau.org  Wed Apr 24 20:55:42 2019
From: kevin.miller at juneau.org (Kevin Miller)
Date: Wed, 24 Apr 2019 19:55:42 +0000
Subject: [ZendTo] UFW firewall
References: <9efcab96ba9c4dae99a0086e83266318@City-Exch-DB1.cbj.local>
Message-ID: <WM!c08094856a8608efcc38bbedc2db703932286d1e88bd3e44463b44e316e00bafdc55f2c8ca57ed37062302adfe6af445!@mx.jul.es>

We noticed today that the new zendto server wasn't doing snmp.  Turned out to be the UFW firewall.  Easy enough to add it in, but would it be possible to make that a stock feature (or option in the script)?  I'm sure we're not the only ones using network management of one flavor or another.  Port 161 IIRC.

Thanks...

...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357



From KLE at msktd.com  Wed Apr 24 21:48:09 2019
From: KLE at msktd.com (Ken Etter)
Date: Wed, 24 Apr 2019 16:48:09 -0400
Subject: [ZendTo] Authenticator after update
In-Reply-To: <3D1C77C4020000527314B811@mail.msktd.com>
References: <e232dd06-f1d1-da6f-6084-8808659b08db@alaska.gov>
 <WM!16d95f4a4e68b5a3c9b18eca328410920b3a965833dd40daeb468f9a82d57a78b6a66a497efeb762ecbd9380511f7155a0880585e292a4d52ccdfa7bfc0ad153!@mx.jul.es>
 <5C9CBC8302000013001335A0@mail.msktd.com>
 <WM!25ebe10779e4b2f8cbbdf814c4010d34a2559cd2960398e2357a75510782e7267c76f37714479db8d29f9363bf591bdb!@mx.jul.es>
 <WM!ab33ddb78db808d51ad4b1cfe23cb5bab8d67e21e10ce84626246605edef8532130eb880da67e4697519a194210d3dd1ea33d2a2d00147c7d9712b2080410a21!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F4204A073F@FONEXCH01.sgvwc.local>
 <WM!61d5e9188fb917f2f52e3cad113e4373e21081615ec558dc95dea5c797fb8b16938ffa836eea654856f1cf635ca0b8f6!@mx.jul.es>
 <WM!ceeb6dc5e97371edb35ebbe6d31c4c4d8d2d136b823c1329914e331ad99d926b8fb47999e8830908a99efc1599b3302b898167b9668fa7ad370e3f696de48067!@mx.jul.es>
 <1d7de9d0-991f-62f3-7406-d11939f561dc@alaska.gov>
 <WM!999efad5bf8cb0c5e95a2ee98c9d3844b82302ce3480728f644c309b61d24a9d7977014dd74124289da4bba1927a20a1!@mx.jul.es>
 <b1739317-11a8-2ae1-98bd-3dcf5025cc5a@Zend.To>
 <WM!e10819c4eb2376a951503866c2428f1e613dd4329a578063d1d6f1993579e582139181c150b324a177db91878d795dc8da496d29c89327cb1c0b30d0fc0f4698!@mx.jul.es>
 <8C5A64810200008E7314B811@mail.msktd.com>
 <E18F12640200000D5C3646E4@mail.msktd.com>
 <4F77DDF60200008D7314B811@mail.msktd.com>
 <D9E7E4B8020000787314B811@mail.msktd.com>
 <7B8EE8AC0200002C9BE0E8C9@mail.msktd.com>
 <BF19ED1C020000F27314B811@mail.msktd.com>
 <7B6D23690200003AC84B1EE2@mail.msktd.com>
 <3D1C77C4020000527314B811@mail.msktd.com>
 <5CC0CB8902000013001349CE@mail.msktd.com>
Message-ID: <WM!40fe38db57b0ced88296260d5227c43541f67a0b65e088fa5ce4405336a9aeb9dbaa19902892371d49453e2059f9fd7b!@mx.jul.es>

Just thought I would mention that I also use LDAP but not AD.  So I am one of those "few sites".  I haven't tried the updater yet because last upgrade time I built a new ZendTo server on SLES (moved off my old Ubuntu server).  I'll have to see what happens next update time.

Ken Etter, System Administrator
Architectural Group
260.432.9337 | msktd.com




>>> Jules via ZendTo <zendto at zend.to> 4/21/2019 7:13 AM >>>
> John,

Sorry, I suspect that you are one of the few sites using LDAP, but not AD.
:-(
What happens if you explicitly set them (to quite possibly empty strings), rather than comment them out?
The updater doesn't understand PHP itself, it looks for settings and comments. It can't tell the difference between a commented-out setting and any other sort of comment.
Let me know how you get on. If I need to change some of the behaviour to treat an "empty" value as if it weren't set at all, I can do that no problem.
Cheers,
Jules.
On 28/03/2019 4:26 pm, John Thurston via ZendTo wrote:


Are you using all of the available "authLDAP" config values? 

In my case, the updater re-enables configuration values I have explicitly commented out. Things like: 
'authLDAPBindDn' 
'authLDAPBindPass' 
'authLDAPOrganization' 
'authLDAPUsernameAttr' 
'authLDAPEmailAttr' 
'authLDAPMemberKey' 
'authLDAPMemberRole' 
When they get re-enabled, authentication fails because none of the values are applicable or correct. 
-- 
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 3/28/2019 7:02 AM, Scott Silva via ZendTo wrote: 


I just ran the new upgrade script on an update from 5.15 to 5.17 and everything seems to be going smoothly in my testing. And I am using LDAP auth against an AD system. 

 

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

Jules-- Julian Field MEng CEng CITP MBCS MIEEE MACMThe current UK shipping forecast:East Sole, Lundy, Fastnet: Variable 3 or 4, becoming southeasterly 4 or 5later. Moderate. Fog patches. Moderate or good, occasionally very poor.www.Zend.ToTwitter: @JulesFM 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190424/9fdfc4a0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE.png
Type: image/png
Size: 18080 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20190424/9fdfc4a0/attachment-0001.png>

From Jules at Zend.To  Thu Apr 25 09:03:09 2019
From: Jules at Zend.To (Jules Field)
Date: Thu, 25 Apr 2019 09:03:09 +0100
Subject: [ZendTo] UFW firewall
In-Reply-To: <WM!c08094856a8608efcc38bbedc2db703932286d1e88bd3e44463b44e316e00bafdc55f2c8ca57ed37062302adfe6af445!@mx.jul.es>
References: <9efcab96ba9c4dae99a0086e83266318@City-Exch-DB1.cbj.local>
 <WM!c08094856a8608efcc38bbedc2db703932286d1e88bd3e44463b44e316e00bafdc55f2c8ca57ed37062302adfe6af445!@mx.jul.es>
Message-ID: <60a42130-a0f5-be67-e7d6-80b696d0ef24@Zend.To>

Kevin,

As the ZendTo Installer doesn't actually set up any SNMP configuration, 
I would rather not have the Installer open up access to the SNMP 
service. If you're building ZendTo on top of your own corporate 
"template" image that has things like network management, logging and 
authentication pre-configured, then the ZendTo Installer won't upset that.

Cheers,
Jules.

On 24/04/2019 20:55, Kevin Miller via ZendTo wrote:
> We noticed today that the new zendto server wasn't doing snmp.  Turned out to be the UFW firewall.  Easy enough to add it in, but would it be possible to make that a stock feature (or option in the script)?  I'm sure we're not the only ones using network management of one flavor or another.  Port 161 IIRC.
>
> Thanks...
>
> ...Kevin
> --
> Kevin Miller
> Network/email Administrator, CBJ MIS Dept.
> 155 South Seward Street
> Juneau, Alaska 99801
> Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357
>
>
> _______________________________________________
> 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:
South Fisher, German Bight: Southeasterly 4 or 5. Slight or moderate, becoming
smooth or slight later in German Bight. Fog patches, showers later. Moderate,
occasionally very poor.

www.Zend.To
Twitter: @JulesFM



From Jules at Zend.To  Thu Apr 25 09:07:43 2019
From: Jules at Zend.To (Jules Field)
Date: Thu, 25 Apr 2019 09:07:43 +0100
Subject: [ZendTo] Authenticator after update
In-Reply-To: <WM!40fe38db57b0ced88296260d5227c43541f67a0b65e088fa5ce4405336a9aeb9dbaa19902892371d49453e2059f9fd7b!@mx.jul.es>
References: <e232dd06-f1d1-da6f-6084-8808659b08db@alaska.gov>
 <1d7de9d0-991f-62f3-7406-d11939f561dc@alaska.gov>
 <WM!999efad5bf8cb0c5e95a2ee98c9d3844b82302ce3480728f644c309b61d24a9d7977014dd74124289da4bba1927a20a1!@mx.jul.es>
 <b1739317-11a8-2ae1-98bd-3dcf5025cc5a@Zend.To>
 <WM!e10819c4eb2376a951503866c2428f1e613dd4329a578063d1d6f1993579e582139181c150b324a177db91878d795dc8da496d29c89327cb1c0b30d0fc0f4698!@mx.jul.es>
 <8C5A64810200008E7314B811@mail.msktd.com>
 <E18F12640200000D5C3646E4@mail.msktd.com>
 <4F77DDF60200008D7314B811@mail.msktd.com>
 <D9E7E4B8020000787314B811@mail.msktd.com>
 <7B8EE8AC0200002C9BE0E8C9@mail.msktd.com>
 <BF19ED1C020000F27314B811@mail.msktd.com>
 <7B6D23690200003AC84B1EE2@mail.msktd.com>
 <3D1C77C4020000527314B811@mail.msktd.com>
 <5CC0CB8902000013001349CE@mail.msktd.com>
 <WM!40fe38db57b0ced88296260d5227c43541f67a0b65e088fa5ce4405336a9aeb9dbaa19902892371d49453e2059f9fd7b!@mx.jul.es>
Message-ID: <dc16c195-f6dd-4c1c-f82f-bc45449e3be6@Zend.To>

Ken,

And please note that the /opt/zendto/bin/upgrade script takes a 
"--dryrun" option if you want to see exactly what files it has found, 
and what it will use as the new template, and what it will use as the 
file containing your old settings.
It then shows you exactly what commands it would run to do the upgrade 
of the preferences.php and zendto.conf files.

Cheers,
Jules.

On 24/04/2019 21:48, Ken Etter wrote:
> Just thought I would mention that I also use LDAP but not AD.? So I am 
> one of those "few sites".? I haven't tried the updater yet because 
> last upgrade time I built a new ZendTo server on SLES (moved off my 
> old Ubuntu server).? I'll have to see what happens next update time.
>
> *Ken Etter*, System Administrator
> Architectural Group
> 260.432.9337|msktd.com <http://msktd.com/>
>
> <http://msktd.com/>
>
>
> >>> Jules via ZendTo <zendto at zend.to> 4/21/2019 7:13 AM >>>
> > John,
>
> Sorry, I suspect that you are one of the few sites using LDAP, but not AD.
> :-(
> What happens if you explicitly set them (to quite possibly empty 
> strings), rather than comment them out?
> The updater doesn't understand PHP itself, it looks for settings and 
> comments. It can't tell the difference between a commented-out setting 
> and any other sort of comment.
> Let me know how you get on. If I need to change some of the behaviour 
> to treat an "empty" value as if it weren't set at all, I can do that 
> no problem.
> Cheers,
> Jules.
> On 28/03/2019 4:26 pm, John Thurston via ZendTo wrote:
>> Are you using all of the available "authLDAP" config values?
>>
>> In my case, the updater re-enables configuration values I have 
>> explicitly commented out. Things like:
>> 'authLDAPBindDn'
>> 'authLDAPBindPass'
>> 'authLDAPOrganization'
>> 'authLDAPUsernameAttr'
>> 'authLDAPEmailAttr'
>> 'authLDAPMemberKey'
>> 'authLDAPMemberRole'
>> When they get re-enabled, authentication fails because none of the 
>> values are applicable or correct.
>> -- 
>> 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 3/28/2019 7:02 AM, Scott Silva via ZendTo wrote:
>>> I just ran the new upgrade script on an update from 5.15 to 5.17 and 
>>> everything seems to be going smoothly in my testing. And I am using 
>>> LDAP auth against an AD system.
>>>
>>
>> _______________________________________________
>> 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:
> East Sole, Lundy, Fastnet: Variable 3 or 4, becoming southeasterly 4 or 5
> later. Moderate. Fog patches. Moderate or good, occasionally very poor.
>
> www.Zend.To
> Twitter: @JulesFM

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

The current UK shipping forecast:
North Fisher: Easterly 7 or gale 8, decreasing 5 or 6. Moderate or rough
becoming slight or moderate. Showers. Good.

www.Zend.To
Twitter: @JulesFM

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

From kevin.miller at juneau.org  Thu Apr 25 17:42:18 2019
From: kevin.miller at juneau.org (Kevin Miller)
Date: Thu, 25 Apr 2019 16:42:18 +0000
Subject: [ZendTo] UFW firewall
In-Reply-To: <WM!f9c74e9259e6a28f9c894b504eab5f542b432c33f9e8c810b01996e22a4aae04c109a70aa3e7f84c7185a84d86dc7def517fc15188aa2f88ce58992f9dfced3e!@mx.jul.es>
References: <9efcab96ba9c4dae99a0086e83266318@City-Exch-DB1.cbj.local>
 <WM!c08094856a8608efcc38bbedc2db703932286d1e88bd3e44463b44e316e00bafdc55f2c8ca57ed37062302adfe6af445!@mx.jul.es>
 <60a42130-a0f5-be67-e7d6-80b696d0ef24@Zend.To>
 <WM!f9c74e9259e6a28f9c894b504eab5f542b432c33f9e8c810b01996e22a4aae04c109a70aa3e7f84c7185a84d86dc7def517fc15188aa2f88ce58992f9dfced3e!@mx.jul.es>
 <e956baefe07f4fd6b637ca2b37dd36b7@City-Exch-DB1.cbj.local>
Message-ID: <WM!752b6f14ad58b7c2762f134c01419cb4509aca862f68de60fd87acb40e7397e7893d914418925934a19e06938a9ed48a!@mx.jul.es>

Fair enough.  This was a new build from scratch, but I understand your reasons for not doing it.   In hindsight I'd probably do the same.

Cheers...

...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357

-----Original Message-----
From: ZendTo <zendto-bounces at zend.to> On Behalf Of Jules Field via ZendTo
Sent: Thursday, April 25, 2019 12:03 AM
To: ZendTo Users <zendto at zend.to>
Cc: Jules Field <Jules at Zend.To>; Kevin Miller <kevin.miller at juneau.org>
Subject: Re: [ZendTo] UFW firewall

Kevin,

As the ZendTo Installer doesn't actually set up any SNMP configuration, I would rather not have the Installer open up access to the SNMP service. If you're building ZendTo on top of your own corporate "template" image that has things like network management, logging and authentication pre-configured, then the ZendTo Installer won't upset that.

Cheers,
Jules.

On 24/04/2019 20:55, Kevin Miller via ZendTo wrote:
> We noticed today that the new zendto server wasn't doing snmp.  Turned out to be the UFW firewall.  Easy enough to add it in, but would it be possible to make that a stock feature (or option in the script)?  I'm sure we're not the only ones using network management of one flavor or another.  Port 161 IIRC.
>
> Thanks...
>
> ...Kevin
> --
> Kevin Miller
> Network/email Administrator, CBJ MIS Dept.
> 155 South Seward Street
> Juneau, Alaska 99801
> Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 
> 307357
>
>
> _______________________________________________
> 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:
South Fisher, German Bight: Southeasterly 4 or 5. Slight or moderate, becoming smooth or slight later in German Bight. Fog patches, showers later. Moderate, occasionally very poor.

www.Zend.To
Twitter: @JulesFM


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


From john.thurston at alaska.gov  Thu Apr 25 18:25:49 2019
From: john.thurston at alaska.gov (John Thurston)
Date: Thu, 25 Apr 2019 09:25:49 -0800
Subject: [ZendTo] Feature requests - Global Drop-off List
In-Reply-To: <WM!6eb2c16000e55b0624702f080d2766de37d1fe3f3d0b94c2a0d4e3332de8b4a6cc287e90fa9d34e7779eb152f8d9d59af169340cf1dfa6fdad07288c0c0f1e1b!@mx.jul.es>
References: <eb696566-d2e7-d0a4-aab8-8b8fc9026312@alaska.gov>
 <WM!28188fe001a22bb6ccf2a7b74b506b22ae4d8458cd11e247643900e3c5d5dc8051d275b36fc56594e7857e57ff79ecff!@mx.jul.es>
 <9c01915d-62b9-20fb-9ef1-c3ab0e33e874@Zend.To>
 <WM!6eb2c16000e55b0624702f080d2766de37d1fe3f3d0b94c2a0d4e3332de8b4a6cc287e90fa9d34e7779eb152f8d9d59af169340cf1dfa6fdad07288c0c0f1e1b!@mx.jul.es>
 <201dee0c-1546-1f0f-5bd4-3ee0653669ad@alaska.gov>
Message-ID: <WM!dcf0d4bfcd002263377ea4948f5f7c051976276d18d882340ba3ebee9338fca8d841ba87e714df9a21ff10afabedca1c!@mx.jul.es>


On 4/21/2019 3:22 AM, Jules wrote:
>> John Thurston wrote:
>> It would also be helpful if there were a way to 'open in new tab' from 
>> that screen. If I sort by size and want to examine the 8 largest 
>> dropoffs, I have to open the list, sort the list, identify the claimID 
>> I want, open it, examine it, ... then I must repeat all the steps from 
>> the beginning. If I could ctrl-click on a claimID and open it in a new 
>> tab, I would save a whole bunch of clicks.

> How about I just tweak the template a bit so that all of that type of 
> "list of drop-offs" page opens up a new tab instead?

That would be my preferred behavior, but I'm only one user.

--
    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 Apr 26 09:38:58 2019
From: Jules at Zend.To (Jules Field)
Date: Fri, 26 Apr 2019 09:38:58 +0100
Subject: [ZendTo] Feature requests - Global Drop-off List
In-Reply-To: <WM!dcf0d4bfcd002263377ea4948f5f7c051976276d18d882340ba3ebee9338fca8d841ba87e714df9a21ff10afabedca1c!@mx.jul.es>
References: <eb696566-d2e7-d0a4-aab8-8b8fc9026312@alaska.gov>
 <WM!28188fe001a22bb6ccf2a7b74b506b22ae4d8458cd11e247643900e3c5d5dc8051d275b36fc56594e7857e57ff79ecff!@mx.jul.es>
 <9c01915d-62b9-20fb-9ef1-c3ab0e33e874@Zend.To>
 <WM!6eb2c16000e55b0624702f080d2766de37d1fe3f3d0b94c2a0d4e3332de8b4a6cc287e90fa9d34e7779eb152f8d9d59af169340cf1dfa6fdad07288c0c0f1e1b!@mx.jul.es>
 <201dee0c-1546-1f0f-5bd4-3ee0653669ad@alaska.gov>
 <WM!dcf0d4bfcd002263377ea4948f5f7c051976276d18d882340ba3ebee9338fca8d841ba87e714df9a21ff10afabedca1c!@mx.jul.es>
Message-ID: <bcd60a0a-56fb-dc2c-2140-dde84de11e42@Zend.To>



On 25/04/2019 18:25, John Thurston via ZendTo wrote:
>
> On 4/21/2019 3:22 AM, Jules wrote:
>>> John Thurston wrote:
>>> It would also be helpful if there were a way to 'open in new tab' 
>>> from that screen. If I sort by size and want to examine the 8 
>>> largest dropoffs, I have to open the list, sort the list, identify 
>>> the claimID I want, open it, examine it, ... then I must repeat all 
>>> the steps from the beginning. If I could ctrl-click on a claimID and 
>>> open it in a new tab, I would save a whole bunch of clicks.
>
>> How about I just tweak the template a bit so that all of that type of 
>> "list of drop-offs" page opens up a new tab instead?
>
> That would be my preferred behavior, but I'm only one user.
I figured it would be more useful for everyone, so it now does it that way.

Cheers,

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

The current UK shipping forecast:
Irish Sea: South 5 or 6, becoming cyclonic 6 to gale 8, then northwest 7 to
severe gale 9 later, perhaps storm 10. Slight or moderate, becoming rough or
very rough, occasionally high later in far south. Showers. Good.

www.Zend.To
Twitter: @JulesFM



From kbe2 at lehigh.edu  Fri Apr 26 17:49:14 2019
From: kbe2 at lehigh.edu (Keith Erekson)
Date: Fri, 26 Apr 2019 12:49:14 -0400
Subject: [ZendTo] Authenticator after update
In-Reply-To: <WM!3b317467d173717816e39d6633e1bec450e052e32a2c5c0c618528e1d6418bc00b5ff1c14ee5c4082a48b712da09c41ae90234f23af53bfb630d5be12532a681!@mx.jul.es>
References: <e232dd06-f1d1-da6f-6084-8808659b08db@alaska.gov>
 <b1739317-11a8-2ae1-98bd-3dcf5025cc5a@Zend.To>
 <WM!e10819c4eb2376a951503866c2428f1e613dd4329a578063d1d6f1993579e582139181c150b324a177db91878d795dc8da496d29c89327cb1c0b30d0fc0f4698!@mx.jul.es>
 <8C5A64810200008E7314B811@mail.msktd.com>
 <E18F12640200000D5C3646E4@mail.msktd.com>
 <4F77DDF60200008D7314B811@mail.msktd.com>
 <D9E7E4B8020000787314B811@mail.msktd.com>
 <7B8EE8AC0200002C9BE0E8C9@mail.msktd.com>
 <BF19ED1C020000F27314B811@mail.msktd.com>
 <7B6D23690200003AC84B1EE2@mail.msktd.com>
 <3D1C77C4020000527314B811@mail.msktd.com>
 <5CC0CB8902000013001349CE@mail.msktd.com>
 <WM!40fe38db57b0ced88296260d5227c43541f67a0b65e088fa5ce4405336a9aeb9dbaa19902892371d49453e2059f9fd7b!@mx.jul.es>
 <WM!3b317467d173717816e39d6633e1bec450e052e32a2c5c0c618528e1d6418bc00b5ff1c14ee5c4082a48b712da09c41ae90234f23af53bfb630d5be12532a681!@mx.jul.es>
 <e92abde4-8fcf-6d02-5eef-df45fd038f98@lehigh.edu>
Message-ID: <WM!1bdf18c430fc3ee44f3ab74db0c35d32d86d93482fc6788fc5d4d983142273142772b28b453a24cf13ed4b2ae025ee6a!@mx.jul.es>

I also use LDAP that's not AD, and have had this happen while running
the update script.

~Keith

On 4/24/19 4:48 PM, Ken Etter via ZendTo wrote:
> Just thought I would mention that I also use LDAP but not AD.? So I am
> one of those "few sites".? I haven't tried the updater yet because
> last upgrade time I built a new ZendTo server on SLES (moved off my
> old Ubuntu server).? I'll have to see what happens next update time.
>
> *Ken Etter*, System Administrator
> Architectural Group
> 260.432.9337?|?msktd.com <http://msktd.com/>
>
> <http://msktd.com/>
>
>
> >>> Jules via ZendTo <zendto at zend.to> 4/21/2019 7:13 AM >>>
> > John,
>
> Sorry, I suspect that you are one of the few sites using LDAP, but not AD.
> :-(
> What happens if you explicitly set them (to quite possibly empty
> strings), rather than comment them out?
> The updater doesn't understand PHP itself, it looks for settings and
> comments. It can't tell the difference between a commented-out setting
> and any other sort of comment.
> Let me know how you get on. If I need to change some of the behaviour
> to treat an "empty" value as if it weren't set at all, I can do that
> no problem.
> Cheers,
> Jules.
> On 28/03/2019 4:26 pm, John Thurston via ZendTo wrote:
>> Are you using all of the available "authLDAP" config values?
>>
>> In my case, the updater re-enables configuration values I have
>> explicitly commented out. Things like:
>> 'authLDAPBindDn'
>> 'authLDAPBindPass'
>> 'authLDAPOrganization'
>> 'authLDAPUsernameAttr'
>> 'authLDAPEmailAttr'
>> 'authLDAPMemberKey'
>> 'authLDAPMemberRole'
>> When they get re-enabled, authentication fails because none of the
>> values are applicable or correct.
>> -- 
>> 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 3/28/2019 7:02 AM, Scott Silva via ZendTo wrote:
>>> I just ran the new upgrade script on an update from 5.15 to 5.17 and
>>> everything seems to be going smoothly in my testing. And I am using
>>> LDAP auth against an AD system.
>>>
>>
>> _______________________________________________
>> 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:
> East Sole, Lundy, Fastnet: Variable 3 or 4, becoming southeasterly 4 or 5
> later. Moderate. Fog patches. Moderate or good, occasionally very poor.
>
> 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/20190426/61040a21/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMAGE.png
Type: image/png
Size: 18080 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20190426/61040a21/attachment-0001.png>

From ssilva at sgvwater.com  Fri Apr 26 18:48:42 2019
From: ssilva at sgvwater.com (Scott Silva)
Date: Fri, 26 Apr 2019 17:48:42 +0000
Subject: [ZendTo] Authenticator after update
In-Reply-To: <WM!d245419f14f40eb5aef18d1ceaee2bd9ee9c52c712e52576e9b417ca10a1f66097bfbe908c242684cb8dac5ff69d3dc6059fc771aa6f230fba78b270914a2cc6!@mx.jul.es>
References: <e232dd06-f1d1-da6f-6084-8808659b08db@alaska.gov>
 <b1739317-11a8-2ae1-98bd-3dcf5025cc5a@Zend.To>
 <WM!e10819c4eb2376a951503866c2428f1e613dd4329a578063d1d6f1993579e582139181c150b324a177db91878d795dc8da496d29c89327cb1c0b30d0fc0f4698!@mx.jul.es>
 <8C5A64810200008E7314B811@mail.msktd.com>
 <E18F12640200000D5C3646E4@mail.msktd.com>
 <4F77DDF60200008D7314B811@mail.msktd.com>
 <D9E7E4B8020000787314B811@mail.msktd.com>
 <7B8EE8AC0200002C9BE0E8C9@mail.msktd.com>
 <BF19ED1C020000F27314B811@mail.msktd.com>
 <7B6D23690200003AC84B1EE2@mail.msktd.com>
 <3D1C77C4020000527314B811@mail.msktd.com>
 <5CC0CB8902000013001349CE@mail.msktd.com>
 <WM!40fe38db57b0ced88296260d5227c43541f67a0b65e088fa5ce4405336a9aeb9dbaa19902892371d49453e2059f9fd7b!@mx.jul.es>
 <WM!3b317467d173717816e39d6633e1bec450e052e32a2c5c0c618528e1d6418bc00b5ff1c14ee5c4082a48b712da09c41ae90234f23af53bfb630d5be12532a681!@mx.jul.es>
 <e92abde4-8fcf-6d02-5eef-df45fd038f98@lehigh.edu>
 <WM!1bdf18c430fc3ee44f3ab74db0c35d32d86d93482fc6788fc5d4d983142273142772b28b453a24cf13ed4b2ae025ee6a!@mx.jul.es>
 <WM!d245419f14f40eb5aef18d1ceaee2bd9ee9c52c712e52576e9b417ca10a1f66097bfbe908c242684cb8dac5ff69d3dc6059fc771aa6f230fba78b270914a2cc6!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F420509F1B@FONEXCH01.sgvwc.local>
Message-ID: <WM!a37c7fb313e4c1155f7129f36a97be85d772f1657ec806d262e605a52dbc719a56d8e95cac7be8957bd8d2b856200009!@mx.jul.es>

I just got in the habit of saving a copy of my config files, and diff'ing them with the new to see what changed...


From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Keith Erekson via ZendTo
Sent: Friday, April 26, 2019 9:52 AM
To: Ken Etter via ZendTo <zendto at zend.to>
Cc: Keith Erekson <kbe2 at lehigh.edu>
Subject: Re: [ZendTo] Authenticator after update


I also use LDAP that's not AD, and have had this happen while running the update script.

~Keith
On 4/24/19 4:48 PM, Ken Etter via ZendTo wrote:
Just thought I would mention that I also use LDAP but not AD.  So I am one of those "few sites".  I haven't tried the updater yet because last upgrade time I built a new ZendTo server on SLES (moved off my old Ubuntu server).  I'll have to see what happens next update time.


Ken Etter, System Administrator
Architectural Group
260.432.9337 | msktd.com<http://msktd.com/>

[cid:image001.png at 01D4FC1D.81D491F0]<http://msktd.com/>


>>> Jules via ZendTo <zendto at zend.to><mailto:zendto at zend.to> 4/21/2019 7:13 AM >>>
> John,

Sorry, I suspect that you are one of the few sites using LDAP, but not AD.
:-(
What happens if you explicitly set them (to quite possibly empty strings), rather than comment them out?
The updater doesn't understand PHP itself, it looks for settings and comments. It can't tell the difference between a commented-out setting and any other sort of comment.
Let me know how you get on. If I need to change some of the behaviour to treat an "empty" value as if it weren't set at all, I can do that no problem.
Cheers,
Jules.
On 28/03/2019 4:26 pm, John Thurston via ZendTo wrote:
Are you using all of the available "authLDAP" config values?

In my case, the updater re-enables configuration values I have explicitly commented out. Things like:
'authLDAPBindDn'
'authLDAPBindPass'
'authLDAPOrganization'
'authLDAPUsernameAttr'
'authLDAPEmailAttr'
'authLDAPMemberKey'
'authLDAPMemberRole'
When they get re-enabled, authentication fails because none of the values are applicable or correct.
--
Do things because you should, not just because you can.
John Thurston 907-465-8591
John.Thurston at alaska.gov<mailto:John.Thurston at alaska.gov>
Department of Administration
State of Alaska
On 3/28/2019 7:02 AM, Scott Silva via ZendTo wrote:
I just ran the new upgrade script on an update from 5.15 to 5.17 and everything seems to be going smoothly in my testing. And I am using LDAP auth against an AD system.


_______________________________________________
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:

East Sole, Lundy, Fastnet: Variable 3 or 4, becoming southeasterly 4 or 5

later. Moderate. Fog patches. Moderate or good, occasionally very poor.



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/20190426/32a127c9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 18080 bytes
Desc: image001.png
URL: <http://jul.es/pipermail/zendto/attachments/20190426/32a127c9/attachment-0001.png>

From Jules at Zend.To  Mon Apr 29 12:27:30 2019
From: Jules at Zend.To (Jules Field)
Date: Mon, 29 Apr 2019 12:27:30 +0100
Subject: [ZendTo] Authenticator after update
In-Reply-To: <WM!a37c7fb313e4c1155f7129f36a97be85d772f1657ec806d262e605a52dbc719a56d8e95cac7be8957bd8d2b856200009!@mx.jul.es>
References: <e232dd06-f1d1-da6f-6084-8808659b08db@alaska.gov>
 <BF19ED1C020000F27314B811@mail.msktd.com>
 <7B6D23690200003AC84B1EE2@mail.msktd.com>
 <3D1C77C4020000527314B811@mail.msktd.com>
 <5CC0CB8902000013001349CE@mail.msktd.com>
 <WM!40fe38db57b0ced88296260d5227c43541f67a0b65e088fa5ce4405336a9aeb9dbaa19902892371d49453e2059f9fd7b!@mx.jul.es>
 <WM!3b317467d173717816e39d6633e1bec450e052e32a2c5c0c618528e1d6418bc00b5ff1c14ee5c4082a48b712da09c41ae90234f23af53bfb630d5be12532a681!@mx.jul.es>
 <e92abde4-8fcf-6d02-5eef-df45fd038f98@lehigh.edu>
 <WM!1bdf18c430fc3ee44f3ab74db0c35d32d86d93482fc6788fc5d4d983142273142772b28b453a24cf13ed4b2ae025ee6a!@mx.jul.es>
 <WM!d245419f14f40eb5aef18d1ceaee2bd9ee9c52c712e52576e9b417ca10a1f66097bfbe908c242684cb8dac5ff69d3dc6059fc771aa6f230fba78b270914a2cc6!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F420509F1B@FONEXCH01.sgvwc.local>
 <WM!a37c7fb313e4c1155f7129f36a97be85d772f1657ec806d262e605a52dbc719a56d8e95cac7be8957bd8d2b856200009!@mx.jul.es>
Message-ID: <444fe5bd-ee56-c922-3b5c-00462c62519f@Zend.To>

I think I have fixed this one, had to make upgrade_preferences_php 
(which upgrade calls) somewhat more intelligent to handle the setting 
"authenticator" moving around.

The fix will be in the next beta, due out very soon...

Cheers,
Jules.

On 26/04/2019 18:48, Scott Silva via ZendTo wrote:
>
> I just got in the habit of saving a copy of my config files, and 
> diff?ing them with the new to see what changed?
>
> *From:*ZendTo [mailto:zendto-bounces at zend.to] *On Behalf Of *Keith 
> Erekson via ZendTo
> *Sent:* Friday, April 26, 2019 9:52 AM
> *To:* Ken Etter via ZendTo <zendto at zend.to>
> *Cc:* Keith Erekson <kbe2 at lehigh.edu>
> *Subject:* Re: [ZendTo] Authenticator after update
>
> I also use LDAP that's not AD, and have had this happen while running 
> the update script.
>
> ~Keith
>
> On 4/24/19 4:48 PM, Ken Etter via ZendTo wrote:
>
>     Just thought I would mention that I also use LDAP but not AD.? So
>     I am one of those "few sites".? I haven't tried the updater yet
>     because last upgrade time I built a new ZendTo server on SLES
>     (moved off my old Ubuntu server).? I'll have to see what happens
>     next update time.
>
>
>
>     *Ken Etter*, System Administrator
>
>     Architectural Group
>
>     260.432.9337?| msktd.com <http://msktd.com/>
>
>     <http://msktd.com/>
>
>     >>> Jules via ZendTo <zendto at zend.to> <mailto:zendto at zend.to>
>     4/21/2019 7:13 AM >>>
>
>     > John,
>
>     Sorry, I suspect that you are one of the few sites using LDAP, but
>     not AD.
>
>     :-(
>
>     What happens if you explicitly set them (to quite possibly empty
>     strings), rather than comment them out?
>
>     The updater doesn't understand PHP itself, it looks for settings
>     and comments. It can't tell the difference between a commented-out
>     setting and any other sort of comment.
>
>     Let me know how you get on. If I need to change some of the
>     behaviour to treat an "empty" value as if it weren't set at all, I
>     can do that no problem.
>
>     Cheers,
>
>     Jules.
>
>     On 28/03/2019 4:26 pm, John Thurston via ZendTo wrote:
>
>         Are you using all of the available "authLDAP" config values?
>
>         In my case, the updater re-enables configuration values I have
>         explicitly commented out. Things like:
>
>         'authLDAPBindDn'
>
>         'authLDAPBindPass'
>
>         'authLDAPOrganization'
>
>         'authLDAPUsernameAttr'
>
>         'authLDAPEmailAttr'
>
>         'authLDAPMemberKey'
>
>         'authLDAPMemberRole'
>
>         When they get re-enabled, authentication fails because none of
>         the values are applicable or correct.
>
>         -- 
>
>         Do things because you should, not just because you can.
>
>         John Thurston 907-465-8591
>
>         John.Thurston at alaska.gov <mailto:John.Thurston at alaska.gov>
>
>         Department of Administration
>
>         State of Alaska
>
>         On 3/28/2019 7:02 AM, Scott Silva via ZendTo wrote:
>
>             I just ran the new upgrade script on an update from 5.15
>             to 5.17 and everything seems to be going smoothly in my
>             testing. And I am using LDAP auth against an AD system.
>
>         _______________________________________________
>
>         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:
>
>     East Sole, Lundy, Fastnet: Variable 3 or 4, becoming southeasterly
>     4 or 5
>
>     later. Moderate. Fog patches. Moderate or good, occasionally very
>     poor.
>
>     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
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

The current UK shipping forecast:
Malin, Hebrides, Bailey: East or southeast 5 or 6, decreasing 4 at times.
Moderate or rough. Occasional rain. Good, occasionally poor.

www.Zend.To
Twitter: @JulesFM

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

From Jules at Zend.To  Mon Apr 29 12:31:41 2019
From: Jules at Zend.To (Jules Field)
Date: Mon, 29 Apr 2019 12:31:41 +0100
Subject: [ZendTo] Feature requests - Global Drop-off List
In-Reply-To: <9c01915d-62b9-20fb-9ef1-c3ab0e33e874@Zend.To>
References: <eb696566-d2e7-d0a4-aab8-8b8fc9026312@alaska.gov>
 <WM!28188fe001a22bb6ccf2a7b74b506b22ae4d8458cd11e247643900e3c5d5dc8051d275b36fc56594e7857e57ff79ecff!@mx.jul.es>
 <9c01915d-62b9-20fb-9ef1-c3ab0e33e874@Zend.To>
Message-ID: <00df9690-dda7-ae94-b685-6b03d5c30488@Zend.To>

Both of these requests:
* Show "picked up" and "encrypted" indicators in lists of drop-offs
* Open dropoffs from indexes in new tabs
are done.

They will be in the next beta, due out very soon.

Cheers,
Jules.

On 21/04/2019 12:22, Jules wrote:
> John,
>
> On 28/03/2019 5:33 pm, John Thurston via ZendTo wrote:
>> The part of ZendTo with which I interact most often is the 'Global 
>> Drop-off List". It would be wonderful to have some more information 
>> there. I'm thinking specifically of
>> ? Indicators for "encrypted" and "picked-up"
> Added to the list. Should be fairly easy to do with luck.
>
>>
>> It would also be helpful if there were a way to 'open in new tab' 
>> from that screen. If I sort by size and want to examine the 8 largest 
>> dropoffs, I have to open the list, sort the list, identify the 
>> claimID I want, open it, examine it, ... then I must repeat all the 
>> steps from the beginning. If I could ctrl-click on a claimID and open 
>> it in a new tab, I would save a whole bunch of clicks.
> How about I just tweak the template a bit so that all of that type of 
> "list of drop-offs" page opens up a new tab instead?
> Is there any reason or situation where the current behaviour would be 
> *better* than opening the drop-off in a new tab?
> Changing all of them is trivial.
>
> Jules
>
> -- 
> Julian Field MEng CEng CITP MBCS MIEEE MACM
>
> 'There is always one moment in childhood when the door opens and
>   lets the future in.' - Graham Greene
>
> www.Zend.To
> Twitter: @JulesFM

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Science is an integral part of culture. It's not this foreign
  thing, done by an arcane priesthood. It's one of the glories of
  human intellectual tradition.' - Stephen Jay Gould

www.Zend.To
Twitter: @JulesFM



From Jules at Zend.To  Mon Apr 29 15:19:29 2019
From: Jules at Zend.To (Jules Field)
Date: Mon, 29 Apr 2019 15:19:29 +0100
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!2259e31bcbec5992430418f002c490bbc3dd01ed4b2c0329743d8fc779d9efef6d0061ecc3c40991a151f8b11ffe7010!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <WM!04ac29d9b1cb683f7de0e78e84e4e2f34923d59c81d707d8829575b8c92b00a79e43ddd45ef21721380bef949edd6a9c!@mx.jul.es>
 <68797d56-996b-b3fe-122c-5d076cd94553@Zend.To>
 <WM!79697c98063608f12637d627205225e506bd16c422cf2e658b71dc91c96e4d93d6992b06c09415a55ed033135a0e0804eb61b1e883ecc1b85f1b57981f916e16!@mx.jul.es>
 <5F237D6D-5E93-4097-ACD0-F64A2485F135@yahoo.com>
 <WM!70ecf74f9e7d0b8945733332927203aaee6acd5c28f43499004c3696c297dd37eb1ba48282437d0b6734377ab4e96d6d!@mx.jul.es>
 <WM!a19dcdb9c2fb31a686ce792da4aa12c43d3ba00e35a4a16664a231c772ba25bdf2971934cb3c63b3b06a4fec57930a2506d42cd5112dbe4ad05a20e79c8bf783!@mx.jul.es>
 <E2766566-A872-4994-AE6C-2B8354C2B2A3@pcfreak.de>
 <WM!2259e31bcbec5992430418f002c490bbc3dd01ed4b2c0329743d8fc779d9efef6d0061ecc3c40991a151f8b11ffe7010!@mx.jul.es>
Message-ID: <ff78c6c1-e9aa-8054-3095-40f684711936@Zend.To>

Folks,

I'm having a think about this one.

The idea of the prefix is pretty simple, basically I would give you the 
"[ZendTo]" string (as an initial default value) in a "Subject" box in 
the new drop-off form.

Whatever you end up putting in there gets used instead of [ZendTo] at 
the start of the email subject lines.

However......

If you request a drop-off, you get to supply the whole Subject line for 
the email to the person you want to send you their files.
Ideally, that same Subject line would be used in all notifications etc 
about that drop-off.
But they have entered the *whole* Subject line, not just the prefix to it.
If I use their whole Subject line as a prefix, it's going to look weird.

So what do I do for the Subject prefix, when it was created as a result 
of a request which had the entire Subject line supplied?
I clearly can't ask the person sending the request to supply 2 Subject 
entries ? both the current whole Subject line *and* the prefix to use ? 
as that would confuse the hell out of them.

Any ideas please?

Cheers,
Jules.

On 21/04/2019 14:29, Mailing Lists via ZendTo wrote:
> Hi Jules,
>
> yes it would be enough to allow 20 editable characters.
>
> via Smartphone
>
> Am 21.04.2019 um 15:13 schrieb Travis McDugald via ZendTo 
> <zendto at zend.to <mailto:zendto at zend.to>>:
>
>> While no one has asked for this yet, I do see it?s usefulness.
>> I do use custom strings in email subjects for some projects as well. 
>> ?Helps with sorting, searching, and filtering.
>>
>> Side note: great job on everything Jules, thank you.
>>
>> Sent from my iPad
>>
>> On Apr 21, 2019, at 7:40 AM, Jules via ZendTo <zendto at zend.to 
>> <mailto:zendto at zend.to>> wrote:
>>
>>> Peter,
>>>
>>> You effectively just want to allow senders to customise the 
>>> "[ZENDTO]" subject line tag in each drop-off, correct?
>>>
>>> Does anyone else need to do this too?
>>>
>>> Cheers,
>>> Jules.
>>>
>>> On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
>>>> Hi Jules, hi all.
>>>>
>>>> I have a strange request from our ZendTo users. They asked if it 
>>>> would be possible to add a custom field when sending a DropOff
>>>> that results in a custom text in all ZendTo email concerning this 
>>>> specific DropOff.
>>>>
>>>> Example current:
>>>>
>>>> [ZENDTO] One of the recipients has picked up your drop-off!
>>>>
>>>> Example requested:
>>>>
>>>> [ZENDTO] CUSTOM_STRING One of the recipients has picked up your 
>>>> drop-off!
>>>>
>>>> I asked a little bit about the purpose of their request and they 
>>>> told me that project teams sort their email by subject and
>>>> consequently keep the project name (CUSTOM_STRING) in every subject 
>>>> of their emails concerning that specific project.
>>>> So later they could sort by project name (CUSTOM_STRING) within 
>>>> Outlook to be able to verify when they sent a specific DropOff.
>>>>
>>>> Question:
>>>> Is it possible to implement such a feature?
>>>>
>>>> I know that I could handcraft it but I don't want to make big 
>>>> changes to the source and always have to keep track of them when 
>>>> upgrading.
>>>>
>>>> I am currently not on the latest version of ZendTo, so if such a 
>>>> feature is maybe already present in the latest version, feel free
>>>> to tell me.
>>>>
>>>> Thanks in advance.
>>>>
>>>> Peter
>>>>
>>>>
>>>> _______________________________________________
>>>> ZendTo mailing list
>>>> ZendTo at zend.to
>>>> http://jul.es/mailman/listinfo/zendto
>>>
>>> Jules
>>>
>>> -- 
>>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>>
>>> 'Once is happenstance, twice is coincidence, three times is enemy
>>>   action.' - Ian Fleming
>>>
>>> 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
> 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/20190429/1309572c/attachment.html>

From Jules at Zend.To  Mon Apr 29 16:43:36 2019
From: Jules at Zend.To (Jules Field)
Date: Mon, 29 Apr 2019 16:43:36 +0100
Subject: [ZendTo] New beta 5.18-1 released (new features!)
Message-ID: <7d290f7f-99d5-94d7-c46a-89297cfc966d@Zend.To>

Afternoon folks!

I have just released a new beta 5.18-1.

This is mostly a "feature" release, but does also include fixes for any 
bugs I have been told about.

New features this time around:
* Users can remove unwanted addresses from their address book.
* Lists of drop-offs now indicate encrypted drop-offs and picked-up 
drop-offs.
* Selecting a drop-off from a list opens it in a new tab.
* Sending a request for a drop-off is now scriptable.
* upgrade and upgrade_preferences_php handle authenticator settings 
(particular LDAP!) much better.

See the download and installation instructions for the beta at
*https://zend.to/beta.php*

Please try it out and let me know as soon as possible if you find any 
problems. And also tell me what you think of the new features and how 
they could be improved!

Here is the full Change Log:

- Autocomplete list of address book matches when entering recipients now 
has an "X" button at the end of each line which deletes that entry.
- Lists of drop-offs now show if the drop-off has been picked up, and if 
it was encrypted.
- Selecting a drop-off from any list of drop-offs now shows it in a new tab.
- New command /opt/zendto/bin/autorequest will generate a request for a 
drop-off from a script. Run it with no parameters to see the usage. If 
you want to use this, you will need to create a user specifically for 
the automation to use, and set it in the new 'automationUsers' setting 
in preferences.php. The autorequest gives you a return code back and a 
bit of JSON to say what happened.
- "upgrade_preferences_php", and hence also "upgrade", have been 
improved to fix problems for people using LDAP but not AD, as they 
highlighted a lacking in the intelligence of the tool.
- Lists of drop-offs show a tooltip explaining the "Picked up" column.
- Log clean virus scans of new drop-offs as well as viruses and errors.
- Logo image should display better now if it's a bit too tall.
- Security fix highlighted by Michael Radford. All users should upgrade.
- Fixed string formatting bug when a user tries to send a drop-off 
request with a Subject: line that is too long. Thanks for Tobias Tafart 
for this fix!
- Installer for RHEL8 is now working, except for ClamAV which needs to 
come from EPEL but there isn't an EPEL archive for RHEL8/CentOS8 yet. 
Don't want to use the 7 archive as I'm hoping the clamd problems will 
get fixed.

Cheers,

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'There have been nearly 3000 Gods so far but only yours actually exists.
  The others are silly made up nonsense. But not yours. Yours is real.' - Anon

www.Zend.To
Twitter: @JulesFM

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

From kevin.miller at juneau.org  Mon Apr 29 17:53:13 2019
From: kevin.miller at juneau.org (Kevin Miller)
Date: Mon, 29 Apr 2019 16:53:13 +0000
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!065345b86971656b47aea8a854e1311b5d60c747358927f81b5294bcfe41e8d4acbab259d3f9a9ce2dc663f68a4fee92e2f366a0185621a2a89ed2aca5874f29!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <WM!04ac29d9b1cb683f7de0e78e84e4e2f34923d59c81d707d8829575b8c92b00a79e43ddd45ef21721380bef949edd6a9c!@mx.jul.es>
 <68797d56-996b-b3fe-122c-5d076cd94553@Zend.To>
 <WM!79697c98063608f12637d627205225e506bd16c422cf2e658b71dc91c96e4d93d6992b06c09415a55ed033135a0e0804eb61b1e883ecc1b85f1b57981f916e16!@mx.jul.es>
 <5F237D6D-5E93-4097-ACD0-F64A2485F135@yahoo.com>
 <WM!70ecf74f9e7d0b8945733332927203aaee6acd5c28f43499004c3696c297dd37eb1ba48282437d0b6734377ab4e96d6d!@mx.jul.es>
 <WM!a19dcdb9c2fb31a686ce792da4aa12c43d3ba00e35a4a16664a231c772ba25bdf2971934cb3c63b3b06a4fec57930a2506d42cd5112dbe4ad05a20e79c8bf783!@mx.jul.es>
 <E2766566-A872-4994-AE6C-2B8354C2B2A3@pcfreak.de>
 <WM!2259e31bcbec5992430418f002c490bbc3dd01ed4b2c0329743d8fc779d9efef6d0061ecc3c40991a151f8b11ffe7010!@mx.jul.es>
 <ff78c6c1-e9aa-8054-3095-40f684711936@Zend.To>
 <WM!065345b86971656b47aea8a854e1311b5d60c747358927f81b5294bcfe41e8d4acbab259d3f9a9ce2dc663f68a4fee92e2f366a0185621a2a89ed2aca5874f29!@mx.jul.es>
 <72d61410dcb94e67a16481300a961282@City-Exch-DB1.cbj.local>
Message-ID: <WM!66f223a219ffe1a20f3a0b0a994b137c61f28ba5d8fbfb670d1735e97c85b18fdba6d830aa97933f17af652e1e6f0a4e!@mx.jul.es>

Unless I?m misunderstand the conundrum, I?d say to let the requester enter the subject line, sans prefix, then prepend the system defined prefix at upload generation time.  I.e., if I was requesting a dropoff I?d put in ?My appropriate subject?.  The person that is actually doing the dropoff would see that, and probably won?t think twice about it.  Then, when the outgoing upload  notification is actually complete, Zendto can prepend the system supplied prefix [Zendto] or [Whatever] and send that.  I don?t think folks are in the habit of hand coding prefixes, so it?s unlikely one would end up with dual prefixes.

Maybe there?s coding issues with that that make it difficult?  Anyway, my tuppence worth?

...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357

From: ZendTo <zendto-bounces at zend.to> On Behalf Of Jules Field via ZendTo
Sent: Monday, April 29, 2019 6:19 AM
To: ZendTo Users <zendto at zend.to>
Cc: Jules Field <Jules at Zend.To>
Subject: Re: [ZendTo] [Feature Request custom string in subject per DropOff]

Folks,

I'm having a think about this one.

The idea of the prefix is pretty simple, basically I would give you the "[ZendTo]" string (as an initial default value) in a "Subject" box in the new drop-off form.

Whatever you end up putting in there gets used instead of [ZendTo] at the start of the email subject lines.

However......

If you request a drop-off, you get to supply the whole Subject line for the email to the person you want to send you their files.
Ideally, that same Subject line would be used in all notifications etc about that drop-off.
But they have entered the *whole* Subject line, not just the prefix to it.
If I use their whole Subject line as a prefix, it's going to look weird.

So what do I do for the Subject prefix, when it was created as a result of a request which had the entire Subject line supplied?
I clearly can't ask the person sending the request to supply 2 Subject entries ? both the current whole Subject line *and* the prefix to use ? as that would confuse the hell out of them.

Any ideas please?

Cheers,
Jules.
On 21/04/2019 14:29, Mailing Lists via ZendTo wrote:
Hi Jules,

yes it would be enough to allow 20 editable characters.
via Smartphone

Am 21.04.2019 um 15:13 schrieb Travis McDugald via ZendTo <zendto at zend.to<mailto:zendto at zend.to>>:
While no one has asked for this yet, I do see it?s usefulness.
I do use custom strings in email subjects for some projects as well.  Helps with sorting, searching, and filtering.

Side note: great job on everything Jules, thank you.

Sent from my iPad

On Apr 21, 2019, at 7:40 AM, Jules via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> wrote:
Peter,

You effectively just want to allow senders to customise the "[ZENDTO]" subject line tag in each drop-off, correct?

Does anyone else need to do this too?

Cheers,
Jules.
On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
Hi Jules, hi all.

I have a strange request from our ZendTo users. They asked if it would be possible to add a custom field when sending a DropOff
that results in a custom text in all ZendTo email concerning this specific DropOff.

Example current:

[ZENDTO] One of the recipients has picked up your drop-off!

Example requested:

[ZENDTO] CUSTOM_STRING One of the recipients has picked up your drop-off!

I asked a little bit about the purpose of their request and they told me that project teams sort their email by subject and
consequently keep the project name (CUSTOM_STRING) in every subject of their emails concerning that specific project.
So later they could sort by project name (CUSTOM_STRING) within Outlook to be able to verify when they sent a specific DropOff.

Question:
Is it possible to implement such a feature?

I know that I could handcraft it but I don't want to make big changes to the source and always have to keep track of them when upgrading.

I am currently not on the latest version of ZendTo, so if such a feature is maybe already present in the latest version, feel free
to tell me.

Thanks in advance.

Peter


_______________________________________________
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



'Once is happenstance, twice is coincidence, three times is enemy

 action.' - Ian Fleming



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



'Find a place inside where there's joy, and the joy will burn out

 the pain.' - Joseph Campbell



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

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

From TZimmerman at fsu.edu  Mon Apr 29 19:44:49 2019
From: TZimmerman at fsu.edu (Travis Zimmerman)
Date: Mon, 29 Apr 2019 18:44:49 +0000
Subject: [ZendTo] alternate AD attribute
References: <58299ADB-FC43-42C7-BF6C-5098A8060A51@fsu.edu>
Message-ID: <WM!34928f50d1e542023efee6bfe83be1c470660949703bffafce8c6f4178edad8b8c7faf56bbb71c28f0ef373d9e32c2a0!@mx.jul.es>

Would it be possible to add a variable to the AD auth config to use an alternate attribute for the username?
Something like: ?authLDAPAltAttr?     =>    ?preferredEmail?,

Our Microsoft sysadmins had to setup a different AD for students on a different domain (my.fsu.edu<http://my.fsu.edu>) from the one used by faculty and staff (fsu.edu<http://fsu.edu>). For some reason at the time they had to store the student e-mail address in a different attribute than the standard attribute, in the normal attribute they are storing a student ID number.

Up until now I worked around this problem by using the IMAP authentication, not as nice as AD but it did the job to allow students to authenticate in, receive e-mail from the ZendTo server, and view drop-offs for them in their Inbox.

We got a new CIO at my university about a month ago and it has been decided to shutdown IMAP and SMTP completely, in favor of MAPI with MFA only. I found out that this change was being talked about last week, upper management came to a decision last Friday and plan to go ahead with this change starting next week.

I appreciate all the work you?ve put into ZendTo over the years.

------------------------------------------------------
Travis Zimmerman tzimmerman at fsu.edu<mailto:tzimmerman at fsu.edu> 850-645-8030
Linux Enterprise Applications & Systems its-linuxadmins at fsu.edu<mailto:its-linuxadmins at fsu.edu>
Information Technology Services, Florida State University

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

From KLE at msktd.com  Mon Apr 29 19:47:46 2019
From: KLE at msktd.com (Ken Etter)
Date: Mon, 29 Apr 2019 14:47:46 -0400
Subject: [ZendTo] alternate AD attribute
In-Reply-To: <WM!671680fd4c4b67ee58fe6c0c02c0e7557f993f374c12d1453af214ee080a3285886c3c6282857e18c984ddfdedbccd9606081dd75191ab927b2789cdb5fdc0ba!@mx.jul.es>
References: <58299ADB-FC43-42C7-BF6C-5098A8060A51@fsu.edu>
 <WM!34928f50d1e542023efee6bfe83be1c470660949703bffafce8c6f4178edad8b8c7faf56bbb71c28f0ef373d9e32c2a0!@mx.jul.es>
 <WM!671680fd4c4b67ee58fe6c0c02c0e7557f993f374c12d1453af214ee080a3285886c3c6282857e18c984ddfdedbccd9606081dd75191ab927b2789cdb5fdc0ba!@mx.jul.es>
 <5CC746D20200001300134C87@mail.msktd.com>
Message-ID: <WM!75ec5f5a9aa984abde712e7d6850b4014652a3e648b9baa951b0dbbcff3ed92409e245097be5c393a6bb1aac06099311!@mx.jul.es>

No SMTP?  How are they going to send email to other domains?
>>> Travis Zimmerman via ZendTo <zendto at zend.to> 4/29/2019 2:44 PM >>>
Would it be possible to add a variable to the AD auth config to use an
alternate attribute for the username?
Something like:?authLDAPAltAttr?     =>    ?preferredEmail?,

Our Microsoft sysadmins had to setup a different AD for students on a
different domain (my.fsu.edu) from the one used by faculty and staff
(fsu.edu). For some reason at the time they had to store the student
e-mail address in a different attribute than the standard attribute, in
the normal attribute they are storing a student ID number.

Up until now I worked around this problem by using the IMAP
authentication, not as nice as AD but it did the job to allow students
to authenticate in, receive e-mail from the ZendTo server, and view
drop-offs for them in their Inbox.

We got a new CIO at my university about a month ago and it has been
decided to shutdown IMAP and SMTP completely, in favor of MAPI with MFA
only. I found out that this change was being talked about last week,
upper management came to a decision last Friday and plan to go ahead
with this change starting next week.

I appreciate all the work you?ve put into ZendTo over the years.

------------------------------------------------------
Travis Zimmermantzimmerman at fsu.edu850-645-8030
Linux Enterprise Applications & Systemsits-linuxadmins at fsu.edu
Information Technology Services, Florida State University

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

From TZimmerman at fsu.edu  Mon Apr 29 20:02:15 2019
From: TZimmerman at fsu.edu (Travis Zimmerman)
Date: Mon, 29 Apr 2019 19:02:15 +0000
Subject: [ZendTo] alternate AD attribute
In-Reply-To: <WM!2cd598870fe151547e3b0f6e5bf909b72ddc4080987cae39657a5169e5556df955ffba7a1f7c4b6407c0bb751f6bb790c49c5769027285217e0367d5fab09162!@mx.jul.es>
References: <58299ADB-FC43-42C7-BF6C-5098A8060A51@fsu.edu>
 <WM!34928f50d1e542023efee6bfe83be1c470660949703bffafce8c6f4178edad8b8c7faf56bbb71c28f0ef373d9e32c2a0!@mx.jul.es>
 <WM!671680fd4c4b67ee58fe6c0c02c0e7557f993f374c12d1453af214ee080a3285886c3c6282857e18c984ddfdedbccd9606081dd75191ab927b2789cdb5fdc0ba!@mx.jul.es>
 <5CC746D20200001300134C87@mail.msktd.com>
 <WM!75ec5f5a9aa984abde712e7d6850b4014652a3e648b9baa951b0dbbcff3ed92409e245097be5c393a6bb1aac06099311!@mx.jul.es>
 <WM!2cd598870fe151547e3b0f6e5bf909b72ddc4080987cae39657a5169e5556df955ffba7a1f7c4b6407c0bb751f6bb790c49c5769027285217e0367d5fab09162!@mx.jul.es>
 <C30F3FC2-8E0E-4050-9469-E7D9FAB58F65@fsu.edu>
Message-ID: <WM!b6ced1c39c94e4c26a2f61301804ef4d00615609f1b09a210d99d84eeb3637ccd668c51ba53c7454fcd82c4207ed5835!@mx.jul.es>

I?m assuming they plan to use some Exchange only tech for sending e-mail, I would have to ask the Microsoft team here how that will work. This is just what was laid out in an e-mail sent to my department by the university?s CIO, no real specifics given just goals.

------------------------------------------------------
Travis Zimmerman tzimmerman at fsu.edu<mailto:tzimmerman at fsu.edu> 850-645-8030
Linux Enterprise Applications & Systems its-linuxadmins at fsu.edu<mailto:its-linuxadmins at fsu.edu>
Information Technology Services, Florida State University

On Apr 29, 2019, at 2:47 PM, Ken Etter via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> wrote:

No SMTP?  How are they going to send email to other domains?
>>> Travis Zimmerman via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> 4/29/2019 2:44 PM >>>
Would it be possible to add a variable to the AD auth config to use an alternate attribute for the username?
Something like: ?authLDAPAltAttr?     =>    ?preferredEmail?,

Our Microsoft sysadmins had to setup a different AD for students on a different domain (my.fsu.edu<http://my.fsu.edu/>) from the one used by faculty and staff (fsu.edu<http://fsu.edu/>). For some reason at the time they had to store the student e-mail address in a different attribute than the standard attribute, in the normal attribute they are storing a student ID number.

Up until now I worked around this problem by using the IMAP authentication, not as nice as AD but it did the job to allow students to authenticate in, receive e-mail from the ZendTo server, and view drop-offs for them in their Inbox.

We got a new CIO at my university about a month ago and it has been decided to shutdown IMAP and SMTP completely, in favor of MAPI with MFA only. I found out that this change was being talked about last week, upper management came to a decision last Friday and plan to go ahead with this change starting next week.

I appreciate all the work you?ve put into ZendTo over the years.

------------------------------------------------------
Travis Zimmerman tzimmerman at fsu.edu<mailto:tzimmerman at fsu.edu> 850-645-8030
Linux Enterprise Applications & Systems its-linuxadmins at fsu.edu<mailto:its-linuxadmins at fsu.edu>
Information Technology Services, Florida State University

_______________________________________________
ZendTo mailing list
ZendTo at zend.to<mailto:ZendTo at zend.to>
https://urldefense.proofpoint.com/v2/url?u=http-3A__jul.es_mailman_listinfo_zendto&d=DwICAg&c=HPMtquzZjKY31rtkyGRFnQ&r=TZ3x4Nnv5Pp03uwRWF9UlLOaC296m8a1MGVEkWJljsg&m=iRpUWQEOCA1yDCFd7NOHnIITTURn-cKM4vtBVPbVZnE&s=uVuBYChZLMLqD-gZacK1oq3fmFNUcVEgqE0ehtNg9-M&e=

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

From ssilva at sgvwater.com  Mon Apr 29 21:22:32 2019
From: ssilva at sgvwater.com (Scott Silva)
Date: Mon, 29 Apr 2019 20:22:32 +0000
Subject: [ZendTo] alternate AD attribute
In-Reply-To: <WM!2460a03b90be8084fe408625266b0e2211e16c72163fd4a7bf1d43c86d4e71e26b1a26309bc4ef24dd1b4a9fec66b972c17cb7f94032ca13fe8df9eba00d3bf7!@mx.jul.es>
References: <58299ADB-FC43-42C7-BF6C-5098A8060A51@fsu.edu>
 <WM!34928f50d1e542023efee6bfe83be1c470660949703bffafce8c6f4178edad8b8c7faf56bbb71c28f0ef373d9e32c2a0!@mx.jul.es>
 <WM!671680fd4c4b67ee58fe6c0c02c0e7557f993f374c12d1453af214ee080a3285886c3c6282857e18c984ddfdedbccd9606081dd75191ab927b2789cdb5fdc0ba!@mx.jul.es>
 <5CC746D20200001300134C87@mail.msktd.com>
 <WM!75ec5f5a9aa984abde712e7d6850b4014652a3e648b9baa951b0dbbcff3ed92409e245097be5c393a6bb1aac06099311!@mx.jul.es>
 <WM!2cd598870fe151547e3b0f6e5bf909b72ddc4080987cae39657a5169e5556df955ffba7a1f7c4b6407c0bb751f6bb790c49c5769027285217e0367d5fab09162!@mx.jul.es>
 <C30F3FC2-8E0E-4050-9469-E7D9FAB58F65@fsu.edu>
 <WM!b6ced1c39c94e4c26a2f61301804ef4d00615609f1b09a210d99d84eeb3637ccd668c51ba53c7454fcd82c4207ed5835!@mx.jul.es>
 <WM!2460a03b90be8084fe408625266b0e2211e16c72163fd4a7bf1d43c86d4e71e26b1a26309bc4ef24dd1b4a9fec66b972c17cb7f94032ca13fe8df9eba00d3bf7!@mx.jul.es>
 <54D3F6A07E3F2A4AAD4CBA73922025F42050AB75@FONEXCH01.sgvwc.local>
Message-ID: <WM!80a5fe2f7415bf65f0aef25d2339148cbed7b0cb861d3723eb2b2935e9f304855b64f771f3c41ec8eddf59b12adf863b!@mx.jul.es>

It does sound like someone making rules that doesn?t know how things work to me?
That would eliminate macs onless they have office, it would kill Linux workstations, and cell phones.


From: ZendTo [mailto:zendto-bounces at zend.to] On Behalf Of Travis Zimmerman via ZendTo
Sent: Monday, April 29, 2019 12:03 PM
To: ZendTo Users <zendto at zend.to>
Cc: Travis Zimmerman <TZimmerman at fsu.edu>
Subject: Re: [ZendTo] alternate AD attribute

I?m assuming they plan to use some Exchange only tech for sending e-mail, I would have to ask the Microsoft team here how that will work. This is just what was laid out in an e-mail sent to my department by the university?s CIO, no real specifics given just goals.

------------------------------------------------------
Travis Zimmerman
tzimmerman at fsu.edu<mailto:tzimmerman at fsu.edu>
850-645-8030
Linux Enterprise Applications & Systems
its-linuxadmins at fsu.edu<mailto:its-linuxadmins at fsu.edu>
Information Technology Services, Florida State University


On Apr 29, 2019, at 2:47 PM, Ken Etter via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> wrote:

No SMTP?  How are they going to send email to other domains?
>>> Travis Zimmerman via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> 4/29/2019 2:44 PM >>>
Would it be possible to add a variable to the AD auth config to use an alternate attribute for the username?
Something like:
?authLDAPAltAttr?     =>    ?preferredEmail?,

Our Microsoft sysadmins had to setup a different AD for students on a different domain (my.fsu.edu<http://my.fsu.edu/>) from the one used by faculty and staff (fsu.edu<http://fsu.edu/>). For some reason at the time they had to store the student e-mail address in a different attribute than the standard attribute, in the normal attribute they are storing a student ID number.

Up until now I worked around this problem by using the IMAP authentication, not as nice as AD but it did the job to allow students to authenticate in, receive e-mail from the ZendTo server, and view drop-offs for them in their Inbox.

We got a new CIO at my university about a month ago and it has been decided to shutdown IMAP and SMTP completely, in favor of MAPI with MFA only. I found out that this change was being talked about last week, upper management came to a decision last Friday and plan to go ahead with this change starting next week.

I appreciate all the work you?ve put into ZendTo over the years.

------------------------------------------------------
Travis Zimmerman
tzimmerman at fsu.edu<mailto:tzimmerman at fsu.edu>
850-645-8030
Linux Enterprise Applications & Systems
its-linuxadmins at fsu.edu<mailto:its-linuxadmins at fsu.edu>
Information Technology Services, Florida State University

_______________________________________________
ZendTo mailing list
ZendTo at zend.to<mailto:ZendTo at zend.to>
https://urldefense.proofpoint.com/v2/url?u=http-3A__jul.es_mailman_listinfo_zendto&d=DwICAg&c=HPMtquzZjKY31rtkyGRFnQ&r=TZ3x4Nnv5Pp03uwRWF9UlLOaC296m8a1MGVEkWJljsg&m=iRpUWQEOCA1yDCFd7NOHnIITTURn-cKM4vtBVPbVZnE&s=uVuBYChZLMLqD-gZacK1oq3fmFNUcVEgqE0ehtNg9-M&e=

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

From Jordack at yahoo.com  Mon Apr 29 23:17:43 2019
From: Jordack at yahoo.com (Travis McDugald)
Date: Mon, 29 Apr 2019 18:17:43 -0400
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!30dadf945a9375e86ea36b14e901ad04cd075b79a3fdd9920d71234b945493e2c455756881e40207d6a18c43583745bcd7aee179a1138bd1599f7d1233fb11dc!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <WM!04ac29d9b1cb683f7de0e78e84e4e2f34923d59c81d707d8829575b8c92b00a79e43ddd45ef21721380bef949edd6a9c!@mx.jul.es>
 <68797d56-996b-b3fe-122c-5d076cd94553@Zend.To>
 <WM!79697c98063608f12637d627205225e506bd16c422cf2e658b71dc91c96e4d93d6992b06c09415a55ed033135a0e0804eb61b1e883ecc1b85f1b57981f916e16!@mx.jul.es>
 <5F237D6D-5E93-4097-ACD0-F64A2485F135@yahoo.com>
 <WM!70ecf74f9e7d0b8945733332927203aaee6acd5c28f43499004c3696c297dd37eb1ba48282437d0b6734377ab4e96d6d!@mx.jul.es>
 <WM!a19dcdb9c2fb31a686ce792da4aa12c43d3ba00e35a4a16664a231c772ba25bdf2971934cb3c63b3b06a4fec57930a2506d42cd5112dbe4ad05a20e79c8bf783!@mx.jul.es>
 <E2766566-A872-4994-AE6C-2B8354C2B2A3@pcfreak.de>
 <WM!2259e31bcbec5992430418f002c490bbc3dd01ed4b2c0329743d8fc779d9efef6d0061ecc3c40991a151f8b11ffe7010!@mx.jul.es>
 <ff78c6c1-e9aa-8054-3095-40f684711936@Zend.To>
 <WM!30dadf945a9375e86ea36b14e901ad04cd075b79a3fdd9920d71234b945493e2c455756881e40207d6a18c43583745bcd7aee1
 79a1138bd1599f7d1233fb11dc!@mx.jul.es>
 <618D9028-4D73-44E6-8CDC-38ED37F935A7@yahoo.com>
Message-ID: <WM!152776975ae3f5b5db26dee44b266b256e5a627fffc4fd2c8dbb1ac2a002fd614a27d391eed1b11b9b09b3332bb71131!@mx.jul.es>

I think the original poster and I may have different use cases.

Perhaps present it to the user not as part of the subject.  Perhaps label it as ?Message ID?. I would assume displaying would be a setting pref file.  So this way, 

 If (isset($messageID)) then $subject = [Zendto] . $messageID . $subject; else $subject = [Zendto] . $subject;

 I know that?s not even close to proper code, but I hope you get the gist.
 
For me, the [ZendTo] can stay or be replaced.

I?m guessing anyone else who would use the feature has another ticketing or request system they are using that generates the custom string they need to use.  For me, even the term request ID would work.

My thought behind it is to making merging these mails into another system easier to automate. It would also make it easier to display in email in a conversation view.  Anyone using the feature would have a internal custom name for the custom string.

Then again, long day and I?ll stop rambling. 

Sent from my iPad

> On Apr 29, 2019, at 10:19 AM, Jules Field <Jules at zend.to> wrote:
> 
> Folks,
> 
> I'm having a think about this one.
> 
> The idea of the prefix is pretty simple, basically I would give you the "[ZendTo]" string (as an initial default value) in a "Subject" box in the new drop-off form.
> 
> Whatever you end up putting in there gets used instead of [ZendTo] at the start of the email subject lines.
> 
> However......
> 
> If you request a drop-off, you get to supply the whole Subject line for the email to the person you want to send you their files.
> Ideally, that same Subject line would be used in all notifications etc about that drop-off.
> But they have entered the *whole* Subject line, not just the prefix to it.
> If I use their whole Subject line as a prefix, it's going to look weird.
> 
> So what do I do for the Subject prefix, when it was created as a result of a request which had the entire Subject line supplied?
> I clearly can't ask the person sending the request to supply 2 Subject entries ? both the current whole Subject line *and* the prefix to use ? as that would confuse the hell out of them.
> 
> Any ideas please?
> 
> Cheers,
> Jules.
> 
>> On 21/04/2019 14:29, Mailing Lists via ZendTo wrote:
>> Hi Jules,
>> 
>> yes it would be enough to allow 20 editable characters.
>> 
>> via Smartphone
>> 
>> Am 21.04.2019 um 15:13 schrieb Travis McDugald via ZendTo <zendto at zend.to>:
>> 
>>> While no one has asked for this yet, I do see it?s usefulness.
>>> I do use custom strings in email subjects for some projects as well.  Helps with sorting, searching, and filtering.
>>> 
>>> Side note: great job on everything Jules, thank you.
>>> 
>>> Sent from my iPad
>>> 
>>> On Apr 21, 2019, at 7:40 AM, Jules via ZendTo <zendto at zend.to> wrote:
>>> 
>>>> Peter,
>>>> 
>>>> You effectively just want to allow senders to customise the "[ZENDTO]" subject line tag in each drop-off, correct?
>>>> 
>>>> Does anyone else need to do this too?
>>>> 
>>>> Cheers,
>>>> Jules.
>>>> 
>>>>> On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
>>>>> Hi Jules, hi all. 
>>>>> 
>>>>> I have a strange request from our ZendTo users. They asked if it would be possible to add a custom field when sending a DropOff 
>>>>> that results in a custom text in all ZendTo email concerning this specific DropOff. 
>>>>> 
>>>>> Example current: 
>>>>> 
>>>>> [ZENDTO] One of the recipients has picked up your drop-off! 
>>>>> 
>>>>> Example requested: 
>>>>> 
>>>>> [ZENDTO] CUSTOM_STRING One of the recipients has picked up your drop-off! 
>>>>> 
>>>>> I asked a little bit about the purpose of their request and they told me that project teams sort their email by subject and 
>>>>> consequently keep the project name (CUSTOM_STRING) in every subject of their emails concerning that specific project. 
>>>>> So later they could sort by project name (CUSTOM_STRING) within Outlook to be able to verify when they sent a specific DropOff. 
>>>>> 
>>>>> Question: 
>>>>> Is it possible to implement such a feature? 
>>>>> 
>>>>> I know that I could handcraft it but I don't want to make big changes to the source and always have to keep track of them when upgrading. 
>>>>> 
>>>>> I am currently not on the latest version of ZendTo, so if such a feature is maybe already present in the latest version, feel free 
>>>>> to tell me. 
>>>>> 
>>>>> Thanks in advance. 
>>>>> 
>>>>> Peter 
>>>>> 
>>>>> 
>>>>> _______________________________________________ 
>>>>> ZendTo mailing list 
>>>>> ZendTo at zend.to 
>>>>> http://jul.es/mailman/listinfo/zendto 
>>>> 
>>>> Jules
>>>> 
>>>> -- 
>>>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>>> 
>>>> 'Once is happenstance, twice is coincidence, three times is enemy
>>>>  action.' - Ian Fleming
>>>> 
>>>> 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
>> 
>> 
>> _______________________________________________
>> 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/20190429/ead34295/attachment-0001.html>

From mailinglists at pcfreak.de  Tue Apr 30 06:32:52 2019
From: mailinglists at pcfreak.de (Der PCFreak)
Date: Tue, 30 Apr 2019 07:32:52 +0200
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!30dadf945a9375e86ea36b14e901ad04cd075b79a3fdd9920d71234b945493e2c455756881e40207d6a18c43583745bcd7aee179a1138bd1599f7d1233fb11dc!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <68797d56-996b-b3fe-122c-5d076cd94553@Zend.To>
 <WM!79697c98063608f12637d627205225e506bd16c422cf2e658b71dc91c96e4d93d6992b06c09415a55ed033135a0e0804eb61b1e883ecc1b85f1b57981f916e16!@mx.jul.es>
 <5F237D6D-5E93-4097-ACD0-F64A2485F135@yahoo.com>
 <WM!70ecf74f9e7d0b8945733332927203aaee6acd5c28f43499004c3696c297dd37eb1ba48282437d0b6734377ab4e96d6d!@mx.jul.es>
 <WM!a19dcdb9c2fb31a686ce792da4aa12c43d3ba00e35a4a16664a231c772ba25bdf2971934cb3c63b3b06a4fec57930a2506d42cd5112dbe4ad05a20e79c8bf783!@mx.jul.es>
 <E2766566-A872-4994-AE6C-2B8354C2B2A3@pcfreak.de>
 <WM!2259e31bcbec5992430418f002c490bbc3dd01ed4b2c0329743d8fc779d9efef6d0061ecc3c40991a151f8b11ffe7010!@mx.jul.es>
 <ff78c6c1-e9aa-8054-3095-40f684711936@Zend.To>
 <WM!30dadf945a9375e86ea36b14e901ad04cd075b79a3fdd9920d71234b945493e2c455756881e40207d6a18c43583745bcd7aee179a1138bd1599f7d1233fb11dc!@mx.jul.es>
 <455b6c8e-983f-bcfd-6d4d-f8303bab70e4@pcfreak.de>
Message-ID: <WM!7aa39a44ae1dbc0e19c518412be0533dda4a042e4730b2f1bd2f764bbb931c0c9cb3140fa493cc04241068b105e5cf53!@mx.jul.es>

Hi,

for me it would be enough to have a small (eg. max 20 characters) suffix 
(not prefix) added to the default subject line. In my company people 
like to add the project number to the end of the subject line (or at 
least somewhere) to be able to sort their emails by this number (often 
after years) to reproduce project work-flows and data exchange.

Maybe a suffix would be enough even for others that need it for ticketing?

Regards

Peter

On 29.04.2019 16:19, Jules Field wrote:
> Folks,
>
> I'm having a think about this one.
>
> The idea of the prefix is pretty simple, basically I would give you 
> the "[ZendTo]" string (as an initial default value) in a "Subject" box 
> in the new drop-off form.
>
> Whatever you end up putting in there gets used instead of [ZendTo] at 
> the start of the email subject lines.
>
> However......
>
> If you request a drop-off, you get to supply the whole Subject line 
> for the email to the person you want to send you their files.
> Ideally, that same Subject line would be used in all notifications etc 
> about that drop-off.
> But they have entered the *whole* Subject line, not just the prefix to it.
> If I use their whole Subject line as a prefix, it's going to look weird.
>
> So what do I do for the Subject prefix, when it was created as a 
> result of a request which had the entire Subject line supplied?
> I clearly can't ask the person sending the request to supply 2 Subject 
> entries ? both the current whole Subject line *and* the prefix to use 
> ? as that would confuse the hell out of them.
>
> Any ideas please?
>
> Cheers,
> Jules.
>
> On 21/04/2019 14:29, Mailing Lists via ZendTo wrote:
>> Hi Jules,
>>
>> yes it would be enough to allow 20 editable characters.
>>
>> via Smartphone
>>
>> Am 21.04.2019 um 15:13 schrieb Travis McDugald via ZendTo 
>> <zendto at zend.to <mailto:zendto at zend.to>>:
>>
>>> While no one has asked for this yet, I do see it?s usefulness.
>>> I do use custom strings in email subjects for some projects as well. 
>>> ?Helps with sorting, searching, and filtering.
>>>
>>> Side note: great job on everything Jules, thank you.
>>>
>>> Sent from my iPad
>>>
>>> On Apr 21, 2019, at 7:40 AM, Jules via ZendTo <zendto at zend.to 
>>> <mailto:zendto at zend.to>> wrote:
>>>
>>>> Peter,
>>>>
>>>> You effectively just want to allow senders to customise the 
>>>> "[ZENDTO]" subject line tag in each drop-off, correct?
>>>>
>>>> Does anyone else need to do this too?
>>>>
>>>> Cheers,
>>>> Jules.
>>>>
>>>> On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
>>>>> Hi Jules, hi all.
>>>>>
>>>>> I have a strange request from our ZendTo users. They asked if it 
>>>>> would be possible to add a custom field when sending a DropOff
>>>>> that results in a custom text in all ZendTo email concerning this 
>>>>> specific DropOff.
>>>>>
>>>>> Example current:
>>>>>
>>>>> [ZENDTO] One of the recipients has picked up your drop-off!
>>>>>
>>>>> Example requested:
>>>>>
>>>>> [ZENDTO] CUSTOM_STRING One of the recipients has picked up your 
>>>>> drop-off!
>>>>>
>>>>> I asked a little bit about the purpose of their request and they 
>>>>> told me that project teams sort their email by subject and
>>>>> consequently keep the project name (CUSTOM_STRING) in every 
>>>>> subject of their emails concerning that specific project.
>>>>> So later they could sort by project name (CUSTOM_STRING) within 
>>>>> Outlook to be able to verify when they sent a specific DropOff.
>>>>>
>>>>> Question:
>>>>> Is it possible to implement such a feature?
>>>>>
>>>>> I know that I could handcraft it but I don't want to make big 
>>>>> changes to the source and always have to keep track of them when 
>>>>> upgrading.
>>>>>
>>>>> I am currently not on the latest version of ZendTo, so if such a 
>>>>> feature is maybe already present in the latest version, feel free
>>>>> to tell me.
>>>>>
>>>>> Thanks in advance.
>>>>>
>>>>> Peter
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> ZendTo mailing list
>>>>> ZendTo at zend.to
>>>>> http://jul.es/mailman/listinfo/zendto
>>>>
>>>> Jules
>>>>
>>>> -- 
>>>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>>>
>>>> 'Once is happenstance, twice is coincidence, three times is enemy
>>>>   action.' - Ian Fleming
>>>>
>>>> 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
>> 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/20190430/c2a466c5/attachment.html>

From Jules at Zend.To  Tue Apr 30 09:34:52 2019
From: Jules at Zend.To (Jules Field)
Date: Tue, 30 Apr 2019 09:34:52 +0100
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!66f223a219ffe1a20f3a0b0a994b137c61f28ba5d8fbfb670d1735e97c85b18fdba6d830aa97933f17af652e1e6f0a4e!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <5F237D6D-5E93-4097-ACD0-F64A2485F135@yahoo.com>
 <WM!70ecf74f9e7d0b8945733332927203aaee6acd5c28f43499004c3696c297dd37eb1ba48282437d0b6734377ab4e96d6d!@mx.jul.es>
 <WM!a19dcdb9c2fb31a686ce792da4aa12c43d3ba00e35a4a16664a231c772ba25bdf2971934cb3c63b3b06a4fec57930a2506d42cd5112dbe4ad05a20e79c8bf783!@mx.jul.es>
 <E2766566-A872-4994-AE6C-2B8354C2B2A3@pcfreak.de>
 <WM!2259e31bcbec5992430418f002c490bbc3dd01ed4b2c0329743d8fc779d9efef6d0061ecc3c40991a151f8b11ffe7010!@mx.jul.es>
 <ff78c6c1-e9aa-8054-3095-40f684711936@Zend.To>
 <WM!065345b86971656b47aea8a854e1311b5d60c747358927f81b5294bcfe41e8d4acbab259d3f9a9ce2dc663f68a4fee92e2f366a0185621a2a89ed2aca5874f29!@mx.jul.es>
 <72d61410dcb94e67a16481300a961282@City-Exch-DB1.cbj.local>
 <WM!66f223a219ffe1a20f3a0b0a994b137c61f28ba5d8fbfb670d1735e97c85b18fdba6d830aa97933f17af652e1e6f0a4e!@mx.jul.es>
Message-ID: <19accbbc-b2b1-241d-531d-a717fc8dc15a@Zend.To>

Kevin,

But in the case of a request, as much as possible is pre-filled for the 
customer dropping off files.
All the other Subject lines generated are hard-coded (apart from 
translations).

If you are thinking of either changing the [ZendTo] prefix to some other 
string, or adding something between the [ZendTo] prefix and the rest of 
the string, where and when is that going to be set?

The "new dropoff" form needs to gain an extra "Message ID" (or whatever) 
box so people can put in their magic string.

Are you saying the "send a request" form needs to gain it too?
(And presumably if the answer to that is "yes", the "new dropoff" form 
would pre-fill the "Message ID" value from what was given in the 
request. And if that is the case, should the customer doing the dropoff 
be able to change the "Message ID" value at that point? I would suggest 
not.)

I think we're all thinking about variations on either ticketing systems 
or people with multiple projects, where they need some magic value in 
the Subject line of *every* email message sent by ZendTo so that they 
can all be tracked and filed automatically.

Cheers,
Jules.

On 29/04/2019 17:53, Kevin Miller via ZendTo wrote:
>
> Unless I?m misunderstand the conundrum, I?d say to let the requester 
> enter the subject line, sans prefix, then prepend the system defined 
> prefix at upload generation time.? I.e., if I was requesting a dropoff 
> I?d put in ?My appropriate subject?.? The person that is actually 
> doing the dropoff would see that, and probably won?t think twice about 
> it. Then, when the outgoing upload ?notification is actually complete, 
> Zendto can prepend the system supplied prefix [Zendto] or [Whatever] 
> and send that.? I don?t think folks are in the habit of hand coding 
> prefixes, so it?s unlikely one would end up with dual prefixes.
>
> Maybe there?s coding issues with that that make it difficult? Anyway, 
> my tuppence worth?
>
> ...Kevin
>
> --
>
> Kevin Miller
>
> Network/email Administrator, CBJ MIS Dept.
>
> 155 South Seward Street
>
> Juneau, Alaska 99801
>
> Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 
> 307357
>
> *From:*ZendTo <zendto-bounces at zend.to> *On Behalf Of *Jules Field via 
> ZendTo
> *Sent:* Monday, April 29, 2019 6:19 AM
> *To:* ZendTo Users <zendto at zend.to>
> *Cc:* Jules Field <Jules at Zend.To>
> *Subject:* Re: [ZendTo] [Feature Request custom string in subject per 
> DropOff]
>
> Folks,
>
> I'm having a think about this one.
>
> The idea of the prefix is pretty simple, basically I would give you 
> the "[ZendTo]" string (as an initial default value) in a "Subject" box 
> in the new drop-off form.
>
> Whatever you end up putting in there gets used instead of [ZendTo] at 
> the start of the email subject lines.
>
> However......
>
> If you request a drop-off, you get to supply the whole Subject line 
> for the email to the person you want to send you their files.
> Ideally, that same Subject line would be used in all notifications etc 
> about that drop-off.
> But they have entered the *whole* Subject line, not just the prefix to it.
> If I use their whole Subject line as a prefix, it's going to look weird.
>
> So what do I do for the Subject prefix, when it was created as a 
> result of a request which had the entire Subject line supplied?
> I clearly can't ask the person sending the request to supply 2 Subject 
> entries ? both the current whole Subject line *and* the prefix to use 
> ? as that would confuse the hell out of them.
>
> Any ideas please?
>
> Cheers,
> Jules.
>
> On 21/04/2019 14:29, Mailing Lists via ZendTo wrote:
>
>     Hi Jules,
>
>     yes it would be enough to allow 20 editable characters.
>
>     via Smartphone
>
>
>     Am 21.04.2019 um 15:13 schrieb Travis McDugald via ZendTo
>     <zendto at zend.to <mailto:zendto at zend.to>>:
>
>         While no one has asked for this yet, I do see it?s usefulness.
>
>         I do use custom strings in email subjects for some projects as
>         well. ?Helps with sorting, searching, and filtering.
>
>         Side note: great job on everything Jules, thank you.
>
>         Sent from my iPad
>
>
>         On Apr 21, 2019, at 7:40 AM, Jules via ZendTo <zendto at zend.to
>         <mailto:zendto at zend.to>> wrote:
>
>             Peter,
>
>             You effectively just want to allow senders to customise
>             the "[ZENDTO]" subject line tag in each drop-off, correct?
>
>             Does anyone else need to do this too?
>
>             Cheers,
>             Jules.
>
>             On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
>
>                 Hi Jules, hi all.
>
>                 I have a strange request from our ZendTo users. They
>                 asked if it would be possible to add a custom field
>                 when sending a DropOff
>                 that results in a custom text in all ZendTo email
>                 concerning this specific DropOff.
>
>                 Example current:
>
>                 [ZENDTO] One of the recipients has picked up your
>                 drop-off!
>
>                 Example requested:
>
>                 [ZENDTO] CUSTOM_STRING One of the recipients has
>                 picked up your drop-off!
>
>                 I asked a little bit about the purpose of their
>                 request and they told me that project teams sort their
>                 email by subject and
>                 consequently keep the project name (CUSTOM_STRING) in
>                 every subject of their emails concerning that specific
>                 project.
>                 So later they could sort by project name
>                 (CUSTOM_STRING) within Outlook to be able to verify
>                 when they sent a specific DropOff.
>
>                 Question:
>                 Is it possible to implement such a feature?
>
>                 I know that I could handcraft it but I don't want to
>                 make big changes to the source and always have to keep
>                 track of them when upgrading.
>
>                 I am currently not on the latest version of ZendTo, so
>                 if such a feature is maybe already present in the
>                 latest version, feel free
>                 to tell me.
>
>                 Thanks in advance.
>
>                 Peter
>
>
>                 _______________________________________________
>                 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
>
>             'Once is happenstance, twice is coincidence, three times is enemy
>
>               action.' - Ian Fleming
>
>             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
> 'Find a place inside where there's joy, and the joy will burn out
>   the pain.' - Joseph Campbell
> 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

'Teach a man to reason, and he will think for a lifetime.' - Phil Plait

www.Zend.To
Twitter: @JulesFM

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

From Jules at Zend.To  Tue Apr 30 09:39:37 2019
From: Jules at Zend.To (Jules Field)
Date: Tue, 30 Apr 2019 09:39:37 +0100
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!5b2e6ed2226defbda1cc032ce023bad7b1f7d44279a26ef340bbf22261afa77fd18d89199b416cd979e00d3c7bd1a76bcd1911d083a28097beb9cc49b269a2dad5a6d0c855b35e09e612c7b44d2c3c60!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <5F237D6D-5E93-4097-ACD0-F64A2485F135@yahoo.com>
 <WM!70ecf74f9e7d0b8945733332927203aaee6acd5c28f43499004c3696c297dd37eb1ba48282437d0b6734377ab4e96d6d!@mx.jul.es>
 <WM!a19dcdb9c2fb31a686ce792da4aa12c43d3ba00e35a4a16664a231c772ba25bdf2971934cb3c63b3b06a4fec57930a2506d42cd5112dbe4ad05a20e79c8bf783!@mx.jul.es>
 <E2766566-A872-4994-AE6C-2B8354C2B2A3@pcfreak.de>
 <WM!2259e31bcbec5992430418f002c490bbc3dd01ed4b2c0329743d8fc779d9efef6d0061ecc3c40991a151f8b11ffe7010!@mx.jul.es>
 <ff78c6c1-e9aa-8054-3095-40f684711936@Zend.To>
 <WM!30dadf945a9375e86ea36b14e901ad04cd075b79a3fdd9920d71234b945493e2c455756881e40207d6a18c43583745bcd7aee1
 79a1138bd1599f7d1233fb11dc!@mx.jul.es>
 <618D9028-4D73-44E6-8CDC-38ED37F935A7@yahoo.com>
 <WM!5b2e6ed2226defbda1cc032ce023bad7b1f7d44279a26ef340bbf22261afa77fd18d89199b416cd979e00d3c7bd1a76bcd1911d083a28097beb9cc49b269a2dad5a6d0c855b35e09e612c7b44d2c3c60!@mx.jul.es>
Message-ID: <46738449-c49e-d6f3-39b1-1a4bb2a0060c@Zend.To>

Travis,

Okay, this makes some sense.

The visibility of this whole "Message ID" feature would be on/off 
controlled by preferences.php. I would suggest off by default? Thoughts?

The actual name of the "Message ID" field would be customisable: as you 
say, different organisations will have different names for it, but 
basically it's some form of ticket number or project codename.

If it's set, I insert it between the [ZendTo] tag and the normal email 
subject line.

In the case of making a request for a drop-off, the (internal) user is 
asked for the Subject line of the email to send. Should I also ask for 
the "Message ID" string as part of the request form?

Cheers,
Jules.

On 29/04/2019 23:17, Travis McDugald wrote:
> I think the original poster and I may have different use cases.
>
> Perhaps present it to the user not as part of the subject. ?Perhaps 
> label it as ?Message ID?. I would assume displaying would be a setting 
> pref file. ?So this way,
>
> ?If (isset($messageID)) then $subject = [Zendto] . $messageID . 
> $subject; else $subject = [Zendto] . $subject;
>
> ?I know that?s not even close to proper code, but I hope you get the gist.
> For me, the [ZendTo] can stay or be replaced.
>
> I?m guessing anyone else who would use the feature has another 
> ticketing or request system they are using that generates the custom 
> string they need to use. ?For me, even the term request ID would work.
>
> My thought behind it is to making merging these mails into another 
> system easier to automate. It would also make it easier to display in 
> email in a conversation view. ?Anyone using the feature would have a 
> internal custom name for the custom string.
>
> Then again, long day and I?ll stop rambling.
>
> Sent from my iPad
>
> On Apr 29, 2019, at 10:19 AM, Jules Field <Jules at zend.to 
> <mailto:Jules at zend.to>> wrote:
>
>> Folks,
>>
>> I'm having a think about this one.
>>
>> The idea of the prefix is pretty simple, basically I would give you 
>> the "[ZendTo]" string (as an initial default value) in a "Subject" 
>> box in the new drop-off form.
>>
>> Whatever you end up putting in there gets used instead of [ZendTo] at 
>> the start of the email subject lines.
>>
>> However......
>>
>> If you request a drop-off, you get to supply the whole Subject line 
>> for the email to the person you want to send you their files.
>> Ideally, that same Subject line would be used in all notifications 
>> etc about that drop-off.
>> But they have entered the *whole* Subject line, not just the prefix 
>> to it.
>> If I use their whole Subject line as a prefix, it's going to look weird.
>>
>> So what do I do for the Subject prefix, when it was created as a 
>> result of a request which had the entire Subject line supplied?
>> I clearly can't ask the person sending the request to supply 2 
>> Subject entries ? both the current whole Subject line *and* the 
>> prefix to use ? as that would confuse the hell out of them.
>>
>> Any ideas please?
>>
>> Cheers,
>> Jules.
>>
>> On 21/04/2019 14:29, Mailing Lists via ZendTo wrote:
>>> Hi Jules,
>>>
>>> yes it would be enough to allow 20 editable characters.
>>>
>>> via Smartphone
>>>
>>> Am 21.04.2019 um 15:13 schrieb Travis McDugald via ZendTo 
>>> <zendto at zend.to <mailto:zendto at zend.to>>:
>>>
>>>> While no one has asked for this yet, I do see it?s usefulness.
>>>> I do use custom strings in email subjects for some projects as 
>>>> well. ?Helps with sorting, searching, and filtering.
>>>>
>>>> Side note: great job on everything Jules, thank you.
>>>>
>>>> Sent from my iPad
>>>>
>>>> On Apr 21, 2019, at 7:40 AM, Jules via ZendTo <zendto at zend.to 
>>>> <mailto:zendto at zend.to>> wrote:
>>>>
>>>>> Peter,
>>>>>
>>>>> You effectively just want to allow senders to customise the 
>>>>> "[ZENDTO]" subject line tag in each drop-off, correct?
>>>>>
>>>>> Does anyone else need to do this too?
>>>>>
>>>>> Cheers,
>>>>> Jules.
>>>>>
>>>>> On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
>>>>>> Hi Jules, hi all.
>>>>>>
>>>>>> I have a strange request from our ZendTo users. They asked if it 
>>>>>> would be possible to add a custom field when sending a DropOff
>>>>>> that results in a custom text in all ZendTo email concerning this 
>>>>>> specific DropOff.
>>>>>>
>>>>>> Example current:
>>>>>>
>>>>>> [ZENDTO] One of the recipients has picked up your drop-off!
>>>>>>
>>>>>> Example requested:
>>>>>>
>>>>>> [ZENDTO] CUSTOM_STRING One of the recipients has picked up your 
>>>>>> drop-off!
>>>>>>
>>>>>> I asked a little bit about the purpose of their request and they 
>>>>>> told me that project teams sort their email by subject and
>>>>>> consequently keep the project name (CUSTOM_STRING) in every 
>>>>>> subject of their emails concerning that specific project.
>>>>>> So later they could sort by project name (CUSTOM_STRING) within 
>>>>>> Outlook to be able to verify when they sent a specific DropOff.
>>>>>>
>>>>>> Question:
>>>>>> Is it possible to implement such a feature?
>>>>>>
>>>>>> I know that I could handcraft it but I don't want to make big 
>>>>>> changes to the source and always have to keep track of them when 
>>>>>> upgrading.
>>>>>>
>>>>>> I am currently not on the latest version of ZendTo, so if such a 
>>>>>> feature is maybe already present in the latest version, feel free
>>>>>> to tell me.
>>>>>>
>>>>>> Thanks in advance.
>>>>>>
>>>>>> Peter
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> ZendTo mailing list
>>>>>> ZendTo at zend.to
>>>>>> http://jul.es/mailman/listinfo/zendto
>>>>>
>>>>> Jules
>>>>>
>>>>> -- 
>>>>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>>>>
>>>>> 'Once is happenstance, twice is coincidence, three times is enemy
>>>>>   action.' - Ian Fleming
>>>>>
>>>>> 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
>>> 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

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

The current UK shipping forecast:
German Bight: Northwest 3 or 4, occasionally 5 later. Smooth or slight,
becoming slight or moderate later. Fog patches. Moderate or good, occasionally
very poor.

www.Zend.To
Twitter: @JulesFM

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

From Jules at Zend.To  Tue Apr 30 09:42:01 2019
From: Jules at Zend.To (Jules Field)
Date: Tue, 30 Apr 2019 09:42:01 +0100
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!7aa39a44ae1dbc0e19c518412be0533dda4a042e4730b2f1bd2f764bbb931c0c9cb3140fa493cc04241068b105e5cf53!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <5F237D6D-5E93-4097-ACD0-F64A2485F135@yahoo.com>
 <WM!70ecf74f9e7d0b8945733332927203aaee6acd5c28f43499004c3696c297dd37eb1ba48282437d0b6734377ab4e96d6d!@mx.jul.es>
 <WM!a19dcdb9c2fb31a686ce792da4aa12c43d3ba00e35a4a16664a231c772ba25bdf2971934cb3c63b3b06a4fec57930a2506d42cd5112dbe4ad05a20e79c8bf783!@mx.jul.es>
 <E2766566-A872-4994-AE6C-2B8354C2B2A3@pcfreak.de>
 <WM!2259e31bcbec5992430418f002c490bbc3dd01ed4b2c0329743d8fc779d9efef6d0061ecc3c40991a151f8b11ffe7010!@mx.jul.es>
 <ff78c6c1-e9aa-8054-3095-40f684711936@Zend.To>
 <WM!30dadf945a9375e86ea36b14e901ad04cd075b79a3fdd9920d71234b945493e2c455756881e40207d6a18c43583745bcd7aee179a1138bd1599f7d1233fb11dc!@mx.jul.es>
 <455b6c8e-983f-bcfd-6d4d-f8303bab70e4@pcfreak.de>
 <WM!7aa39a44ae1dbc0e19c518412be0533dda4a042e4730b2f1bd2f764bbb931c0c9cb3140fa493cc04241068b105e5cf53!@mx.jul.es>
Message-ID: <8c32024f-7ee4-cf47-7a3f-b078fce79c5b@Zend.To>

Peter,

I'm tempted to go with a prefix rather than a suffix.
My guess would be that users are more used to ignoring leading prefixes 
on Subject lines, as that is where most ticketing systems put them.
But I might be wrong!

I'm just not sure it warrants yet another bit of extra complexity and 
extra configuration to make its position selectable.

Would a prefix do? Just after the [ZendTo] prefix?

Cheers,
Jules.

On 30/04/2019 06:32, Der PCFreak via ZendTo wrote:
>
> Hi,
>
> for me it would be enough to have a small (eg. max 20 characters) 
> suffix (not prefix) added to the default subject line. In my company 
> people like to add the project number to the end of the subject line 
> (or at least somewhere) to be able to sort their emails by this number 
> (often after years) to reproduce project work-flows and data exchange.
>
> Maybe a suffix would be enough even for others that need it for ticketing?
>
> Regards
>
> Peter
>
> On 29.04.2019 16:19, Jules Field wrote:
>> Folks,
>>
>> I'm having a think about this one.
>>
>> The idea of the prefix is pretty simple, basically I would give you 
>> the "[ZendTo]" string (as an initial default value) in a "Subject" 
>> box in the new drop-off form.
>>
>> Whatever you end up putting in there gets used instead of [ZendTo] at 
>> the start of the email subject lines.
>>
>> However......
>>
>> If you request a drop-off, you get to supply the whole Subject line 
>> for the email to the person you want to send you their files.
>> Ideally, that same Subject line would be used in all notifications 
>> etc about that drop-off.
>> But they have entered the *whole* Subject line, not just the prefix 
>> to it.
>> If I use their whole Subject line as a prefix, it's going to look weird.
>>
>> So what do I do for the Subject prefix, when it was created as a 
>> result of a request which had the entire Subject line supplied?
>> I clearly can't ask the person sending the request to supply 2 
>> Subject entries ? both the current whole Subject line *and* the 
>> prefix to use ? as that would confuse the hell out of them.
>>
>> Any ideas please?
>>
>> Cheers,
>> Jules.
>>
>> On 21/04/2019 14:29, Mailing Lists via ZendTo wrote:
>>> Hi Jules,
>>>
>>> yes it would be enough to allow 20 editable characters.
>>>
>>> via Smartphone
>>>
>>> Am 21.04.2019 um 15:13 schrieb Travis McDugald via ZendTo 
>>> <zendto at zend.to <mailto:zendto at zend.to>>:
>>>
>>>> While no one has asked for this yet, I do see it?s usefulness.
>>>> I do use custom strings in email subjects for some projects as 
>>>> well. ?Helps with sorting, searching, and filtering.
>>>>
>>>> Side note: great job on everything Jules, thank you.
>>>>
>>>> Sent from my iPad
>>>>
>>>> On Apr 21, 2019, at 7:40 AM, Jules via ZendTo <zendto at zend.to 
>>>> <mailto:zendto at zend.to>> wrote:
>>>>
>>>>> Peter,
>>>>>
>>>>> You effectively just want to allow senders to customise the 
>>>>> "[ZENDTO]" subject line tag in each drop-off, correct?
>>>>>
>>>>> Does anyone else need to do this too?
>>>>>
>>>>> Cheers,
>>>>> Jules.
>>>>>
>>>>> On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
>>>>>> Hi Jules, hi all.
>>>>>>
>>>>>> I have a strange request from our ZendTo users. They asked if it 
>>>>>> would be possible to add a custom field when sending a DropOff
>>>>>> that results in a custom text in all ZendTo email concerning this 
>>>>>> specific DropOff.
>>>>>>
>>>>>> Example current:
>>>>>>
>>>>>> [ZENDTO] One of the recipients has picked up your drop-off!
>>>>>>
>>>>>> Example requested:
>>>>>>
>>>>>> [ZENDTO] CUSTOM_STRING One of the recipients has picked up your 
>>>>>> drop-off!
>>>>>>
>>>>>> I asked a little bit about the purpose of their request and they 
>>>>>> told me that project teams sort their email by subject and
>>>>>> consequently keep the project name (CUSTOM_STRING) in every 
>>>>>> subject of their emails concerning that specific project.
>>>>>> So later they could sort by project name (CUSTOM_STRING) within 
>>>>>> Outlook to be able to verify when they sent a specific DropOff.
>>>>>>
>>>>>> Question:
>>>>>> Is it possible to implement such a feature?
>>>>>>
>>>>>> I know that I could handcraft it but I don't want to make big 
>>>>>> changes to the source and always have to keep track of them when 
>>>>>> upgrading.
>>>>>>
>>>>>> I am currently not on the latest version of ZendTo, so if such a 
>>>>>> feature is maybe already present in the latest version, feel free
>>>>>> to tell me.
>>>>>>
>>>>>> Thanks in advance.
>>>>>>
>>>>>> Peter
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> ZendTo mailing list
>>>>>> ZendTo at zend.to
>>>>>> http://jul.es/mailman/listinfo/zendto
>>>>>
>>>>> Jules
>>>>>
>>>>> -- 
>>>>> Julian Field MEng CEng CITP MBCS MIEEE MACM
>>>>>
>>>>> 'Once is happenstance, twice is coincidence, three times is enemy
>>>>>   action.' - Ian Fleming
>>>>>
>>>>> 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
>>> 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
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'Give a man a fish, and you feed him for a day.
  Teach a man to fish, and he'll sit in a boat and drink beer all day.'
    - Anon

www.Zend.To
Twitter: @JulesFM

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

From Jules at Zend.To  Tue Apr 30 09:46:28 2019
From: Jules at Zend.To (Jules Field)
Date: Tue, 30 Apr 2019 09:46:28 +0100
Subject: [ZendTo] alternate AD attribute
In-Reply-To: <WM!34928f50d1e542023efee6bfe83be1c470660949703bffafce8c6f4178edad8b8c7faf56bbb71c28f0ef373d9e32c2a0!@mx.jul.es>
References: <58299ADB-FC43-42C7-BF6C-5098A8060A51@fsu.edu>
 <WM!34928f50d1e542023efee6bfe83be1c470660949703bffafce8c6f4178edad8b8c7faf56bbb71c28f0ef373d9e32c2a0!@mx.jul.es>
Message-ID: <c1814b81-4f77-2873-83c0-8bc0d2ea82fc@Zend.To>

Travis,

Do you mean an alternate attribute for the username, or an alternate 
attribute from which to read the user's email address?
I'm rather assuming the latter, but may be wrong...

Currently it reads the user's email address from the "mail" attribute in 
AD; is it the string "mail" that you want to be able to change for a 
particular AD forest?

Cheers,
Jules.

On 29/04/2019 19:44, Travis Zimmerman via ZendTo wrote:
> Would it be possible to add a variable to the AD auth config to use an 
> alternate attribute for the username?
> Something like:?authLDAPAltAttr? ? ? => ? ??preferredEmail?,
>
> Our Microsoft sysadmins had to setup a different AD for students on a 
> different domain (my.fsu.edu <http://my.fsu.edu>) from the one used by 
> faculty and staff (fsu.edu <http://fsu.edu>). For some reason at the 
> time they had to store the student e-mail address in a different 
> attribute than the standard attribute, in the normal attribute they 
> are storing a student ID number.
>
> Up until now I worked around this problem by using the IMAP 
> authentication, not as nice as AD but it did the job to allow students 
> to authenticate in, receive e-mail from the ZendTo server, and view 
> drop-offs for them in their Inbox.
>
> We got a new CIO at my university about a month ago and it has been 
> decided to shutdown IMAP and SMTP completely, in favor of MAPI with 
> MFA only. I found out that this change was being talked about last 
> week, upper management came to a decision last Friday and plan to go 
> ahead with this change starting next week.
>
> I appreciate all the work you?ve put into ZendTo over the years.
>
> ------------------------------------------------------
> Travis Zimmermantzimmerman at fsu.edu <mailto:tzimmerman at fsu.edu>850-645-8030
> Linux Enterprise Applications & Systemsits-linuxadmins at fsu.edu 
> <mailto:its-linuxadmins at fsu.edu>
> Information Technology Services, Florida State University
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'What happened in the past that was painful, has a great deal to
  do with what we are today.' - William Glasser

www.Zend.To
Twitter: @JulesFM

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

From mailinglists at pcfreak.de  Tue Apr 30 11:40:40 2019
From: mailinglists at pcfreak.de (Der PCFreak)
Date: Tue, 30 Apr 2019 12:40:40 +0200
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!3b8250c48dc65a79f4d93ac6af4248f1a60798d6a4029a3a2da9b91259299fd13dde7cc9f43bb97f2ca931775c18a217d738f8794b61b811a8c80a1c82d0fa5a!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <WM!a19dcdb9c2fb31a686ce792da4aa12c43d3ba00e35a4a16664a231c772ba25bdf2971934cb3c63b3b06a4fec57930a2506d42cd5112dbe4ad05a20e79c8bf783!@mx.jul.es>
 <E2766566-A872-4994-AE6C-2B8354C2B2A3@pcfreak.de>
 <WM!2259e31bcbec5992430418f002c490bbc3dd01ed4b2c0329743d8fc779d9efef6d0061ecc3c40991a151f8b11ffe7010!@mx.jul.es>
 <ff78c6c1-e9aa-8054-3095-40f684711936@Zend.To>
 <WM!30dadf945a9375e86ea36b14e901ad04cd075b79a3fdd9920d71234b945493e2c455756881e40207d6a18c43583745bcd7aee179a1138bd1599f7d1233fb11dc!@mx.jul.es>
 <455b6c8e-983f-bcfd-6d4d-f8303bab70e4@pcfreak.de>
 <WM!7aa39a44ae1dbc0e19c518412be0533dda4a042e4730b2f1bd2f764bbb931c0c9cb3140fa493cc04241068b105e5cf53!@mx.jul.es>
 <8c32024f-7ee4-cf47-7a3f-b078fce79c5b@Zend.To>
 <WM!3b8250c48dc65a79f4d93ac6af4248f1a60798d6a4029a3a2da9b91259299fd13dde7cc9f43bb97f2ca931775c18a217d738f8794b61b811a8c80a1c82d0fa5a!@mx.jul.es>
 <42d9ed3b-ac0d-9c0a-aa6a-c3bc7b5461bd@pcfreak.de>
Message-ID: <WM!f90b275523e4b1d3dae40d6aae08da2ac62d9e029e2427d3951400e6321aabd52996553214869bf86eaa2fc98633d5cd!@mx.jul.es>

Hi Jules,


>
> Would a prefix do? Just after the [ZendTo] prefix?
>

Yeah that would be good enough for me! - Thanks.

Regards

Peter



From Guy.Bertrand at exelaonline.com  Tue Apr 30 23:11:28 2019
From: Guy.Bertrand at exelaonline.com (Guy Bertrand)
Date: Tue, 30 Apr 2019 22:11:28 +0000
Subject: [ZendTo] email vs username REGEX
References: <43eba1089e8a41f19fa988953ca2e060@exelaonline.com>
Message-ID: <WM!e4a54f5b514a0a863944fc9a2d8fa27928e4c94a4b666970333a29ab3dc9eb3f52f12c251c0b6a8ccb6c97f458245678!@mx.jul.es>

Hi all,

I'm using the AD authenticator.  Users are login in using their email addresses, which are checked against our AD servers.  All is good.

Almost...I have one user who has an apostrophe in his email/account name, and cannot login.

I noticed that in the preferences.php file, the REGEX for username and email address do not match.  I've looked at the code, and I was trying to find (unsucessfully) if there is some type of filtering or conversion being done, and the actual lookup against AD uses a modifed usernameRegexp instead of the raw username as the user typed in the login screen.  The usernameRegexp does not seem to allow the apostrophe.

I'm still looking, but if anybody has a suggestion or an explanation why the username cannot use an apostrophe, I'd appreciate it.  Or do I simply change the username regex to allow for the apostrophe?

Regards,

Guy

// Regular expression defining a valid username for the Login page.
// Usually no need to change this.
'usernameRegexp'    => '/^([a-zA-Z0-9][a-zA-Z0-9\_\.\-\@\\\]*)$/i',

// regular expression defining a valid email address for anyone.
// Usually no need to change this.
// Must look like /^(user)\@(domain)$/
'validEmailRegexp' => '/^([a-zA-Z0-9][a-zA-Z0-9\.\_\-\+\&\']*)\@([a-zA-Z0-9][a-zA-Z0-9\_\-\.]+)$/i',

________________________________
Please consider the environment before printing or forwarding this email. If you do print this email, please recycle the paper.

This email message may contain confidential, proprietary and/or privileged information. It is intended only for the use of the intended recipient(s). If you have received it in error, please immediately advise the sender by reply email and then delete this email message. Any disclosure, copying, distribution or use of the information contained in this email message to or by anyone other than the intended recipient is strictly prohibited. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Exela Technologies, Inc. or its subsidiaries.

This email does not constitute an agreement to conduct transactions by electronic means and does not create any legally binding contract or enforceable obligation against Exela in the absence of a fully signed written agreement.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190430/57e4e79d/attachment.html>

From kevin.miller at juneau.org  Tue Apr 30 23:42:07 2019
From: kevin.miller at juneau.org (Kevin Miller)
Date: Tue, 30 Apr 2019 22:42:07 +0000
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!91306e4c1a677138e683775b2c685f984b3d5140822b033a3a0d230b027e80c6fdebc95ad088b8f626253f15f41761e06b434fb19755f81e0b6ece93a423583a!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <5F237D6D-5E93-4097-ACD0-F64A2485F135@yahoo.com>
 <WM!70ecf74f9e7d0b8945733332927203aaee6acd5c28f43499004c3696c297dd37eb1ba48282437d0b6734377ab4e96d6d!@mx.jul.es>
 <WM!a19dcdb9c2fb31a686ce792da4aa12c43d3ba00e35a4a16664a231c772ba25bdf2971934cb3c63b3b06a4fec57930a2506d42cd5112dbe4ad05a20e79c8bf783!@mx.jul.es>
 <E2766566-A872-4994-AE6C-2B8354C2B2A3@pcfreak.de>
 <WM!2259e31bcbec5992430418f002c490bbc3dd01ed4b2c0329743d8fc779d9efef6d0061ecc3c40991a151f8b11ffe7010!@mx.jul.es>
 <ff78c6c1-e9aa-8054-3095-40f684711936@Zend.To>
 <WM!065345b86971656b47aea8a854e1311b5d60c747358927f81b5294bcfe41e8d4acbab259d3f9a9ce2dc663f68a4fee92e2f366a0185621a2a89ed2aca5874f29!@mx.jul.es>
 <72d61410dcb94e67a16481300a961282@City-Exch-DB1.cbj.local>
 <WM!66f223a219ffe1a20f3a0b0a994b137c61f28ba5d8fbfb670d1735e97c85b18fdba6d830aa97933f17af652e1e6f0a4e!@mx.jul.es>
 <19accbbc-b2b1-241d-531d-a717fc8dc15a@Zend.To>
 <WM!91306e4c1a677138e683775b2c685f984b3d5140822b033a3a0d230b027e80c6fdebc95ad088b8f626253f15f41761e06b434fb19755f81e0b6ece93a423583a!@mx.jul.es>
 <736600cebd8d4738999450bcac9783c1@City-Exch-DB1.cbj.local>
Message-ID: <WM!52928295614ebd317f048ce5a0d91c3c1461701a063f04052582261f0eb319560831349c5b1108f1aab7722838d07060!@mx.jul.es>

I was thinking of something sort of along the lines of what Travis McDugald proposed:
  If (isset($messageID)) then $subject = [Zendto] . $messageID . $subject; else $subject = [Zendto] . $subject;
although rather than an additional messageID I was envisioning just changing the prefix.

I.e. I was thinking that [Zendto] would be a variable set in preferneces.php which could be customized.  Something like:
?Zendto_prefix?      => ?[Zendto]?,
which folks could simply change to what they wanted or leave it as the default.  I didn?t really explain it very clearly.

We?re probably the outlier, but the powers that be upstream of me decided we?d call our system ?fileshare? rather than Zendto.  So in my case I?d change the prefix itself if such was available.  I can see the use case for what Travis, et. al. are proposing as well?

...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357

From: ZendTo <zendto-bounces at zend.to> On Behalf Of Jules Field via ZendTo
Sent: Tuesday, April 30, 2019 12:35 AM
To: ZendTo Users <zendto at zend.to>
Cc: Jules Field <Jules at Zend.To>; Kevin Miller <kevin.miller at juneau.org>
Subject: Re: [ZendTo] [Feature Request custom string in subject per DropOff]

Kevin,

But in the case of a request, as much as possible is pre-filled for the customer dropping off files.
All the other Subject lines generated are hard-coded (apart from translations).

If you are thinking of either changing the [ZendTo] prefix to some other string, or adding something between the [ZendTo] prefix and the rest of the string, where and when is that going to be set?

The "new dropoff" form needs to gain an extra "Message ID" (or whatever) box so people can put in their magic string.

Are you saying the "send a request" form needs to gain it too?
(And presumably if the answer to that is "yes", the "new dropoff" form would pre-fill the "Message ID" value from what was given in the request. And if that is the case, should the customer doing the dropoff be able to change the "Message ID" value at that point? I would suggest not.)

I think we're all thinking about variations on either ticketing systems or people with multiple projects, where they need some magic value in the Subject line of *every* email message sent by ZendTo so that they can all be tracked and filed automatically.

Cheers,
Jules.
On 29/04/2019 17:53, Kevin Miller via ZendTo wrote:
Unless I?m misunderstand the conundrum, I?d say to let the requester enter the subject line, sans prefix, then prepend the system defined prefix at upload generation time.  I.e., if I was requesting a dropoff I?d put in ?My appropriate subject?.  The person that is actually doing the dropoff would see that, and probably won?t think twice about it.  Then, when the outgoing upload  notification is actually complete, Zendto can prepend the system supplied prefix [Zendto] or [Whatever] and send that.  I don?t think folks are in the habit of hand coding prefixes, so it?s unlikely one would end up with dual prefixes.

Maybe there?s coding issues with that that make it difficult?  Anyway, my tuppence worth?

...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357

From: ZendTo <zendto-bounces at zend.to><mailto:zendto-bounces at zend.to> On Behalf Of Jules Field via ZendTo
Sent: Monday, April 29, 2019 6:19 AM
To: ZendTo Users <zendto at zend.to><mailto:zendto at zend.to>
Cc: Jules Field <Jules at Zend.To><mailto:Jules at Zend.To>
Subject: Re: [ZendTo] [Feature Request custom string in subject per DropOff]

Folks,

I'm having a think about this one.

The idea of the prefix is pretty simple, basically I would give you the "[ZendTo]" string (as an initial default value) in a "Subject" box in the new drop-off form.

Whatever you end up putting in there gets used instead of [ZendTo] at the start of the email subject lines.

However......

If you request a drop-off, you get to supply the whole Subject line for the email to the person you want to send you their files.
Ideally, that same Subject line would be used in all notifications etc about that drop-off.
But they have entered the *whole* Subject line, not just the prefix to it.
If I use their whole Subject line as a prefix, it's going to look weird.

So what do I do for the Subject prefix, when it was created as a result of a request which had the entire Subject line supplied?
I clearly can't ask the person sending the request to supply 2 Subject entries ? both the current whole Subject line *and* the prefix to use ? as that would confuse the hell out of them.

Any ideas please?

Cheers,
Jules.
On 21/04/2019 14:29, Mailing Lists via ZendTo wrote:
Hi Jules,

yes it would be enough to allow 20 editable characters.
via Smartphone

Am 21.04.2019 um 15:13 schrieb Travis McDugald via ZendTo <zendto at zend.to<mailto:zendto at zend.to>>:
While no one has asked for this yet, I do see it?s usefulness.
I do use custom strings in email subjects for some projects as well.  Helps with sorting, searching, and filtering.

Side note: great job on everything Jules, thank you.

Sent from my iPad

On Apr 21, 2019, at 7:40 AM, Jules via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> wrote:
Peter,

You effectively just want to allow senders to customise the "[ZENDTO]" subject line tag in each drop-off, correct?

Does anyone else need to do this too?

Cheers,
Jules.
On 21/02/2019 2:21 pm, Der PCFreak via ZendTo wrote:
Hi Jules, hi all.

I have a strange request from our ZendTo users. They asked if it would be possible to add a custom field when sending a DropOff
that results in a custom text in all ZendTo email concerning this specific DropOff.

Example current:

[ZENDTO] One of the recipients has picked up your drop-off!

Example requested:

[ZENDTO] CUSTOM_STRING One of the recipients has picked up your drop-off!

I asked a little bit about the purpose of their request and they told me that project teams sort their email by subject and
consequently keep the project name (CUSTOM_STRING) in every subject of their emails concerning that specific project.
So later they could sort by project name (CUSTOM_STRING) within Outlook to be able to verify when they sent a specific DropOff.

Question:
Is it possible to implement such a feature?

I know that I could handcraft it but I don't want to make big changes to the source and always have to keep track of them when upgrading.

I am currently not on the latest version of ZendTo, so if such a feature is maybe already present in the latest version, feel free
to tell me.

Thanks in advance.

Peter


_______________________________________________
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



'Once is happenstance, twice is coincidence, three times is enemy

 action.' - Ian Fleming



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



'Find a place inside where there's joy, and the joy will burn out

 the pain.' - Joseph Campbell



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



Jules



--

Julian Field MEng CEng CITP MBCS MIEEE MACM



'Teach a man to reason, and he will think for a lifetime.' - Phil Plait



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

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