Re: [dspace-tech] SMTP over TLS Failed

[Cristhian Andres Rey Casadiego]

Hi everybody I had the same issue in debian and fixed it adding this in 
dspace.conf:

mail.extraproperties = mail.smtp.socketFactory.port=587, \

mail.smtp.starttls.enable=true, \

mail.smtp.starttls.required=true, \

mail.smtp.ssl.protocols=TLSv1.2


Best Regards,


Cristhian Rey

Colombia

El miércoles, 17 de marzo de 2021 a las 14:08:24 UTC-5, gonza...@gmail.com 
escribió:

> Just adding some info I've found troubleshooting the same error 
> (javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is 
> disabled or cipher suites are inappropriate)
>
> Running DSpace on Centos8 could require that command, depending on your 
> mail provider, as far as TLS 1.0 and 1.1 are deprecated and a legacy mode 
> is needed. 
>
> This solved the issue to me, using SMTPS under TLS on port 465
>
>
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/considerations_in_adopting_rhel_8/security_considerations-in-adopting-rhel-8#tls-v10-v11_security
>
>
> El Wednesday, December 9, 2020 a la(s) 5:39:39 PM UTC-3, hbla...@gmail.com 
> escribió:
>
>> Hi for all, 
>> Today I finally found a solution, the problem was with the operating 
>> system. execute the following command 
>>
>>  update-crypto-policies --set LEGACY  
>>
>> and after reboot it has worked.
>> Thanks to everyone for your support.
>>
>> El martes, 8 de diciembre de 2020 a la(s) 16:45:42 UTC-5, jacob.cameron 
>> escribió:
>>
>>> That should have said TLS 1.0 and 1.1 support.
>>>
>>>  
>>>
>>>  
>>>
>>> --
>>>
>>> Jake Cameron, BCS(UNB)
>>>
>>> Systems Support Specialist III
>>>
>>> Information Systems and Technical Services University of Lethbridge 
>>> Library
>>>
>>> Phone:(403)329-2756 <(403)%20329-2756>
>>>
>>> This e-mail, including any and all attachments, is only for the use of 
>>> the intended recipient(s) and may contain information that is confidential 
>>> or privileged. If you are not the intended recipient, you are advised that 
>>> any dissemination, copying or other use of this e-mail is prohibited. 
>>> Please notify the sender of the error in communication by return e-mail and 
>>> destroy all copies of this e-mail. Thank you.
>>>
>>>  
>>>
>>> *From:* dspac...@googlegroups.com  *On 
>>> Behalf Of *Cameron, Jacob
>>> *Sent:* Tuesday, December 8, 2020 8:54 AM
>>> *To:* Humberto Blanco Castillo ; DSpace Technical 
>>> Support 
>>> *Subject:* RE: [dspace-tech] SMTP over TLS Failed
>>>
>>>  
>>>
>>> Hello Humberto,
>>>
>>>  
>>>
>>> Microsoft has ended TLS 1.0 and TLS 1.2 support for all their mail 
>>> products.  You need to ensure you are using TLS 1.2 or higher on your 
>>> server or the messages will fail.
>>>
>>>  
>>>
>>>  
>>>
>>> --
>>>
>>> Jake Cameron, BCS(UNB)
>>>
>>> Systems Support Specialist III
>>>
>>> Information Systems and Technical Services University of Lethbridge 
>>> Library
>>>
>>> Phone:(403)329-2756 <(403)%20329-2756>
>>>
>>> This e-mail, including any and all attachments, is only for the use of 
>>> the intended recipient(s) and may contain information that is confidential 
>>> or privileged. If you are not the intended recipient, you are advised that 
>>> any dissemination, copying or other use of this e-mail is prohibited. 
>>> Please notify the sender of the error in communication by return e-mail and 
>>> destroy all copies of this e-mail. Thank you.
>>>
>>>  
>>>
>>> *From:* dspac...@googlegroups.com  *On 
>>> Behalf Of *Humberto Blanco Castillo
>>> *Sent:* Tuesday, December 8, 2020 8:26 AM
>>> *To:* DSpace Technical Support 
>>> *Subject:* [dspace-tech] SMTP over TLS Failed
>>>
>>>  
>>>
>>> Caution: This email was sent from someone *outside of the University of 
>>> Lethbridge*. Do not click on links or open attachments unless you know 
>>> they are safe. Suspicious emails should be forwarded to phis...@uleth.ca
>>> .
>>>
>>>  
>>>
>>> My dspace server was working with the following configuration 
>>>
>>>  
>>>
>>> *mail.server = outlook.office365.com *
>>>
>>> *mail.server.username = **myu...@mydomain.com*
>>>
>>> *mail.server.password = mypassword*
>>>
>>> *mail.server.port = 587*
>>>
>>> *mail.from.address = **myu...@mydomain.com*
>>>
>>> *mail.feedback.recipient = ${mail.from.address}*
>>>
>>> *mail.admin = ${mail.from.address}*
>>>
>>> *mail.alert.recipient = ${mail.from.address}*
>>>
>>> *mail.registration.notify = ${mail.from.address}*
>>>
>>>  
>>>
>>> *mail.extraproperties =  mail.smtp.starttls.enable=true, \*
>>>
>>> *mail.smtp.socketFactory.port=587, \*
>>>
>>> *mail.smtp.socketFactory.fallback=false*
>>>
>>>  
>>>
>>> But a few days ago it stopped working,:
>>>
>>>  
>>>
>>> *About to send test email:*
>>>
>>> * - To: **myu...@mydomain.com*
>>>
>>> * - Subject: DSpace test email*
>>>
>>> * - Server: outlook.office365.com *
>>>
>>>  
>>>
>>>  
>>>
>>> *Error sending email:*
>>>
>>> * - 

RE: [dspace-tech] How do I create an exclusion list for filter-media?

[Bouchard, Kerry]

Thank you!

-Kerry

From: Sean Kalynuk 
Sent: Wednesday, May 5, 2021 3:42 PM
To: Bouchard, Kerry ; DSpace Technical Support 

Subject: Re: [dspace-tech] How do I create an exclusion list for filter-media?

Hi Kerry,

There is a Skip mode option (-s) for the filter-media command:

https://wiki.lyrasis.org/display/DSDOC6x/Mediafilters+for+Transforming+DSpace+Content#MediafiltersforTransformingDSpaceContent-Executing(viaCommandLine)

--
Sean

From: dspace-tech@googlegroups.com 
mailto:dspace-tech@googlegroups.com>> on behalf 
of Kerry Bouchard mailto:k.bouch...@tcu.edu>>
Date: Wednesday, May 5, 2021 at 3:20 PM
To: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: [dspace-tech] How do I create an exclusion list for filter-media?
Caution: This message was sent from outside the University of Manitoba.

We are running into the problem described here: 
http://dspace.2283337.n4.nabble.com/Filter-media-on-PDFs-exported-from-Outlook-causes-a-TikaException-error-and-prevents-Items-from-inde-td4683489.html
 , where the *.pdf.txt files output by the PDF Text Extractor media filter for 
a couple of PDFs in our repository causes indexing to fail for not just the PDF 
full text, but all the associated metadata. (In our case, the PDFs were not 
output from Microsoft Outlook mail folders, but I'm seeing the same 
"org.apache.tika.exception.TikaException: Failed to parse an email message" in 
the dspace log file.)

The posting at the URL above refers to a work-around by creating an exclusion 
list for filter-media. But I can find any documentation on how to create an 
exclusion list. Can someone point me to that?

Thanks, Kerry
--
All messages to this mailing list should adhere to the 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/85e9b754-31d4-4558-8bde-071facdf9d0bn%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/ca7904aadba04262a99a2592446fbf61%40tcu.edu.

Re: [dspace-tech] How do I create an exclusion list for filter-media?

[Sean Kalynuk]

Hi Kerry,

There is a Skip mode option (-s) for the filter-media command:

https://wiki.lyrasis.org/display/DSDOC6x/Mediafilters+for+Transforming+DSpace+Content#MediafiltersforTransformingDSpaceContent-Executing(viaCommandLine)

--
Sean

From: dspace-tech@googlegroups.com  on behalf of 
Kerry Bouchard 
Date: Wednesday, May 5, 2021 at 3:20 PM
To: DSpace Technical Support 
Subject: [dspace-tech] How do I create an exclusion list for filter-media?
Caution: This message was sent from outside the University of Manitoba.
We are running into the problem described here: 
http://dspace.2283337.n4.nabble.com/Filter-media-on-PDFs-exported-from-Outlook-causes-a-TikaException-error-and-prevents-Items-from-inde-td4683489.html
 , where the *.pdf.txt files output by the PDF Text Extractor media filter for 
a couple of PDFs in our repository causes indexing to fail for not just the PDF 
full text, but all the associated metadata. (In our case, the PDFs were not 
output from Microsoft Outlook mail folders, but I'm seeing the same 
"org.apache.tika.exception.TikaException: Failed to parse an email message" in 
the dspace log file.)

The posting at the URL above refers to a work-around by creating an exclusion 
list for filter-media. But I can find any documentation on how to create an 
exclusion list. Can someone point me to that?

Thanks, Kerry
--
All messages to this mailing list should adhere to the 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/85e9b754-31d4-4558-8bde-071facdf9d0bn%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YTXPR0101MB08480475F87E87D0014942DEE8599%40YTXPR0101MB0848.CANPRD01.PROD.OUTLOOK.COM.

[dspace-tech] How do I create an exclusion list for filter-media?

[Kerry Bouchard]

We are running into the problem described 
here: 
http://dspace.2283337.n4.nabble.com/Filter-media-on-PDFs-exported-from-Outlook-causes-a-TikaException-error-and-prevents-Items-from-inde-td4683489.html
 
, where the *.pdf.txt files output by the PDF Text Extractor media filter 
for a couple of PDFs in our repository causes indexing to fail for not just 
the PDF full text, but all the associated metadata. (In our case, the PDFs 
were not output from Microsoft Outlook mail folders, but I'm seeing the 
same "org.apache.tika.exception.TikaException: Failed to parse an email 
message" in the dspace log file.)

The posting at the URL above refers to a work-around by creating an 
exclusion list for filter-media. But I can find any documentation on how to 
create an exclusion list. Can someone point me to that?

Thanks, Kerry

-- 
All messages to this mailing list should adhere to the 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/85e9b754-31d4-4558-8bde-071facdf9d0bn%40googlegroups.com.

Re: [dspace-tech] DSpace7b5: Cross-Origin Request Blocked

[Armin Wenz]

I'm sorry. Like so often, I located the error in front of the keyboard.

After your mail I double checked the Common Installation Issues section 
again and the https://wiki.lyrasis.org/display/DSDOC7x/REST+API page. 
And everything seems to be alright.


But what I have overseen was my SSH-tunnel connection.

Just to clarify:
I work on my development PC and had DSpace7-Rest and DSpace-Angular 
running on ports 8080 and 4000.
I afterwards installed DSpace7 on a local server for my collegues to 
access and test it. And that server doesn't have a grafical interface.
Because tomcat and dspace-angular are configured to accept only local 
connections I had set up a tunnel from my development PC to the 
dspace-server (-L 5000:localhost:4000, 4000 was occupied by my local 
installation). And therefore my browser connection was http://localhost:5000

After adding localhost:5000 to rest.cors.allow-origins it works.

With that in mind I also got the installation with apache on top running.

Thanks for your help and may my error help somebody else.



El 4/5/21 a las 16:59, 'Tim Donohue' via DSpace Technical Support escribió:


That's unexpected...but, let me ask a few questions to make sure I 
understand your setup correctly & am not making assumptions.


1) I'm assuming *both*​ the UI and the backend are running on the same 
machine/server?  That's the only way you can run them both on 
'localhost' under HTTP...otherwise, at least the backend needs a valid, 
public URL and be running under HTTPS.

>
2) Is the backend/REST API accessible in your browser at 
http://localhost:8080/server/  ?   It 
should be, as that's the URL your UI is trying to use.

>
3) Could you verify there are no other errors in your Tomcat logs?  
Sometimes if Tomcat throws a major error, it can result in a CORS error 
(as a side effect of the larger error)


Finally, we have started to create a guide for "Common Installation 
Issues".  Check out the advice in that section to see if any of it is 
helpful : 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues 



If you figure it out, please let us know what it was.  We have found a 
variety of scenarios that can result in these sorts of issues (hence the 
guide) and we're trying to document them all.  So far, though, 
the problem has always been a configuration issueso, I'd recommend 
taking a closer look there first.  But, glad to try and offer more 
advice if you are still hitting issues.


Tim


*From:* dspace-tech@googlegroups.com  on 
behalf of Armin Wenz 

*Sent:* Tuesday, May 4, 2021 7:32 AM
*To:* DSpace Technical Support 
*Subject:* [dspace-tech] DSpace7b5: Cross-Origin Request Blocked
Hallo,

Installed DSpace7 beta5 and got tomcat9 running on localhost:8080 and
dspace-angular on localhost:4000

I can reach the HAL Browser, log in and request all the stuff that's there.

I started dspace-angular with yarn run start:dev which ends with
** Angular Live Development Server is listening on localhost:4000, open
your browser on http://localhost:4000/  **
: Compiled successfully.

my environment.dev.ts is

export const environment = {
    ui: {
  ssl: false,
  host: 'localhost',
  port: 4000,
  nameSpace: '/'
    },
    rest: {
  ssl: false,
  host: 'localhost',
  port: 8080,
  nameSpace: '/server'
    },
};

When trying to connect to localhost:4000 with the browser, I see the
DSpace angular header and moving sot. In the developer console I found
the error:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading
the remote resource at http://localhost:8080/server/api 
.


After searching a while I found a similar thread on gihub
(https://github.com/DSpace/dspace-angular/issues/1036 
) and set


rest.cors.allowed-origins = ${dspace.ui.url}, http://localhost:4000 
,

http://localhost:8080 

I did not set proxies.trusted.ipranges according to
https://github.com/DSpace/DSpace/pull/3171 
.


Any ideas what I have missed?
--

Armin Wenz
Universitätsbibliothek Mainz
Leitung Bibliotheksanwendungen
Jakob-Welder-Weg 12
55128 Mainz
Tel.: +49 6131 39-29830
http://www.ub.uni-mainz.de 

--
All messages to this mailing list should adhere to the 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