From greg.clarke at waikato.ac.nz  Wed May  1 03:03:37 2019
From: greg.clarke at waikato.ac.nz (Greg Clarke)
Date: Wed, 1 May 2019 14:03:37 +1200
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!75f7c232fba354b48a23de381ff2f4ebe23c059ff904e747d9648711cbb452a1b2d89762352ff812e8fffff2bac3238edb00b5def4c5973ebbd296a4343b04cf!@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>
 <736600cebd8d4738999450bcac9783c1@City-Exch-DB1.cbj.local>
 <WM!52928295614ebd317f048ce5a0d91c3c1461701a063f04052582261f0eb319560831349c5b1108f1aab7722838d07060!@mx.jul.es>
 <WM!91306e4c1a677138e683775b2c685f984b3d5140822b033a3a0d230b027e80c6fdebc95ad088b8f626253f15f41761e06b434fb19755f81e0b6ece93a423583a!@mx.jul.es>
 <WM!75f7c232fba354b48a23de381ff2f4ebe23c059ff904e747d9648711cbb452a1b2d89762352ff812e8fffff2bac3238edb00b5def4c5973ebbd296a4343b04cf!@mx.jul.es>
 <CAHONktPz6pwxe9WZj0ccA7cdMUSDHJgyBG6jixorDyeF3dqv=Q@mail.gmail.com>
Message-ID: <WM!6583779667038f1b9fa304b5b691e3d184198b2a4b77efa25f2ca4ab9534b965277e3f2ceef1647c631218d038c25080!@mx.jul.es>

Hi there

On Wed, 1 May 2019 at 11:24, Kevin Miller via ZendTo <zendto at zend.to> wrote:

>
>
> 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?
>

The subject prefix is a variable defined in zendto.conf. You can set it:

EmailSubjectTag = "[fileshare] "



Greg


Greg Clarke
SysAdmin, Systems, ITS
The University of Waikato
New Zealand
http://www.waikato.ac.nz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190501/9927f2f0/attachment.html>

From Jules at Zend.To  Wed May  1 10:00:54 2019
From: Jules at Zend.To (Jules Field)
Date: Wed, 1 May 2019 10:00:54 +0100
Subject: [ZendTo] email vs username REGEX
In-Reply-To: <WM!e4a54f5b514a0a863944fc9a2d8fa27928e4c94a4b666970333a29ab3dc9eb3f52f12c251c0b6a8ccb6c97f458245678!@mx.jul.es>
References: <43eba1089e8a41f19fa988953ca2e060@exelaonline.com>
 <WM!e4a54f5b514a0a863944fc9a2d8fa27928e4c94a4b666970333a29ab3dc9eb3f52f12c251c0b6a8ccb6c97f458245678!@mx.jul.es>
Message-ID: <7e2f985f-88d2-cda8-29d1-6ca5ac76b8e7@Zend.To>

Guy,

Most sites have users login using just their username rather than email 
address.
So my default supplied regex for the username is more restrictive than 
the one for the email address, as you want to keep it as tight as you can.

If you want to allow an email address for the username, then the 
simplest solution is to just copy the regex from 'validEmailRegexp' into 
the value for 'usernameRegexp' in preferences.php.

That's one of the reasons I have those 2 specified in a config file 
rather than hard-wired. :-)

Cheers,
Jules.

On 30/04/2019 23:11, Guy Bertrand via ZendTo wrote:
>
> 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.
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'A committee is a group of the unwilling, chosen from the unfit,
  to do the unnecessary.' - Anon

www.Zend.To
Twitter: @JulesFM

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

From Jules at Zend.To  Wed May  1 10:03:44 2019
From: Jules at Zend.To (Jules Field)
Date: Wed, 1 May 2019 10:03:44 +0100
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!52928295614ebd317f048ce5a0d91c3c1461701a063f04052582261f0eb319560831349c5b1108f1aab7722838d07060!@mx.jul.es>
References: <aead44e4-5d09-9840-05a3-40bd6e0232b6@pcfreak.de>
 <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>
 <WM!52928295614ebd317f048ce5a0d91c3c1461701a063f04052582261f0eb319560831349c5b1108f1aab7722838d07060!@mx.jul.es>
Message-ID: <a427bcc8-c46b-245e-4da7-ed726c099244@Zend.To>



On 30/04/2019 23:42, Kevin Miller via ZendTo wrote:
>
> 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 am wary of allowing things like ticket numbers in the [] prefix, as I 
bet some lousy ticketing systems out there will only spot the ticket 
number if it has whitespace after it and not some bracket or other 
punctuation.

> 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?
>
Greg has already answered that one for me. :-)

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
>
> *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
>
> _______________________________________________
> 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/20190501/4b2da351/attachment-0001.html>

From kevin.miller at juneau.org  Wed May  1 17:31:11 2019
From: kevin.miller at juneau.org (Kevin Miller)
Date: Wed, 1 May 2019 16:31:11 +0000
Subject: [ZendTo] [Feature Request custom string in subject per DropOff]
In-Reply-To: <WM!7af04a35b81d3cc6e455bfeca085568866d72c66305136f2844dc9a7ba7d96dea849ec04718cdd7585cd88c2ca84b21d61471ac38d653bd779cc59cda529ef78!@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>
 <736600cebd8d4738999450bcac9783c1@City-Exch-DB1.cbj.local>
 <WM!52928295614ebd317f048ce5a0d91c3c1461701a063f04052582261f0eb319560831349c5b1108f1aab7722838d07060!@mx.jul.es>
 <WM!91306e4c1a677138e683775b2c685f984b3d5140822b033a3a0d230b027e80c6fdebc95ad088b8f626253f15f41761e06b434fb19755f81e0b6ece93a423583a!@mx.jul.es>
 <WM!75f7c232fba354b48a23de381ff2f4ebe23c059ff904e747d9648711cbb452a1b2d89762352ff812e8fffff2bac3238edb00b5def4c5973ebbd296a4343b04cf!@mx.jul.es>
 <CAHONktPz6pwxe9WZj0ccA7cdMUSDHJgyBG6jixorDyeF3dqv=Q@mail.gmail.com>
 <WM!6583779667038f1b9fa304b5b691e3d184198b2a4b77efa25f2ca4ab9534b965277e3f2ceef1647c631218d038c25080!@mx.jul.es>
 <WM!7af04a35b81d3cc6e455bfeca085568866d72c66305136f2844dc9a7ba7d96dea849ec04718cdd7585cd88c2ca84b21d61471ac38d653bd779cc59cda529ef78!@mx.jul.es>
 <6b595cf71d4341d5b670e3509ca09df2@City-Exch-DB1.cbj.local>
Message-ID: <WM!a08e614f444357f20bd2a123281f262d719393d706c51d222690061e0616cdc262abbcaff245cb9ed7c7010b4c210fdb!@mx.jul.es>

Ah ? perfect, thanks.  Never noticed that before.

...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 Greg Clarke via ZendTo
Sent: Tuesday, April 30, 2019 6:04 PM
To: ZendTo Users <zendto at zend.to>
Cc: Greg Clarke <greg.clarke at waikato.ac.nz>
Subject: Re: [ZendTo] [Feature Request custom string in subject per DropOff]

Hi there

On Wed, 1 May 2019 at 11:24, Kevin Miller via ZendTo <zendto at zend.to<mailto:zendto at zend.to>> wrote:

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?

The subject prefix is a variable defined in zendto.conf. You can set it:
EmailSubjectTag = "[fileshare] "


Greg


Greg Clarke
SysAdmin, Systems, ITS
The University of Waikato
New Zealand
http://www.waikato.ac.nz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190501/3eb6b181/attachment.html>

From TZimmerman at fsu.edu  Thu May  2 20:00:19 2019
From: TZimmerman at fsu.edu (Travis Zimmerman)
Date: Thu, 2 May 2019 19:00:19 +0000
Subject: [ZendTo] alternate AD attribute
In-Reply-To: <WM!0ba51590b42c82bc78035c5148a8fd0736b2f0ab443acbc6dc219a4d2bd7d6e8c43e9d2b9ae41bcbc58008e16543db30accbd7f366bcb98aef8105b37580e5cb!@mx.jul.es>
References: <58299ADB-FC43-42C7-BF6C-5098A8060A51@fsu.edu>
 <WM!34928f50d1e542023efee6bfe83be1c470660949703bffafce8c6f4178edad8b8c7faf56bbb71c28f0ef373d9e32c2a0!@mx.jul.es>
 <c1814b81-4f77-2873-83c0-8bc0d2ea82fc@Zend.To>
 <WM!0ba51590b42c82bc78035c5148a8fd0736b2f0ab443acbc6dc219a4d2bd7d6e8c43e9d2b9ae41bcbc58008e16543db30accbd7f366bcb98aef8105b37580e5cb!@mx.jul.es>
 <36317C70-693D-438F-A754-66C92353B8BA@fsu.edu>
Message-ID: <WM!f017aadf46d5937b7f9ff5adc63e3e628a33e6edb2acc4eb89547b27871de47194b07913198c6dfec0260e6ed3f99ea3!@mx.jul.es>

Username, but it looks like it?s more complicated. I just got out of a meeting and one of the AD admins gave me several examples of student attribute listing. Looking at the attributes and their values there isn?t actually a specific username, there is a unique identifier by way of an ID number; and then there are several different attributes with the student?s e-mail address.

So I think for right now I may have to hack together a fix for my specific problem and then talk to you about a possible way to incorporate it into the code in a more general way that may be useful for others. ????

If I?m reading the NSSADAuthenticator.php correctly, you compare their username against ?sAMAccountName? but before you do that if someone logged in with an e-mail address, you remove the @domain part.
I don?t suppose the @domain that gets chopped off is stored in a variable that I could use for comparisons to force a different search using the full e-mail address against a different attribute? If not I?ll work out something.

Again thanks for any help you can provide.

------------------------------------------------------
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 30, 2019, at 4:46 AM, Jules Field <Jules at Zend.To<mailto:Jules at Zend.To>> wrote:

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 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>
http://jul.es/mailman/listinfo/zendto<https://urldefense.proofpoint.com/v2/url?u=http-3A__jul.es_mailman_listinfo_zendto&d=DwMDaQ&c=HPMtquzZjKY31rtkyGRFnQ&r=TZ3x4Nnv5Pp03uwRWF9UlLOaC296m8a1MGVEkWJljsg&m=Ky15pezwlDoQcfjl_3RZsdfB5VdZYIPMvFC_uDgO6YA&s=EcKKZFVwDujx3aSUu3dGlvXh-eVwOT-rNcQuXml2qJw&e=>



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<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.Zend.To&d=DwMDaQ&c=HPMtquzZjKY31rtkyGRFnQ&r=TZ3x4Nnv5Pp03uwRWF9UlLOaC296m8a1MGVEkWJljsg&m=Ky15pezwlDoQcfjl_3RZsdfB5VdZYIPMvFC_uDgO6YA&s=7VwiZXK634fmUzQAubkdp5Qajj1qVnqk1n-f4bggYLU&e=>
Twitter: @JulesFM


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

From Jules at Zend.To  Fri May  3 09:20:00 2019
From: Jules at Zend.To (Jules Field)
Date: Fri, 3 May 2019 09:20:00 +0100
Subject: [ZendTo] alternate AD attribute
In-Reply-To: <WM!f017aadf46d5937b7f9ff5adc63e3e628a33e6edb2acc4eb89547b27871de47194b07913198c6dfec0260e6ed3f99ea3!@mx.jul.es>
References: <58299ADB-FC43-42C7-BF6C-5098A8060A51@fsu.edu>
 <WM!34928f50d1e542023efee6bfe83be1c470660949703bffafce8c6f4178edad8b8c7faf56bbb71c28f0ef373d9e32c2a0!@mx.jul.es>
 <c1814b81-4f77-2873-83c0-8bc0d2ea82fc@Zend.To>
 <WM!0ba51590b42c82bc78035c5148a8fd0736b2f0ab443acbc6dc219a4d2bd7d6e8c43e9d2b9ae41bcbc58008e16543db30accbd7f366bcb98aef8105b37580e5cb!@mx.jul.es>
 <36317C70-693D-438F-A754-66C92353B8BA@fsu.edu>
 <WM!f017aadf46d5937b7f9ff5adc63e3e628a33e6edb2acc4eb89547b27871de47194b07913198c6dfec0260e6ed3f99ea3!@mx.jul.es>
Message-ID: <ef683274-639f-f5ae-3936-f64c49b86e59@Zend.To>

Travis,

On 02/05/2019 20:00, Travis Zimmerman wrote:
> Username, but it looks like it?s more complicated. I just got out of a 
> meeting and one of the AD admins gave me several examples of student 
> attribute listing. Looking at the attributes and their values there 
> isn?t actually a specific username, there is a unique identifier by 
> way of an ID number; and then there are several different attributes 
> with the student?s e-mail address.
>
> So I think for right now I may have to hack together a fix for my 
> specific problem and then talk to you about a possible way to 
> incorporate it into the code in a more general way that may be useful 
> for others. ????
That sounds like a good idea. :)
>
> If I?m reading the NSSADAuthenticator.php correctly, you compare their 
> username against ?sAMAccountName? but before you do that if someone 
> logged in with an e-mail address, you remove the @domain part.
> I don?t suppose the @domain that gets chopped off is stored in a 
> variable that I could use for comparisons to force a different search 
> using the full e-mail address against a different attribute? If not 
> I?ll work out something.
I chop off the domain part, as a lot of people (certainly here!) will 
tend to type in their whole username at domain.com address rather than just 
their username. Entering the whole of username at domain.com is needed for 
things like Eduroam Wifi (as Eduroam can't authenticate you if it 
doesn't know what Uni you belong to). And with AD-based logins, 
username at domain.com is usually equivalent to DOMAIN\username. So that 
usually works okay too.

I don't think it gets stored anywhere at the moment.

However, the easiest thing for you to do is probably write your own 
authenticator module. Call it something like 
"NSSTravisAuthenticator.php" and then you can refer to it in 
preferences.php as an authenticator called "Travis".
There are only 2 calls you need to implement. 1 that checks for a valid 
username and 1 that checks a username/password pair and retrieves info 
about the user. Get the information you need from wherever you want it, 
and put it into the same members of the class as the other 
authenticators do, and it will work.

Take a look at the NSSLocalAuthenticator.php to see the structure in a 
fairly simple way (NSSStaticAuthenticator.php is the trivial case but 
doesn't tell you much), then see how that maps onto 
NSSADAuthenticator.php. The LDAP authenticator is almost identical to 
the AD one, but is much simpler as it only supports one "forest".

For the preferences.php settings for your authenticator, just make sure 
you don't use any names I've already used.

Then even the "upgrade" and "upgrade_preferences_php" will perfectly 
happily handle your new authenticator module.

That way you aren't changing any of the existing code (as far as 
rpm/dpkg/apt/yum are concerned), you are just adding a whole new file. 
The package managers will leave that alone.

Hope that helps,
Jules.


>
> Again thanks for any help you can provide.
>
> ------------------------------------------------------
> 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
>
>> On Apr 30, 2019, at 4:46 AM, Jules Field <Jules at Zend.To 
>> <mailto:Jules at Zend.To>> wrote:
>>
>> 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
>

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

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

www.Zend.To
Twitter: @JulesFM

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

From Jules at Zend.To  Fri May  3 12:16:42 2019
From: Jules at Zend.To (Jules Field)
Date: Fri, 3 May 2019 12:16:42 +0100
Subject: [ZendTo] ZendTo demo site running latest beta
Message-ID: <8e86ca69-3ce8-7110-bfb8-0214025da2bf@Zend.To>

Folks,

I have a ZendTo demo site. It's just a normal installation of ZendTo 
with manually-created local users, and a few extra domains added to 
internaldomains.conf.

Please don't all yell at once, as I still create users manually on it.

But if you would like to see the user interface improvements in the 
latest betas, or want to test anything else about it, such as maybe 
grabbing some screenshots to show your management, then please do let me 
know.

Cheers,

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'The AI does not hate you, nor does it love you, but you are made
  out of atoms which it can use for something else.' - Eliezer Yudkowsky

www.Zend.To
Twitter: @JulesFM



From Jules at Zend.To  Fri May 10 17:14:16 2019
From: Jules at Zend.To (Jules Field)
Date: Fri, 10 May 2019 17:14:16 +0100
Subject: [ZendTo] =?utf-8?q?Major_new_feature_=28please_test!=29_?=
 =?utf-8?q?=E2=80=94_Automated_ZendTo?=
Message-ID: <80095991-171c-ffad-f8c0-44a5a1c2b174@Zend.To>

Folks,

I have finally implemented automatic command-line generation of
 ??? 1. A new drop-off
 ??? 2. A request for a drop-off

This is included in the latest beta release, 5.18-3. See the beta page at
 ??? https://zend.to/beta.php
and the Changelog at
 ??? https://zend.to/changelog.php
for more information.

The 2 scripts that do it are in
 ??? /opt/zendto/bin/autodropoff
 ??? /opt/zendto/bin/autorequest

To find out how to drive them,
 ??? 1. See the comments above the new 'automationUsers' settings in 
preferences.php, and
 ??? 2. Run each of the scripts without any command-line parameters.

Basically you give them everything they need to know via command-line 
options.

They then construct and either print or run (depending on the presence 
of "--debug") a big "curl" command.

The results from the ZendTo server are a JSON data structure, which is 
hopefully the easiest thing for most of you to handle automatically.

So please do test them out.

Do they work?
Do they do what you need / want?
Is there enough detail in the data structure returned?

I know you folks have been waiting very patiently for this for a very 
long time. Sorry it's taken me quite so long to figure out a relatively 
easy way of doing it.

If you need to automate it from a platform that can't run bash, just 
take a look at the scripts. Almost all of both of them is parsing 
command-line parameters and error-detection. If you look at the "curl" 
command they generate, and read the "curl" documentation, you will see 
it is *actually* very simple.

Anyway, have a go and let me know how you get on!

Enjoy your weekend...

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

'We face neither East nor West: we face forward.' - Kwame Nkrumah

www.Zend.To
Twitter: @JulesFM



From mrm at medicine.wisc.edu  Wed May 15 19:37:31 2019
From: mrm at medicine.wisc.edu (MICHAEL R MASSE)
Date: Wed, 15 May 2019 18:37:31 +0000
Subject: [ZendTo] User notification of problems with email
References: <DM5PR06MB34505771AC5D6C0F76C539E5F6090@DM5PR06MB3450.namprd06.prod.outlook.com>
Message-ID: <WM!dd216b511731108af2e50f9fee3b6ba1877abb211eca81a27dcc86bb6f5780b0a5f53b7584f4a1592c8e6c77b078adf4!@mx.jul.es>

if a user tries to send a file to someone but enters the email address
incorrectly, the 'EmailSenderAddress' email address gets the bounceback,
which I then have automatically forwarded to an administrator, but the
actual sending user doesn't get any warning or error without manual
intervention.     Is there a setting to allow the sender to receive email
bouncebacks without having to rely on an administrator manually forwarding
bounceback emails?

 

-Mike

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20190515/91279dd2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5727 bytes
Desc: not available
URL: <http://jul.es/pipermail/zendto/attachments/20190515/91279dd2/attachment-0001.p7s>

From zend.to at neilzone.co.uk  Thu May 30 08:51:44 2019
From: zend.to at neilzone.co.uk (zend.to at neilzone.co.uk)
Date: Thu, 30 May 2019 08:51:44 +0100
Subject: [ZendTo] I sent my first automated drop-off request today
References: <01555D7A-179E-41EE-8D4B-AD7AA33AFD02@neilzone.co.uk>
Message-ID: <WM!18c4ae280326b3dc781dd9e78d79dbea3d3c922cae0fcd2a6cb8d9ac2e23eb131f1b3032873b65585d463e43260ac714!@mx.jul.es>

Thanks Jules!

The beta upgrade went smoothly, and your instructions for using the auto functions were clear and comprehensive.

Thank you!

Neil



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

From Jules at Zend.To  Thu May 30 12:22:59 2019
From: Jules at Zend.To (Jules Field)
Date: Thu, 30 May 2019 12:22:59 +0100
Subject: [ZendTo] I sent my first automated drop-off request today
In-Reply-To: <WM!18c4ae280326b3dc781dd9e78d79dbea3d3c922cae0fcd2a6cb8d9ac2e23eb131f1b3032873b65585d463e43260ac714!@mx.jul.es>
References: <01555D7A-179E-41EE-8D4B-AD7AA33AFD02@neilzone.co.uk>
 <WM!18c4ae280326b3dc781dd9e78d79dbea3d3c922cae0fcd2a6cb8d9ac2e23eb131f1b3032873b65585d463e43260ac714!@mx.jul.es>
Message-ID: <8b49064a-80f0-01dd-6405-b6dccf9626f4@Zend.To>

Neil,

Yay! It worked! :-)

I've got 1 person who needs to be able to automate the pick-up process 
as well. But now I've done the 2 hard ones, the pick-up will be very 
easy to write.

I do admit the massive "curl" is hardly the most elegant solution in the 
world, but hopefully once you have your head around what "curl" the 
shell scripts create, it should be fairly easy to implement the same 
thing on systems such as Windows desktops where you might need to use a 
totally different language to do the HTTP POST request.

But at least I made it return a JSON result to you, so the output looks 
trendy!
*me goes and checks that JSON is still in fashion today*

Cheers,
Jules.

On 30/05/2019 08:51, Neil via ZendTo wrote:
> Thanks Jules!
>
> The beta upgrade went smoothly, and your instructions for using the 
> auto functions were clear and comprehensive.
>
> Thank you!
>
> Neil
>
>
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE MACM

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

www.Zend.To
Twitter: @JulesFM

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

From zend.to at neilzone.co.uk  Thu May 30 12:33:08 2019
From: zend.to at neilzone.co.uk (zend.to at neilzone.co.uk)
Date: Thu, 30 May 2019 12:33:08 +0100
Subject: [ZendTo] I sent my first automated drop-off request today
In-Reply-To: <WM!883436aeb242f5e15d410c126156f76cb35f4a3ec9811c237828cf1a9800d08a0f90c459dd69b44f8772a137715bc803ce8ba643c329d6df00ef232660be2666!@mx.jul.es>
References: <01555D7A-179E-41EE-8D4B-AD7AA33AFD02@neilzone.co.uk>
 <WM!18c4ae280326b3dc781dd9e78d79dbea3d3c922cae0fcd2a6cb8d9ac2e23eb131f1b3032873b65585d463e43260ac714!@mx.jul.es>
 <8b49064a-80f0-01dd-6405-b6dccf9626f4@Zend.To>
 <WM!883436aeb242f5e15d410c126156f76cb35f4a3ec9811c237828cf1a9800d08a0f90c459dd69b44f8772a137715bc803ce8ba643c329d6df00ef232660be2666!@mx.jul.es>
 <38B534EC-B245-44CD-9801-8CB215D2A5E7@neilzone.co.uk>
Message-ID: <WM!5600448335bff2bfcf06d1f12e13a9e0a45ebb8bed23daf06fbc68787c053c7f1403b172552d792c3c099921d601dd74!@mx.jul.es>



> On 30 May 2019, at 12:22, Jules Field via ZendTo <zendto at zend.to> wrote:
> 
> I do admit the massive "curl" is hardly the most elegant solution in the world, but hopefully once you have your head around what "curl" the shell scripts create, it should be fairly easy to implement the same thing on systems such as Windows desktops where you might need to use a totally different language to do the HTTP POST request.

I?ve only tried it on a Mac, and I?ve tried it via:

- running an ssh command, to call the script directly; and
- a curl, using a URL built using your script.

Both worked, as expected.

I?ve yet to play around with parsing the returned JSON...


Best wishes

Neil



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