date:20190213

[dspace-tech] Enable Static Aspect in Mirage 2.

2019-02-13 Thread Kev Evans

Hi

Apologies for bombarding this group with questions!

I want to enable the Static Aspect to use with Mirage 2. 

Documentation references it is possible with xmlui/Mirage. But will the 
same steps work with Mirage 2?

Cheers

Kev

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] problems building with mirage2

2019-02-13 Thread Alan Orth

Dear Stefan,

When you use '-Dmirage2.on=true' the maven build system downloads some
versions of Node.js/NPM/Ruby from 2015 and then tries to install a list of
packages from some repositories. As the frontend web development ecosystem
moves so fast I'm actually surprised that this build system has worked this
long at all! The alternative for building Mirage2 is to satisfy the
Node.js/NPM/Ruby dependencies yourself locally and then build DSpace with
an extra option that tells maven to use the local Node.JS/NPM/Ruby:

$ mvn -Dmirage2.on=true -Dmirage2.deps.included=false clean package

I've made some notes about how I prepare my DSpace 5.x build environment on
Ubuntu 16.04 in a GitHub Gist[0]. Basically, I use NVM to download Node.js
and RVM to download Ruby in my build user's environment. In Ubuntu 18.04
it's a bit easier and I've done away with using NVM/RVM.

[0] https://gist.github.com/alanorth/2cf9c15834dc68a514262fcb04004cb0

Hope that helps,

On Wed, Feb 13, 2019 at 1:16 PM Stefan Kombrink 
wrote:

> Hi,
>
>  I am having constant troubles building DSpace 5/6 with -Dmirage2.on=true
>
> maven gives me this output:
>
> [INFO] Found NPM version 1.4.23
> [INFO] -- (Mirage2)
> com.github.eirslett:frontend-maven-plugin:0.0.23:npm
> [INFO] Running 'npm install --color=false' in
> /tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2
> [ERROR] npm WARN package.json Mirage2@0.1.1 No description
> [ERROR] npm WARN package.json Mirage2@0.1.1 No repository field.
> [ERROR] npm WARN package.json Mirage2@0.1.1 No README data
> [INFO]
> [INFO] > Mirage2@0.1.1 postinstall
> /tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2
> [INFO] > bower install
> [INFO]
> [ERROR]
> [ERROR]
>
> /tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/bower-registry-client/node_modules/request/node_modules/tough-cookie/node_modules/ip-regex/index.js:3
> [ERROR] const v4 =
> '(?:25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])(?:\\.(?:25[0-
> [ERROR] ^
> [ERROR] bowererror Use of const in strict mode.
> [ERROR]
> [ERROR] Stack trace:
> [ERROR] SyntaxError: Use of const in strict mode.
> [ERROR] at Module._compile (module.js:439:25)
> [ERROR] at Object.Module._extensions..js (module.js:474:10)
> [ERROR] at Module.load (module.js:356:32)
> [ERROR] at Function.Module._load (module.js:312:12)
> [ERROR] at Module.require (module.js:364:17)
> [ERROR] at require (module.js:380:17)
> [ERROR] at Object.
>
> (/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/bower-registry-client/node_modules/request/node_modules/tough-cookie/lib/cookie.js:34:15)
> [ERROR] at Module._compile (module.js:456:26)
> [ERROR] at Object.Module._extensions..js (module.js:474:10)
> [ERROR] at Module.load (module.js:356:32)
> [ERROR]
> [ERROR] Console trace:
> [ERROR] Trace
> [ERROR] at StandardRenderer.error
>
> (/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/lib/renderers/StandardRenderer.js:82:17)
> [ERROR] at Logger.
>
> (/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/bin/bower:110:22)
> [ERROR] at Logger.emit (events.js:95:17)
> [ERROR] at Logger.emit
>
> (/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39)
> [ERROR] at
>
> /tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/lib/commands/index.js:40:20
> [ERROR] at _rejected
>
> (/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/q/q.js:797:24)
> [ERROR] at
>
> /tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/q/q.js:823:30
> [ERROR] at Promise.when
>
> (/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/q/q.js:1035:31)
> [ERROR] at Promise.promise.promiseDispatch
>
> (/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/q/q.js:741:41)
> [ERROR] at
>
> /tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/q/q.js:509:49
> [ERROR]
> [ERROR] System info:
> [ERROR] Bower version: 1.3.12
> [ERROR] Node version: 0.10.31
> [ERROR] OS: Linux 4.15.0-1011-kvm x64
> [ERROR]
> [ERROR] npm ERR! Mirage2@0.1.1 postinstall: `bower install`
> [ERROR] npm ERR! Exit status 1
> [ERROR] npm ERR!
> [ERROR] npm ERR! Failed at the Mirage2@0.1.1 postinstall script.
> [ERROR] npm ERR! This is most likely a problem with the Mirage2 package,
> [ERROR] npm ERR! not with npm itself.
> [ERROR] npm ERR! Tell the author that this fails on your system:
> [ERROR] npm ERR! bower install
> [ERROR] npm ERR! You can get their info via:
> [ERROR] npm ERR! npm owner ls Mirage2
> [ERROR] npm ERR

Re: [dspace-tech] Editing a submitted item

2019-02-13 Thread Evgeni Dimitrov

Yes, it works fine. I gave the user (in a last submission step) only WRITE 
permission on the item. Now the user can edit the metadata (in xmlui). The 
user can not delete the item and can not add/delete bitstreams. And this is 
in DSpace 6.2

Best regards
Evgeni



On Tuesday, February 12, 2019 at 11:56:10 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> To be honest, I don't know whether the UI (either XMLUI or JSPUI) will 
> even provide the user with a link to edit the Item, regardless of whether 
> he/she has Item WRITE permissions.  Originally, both UIs allowed 
> Administrators to edit items.  As noted in my previous message this only 
> began to change in the DSpace 6 JSPUI.
>
> So, that's a long way of saying, you might need to also modify/customize 
> the UI to get this to work.  As this is not a feature that DSpace currently 
> supports out-of-the-box (and I've never tried this before), I don't have 
> any other specific advice I can currently offer.. Hopefully if someone else 
> on this list has experience with this they will speak up.  Otherwise, you 
> could simply try adding an Item WRITE policy and see how the UI reacts to 
> that.
>
> - Tim
>
> On Tue, Feb 12, 2019 at 2:32 PM Evgeni Dimitrov  > wrote:
>
>> Thank you Tim,
>>
>> I am wondering will it work if I add in the end of the submission process 
>> a non-interactive AuthorizationStep?
>> It will add to the item a WRITE policy for the submitter.
>>
>> Best regards
>> Evgeni
>>
>>
>>
>> On Tuesday, February 12, 2019 at 5:54:20 PM UTC+2, Tim Donohue wrote:
>>
>>> Hello Evgeni,
>>>
>>> Unfortunately, as far as I'm aware, this is only supported in DSpace 6.0 
>>> in the JSPUI when you have Item Versioning enabled. See the documentation 
>>> here: 
>>> https://wiki.duraspace.org/display/DSDOC6x/Item+Level+Versioning#ItemLevelVersioning-Allowingsubmitterstoversiontheiritems(JSPUIonly
>>> ) 
>>> 
>>>
>>> See also this answer on StackOverflow: 
>>> https://stackoverflow.com/questions/42564072/how-to-define-a-group-policy-that-to-allow-submitters-to-edit-only-yours-items-s
>>>  
>>>
>>> I expect this will have broader support in a future version of DSpace 
>>> (possibly even 7.0, but we'll have to see).
>>>
>>> If others have found ways around this, I'd love to hear them. It's 
>>> possible there's workarounds I haven't thought of.
>>>
>>> - Tim
>>>
>>>
>>> On Tue, Feb 12, 2019 at 4:51 AM Evgeni Dimitrov  
>>> wrote:
>>>
>> If a user has "Add" permission for a collection, this user can submit an 
 item to the collection.
 Is there a way to allow this user to edit the metadata of "his" item 
 but no other items in the collection?
 Without changing policies after the submission.

 -- 
 All messages to this mailing list should adhere to the DuraSpace Code 
 of Conduct: https://duraspace.org/about/policies/code-of-conduct/
 --- 
 You received this message because you are subscribed to the Google 
 Groups "DSpace Technical Support" group.

>>> To unsubscribe from this group and stop receiving emails from it, send 
 an email to dspace-tech...@googlegroups.com.
 To post to this group, send email to dspac...@googlegroups.com.
>>>
>>>
 Visit this group at https://groups.google.com/group/dspace-tech.
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>>> Tim Donohue
>>> Technical Lead for DSpace & DSpaceDirect
>>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>>
>> -- 
>> All messages to this mailing list should adhere to the DuraSpace Code of 
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] problems building with mirage2

2019-02-13 Thread Stefan Kombrink

Hi,

 I am having constant troubles building DSpace 5/6 with -Dmirage2.on=true

maven gives me this output:

[INFO] Found NPM version 1.4.23
[INFO] -- (Mirage2) com.github.eirslett:frontend-maven-plugin:0.0.23:npm
[INFO] Running 'npm install --color=false' in
/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2
[ERROR] npm WARN package.json Mirage2@0.1.1 No description
[ERROR] npm WARN package.json Mirage2@0.1.1 No repository field.
[ERROR] npm WARN package.json Mirage2@0.1.1 No README data
[INFO]
[INFO] > Mirage2@0.1.1 postinstall
/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2
[INFO] > bower install
[INFO]
[ERROR]
[ERROR]
/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/bower-registry-client/node_modules/request/node_modules/tough-cookie/node_modules/ip-regex/index.js:3
[ERROR] const v4 =
'(?:25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])(?:\\.(?:25[0-
[ERROR] ^
[ERROR] bowererror Use of const in strict mode.
[ERROR]
[ERROR] Stack trace:
[ERROR] SyntaxError: Use of const in strict mode.
[ERROR] at Module._compile (module.js:439:25)
[ERROR] at Object.Module._extensions..js (module.js:474:10)
[ERROR] at Module.load (module.js:356:32)
[ERROR] at Function.Module._load (module.js:312:12)
[ERROR] at Module.require (module.js:364:17)
[ERROR] at require (module.js:380:17)
[ERROR] at Object.
(/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/bower-registry-client/node_modules/request/node_modules/tough-cookie/lib/cookie.js:34:15)
[ERROR] at Module._compile (module.js:456:26)
[ERROR] at Object.Module._extensions..js (module.js:474:10)
[ERROR] at Module.load (module.js:356:32)
[ERROR]
[ERROR] Console trace:
[ERROR] Trace
[ERROR] at StandardRenderer.error
(/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/lib/renderers/StandardRenderer.js:82:17)
[ERROR] at Logger.
(/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/bin/bower:110:22)
[ERROR] at Logger.emit (events.js:95:17)
[ERROR] at Logger.emit
(/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39)
[ERROR] at
/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/lib/commands/index.js:40:20
[ERROR] at _rejected
(/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/q/q.js:797:24)
[ERROR] at
/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/q/q.js:823:30
[ERROR] at Promise.when
(/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/q/q.js:1035:31)
[ERROR] at Promise.promise.promiseDispatch
(/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/q/q.js:741:41)
[ERROR] at
/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node_modules/bower/node_modules/q/q.js:509:49
[ERROR]
[ERROR] System info:
[ERROR] Bower version: 1.3.12
[ERROR] Node version: 0.10.31
[ERROR] OS: Linux 4.15.0-1011-kvm x64
[ERROR]
[ERROR] npm ERR! Mirage2@0.1.1 postinstall: `bower install`
[ERROR] npm ERR! Exit status 1
[ERROR] npm ERR!
[ERROR] npm ERR! Failed at the Mirage2@0.1.1 postinstall script.
[ERROR] npm ERR! This is most likely a problem with the Mirage2 package,
[ERROR] npm ERR! not with npm itself.
[ERROR] npm ERR! Tell the author that this fails on your system:
[ERROR] npm ERR! bower install
[ERROR] npm ERR! You can get their info via:
[ERROR] npm ERR! npm owner ls Mirage2
[ERROR] npm ERR! There is likely additional logging output above.
[ERROR] npm ERR! System Linux 4.15.0-1011-kvm
[ERROR] npm ERR! command
"/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node/node"
"/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node/npm/bin/npm-cli.js"
"install" "--color=false"
[ERROR] npm ERR! cwd
/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2
[ERROR] npm ERR! node -v v0.10.31
[ERROR] npm ERR! npm -v 1.4.23
[ERROR] npm ERR! code ELIFECYCLE
[ERROR] npm ERR!
[ERROR] npm ERR! Additional logging details can be found in:
[ERROR] npm ERR!
/tmp/dspace-src/dspace/modules/xmlui-mirage2/target/themes/Mirage2/npm-debug.log
[ERROR] npm ERR! not ok code 0
[ERROR] MojoFailureException:
org.apache.maven.plugin.MojoFailureException: Failed to run task
at com.github.eirslett.maven.plugins.frontend.mojo.NpmMojo.execute
(NpmMojo.java:62)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:134)
at com.soebes.maven.plugins.iterator.ExecutorMojo.executeMojo
(ExecutorMojo.java:302)
at com.soebes.maven.plugins.iterator.ExecutorMojo.execute
(ExecutorMojo.java:235)
at org.apache

Re: [dspace-tech] Editing a submitted item

2019-02-13 Thread Evgeni Dimitrov

Thank you Tim,

I will try and I will let you know if it works.

Best regards
Evgeni


On Tuesday, February 12, 2019 at 11:56:10 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> To be honest, I don't know whether the UI (either XMLUI or JSPUI) will 
> even provide the user with a link to edit the Item, regardless of whether 
> he/she has Item WRITE permissions.  Originally, both UIs allowed 
> Administrators to edit items.  As noted in my previous message this only 
> began to change in the DSpace 6 JSPUI.
>
> So, that's a long way of saying, you might need to also modify/customize 
> the UI to get this to work.  As this is not a feature that DSpace currently 
> supports out-of-the-box (and I've never tried this before), I don't have 
> any other specific advice I can currently offer.. Hopefully if someone else 
> on this list has experience with this they will speak up.  Otherwise, you 
> could simply try adding an Item WRITE policy and see how the UI reacts to 
> that.
>
> - Tim
>
> On Tue, Feb 12, 2019 at 2:32 PM Evgeni Dimitrov  > wrote:
>
>> Thank you Tim,
>>
>> I am wondering will it work if I add in the end of the submission process 
>> a non-interactive AuthorizationStep?
>> It will add to the item a WRITE policy for the submitter.
>>
>> Best regards
>> Evgeni
>>
>>
>>
>> On Tuesday, February 12, 2019 at 5:54:20 PM UTC+2, Tim Donohue wrote:
>>
>>> Hello Evgeni,
>>>
>>> Unfortunately, as far as I'm aware, this is only supported in DSpace 6.0 
>>> in the JSPUI when you have Item Versioning enabled. See the documentation 
>>> here: 
>>> https://wiki.duraspace.org/display/DSDOC6x/Item+Level+Versioning#ItemLevelVersioning-Allowingsubmitterstoversiontheiritems(JSPUIonly
>>> ) 
>>> 
>>>
>>> See also this answer on StackOverflow: 
>>> https://stackoverflow.com/questions/42564072/how-to-define-a-group-policy-that-to-allow-submitters-to-edit-only-yours-items-s
>>>  
>>>
>>> I expect this will have broader support in a future version of DSpace 
>>> (possibly even 7.0, but we'll have to see).
>>>
>>> If others have found ways around this, I'd love to hear them. It's 
>>> possible there's workarounds I haven't thought of.
>>>
>>> - Tim
>>>
>>>
>>> On Tue, Feb 12, 2019 at 4:51 AM Evgeni Dimitrov  
>>> wrote:
>>>
>> If a user has "Add" permission for a collection, this user can submit an 
 item to the collection.
 Is there a way to allow this user to edit the metadata of "his" item 
 but no other items in the collection?
 Without changing policies after the submission.

 -- 
 All messages to this mailing list should adhere to the DuraSpace Code 
 of Conduct: https://duraspace.org/about/policies/code-of-conduct/
 --- 
 You received this message because you are subscribed to the Google 
 Groups "DSpace Technical Support" group.

>>> To unsubscribe from this group and stop receiving emails from it, send 
 an email to dspace-tech...@googlegroups.com.
 To post to this group, send email to dspac...@googlegroups.com.
>>>
>>>
 Visit this group at https://groups.google.com/group/dspace-tech.
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>>> Tim Donohue
>>> Technical Lead for DSpace & DSpaceDirect
>>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>>
>> -- 
>> All messages to this mailing list should adhere to the DuraSpace Code of 
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] mail server office365.com

2019-02-13 Thread Alan Orth

Dear list,

Having just gone through this issue myself, I thought I'd share my
experiences. We are using DSpace 5.8 with OpenJDK 8. If your organization
is using Office 365 you will need to reconfigure the following mail
settings in dspace.cfg:

mail.server = smtp.office365.com
mail.server.port = 587
mail.extraproperties = mail.smtp.starttls.enable=true

Note that you do not need to use any of the socketFactory settings (see the
JavaMail common mistakes guide listing these as unnecessary since at least
2015[0]). You only need to enable the extra property for STARTTLS. Also of
use is the Microsoft Office 365 documentation about "client send" support
in their SMTP support[1].

Perhaps we should remove the antiquated settings from dspace.cfg? Shall I
file a bug for this?

Regards,

[0] https://javaee.github.io/javamail/FAQ#commonmistakes
[1]
https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-3

On Sun, Feb 3, 2019 at 1:33 PM francesco chiurco 
wrote:

> Thank you Marc, your reply made me think atout possibile
> misconfigurations. i found an entry in dspace.cf used in the past That
> Was overriding My new username in local.cfg
>
>
> Il giorno lun 14 gen 2019 alle ore 17:08 Mark H. Wood <
> mwoodiu...@gmail.com> ha scritto:
> >
> > On Saturday, January 12, 2019 at 9:23:20 AM UTC-5, francesco wrote:
> >>
> >> Hi, anybody succesful with configuring email settings with
> office365.com ?
> >>
> >>
> >>
> >> mail.server = smtp.office365.com
> >>
> >>
> >>
> >> # SMTP mail server authentication username and password (if required)
> >>
> >> mail.server.username = u...@domain.com
> >>
> >> mail.server.password = password
> >>
> >>
> >>
> >> # SMTP mail server alternate port (defaults to 25)
> >>
> >> mail.server.port = 587
> >>
> >>
> >>
> >> I have tried to enable starttls with the following
> >>
> >> mail.extraproperties=mail.smtp.starttls.required = true, \
> >>
> >> mail.smtp.auth=true
> >>
> >>
> >>
> >> at least now I get a new error:
> >>
> >> 535 5.7.3 Authentication unsuccessful [
> AM6P193CA0138.EURP193.PROD.OUTLOOK.COM]
> >>
> >>
> >
> >
> > For "authentication unsuccessful" I would first check that the values of
> mail.server.username and mail.server.password are correct.  It seems that
> you are connecting to the proper service and SMTP is working, but the
> credentials are not accepted.
> >
> > --
> > All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> > ---
> > You received this message because you are subscribed to a topic in the
> Google Groups "DSpace Technical Support" group.
> > To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/dspace-tech/iMdojwAxOAs/unsubscribe.
> > To unsubscribe from this group and all its topics, send an email to
> dspace-tech+unsubscr...@googlegroups.com.
> > To post to this group, send email to dspace-tech@googlegroups.com.
> > Visit this group at https://groups.google.com/group/dspace-tech.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Alan Orth
alan.o...@gmail.com
https://picturingjordan.com
https://englishbulgaria.net
https://mjanja.ch
"In heaven all the interesting people are missing." ―Friedrich Nietzsche

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Enable Static Aspect in Mirage 2.

Re: [dspace-tech] problems building with mirage2

Re: [dspace-tech] Editing a submitted item

[dspace-tech] problems building with mirage2

Re: [dspace-tech] Editing a submitted item

Re: [dspace-tech] mail server office365.com

6 matches

Site Navigation

Mail list logo

Footer information