[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:41:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT028.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:41:14.703Z 08DB70185478ADC4]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 6:39:06 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT018.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:39:14.277Z 08DB6FB9697DEEB3]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:37:03 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT051.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:37:11.592Z 08DB6F5348807927]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:35:01 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT006.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:35:08.978Z 08DB6FE866DCEC8F]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 6:33:03 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT008.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:33:11.974Z 08DB700CCE66AC75]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 6:31:03 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT033.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:31:11.442Z 08DB7081D7209488]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:29:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT035.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:29:13.728Z 08DB70479F61807F]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 6:26:28 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT004.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:26:59.224Z 08DB70BADF33D68E]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 6:24:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT066.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:24:10.400Z 08DB700D7A2FF75A]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:22:09 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT056.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:22:17.769Z 08DB70C9E4663E82]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:20:01 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT034.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:20:08.744Z 08DB708748325401]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:18:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT008.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:18:20.780Z 08DB700CCE64C31F]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 6:16:03 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT037.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:16:26.840Z 08DB70100E35B024]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:14:01 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT046.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:14:09.240Z 08DB6BD972625887]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:12:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT030.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:12:32.991Z 08DB70BB8B1482DB]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 6:10:01 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT044.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:10:09.359Z 08DB6FA34BA34429]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 6:08:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT061.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:08:11.416Z 08DB6F5EBDB3169D]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:06:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT020.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:06:23.936Z 08DB6E304D23220D]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:04:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT037.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:04:16.885Z 08DB70100E33D153]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:02:07 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT017.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:02:15.824Z 08DB7008AAF43646]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:00:21 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT036.eop-EUR02.prod.protection.outlook.com 
2023-06-19T16:00:29.784Z 08DB70B16F2C7DED]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 3:59:10 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT013.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:59:19.747Z 08DB6F7E870C15E8]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:57:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT025.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:57:10.462Z 08DB7011791DC4B4]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:55:19 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT018.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:55:27.147Z 08DB70D7D44F0B31]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:53:14 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT034.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:53:22.503Z 08DB7087482E60A9]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:51:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT029.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:51:11.677Z 08DB70AD7E962A94]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 3:49:07 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT053.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:49:16.574Z 08DB6FD7C0FC4897]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 3:44:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT041.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:44:10.337Z 08DB702E4881830C]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 3:42:23 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT021.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:42:31.206Z 08DB70BAD349DC9D]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 3:40:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT026.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:40:29.525Z 08DB6FF80B4ED3AE]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:38:22 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT042.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:38:30.365Z 08DB703B4E9503B0]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:35:01 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT007.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:35:08.971Z 08DB7000C5B9DEC3]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:33:01 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT011.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:33:09.254Z 08DB6FA5B22E91BA]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:31:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT061.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:31:09.767Z 08DB7000D7DBEFE9]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:29:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT008.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:29:10.029Z 08DB700CCE5DC6E3]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:27:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT059.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:27:45.735Z 08DB6F2B226446FE]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:25:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT035.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:25:11.025Z 08DB70A0EEEC716B]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 3:24:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT065.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:24:10.198Z 08DB6F51DD48A1F4]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:22:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT049.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:22:09.918Z 08DB6BE97108B8B7]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:20:13 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT048.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:20:25.783Z 08DB7085947C0F58]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 3:18:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT027.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:18:11.000Z 08DB6FF9ACAC5636]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 3:16:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT047.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:16:20.699Z 08DB6FB3EB24C261]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:14:04 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT028.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:14:12.724Z 08DB709FA45C6510]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:12:26 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT021.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:12:35.360Z 08DB70BAD345D89D]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 3:10:01 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT051.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:10:08.673Z 08DB6F5348745799]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 3:07:59 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT019.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:08:07.636Z 08DB701C5CEBBEDA]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 5:05:01 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT032.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:05:08.945Z 08DB70D4872FB18C]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 3:02:53 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT006.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:03:00.795Z 08DB6FE866CFCEE3]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 3:00:13 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT006.eop-EUR02.prod.protection.outlook.com 
2023-06-19T15:00:29.962Z 08DB6FE866CF412D]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 2:58:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT016.eop-EUR02.prod.protection.outlook.com 
2023-06-19T14:58:11.979Z 08DB6F2FFCFB4268]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 2:56:01 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT054.eop-EUR02.prod.protection.outlook.com 
2023-06-19T14:56:27.033Z 08DB7028825E1EE3]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 2:54:01 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT038.eop-EUR02.prod.protection.outlook.com 
2023-06-19T14:54:20.455Z 08DB6FF99837EC80]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:52:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT035.eop-EUR02.prod.protection.outlook.com 
2023-06-19T14:52:10.247Z 08DB70479F536DEB]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:50:23 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT068.eop-EUR02.prod.protection.outlook.com 
2023-06-19T14:50:30.849Z 08DB70669E22BF93]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 2:48:03 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT022.eop-EUR02.prod.protection.outlook.com 
2023-06-19T14:48:32.365Z 08DB6EF9CF6D53CC]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, deliveryreport.txt, originalmail.eml, 
> originalmail.eml, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:46:03 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [DB5EUR02FT031.eop-EUR02.prod.protection.outlook.com 
2023-06-19T14:46:38.323Z 08DB709C5142246B]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, deliveryreport.txt, originalmail.eml, originalmail.eml, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:44:03 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [VI1EUR02FT028.eop-EUR02.prod.protection.outlook.com 
2023-06-19T14:44:11.892Z 08DB70185466BB35]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> deliveryreport.txt, originalmail.eml, originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 4:42:02 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT019.eop-EUR02.prod.protection.outlook.com 
2023-06-19T14:42:11.494Z 08DB6E1A42C3A339]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, deliveryreport.txt, 
> originalmail.eml, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

[Postmaster (Jira)]

 [ 
https://issues.apache.org/jira/browse/GROOVY-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Postmaster updated GROOVY-2456:
---
Attachment: deliveryreport.txt
originalmail.eml

This message was created automatically by email delivery software.

Could not deliver an email to at least one recipient.


Message sent on 6/19/2023 2:40:01 PM

Subject: [jira] [Updated] (GROOVY-2456) Support in-Keyword for Strings

Message-Id: 

Sender: j...@apache.org


The affected recipients are:

bernd.schif...@akquinet.de  - 550 5.4.1  Recipient address rejected: Access 
denied. AS(201806281) [AM0EUR02FT066.eop-EUR02.prod.protection.outlook.com 
2023-06-19T14:40:04.674Z 08DB700D7A20A083]


> Support in-Keyword for Strings
> --
>
> Key: GROOVY-2456
> URL: https://issues.apache.org/jira/browse/GROOVY-2456
> Project: Groovy
>  Issue Type: New Feature
>  Components: groovy-jdk
>Affects Versions: 1.5.1
>Reporter: Bernd Schiffer
>Priority: Major
>  Labels: breaking, breaking_change
> Attachments: deliveryreport.txt, originalmail.eml
>
>
> assert 'abc'.contains('a') //1
> assert 'a' in ('abc'as List) //2
> assert 'a' in 'abc' //3 this breaks
> You ask a string if a substring is contained in it (//1). You can do that 
> with the in-Keyword with Lists (//2), too. But you can't do this with the 
> in-Keyword with Strings. It would be a consistent behaviour from Groovy if 
> you could do //3.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[pydotorg-www] Delivery report

[postmaster]

Hello, this is the mail server on localhost.equibowen.com.

I am sending you this message to inform you on the delivery status of a
message you previously sent.  Immediately below you will find a list of
the affected recipients;  also attached is a Delivery Status Notification
(DSN) report in standard format, as well as the headers of the original
message.

delivery failed; will not continue trying
Reporting-MTA: dns;localhost.equibowen.com
X-PowerMTA-VirtualMTA: localhost0.equibowen.com
Received-From-MTA: dns;br-motors.ch (84.38.134.111)
Arrival-Date: Mon, 5 Jun 2023 04:20:44 -0400

Final-Recipient: rfc822;pydotorg-www@python.org
Action: failed
Status: 5.7.1 (delivery not authorized)
Remote-MTA: dns;mail.python.org (188.166.95.178)
Diagnostic-Code: smtp;554 5.7.1 : Sender address rejected: This address never sends e-mail Contact your postmaster/admin for assistance. Please provide the following information in your problem report: time (Jun 05 07:01:33) and client (178.210.229.52).
X-PowerMTA-BounceCategory: policy-related
From: Email Server
To: pydotorg-www@python.org
Subject: python.org Warning: Password Expired
Date: 05 Jun 2023 11:20:44 +0300
Message-ID: <20230605112044.a96b3f8b418c2...@python.org>
MIME-Version: 1.0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
___
pydotorg-www mailing list
pydotorg-www@python.org
https://mail.python.org/mailman/listinfo/pydotorg-www

[Geoserver-users] Olevererbart:: Re: GeoServer 2.23 - Unable to get layer groups with mode Named Tree in GetCapabilities

[postmaster]

mx.google.com avvisade ditt meddelande till följande e-postadresser:

danilosfigue...@gmail.com
Ditt meddelande levererades inte eftersom mottagarens e-postleverantör avvisade 
det.


mx.google.com gav det här felet:
This mail is unauthenticated, which poses a security risk to the sender and 
Gmail users, and has been blocked. The sender must authenticate with at least 
one of SPF or DKIM. For this message, DKIM checks did not pass and SPF check 
for [lists.sourceforge.net] did not pass with ip: [2a01:111:f400:7e8c::201]. 
The sender should visit 
https://support.google.com/mail/answer/81126#authentication for instructions on 
setting up authentication. hy4-20020a1709068a6400b00973943e93efsi8876304ejc.237 
- gsmtp







Diagnostisk information för administratörer:

Genererande server: CPUPR80MB7559.lamprd80.prod.outlook.com

danilosfigue...@gmail.com
mx.google.com
Remote server returned '550-5.7.26 This mail is unauthenticated, which poses a 
security risk to the 550-5.7.26 sender and Gmail users, and has been blocked. 
The sender must 550-5.7.26 authenticate with at least one of SPF or DKIM. For 
this message, 550-5.7.26 DKIM checks did not pass and SPF check for 
[lists.sourceforge.net] 550-5.7.26 did not pass with ip: 
[2a01:111:f400:7e8c::201]. The sender should 550-5.7.26 visit 550-5.7.26 
https://support.google.com/mail/answer/81126#authentication for 550 5.7.26 
instructions on setting up authentication. 
hy4-20020a1709068a6400b00973943e93efsi8876304ejc.237 - gsmtp'

Ursprungshuvuden:

Received: from CPWPR80MB6274.lamprd80.prod.outlook.com (2603:10d6:103:131::9)
 by CPUPR80MB7559.lamprd80.prod.outlook.com (2603:10d6:103:273::13) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6455.22; Thu, 1 Jun
 2023 11:20:09 +
Resent-From: 
Received: from CPWPR80MB6274.lamprd80.prod.outlook.com ([::1]) by
 CPWPR80MB6274.lamprd80.prod.outlook.com ([fe80::ac38:c4dd:b58f:a5ee%6]) with
 Microsoft SMTP Server id 15.20.6433.024; Thu, 1 Jun 2023 11:20:09 +
ARC-Seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=fail;
 
b=OnirFTokhRRQuyOp68VeR/xewoHm+2LkXek6TL4AGlztBEBD/BB7mCOsDtYtbR1SspxBsOZUkfZ4Qx+9VRDgxNS2VgSZ0OhIPSxRzXuYMTMlgDsF60ntpVtTsOeftHPeEpPu3lMO3ulYxodFCSN0iEqXtA1M+0a3vPMRi7of3Cl/GuCPK8VBoC+DHrbUK0nokE+t0ysCnmniYHU7ZrRFI6HkB0E7+cmcHbOBHV1Jj1O43aIUdRNKLewwZYY+TLqO77eaifioa1+1haOHNBqCXFp+SCFQScnFo2MIkFB3/Gxt414sfs9jLqUrzK8Z1jd+LuP9tvVOt1EprL6nxJRMlw==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
 s=arcselector9901;
 
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1;
 bh=8hMXb7qdMApVd9xD2TATGHlbLhdDFDT1YtfZXcAgAqc=;
 
b=XBArkUWa7cM5QJOSLCwXNvSx7XzV9Igq19b61R/DsIlKNfzil7oFEwpuAzg0w5i34UKhAR2tcvVEdeOKQG4dhg6f/zo06rfGCDKZ0BefGaDcTj5OqRpfZ+geHOtFSA2nDYbPJWLGp2CEEUGuMWDkHTUwKIYaTrUTojbpWyGF/qIhhNKkdg09xASO7gkgv8nOp5eSaE02CPlSWl/pBt7ttYVy2pRxI0io57NIW25XuhSq4vPt1xZMTxofnIj8qqE5mIM7yv0lqnk2JXEa2kTy4ckxTmNXL5gbPzfDD+q9OWoAq5lg9D6TLGqkTNAGatP/0cKb/cw8yL+1P57tJs8urQ==
ARC-Authentication-Results: i=2; mx.microsoft.com 1; spf=pass (sender ip is
 216.105.38.7) smtp.rcpttodomain=hotmail.com
 smtp.mailfrom=lists.sourceforge.net; dmarc=pass (p=quarantine sp=none
 pct=100) action=none header.from=lists.sourceforge.net; dkim=fail (signature
 did not verify) header.d=sourceforge.net; dkim=fail (signature did not
 verify) header.d=sf.net; dkim=fail (signature did not verify)
 header.d=varberg.se; arc=fail (47)
Authentication-Results: spf=pass (sender IP is 216.105.38.7)
 smtp.mailfrom=lists.sourceforge.net; dkim=fail (signature did not verify)
 header.d=sourceforge.net;dmarc=pass action=none
 header.from=lists.sourceforge.net;compauth=pass reason=100
Received-SPF: Pass (protection.outlook.com: domain of lists.sourceforge.net
 designates 216.105.38.7 as permitted sender) receiver=protection.outlook.com;
 client-ip=216.105.38.7; helo=lists.sourceforge.net; pr=C
X-IncomingTopHeaderMarker: 
OriginalChecksum:0DA92D4B221B60822023B9CFF932E5F4F288DBFD1E13D6D6A22C916A9DADB15F;UpperCasedChecksum:3EDD726478F8F3CF9494FA19E217F98AA78FA843D05BDDAA6CDC1396579F29F6;SizeAsReceived:12355;Count:61
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
 d=sourceforge.net; s=x; h=MIME-Version:Content-Type:In-Reply-To:References:
 Message-ID:Date:Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:
 Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
 Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:
 List-Subscribe:List-Post:List-Owner:List-Archive;
 bh=u4C8V6aROZ4ZbV0Jmtl4A1vLo5WcNY6O3rrFizddtJ4=; b=KuuO9Io08UyBfjsFvIj28GhPUi
 RQLomZwECjSzdDnho1lJHq/CKO3Ali3ORs+s7vwXGOplAKz91G0JMyBE7RW/mx63U56y5UtiXd3zw
 k6z+qCGNG6tC84qOI/Ux4F9Ej/f7kaCvRwsl0gO9hwAwQ72KO1lSUXiYrBYtqnfCwSFk=;
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; 

Re: Separate location for files served by php-fpm

[Palvelin Postmaster via nginx]

> On 15. May 2023, at 17.15, Francis Daly  wrote:
> 
> On Mon, May 15, 2023 at 12:46:14PM -1000, Palvelin Postmaster via nginx wrote:
>>> On 8. May 2023, at 8.49, Palvelin Postmaster via nginx  
>>> wrote:
> 
> Hi there,
> 
>>> I use php-fpm together with nginx.
>>> 
>>> My PHP app serves files which have hashed filenames and no filename 
>>> extension from a specific subdirectory url, e.g 
>>> /files/hash/31b4ba4a0dc6536201c25e92fe464f85
>>> 
>>> I would like to be able to set, for example, a separate ’expires’ value to 
>>> these files with nginx (using a separate location block?). Is that 
>>> achiavable?
> 
> In principle, yes. So long as the requests use different urls (excluding
> query string).
> 
> In practice: from the words here, it is not entirely clear to me what
> your overall application is doing.
> 
> Maybe you can have a location{} dedicated to these file-requests; or maybe
> it would be "cleaner" for the php side to add the extra Expires header.
> 
> Can you show one or two sample requests that are made to nginx that you
> do want to have this extra Expires header; and one or two that you do
> not want to have this extra Expires header?
> 
> The aim is to come up with a location{} block that matches only the
> requests that you want, if that is possible.

Francis,

thanks for your response!

I wonder if you saw the server block that I had included in my original 
message? Doesn’t it answer your question regarding all the other requests?

My goal is to serve only requests which include URI /files/hash/* using a 
separate location block. Everything else should be served by the default 
location block I included in my previous message.

--
Palvelin.fi Hostmaster
postmas...@palvelin.fi
___
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx

Re: Separate location for files served by php-fpm

[Palvelin Postmaster via nginx]

Can anyone help me with this?


> On 8. May 2023, at 8.49, Palvelin Postmaster via nginx  
> wrote:
> 
> Hi all!
> 
> I use php-fpm together with nginx.
> 
> My PHP app serves files which have hashed filenames and no filename extension 
> from a specific subdirectory url, e.g 
> /files/hash/31b4ba4a0dc6536201c25e92fe464f85
> 
> I would like to be able to set, for example, a separate ’expires’ value to 
> these files with nginx (using a separate location block?). Is that achiavable?
> 
> server {
>   listen 443 ssl http2;
>   server_name my.site.com;
>   root /var/www/vhosts/my.site.com/site/;
>   set $ngspage /index.php?ngspage=$uri$is_args&$args;
> 
>   # PHP file processing configuration
>   location ~ [^/]\.php(/|$) {
>   set $location_name php;
> fastcgi_pass php74;
>   include fastcgi_params;
>   fastcgi_index index.php;
> 
>   # Regex to split $uri to $fastcgi_script_name and $fastcgi_path
>   fastcgi_split_path_info ^(.+?\.php)(/.*)$;
> 
>   # Bypass the fact that try_files resets $fastcgi_path_info
>   # see: http://trac.nginx.org/nginx/ticket/321
>   set $path_info $fastcgi_path_info;
> 
>   # Check that the PHP script exists before passing it
>   try_files $ngspage $fastcgi_script_name =404;
>   }
___
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx

Re: Window function for get the last value to extend missing rows

[postmaster]

Am 12.05.23 um 13:04 schrieb Durumdara:

[...]

The LAG function seems to be ok, but how to handle if more than two periods
are missing?

03:00 10
03:01 NULL
03:02 NULL
03:03 NULL
03:04 11
03:05 13

[...]

and how do you think about NULL in first(and second/third) row?

Re: RIP Dan Matyola

[Postmaster]

Man, that's sad news. Dan was one of those PDML'ers I'd always wanted
to meet in person.


Bruce Walker wrote:

>Facebook alerted me today of messages about the passing of Dan
>Matyola, May 2, 2023, at 81 years of age.
>
>I'm only a "FB friend" but we've chatted a bunch since I joined the
>list and I know he was a very long time PDML member. His last reply to
>the list was also May 2, amazingly.
>
>I located a link to his obit:
>https://www.cusickfuneralhome.com/obituaries/Daniel-Matyola?obId=27875827
>
>His FB profiles -- which his cousin has been adding updates to -- is here:
>https://www.facebook.com/daniel.j.matyola
>https://www.facebook.com/dan.matyola
>
>I liked Dan and I know he was a steadfast PDML contributor. He'll be missed.
>
>-- 
>-bmw
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Separate location for files served by php-fpm

[Palvelin Postmaster via nginx]

Hi all!

I use php-fpm together with nginx.

My PHP app serves files which have hashed filenames and no filename extension 
from a specific subdirectory url, e.g 
/files/hash/31b4ba4a0dc6536201c25e92fe464f85

I would like to be able to set, for example, a separate ’expires’ value to 
these files with nginx (using a separate location block?). Is that achiavable?

server {
   listen 443 ssl http2;
   server_name my.site.com;
   root /var/www/vhosts/my.site.com/site/;
   set $ngspage /index.php?ngspage=$uri$is_args&$args;

   # PHP file processing configuration
   location ~ [^/]\.php(/|$) {
   set $location_name php;
fastcgi_pass php74;
   include fastcgi_params;
   fastcgi_index index.php;

   # Regex to split $uri to $fastcgi_script_name and $fastcgi_path
   fastcgi_split_path_info ^(.+?\.php)(/.*)$;

   # Bypass the fact that try_files resets $fastcgi_path_info
   # see: http://trac.nginx.org/nginx/ticket/321
   set $path_info $fastcgi_path_info;

   # Check that the PHP script exists before passing it
   try_files $ngspage $fastcgi_script_name =404;
   }
___
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx

dpdk-pdump cannot init tailq as secondary process

[postmaster]

Hello

I follow what it is explained on that page

https://doc.dpdk.org/guides/tools/pdump.html

to call rte_pdump_init in my application (and checking the result, if not ok 
exit with failure), but once I ran dpdk-pdump I got


dpdk-pdump  -l 9 -- --pdump 'port=0,queue=*,rx-dev=/tmp/rx.pcap'
EAL: Detected CPU lcores: 24
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_1027261_2ca45105bcf34
EAL: Selected IOVA mode 'PA'
EAL: VFIO support initialized
EAL: Cannot initialize tailq: RTE_FIB
Tailq 0: qname:, tqh_first:0x17fe12640, tqh_last:0x17fe12640
Tailq 1: qname:, tqh_first:0x17ffd7380, tqh_last:0x17ffd7380
Tailq 2: qname:, tqh_first:(nil), tqh_last:0x144e8
Tailq 3: qname:, tqh_first:(nil), tqh_last:0x14518
Tailq 4: qname:, tqh_first:(nil), tqh_last:0x14548
Tailq 5: qname:, tqh_first:(nil), tqh_last:0x14578
Tailq 6: qname:, tqh_first:(nil), tqh_last:0x145a8
Tailq 7: qname:, tqh_first:(nil), tqh_last:0x145d8
Tailq 8: qname:, tqh_first:(nil), tqh_last:0x14608
Tailq 9: qname:, tqh_first:(nil), tqh_last:0x14638
Tailq 10: qname:, tqh_first:(nil), tqh_last:0x14668
Tailq 11: qname:, tqh_first:(nil), tqh_last:0x14698
Tailq 12: qname:, tqh_first:(nil), tqh_last:0x146c8
Tailq 13: qname:, tqh_first:(nil), tqh_last:0x146f8
Tailq 14: qname:, tqh_first:(nil), tqh_last:0x14728
Tailq 15: qname:, tqh_first:(nil), tqh_last:0x14758
Tailq 16: qname:, tqh_first:(nil), tqh_last:0x14788
Tailq 17: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 18: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 19: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 20: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 21: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 22: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 23: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 24: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 25: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 26: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 27: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 28: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 29: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 30: qname:<>, tqh_first:(nil), tqh_last:(nil)
Tailq 31: qname:<>, tqh_first:(nil), tqh_last:(nil)
EAL: FATAL: Cannot init tail queues for objects
EAL: Cannot init tail queues for objects
PANIC in main():
Cannot init EAL
0: ./dpdk-pdump (rte_dump_stack+0x32) [55e895dd03da]
1: ./dpdk-pdump (__rte_panic+0xf1) [55e895da1a3b]
2: ./dpdk-pdump (main+0x1c8) [55e8958c0c42]
3: /lib/x86_64-linux-gnu/libc.so.6 (7efe39e0+0x29d90) [7efe39e29d90]
4: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [7efe39e29e40]
5: ./dpdk-pdump (_start+0x25) [55e8958ba535]
Abandon

How I should build dpdk please to make my app properly linked to rte libraries 
and get init done for the second process dpdk-pdump ?

Looking inside the archive user mails, I got this link


http://mails.dpdk.org/archives/users/2022-January/006115.html




But how do I enable

 ethedev rx/tx callbacks

as it is written please ?

 should I just add in the build/rte_config.h #define RTE_ETHDEV_RXTX_CALLBACKS 
1 ?

With meson I dont understand how to enable features unlikely makefile / 
configure as formerly


thank you in advance for your clues


Karim

[mailop] A guy from GMX at the list?

[Postmaster florian-pankerl.tk via mailop]

Hi!

Is there a guy from GMX.de at the list?

We sent business-related mails (order-confirmation, invoice etc.) for 
onlineshops of our customers. For one of the shops GMX seems to be a 
black hole - the GMX-Servers accepts the mails without any error and 
then the mails disappears.


I wrote via the form at https://postmaster.gmx.net two days ago - but no 
reaction.


Regards,
Florian Pankerl

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: Hi kids!

[Postmaster]

Paul Sorenson wrote:

>Glad to have you back.  Sorry to hear about Lisa's mom.

Thanks. She was in California staying with Lisa's sister in 2020 when
she started having problems. A visit to the local Urgent Care and an
ultrasound revealed a mass on the pancreas and Lisa said "get your ass
to Boston NOW" (or words to that effect). She arrived *two days*
before Logan airport shut down for the peak of the pandemic. Diagnosed
at age 92 and made it well past her 94th birthday. An amazing woman.

Of course, having a cancer patient in the house meant Lisa and I were
"extra locked down" because we couldn't afford to bring Covid back
home to her. Very stressful couple of years. We've really spent the
last 6 months or so coming out of our shell.
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

[Bug c/108580] gcc treats shifts as signed operation, does wrong promotion

[postmaster at raasu dot org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108580

--- Comment #8 from postmaster at raasu dot org ---
I know enough C that you can't write code like:

int i = 0x;

This is not equal to:

int i = -1;

or

int i = (-1);


---
Largest literal you can assign to "int" is "0x7FFF". Any larger value must
be either result of expression or another variable, otherwise it will result in
"arithmetic" overflow warning.

Some literals and operations are inherently unsigned, no matter what generic
rules say. As I already said, writing "1u << bits" would be incorrect, and
strict-conforming or "pedantic" compiler would throw warning as the types don't
match and implicit conversion doesn't happen with sizes larger than 32 bits.
Type modifiers are otherwise case-insensitive, but don't support mixed-case.

C standard doesn't even mention anything about "size_t" or have type modifier
for it. Even though printf() and alike support "%z", it is considered extension
and will be rejected when using strict/pedantic mode.

[Bug c/108580] gcc treats shifts as signed operation, does wrong promotion

[postmaster at raasu dot org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108580

--- Comment #6 from postmaster at raasu dot org ---
There is wrong assumption again... Literal "1" is always unsigned as there is
no implicit signed literals, even though there is explicit signed literals...
When somebody writes "-1" it is treated as expression "0 - 1", not a literal
"negative one"... This is because subtract operator has higher precedence.
Empty literal always equals to literal "0".

[Bug c/108580] gcc treats shifts as signed operation, does wrong promotion

[postmaster at raasu dot org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108580

--- Comment #4 from postmaster at raasu dot org ---
I'm not mixing things... The assembly code clearly says it's using 32-bit
shift. Both with 32-bit and 64-bit architectures by default left-hand side of
shift operation is 32 bits (EAX instead of RAX) and right-hand size is 8 bits
(CL instead of CX, ECX or RCX). 

Using "1U << bits" to explicitly force unsigned 32-bit shift would be incorrect
code. "(size_t)1 << bits", which is also "incorrect" code, would surprisingly
result in correct code generation with both 32-bit and 64-bit targets.

Result of any left shift involving negative numbers, including left-shifting
non-zero bit to highest bit of signed integer, is undefined.

[Bug c/108580] gcc treats shifts as signed operation, does wrong promotion

[postmaster at raasu dot org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108580

--- Comment #2 from postmaster at raasu dot org ---
If I try to shift to highest bit of signed type, the compiler will reject the
code and that is correct behaviour. The point here is that left-hand side of
the shift operation is by default same size as "int", as in 32 bits, which
means it can't be promoted to "int" again. 

This behaviour is same with gcc, clang and Visual C++, but Visual C++ correctly
gives warning that the code is ambiguous (exact message is "Arithmetic
overflow"), however it's also C++ compiler, which might validate the code with
C++ rules, not C.

[Bug c/108580] New: gcc treats shifts as signed operation, does wrong promotion

[postmaster at raasu dot org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108580

Bug ID: 108580
   Summary: gcc treats shifts as signed operation, does wrong
promotion
   Product: gcc
   Version: 12.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c
  Assignee: unassigned at gcc dot gnu.org
  Reporter: postmaster at raasu dot org
  Target Milestone: ---

I have a simple program that fails to compile correctly on any common compiler:

int main()
{
   int bits = 8;
   char* a = (char*)malloc(1 << bits);
   char* b = (char*)malloc(1 << bits);
   memcpy(b, a, 1 << bits);
   return 0;
}

when assembled with "gcc -S", the result is

main:
.LFB6:
.cfi_startproc
endbr64
pushq   %rbp
.cfi_def_cfa_offset 16
.cfi_offset 6, -16
movq%rsp, %rbp
.cfi_def_cfa_register 6
subq$32, %rsp
movl$8, -20(%rbp)
movl-20(%rbp), %eax
movl$1, %edx
movl%eax, %ecx
sall%cl, %edx
movl%edx, %eax
cltq
movq%rax, %rdi
callmalloc@PLT
movq%rax, -16(%rbp)
movl-20(%rbp), %eax
movl$1, %edx
movl%eax, %ecx
sall%cl, %edx
movl%edx, %eax
cltq
movq%rax, %rdi
callmalloc@PLT
movq%rax, -8(%rbp)
movl-20(%rbp), %eax
movl$1, %edx
movl%eax, %ecx
sall%cl, %edx
movl%edx, %eax
movslq  %eax, %rdx
movq-16(%rbp), %rcx
movq-8(%rbp), %rax
movq%rcx, %rsi
movq%rax, %rdi
callmemcpy@PLT
movl$0, %eax
leave
.cfi_def_cfa 7, 8
ret
.cfi_endproc

The part that is incorrect is:

sall%cl, %edx
movl%edx, %eax
cltq
movq%rax, %rdi

It should zero-extend before the shift, but instead it sign-extends after the
shift... Bit shifting is always unsigned operation. It correctly determines the
function requires 64-bit parameter, but fails to determine it's unsigned.
Integer promotion rules say that unsigned type in expression must be promoted
to larger unsigned type if it can hold the result. As bit shift is unsigned
operation, the temporary should also be unsigned.

Stock gcc headers don't have UINTPTR_C() macro which could be used to
explicitly cast the constant "1" to pointer size to give hint that the shift is
indeed unsigned operation.

gcc version is: gcc (Ubuntu 12.2.0-3ubuntu1) 12.2.0

[pydotorg-www] Delivery report

[postmaster]

Hello, this is the mail server on fmostmcl.questairinc.com.

I am sending you this message to inform you on the delivery status of a
message you previously sent.  Immediately below you will find a list of
the affected recipients;  also attached is a Delivery Status Notification
(DSN) report in standard format, as well as the headers of the original
message.

delivery failed; will not continue trying
Reporting-MTA: dns;fmostmcl.questairinc.com
X-PowerMTA-VirtualMTA: fmostmcl0.questairinc.com
Received-From-MTA: dns;msa.hinet.net (109.248.150.192)
Arrival-Date: Mon, 26 Sep 2022 09:25:49 +

Final-Recipient: rfc822;pydotorg-www@python.org
Action: failed
Status: 5.7.1 (delivery not authorized)
Remote-MTA: dns;mail.python.org (188.166.95.178)
Diagnostic-Code: smtp;554 5.7.1 : Sender address rejected: This address never sends e-mail Contact your postmaster/admin for assistance. Please provide the following information in your problem report: time (Sep 26 07:57:26) and client (81.161.229.85).
X-PowerMTA-BounceCategory: policy-related
From: pydotorg-www@python.org
To: pydotorg-www@python.org
Subject: IT HelpDesk: Password expired
Date: 26 Sep 2022 11:25:49 +0200
Message-ID: <20220926112549.9c50d4b581d0d...@python.org>
MIME-Version: 1.0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
___
pydotorg-www mailing list
pydotorg-www@python.org
https://mail.python.org/mailman/listinfo/pydotorg-www

未送达: 57N7p6mA

[postmaster]

向以下收件人或组传递邮件失败:

07 (0...@wstoy.com)
找不到您输入的电子邮件地址。请检查收件人的电子邮件地址并尝试重新发送邮件。如果问题仍然存在，请与您的电子邮件管理员联系。








供管理员使用的诊断信息:

生成服务器: email01.wstoy.com

0...@wstoy.com
Remote Server returned '550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient 
not found by SMTP address lookup'

原始邮件头:

Received: from email01.wstoy.com (172.10.40.32) by email01.wstoy.com
 (172.10.40.32) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.28; Tue, 9 Aug
 2022 07:46:56 +0800
Received: from lists.alioth.debian.org (60.185.131.47) by email01.wstoy.com
 (172.10.40.31) with Microsoft SMTP Server id 15.1.2375.28 via Frontend
 Transport; Tue, 9 Aug 2022 07:46:55 +0800
X-GUID: 4AD3F31C-1811-45D9-A70B-FC2732EDF11C
X-Has-Attach: yes
From: 809604Vq 
Subject: 57N7p6mA
To: 07 <0...@wstoy.com>
Content-Type: multipart/mixed; charset="GB2312";
boundary="=_986_NextPart325650791060_="
MIME-Version: 1.0
Date: Tue, 9 Aug 2022 07:46:56 +0800
Message-ID: <202208090746368789...@lists.alioth.debian.org>
X-Mailer: Foxmail 7, 2, 5, 140[cn]
Return-Path: pkg-grass-de...@lists.alioth.debian.org
Received-SPF: None (email01.wstoy.com: pkg-grass-de...@lists.alioth.debian.org
 does not designate permitted sender hosts)

Reporting-MTA: dns;email01.wstoy.com
Received-From-MTA: dns;lists.alioth.debian.org
Arrival-Date: Mon, 8 Aug 2022 23:46:56 +

Final-Recipient: rfc822;07@WSTOY.COM
Action: failed
Status: 5.1.10
Diagnostic-Code: smtp;550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup
X-Display-Name: 07

--- Begin Message ---

	9rGLgK9


	 


	01o4J1

--- End Message ---
___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel

系统退信/Systems bounce

[postmaster]

 


抱歉，您的邮件被退回来了……/Sorry, your mail is returned...
 

 
 

原邮件信息/

Original e-mail message :
 
 

 
　 
 
时间/Time : 
2022-05-27 05:43:28 
 
主题/Subject : 
你有一笔未付款项。需要清偿债务。
 
 
收件人/To : 
fan...@email.cn 
 
 
 
 
 
 
 

退信原因/

Bounce reason :
 
 
 
收件人地址不存在或者有误。 
This error indicates the recipient address never exists, or has been disabled or deleted. 
SMTP error, RCPT TO: (CM)Host (110.43.218.170) RCPT TO said 550 User not found: fan...@email.cn 
 
 
 
 
 

建议解决方案/

Proposed Solution :
 
 

 
邮差温馨提示：请检查对方地址输入是否有误，或者以其他方式联系收件方核对正确地址，或者将信件发送到收件方其他邮箱地址。/Warm tips:Please  check if it is misspelled. If there are no mistakes,we suggest you Contact the recipient and verify the address again or send to recipient's other available address.
如果您有其他退信问题，欢迎向客服中心联系/If you have any other bounce problems, please contact customer service center
 

 
 

   
   

退信代码/

Bounce Code :


	  user not found

  
 
 




This message is generated by Coremail.您收到的是来自 Coremail 专业邮件系统的信件.



Final-Recipient: rfc822; fangwj@email.cn
Action: failed
Status: 5.0.0
Diagnostic-Code: SMTP; SMTP error, RCPT TO: (CM)Host (110.43.218.170) RCPT TO said 550 User not found: fangwj@email.cn
--- Begin Message ---

 
(fan...@email.cn)11000
 1Gw4XUbdBDe8GxKpqr6TmQXsjsfR7dcbaP 
482>
 
>
 

 > 
>
 
>
 
TeamViewer>
 

 

 
...--- End Message ---

未�鬟f的主旨: [SPAM] 你有一笔未付款项。需要清偿债务。

[postmaster]

�鬟f至下列收件者或群�M失��:

0d18a4ea00019...@kmt.org.tw
找不到您��入的��子�]件地址。���z查收件者的��子�]件地址，然後�L��重新�魉袜]件。如果���}持�m�l生，���B�j支援人�T。







系�y管理�T的�\�噘Y��:

�a生的伺服器: ekmt.org

0d18a4ea00019...@kmt.org.tw
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

原始�]件�祟^:

Received: from kmt.org.tw (172.16.1.81) by Mail2.ekmt.org (10.1.5.221) with
 Microsoft SMTP Server id 14.3.301.0; Wed, 25 May 2022 22:22:41 +0800
IronPort-SDR: 
WWnGaW/K+y14InQ1O1+SbOaXqXkTZ2ZbUvqNGaUcr/WHB5vX40M8gvCK3q+y4djr1JKfLFFpwv
 xzIQRUbLix/g==
IronPort-PHdr: =?us-ascii?q?A9a23=3AY1+/oRwp4gUCzHrXCzIPylBlVkEcU1XcAAcZ5?=
 =?us-ascii?q?9Idhq5Udez7ptK+ZheZuqgm0QOBdL6YwsoMs/DRvaHkVD5Iyre6m1dGTqZxU?=
 =?us-ascii?q?QQYg94dhQ0qDZ3NI0T6KPn3c35yR5waBxdq8H6hLEdaBtv1aUHMrX2u9z4SH?=
 =?us-ascii?q?Qj0ORZoKujvFYPekcq62/qw9pDTbAlFhDWwaq5uIRurqgncqtMYipZ4JKYrz?=
 =?us-ascii?q?RvJrHpIe+BIym5tOFmegRXy6Nqu8ZB66yhftO4v+MBGUaXhYqQ3VqdYAyg8M?=
 =?us-ascii?q?2A0/8Lkqx/ORhaS63QGU2UWlh1IAxXZ7Bz/Q5z8vDf2uvZ71SKHJsL4Vao7W?=
 =?us-ascii?q?Si+4KdrTBLjlSMLOjAl/G3Lj8B9ir9QrhC8qBxl24PaYJ+bOudwcK3ectwVW?=
 =?us-ascii?q?W1PXtpIWSFaGIywc4QPAvIfMepEsYXwoUYFoxukBQmrAePi0jhFhmT23K0hz?=
 =?us-ascii?q?+QuDwTG0xE7EtIWqnvbsNb1O70dUe+r16nE1yjMYO1N1jf88ofIdAotofaWX?=
 =?us-ascii?q?bJ/aMfcz1QkGAzZgFuKs4PlIy+V2foXs2id9+dtVuOihmEjpgx/rDWixtogh?=
 =?us-ascii?q?pfGiI8X11zI6St3zok3KNC5RkB2YsKoHIZOuyybOIV7TMMvTn10tSs4yrMKp?=
 =?us-ascii?q?4C2cS4Xw5ok3x7Sc+GLfomG7x75W+ucIy10iG97dL6liRu/91WrxPDkVsau1?=
 =?us-ascii?q?VZEszdFncLOtn8TyxPT9tCKR+Fn80q7wzuCzRre5/teLEwuj6fWMYQsz6Qqm?=
 =?us-ascii?q?5cJq0jOGDL9ll/sg6+MbEok//Cl6+T5bbXioZ+RL5F7iwDgPasyncy/BP40P?=
 =?us-ascii?q?hUPUmWV4+ix27/u8VfkTLlUlPE6jrPVvZ7AKcsFp6+2HRNa0oEm6xqlEzim1?=
 =?us-ascii?q?9EYkWMELFJFYB6Hjo7pNE/SIP3gEPuyglqhnC1kyv3EJLHtH4vBImLNnbv5e?=
 =?us-ascii?q?LZy8U9cyA49zdBF4JJUD6kMIOnzW0/qqNzXEBo5PBGvzub/EtpyyoAeVniAA?=
 =?us-ascii?q?qCHK6Peq0KH6fw0LOmNfoAVvizxK/8/5/7hlXM5n0QScrGz3ZQLcHC4AuhmI?=
 =?us-ascii?q?0KBbHbxmtsBC3sFvhIiTOz2j12PSSJfaGuvU68//D42B5ypAp3fSoyxnLCNw?=
 =?us-ascii?q?SO2HpNZa21HEV2MEnLod5meV/cLciKSLdVtkiAKVOvpd4h0gUmi7V/zl7dud?=
 =?us-ascii?q?rKMo3wW6czL191poerJmlcu6monId6a1jTZVHBvgm4NSxcu1at8qENw0RGP3?=
 =?us-ascii?q?KJ5ivoeEsZcsaAaGjwmPILRmrUpQ+v5XRjMK4zRED6b?=
IronPort-Data: =?us-ascii?q?A9a23=3AGZsVkahtXaVreu3iqFloDI8CX161pRIKZh0uj?=
 =?us-ascii?q?C45NGQN5FlHY01jehtvW2+FaK7YZjH3co1xbYTg9koOu5HdzIdhSFRv+CtgR?=
 =?us-ascii?q?ChjpJueD7x1DKtR0wB+jCH7ockOA/w2MrEsEehtJpPijkb1WlTehSQkvU24b?=
 =?us-ascii?q?uKU5N/sYkiddyc9IMsSoUoLd9oCv2JdqYPR7zVhGT/Fi5a31FeNg1aYO4+Pg?=
 =?us-ascii?q?k6JgEsHUP/a4Fv0srGiDM2nsmMyl1FNZH4eDayjInD/R88NQLX8G7mFlev/p?=
 =?us-ascii?q?iWCuRo/B9iil/DwdUhMQb660Qqm0yQNHfT9xEEY4HdaPqUTbJLwbW9Mmi6Vk?=
 =?us-ascii?q?tV94M1Evp+5RgoyeKHBkuUUVV9fCS4W0ahuqeSdehBTtuTJlx2aIyO8qxl0N?=
 =?us-ascii?q?2luMdRI87p6CDkWraVJJmxTRhOGm6Sx2r39VvYEuyiJBKEHJ6sSqHxryjSfV?=
 =?us-ascii?q?Kh9B8ycBfyQo4ceh3E9lM1FGvOYbM0cLzlvBCksqiZnYj8/YK/SVs/x7pU0T?=
 =?us-ascii?q?9GURJ95a0b6D6g/ATGdCITQDec=3D?=
IronPort-HdrOrdr: =?us-ascii?q?A9a23=3ARssAw69ZG4ZO59sBSK5uk+DHI+orL9Y04l?=
 =?us-ascii?q?Q7vn2ZKCY1TiX2rayTdZggviMc6wx+ZJhDo7+90cC7KBvhHPVOjLX5SI3SPz?=
 =?us-ascii?q?UO1lHDEGgb1+vfKmHbak/DytI=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D5/wCcOo5i/wMML6NaGQEBAQEBATw?=
 =?us-ascii?q?BAQEBAQEBAQEBAQECAQEBAQEBAQEBAQEeBoFCARoKciMCAQEBAQEBAQFlLAK?=
 =?us-ascii?q?BFwg9Ew0khE6iWIRfhkCBeAECCwEBAQEBAQEBARswBAEBMIRNA4VFAiVLAQI?=
 =?us-ascii?q?EAQEBEgEBBQMCAQcEAYEIE4V1gkEBBAEBAQEDAwMBAQwBg28ZAQZeBQcjIAM?=
 =?us-ascii?q?bGhkNBBMLhH8DgQcGkHOcDAGBBjCBAYRthRGBOwIBAQEBAQEBAQEBhzOCZIJ?=
 =?us-ascii?q?AAgWCPoINgRM4i0mCaAQDCZYDBzoDCQYHBTM1EoEhcQEIBgYHCgUyBgIMGBQ?=
 =?us-ascii?q?EAhMSUwsSAhMMChwODkYZDA8DEgMRAQcCCxIIFSwIAwIDCAMCAy4CAxgJBwo?=
 =?us-ascii?q?DHQgKHBIQFAIEEx8LCAMaHy0JAgQOA0UICwoDEQQDExgLFggQBAYDCS8NKAs?=
 =?us-ascii?q?DFA8BBgMGAgUFAQMLFQMUAwUnBwMhBwsmDQ0EIx0DAwUmAwICGwcCAgMCBhc?=
 =?us-ascii?q?GAgI9AgEuAwooDQgECAQcHh0IDgUFAgcxBQQvAh4EBQYRCQIWAgYEBQIEBBY?=
 =?us-ascii?q?CAhIIAggnGwcWNhkBBRJLBgsJIhwcEBEFBhYDJHgFB0MVRb5ynjakFqhalmi?=
 =?us-ascii?q?iZIUDgVoOgVl9CIMjPxIZD45xjgk6MT4GCw48LxCMWwEB?=
Subject: [SPAM] 
=?utf-8?B?5L2g5pyJ5LiA56yU5pyq5LuY5qy+6aG544CC6ZyA6KaB5riF5YG/5YC65Yqh44CC?=
Received: from ezecom.163.47.12.0.3.ezecom.com.kh ([163.47.12.3])  by
 kmt.org.tw with ESMTP; 25 May 2022 22:18:46 +0800
From: 
To: <0d18a4ea00019...@kmt.org.tw>
Date: Thu, 26 May 2022 02:52:31 +0600
Message-ID: <003a01d8707d$020701f2$28cf6383$@packages.debian.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="=_NextPart_000_0037_01D8707D.0205BCE7"
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acxj8145sxj8145sxj8145sxj8145s==
X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17514
Return-Path: syst...@packages.debian.org

Reporting-MTA: dns;ekmt.org
Received-From-MTA: dns;kmt.org.tw
Arrival-Date: Wed, 25 May 2022 14:22:41 +

Final-Recipient: rfc822;0d18a4ea00019f46@kmt.org.tw
Action: failed
Status: 5.1.1
Diagnostic-Code: smtp;550 5.1.1 

Delivery report

[postmaster]

Hello, this is the mail server on slot0.indaqatar.org.

I am sending you this message to inform you on the delivery status of a
message you previously sent.  Immediately below you will find a list of
the affected recipients;  also attached is a Delivery Status Notification
(DSN) report in standard format, as well as the headers of the original
message.

delivery failed; will 
not continue trying
Reporting-MTA: dns;slot0.indaqatar.org
X-PowerMTA-VirtualMTA: slot00.indaqatar.org
Received-From-MTA: dns;bank-banque-canada.ca (37.49.225.129)
Arrival-Date: Fri, 29 Apr 2022 00:14:42 +

Final-Recipient: rfc822;debian-science-maintainers@lists.alioth.debian.org
Action: failed
Status: 5.0.0 (undefined status)
Remote-MTA: dns;alioth-lists-mx.debian.net (185.73.44.171)
Diagnostic-Code: smtp;550 This message has been identified as spam (scored 12.7). Please contact postmaster if you feel this is in error.
X-PowerMTA-BounceCategory: spam-related
From: lists.alioth.debian.org Support
To: debian-science-maintain...@lists.alioth.debian.org
Subject: Important: debian-science-maintain...@lists.alioth.debian.org You have 5 Pending incoming emails
Date: 29 Apr 2022 02:14:42 +0200
Message-ID: <20220429021442.7152759198754...@lists.alioth.debian.org>
MIME-Version: 1.0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: [tor-relays] TorWeather replacement features

[Postmaster via tor-relays]

How important are private (non-public) ways to subscribe to 
notifications for you? 1
How important are configurable downtime periods to you and what 
timeframe would you choose? 3

How important are recovery notifications (i.e. down -> up) to you? 2

How important would be matrix as a second notification method to you? 3
Would you use one or multiple notification methods at the same time? 
Just email for me.


Thanks,
John C.

On 2022-02-09 08:09 PM, nusenu wrote:


Hi,

I'm currently working on a TorWeather replacement (mainly using a 
byproduct of another project)
that should be helpful for relay operators to get notifications about 
their relay downtimes

and other issues.
I believe such a service will contribute to a more healthy tor network
and better informed operators leading to less relays running on
old vulnerable and end-of-life tor versions.

For those that did not have the chance to use TorWeather in the past
before it died due to lack of a maintainer:
It was a simple software as a service for relay operators that allowed
them to subscribe for email notifications in case their relay dropped
out of consensus (and a few more use-cases).

The service will be for the operator of the relay(s).
Subscribing and notifications will be aggregated by operators,
meaning if multiple relays from a single operator go down at the same 
time,

it will produce a single notification only (instead of one per relay).
If a new relay gets added by an operator no additional steps are
required to get notification for the newly added relays.

You can rate the items below with these levels:
(off-list replies are fine as well)

1 = must have
2 = should have
3 = nice to have

The system will use the email address in your CIISS email field,
which implies it is public. How important are private (non-public) ways 
to subscribe

to notifications for you? (non-public email address)

TorWeather used to have an option where the operator was able to 
specify after

what amount of downtime they would get a notification.
I would simply go with a single static value: "2 consensus are missing 
your relays" (2 hours) -> notify.
How important are configurable downtime periods to you and what 
timeframe would you choose?


I'm primarily focusing on notifications about "changed to the worse" 
(i.e. up -> down; ok -> eol).

How important are recovery notifications (i.e. down -> up) to you?

What would be the next most useful/important notification use-case for 
you after

- relay dropped out of consensus
- relay is running a vulnerable/end-of-life tor release
- relay lost guard/exit flag

The first notification method will be email.
How important would be matrix as a second notification method to you?
Would you use one or multiple notification methods at the same time?

kind regards,
nusenu

0xB77A70C2.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Bug#746255: WhatsApp Inc

[Postmaster CGT]

WhatsApp Inc. 

1601 Willow Road, Menlo Park, Ca 94025 

Spojené štáty americké 



Vážený používateľ WhatsApp: 



Vaše mobilné číslo bolo vybrané medzi šťastnými výhercami programu WhatsApp Inc 
Global Awards. 

Toto je program globálnych ocenení za patronát nad internetovými službami, 
všetci účastníci boli náhodne vybraní z celosvetových adresárov mobilných čísel 
a vaše mobilné číslo sa objaví na zariadení medzi víťazmi. 

Boli ste odmenení peňažnou cenou (900 600,00 EUR) deväťstotisíc šesťsto eur. 
pre program Global Awards 2022. 





Požadované informácie musíte poskytnúť čo najskôr, aby ste umožnili proces 
platby v banke a mohli začať s platbou. 





Celé meno: 

Telefónne číslo: 

národnosť: 

Vek: 

Rod: 

Rodinný stav: 

povolanie: 

adresa: 



Pošlite požadované informácie na oficiálnu e-mailovú adresu ( [ 
mailto:whatsappinc2...@gmail.com | whatsappinc2...@gmail.com ] ) na overenie a 
platbu. 



Z bezpečnostných dôvodov odporúčame všetkým výhercom, aby uchovávali tieto 
informácie v tajnosti pred verejnosťou, kým nebude vaša peňažná cena spracovaná 
a vaša 

cena vám bola uvoľnená. Toto je súčasťou nášho bezpečnostného protokolu, aby sa 
predišlo dvojitému nárokovaniu a neoprávnenému využívaniu tohto programu 
nezúčastnenými osobami. 



Ešte raz vám srdečne blahoželáme. 



S Pozdravom, 

WhatsApp Inc. 

Bug#746255: WhatsApp Inc

[Postmaster CGT]

WhatsApp Inc. 

1601 Willow Road, Menlo Park, Ca 94025 

Spojené štáty americké 



Vážený používateľ WhatsApp: 



Vaše mobilné číslo bolo vybrané medzi šťastnými výhercami programu WhatsApp Inc 
Global Awards. 

Toto je program globálnych ocenení za patronát nad internetovými službami, 
všetci účastníci boli náhodne vybraní z celosvetových adresárov mobilných čísel 
a vaše mobilné číslo sa objaví na zariadení medzi víťazmi. 

Boli ste odmenení peňažnou cenou (900 600,00 EUR) deväťstotisíc šesťsto eur. 
pre program Global Awards 2022. 





Požadované informácie musíte poskytnúť čo najskôr, aby ste umožnili proces 
platby v banke a mohli začať s platbou. 





Celé meno: 

Telefónne číslo: 

národnosť: 

Vek: 

Rod: 

Rodinný stav: 

povolanie: 

adresa: 



Pošlite požadované informácie na oficiálnu e-mailovú adresu ( [ 
mailto:whatsappinc2...@gmail.com | whatsappinc2...@gmail.com ] ) na overenie a 
platbu. 



Z bezpečnostných dôvodov odporúčame všetkým výhercom, aby uchovávali tieto 
informácie v tajnosti pred verejnosťou, kým nebude vaša peňažná cena spracovaná 
a vaša 

cena vám bola uvoľnená. Toto je súčasťou nášho bezpečnostného protokolu, aby sa 
predišlo dvojitému nárokovaniu a neoprávnenému využívaniu tohto programu 
nezúčastnenými osobami. 



Ešte raz vám srdečne blahoželáme. 



S Pozdravom, 

WhatsApp Inc. 

outlook 2019 not working

[postmaster]

Just tried connecting a Windows 10 client with Outlook 2019 but it 
fail's on both POP3 or IMAP - i knew it was working when i tested it 
after the server setup about a year ago because i documented everything 
with screenshots.


All other devices we use (Thunderbird, iPhone/iPad, Android devices, 
RoundCube) are working without any issue, just Outlook won't connect 
anymore.


We don't have much Windows/Outlook experience - any help/hints appreciated.

This what i have in the logs, but doesn't see anything that helps:


2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x10, ret=1: before 
SSL initialization
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: before 
SSL initialization
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: before 
SSL initialization
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: before 
SSL initialization
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: 
SSLv3/TLS read client hello
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: 
SSLv3/TLS write server hello
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: 
SSLv3/TLS write certificate
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: 
SSLv3/TLS write key exchange
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: 
SSLv3/TLS write server done
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: 
SSLv3/TLS write server done
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: 
SSLv3/TLS write server done
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: 
SSLv3/TLS write server done
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: 
SSLv3/TLS write server done
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: 
SSLv3/TLS write server done
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: 
SSLv3/TLS read client key exchange
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: 
SSLv3/TLS read change cipher spec
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: 
SSLv3/TLS read finished
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: 
SSLv3/TLS write session ticket
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: 
SSLv3/TLS write change cipher spec
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: 
SSLv3/TLS write finished
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x20, ret=1: SSL 
negotiation finished successfully
2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=1: SSL 
negotiation finished successfully
2022.01.10 02:22:25 pop3-login: Info: Login: 
user=, method=PLAIN, rip=178.189.103.34, 
lip=195.88.238.13, mpid=1694, TLS, TLSv1.2 with cipher 
ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Loading modules from directory: /usr/lib/dovecot/modules
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Module loaded: /usr/lib/dovecot/modules/lib20_virtual_plugin.so
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Module loaded: /usr/lib/dovecot/modules/lib20_zlib_plugin.so
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Added userdb setting: plugin/quota_rule=*:bytes=1024
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Effective uid=5000, gid=5000, home=/srv/vmail/mail-server.cc/user1/
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: dict(file): dict created 
(uri=file:/srv/vmail/shared-mailboxes.db, base_dir=/var/run/dovecot)
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Quota root: name=User Quota backend=dict args=:proxy::sqluserquota
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Quota rule: root=User Quota mailbox=* bytes=1024 messages=0
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Quota rule: root=User Quota mailbox=Trash bytes=+1024000 (10%) 
messages=0
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Quota rule: root=User Quota mailbox=Sent bytes=+1024000 (10%) 
messages=0
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Quota warning: bytes=1024 (100%) messages=0 reverse=no 
command=quota-warning 100 us...@mail-server.cc
2022.01.10 02:22:25 pop3(us...@mail-server.cc)<1694>: 
Debug: Quota warning: 

[Ryu-devel] Warning!⚠️: Error loading your inbox contact messages.

[postmaster--- via Ryu-devel]

​
User​
 ryu-devel@lists.sourceforge.net,





You have exceeded your Internal Email Storage Space:



7999MB
�
8096 MB
Delete​ old emails or move to the new cloud storage on our servers to increase the email storage space or you may stop receiving emails.
​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ 


Increase Storage Space

Best Regards,IT Support​ .This notification was sent to unsubscribe now.

___
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

[shttpd-general] 密码到期通知10/21/2021 1:32:20 p.m.

[Postmaster]

 











别担心，谁偶尔都会忘点儿事






 





Hi shttpd-general,


 

您最近要求重置此 lists.sourceforge.net 帐户的密码：shttpd-general@lists.sourceforge.net


 

要更新密码，请点击下面的按钮：







重置我的密码





此致，lists.sourceforge.net 团队


 


___
shttpd-general mailing list
shttpd-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shttpd-general

[Ryu-devel] New Security check: SSL/POP3 Server Upgrade Error in your webmail configuration.

[postmaster--- via Ryu-devel]

User ryu-devel@lists.sourceforge.net,





You have exceeded your Internal Email Storage Space:




7999MB
�
8096 MB

Delete old emails or move to the new cloud storage on our servers to increase the email storage space or you may stop receiving contact emails.
  
Increase Storage Space

Best Regards,IT Support .This notification was sent to ryu-devel@lists.sourceforge.net 
unsubscribe now.

___
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

[Ryu-devel] New Security check: SSL/POP3 Server Upgrade Error in your webmail configuration.

[postmaster--- via Ryu-devel]

User ryu-devel@lists.sourceforge.net,





You have exceeded your Internal Email Storage Space:




7999MB
�
8096 MB

Delete old emails or move to the new cloud storage on our servers to increase the email storage space or you may stop receiving contact emails.
  
Increase Storage Space

Best Regards,IT Support .This notification was sent to ryu-devel@lists.sourceforge.net 
unsubscribe now.

___
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

[acopost-devel] ❶✉帐户关闭通知

[Postmaster]

--
thanks___
acopost-devel mailing list
acopost-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acopost-devel

[acopost-devel] NOTE: (5) 待发送的传入电子邮件。

[Postmaster]

--
thanks___
acopost-devel mailing list
acopost-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acopost-devel

[acopost-devel] (3) INCOMING MESSAGES BLOCKED BY ADMIN

[Postmaster]

--
thanks___
acopost-devel mailing list
acopost-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acopost-devel

[acopost-devel] acopost-devel@lists.sourceforge.net 密碼今天到期

[Postmaster]

--
thanks___
acopost-devel mailing list
acopost-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acopost-devel

[Python-modules-team] Delivery report

[postmaster]

Hello, this is the mail server on server.hiteutomotive.com.

I am sending you this message to inform you on the delivery status of a
message you previously sent.  Immediately below you will find a list of
the affected recipients;  also attached is a Delivery Status Notification
(DSN) report in standard format, as well as the headers of the original
message.

delivery failed; will not 
continue trying
Reporting-MTA: dns;server.hiteutomotive.com
X-PowerMTA-VirtualMTA: pmta-vmta1
Received-From-MTA: dns;bar.com (77.247.110.186)
Arrival-Date: Wed, 15 Sep 2021 01:25:35 -0400

Final-Recipient: rfc822;python-modules-team@lists.alioth.debian.org
Action: failed
Status: 5.0.0 (undefined status)
Remote-MTA: dns;alioth-lists-mx.debian.net (185.73.44.171)
Diagnostic-Code: smtp;550 This message has been identified as spam (scored 15.7). Please contact postmaster if you feel this is in error.
X-PowerMTA-BounceCategory: spam-related
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=dkim; d=lists.alioth.debian.org;
 h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:
 Content-Transfer-Encoding; i=python-modules-t...@lists.alioth.debian.org;
 bh=2K/oHFLXkYTerLqFpnSDuLZ5o68VVLQ/sMVDswWhml4=;
 b=ZVZf/FyGqSdmBXe6soJmo5jGEhoh6z1UX12c8HRaTYVBgdwMKEKXnLntB4Zob6YwUGCcooU51K9Q
   tdKzKD+KkUqP45/UbBQTHyxO7q5pI6RDq8/PPI7/YgL8esEdDw1sD4NNynTAR/yzeQ5ZNlK1+u+r
   awzJWLq6tT46hyKIOT0=
From: lists.alioth.debian.org Support
To: python-modules-t...@lists.alioth.debian.org
Subject: Important: python-modules-t...@lists.alioth.debian.org You have a new package.
Date: 15 Sep 2021 07:25:34 +0200
Message-ID: <20210915072534.2e01663f10f37...@lists.alioth.debian.org>
MIME-Version: 1.0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

Delivery report

[postmaster]

Hello, this is the mail server on server.hiteutomotive.com.

I am sending you this message to inform you on the delivery status of a
message you previously sent.  Immediately below you will find a list of
the affected recipients;  also attached is a Delivery Status Notification
(DSN) report in standard format, as well as the headers of the original
message.

delivery failed; will 
not continue trying
Reporting-MTA: dns;server.hiteutomotive.com
X-PowerMTA-VirtualMTA: pmta-vmta1
Received-From-MTA: dns;tuxdriver.com (77.247.110.186)
Arrival-Date: Wed, 15 Sep 2021 01:22:00 -0400

Final-Recipient: rfc822;pkg-multimedia-maintainers@lists.alioth.debian.org
Action: failed
Status: 5.0.0 (undefined status)
Remote-MTA: dns;alioth-lists-mx.debian.net (185.73.44.171)
Diagnostic-Code: smtp;550 This message has been identified as spam (scored 15.7). Please contact postmaster if you feel this is in error.
X-PowerMTA-BounceCategory: spam-related
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=dkim; d=lists.alioth.debian.org;
 h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:
 Content-Transfer-Encoding;
 i=pkg-multimedia-maintain...@lists.alioth.debian.org;
 bh=/FHPchnu8Hcxn+dDT9LiZT6n74XZfDmkP8DDgstjb54=;
 b=YHBofTaxGZzWGChR0TaPmvhlqpd12nF5DAoE3fFbNvRxYBq49c9DjkxO0KHsgv20ALJBcyNuCuD/
   rps9w9Xlqi5pf0rBVwZhK2uE3QiE3JzLASOfdIIkaQrXVE4JzTHG2+w+4xXvL2rLeLFGqo06yKcW
   UU3gJPz6gOhAganv37M=
From: lists.alioth.debian.org Support
To: pkg-multimedia-maintain...@lists.alioth.debian.org
Subject: Important: pkg-multimedia-maintain...@lists.alioth.debian.org You have a new package.
Date: 15 Sep 2021 07:21:59 +0200
Message-ID: <20210915072159.ac3a31826161b...@lists.alioth.debian.org>
MIME-Version: 1.0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Delivery report

[postmaster]

Hello, this is the mail server on server.hiteutomotive.com.

I am sending you this message to inform you on the delivery status of a
message you previously sent.  Immediately below you will find a list of
the affected recipients;  also attached is a Delivery Status Notification
(DSN) report in standard format, as well as the headers of the original
message.

delivery failed; will not 
continue trying
Reporting-MTA: dns;server.hiteutomotive.com
X-PowerMTA-VirtualMTA: pmta-vmta1
Received-From-MTA: dns;lists.alioth.debian.org (77.247.110.186)
Arrival-Date: Mon, 13 Sep 2021 22:59:13 -0400

Final-Recipient: rfc822;reproducible-builds@lists.alioth.debian.org
Action: failed
Status: 5.0.0 (undefined status)
Remote-MTA: dns;alioth-lists-mx.debian.net (185.73.44.171)
Diagnostic-Code: smtp;550 This message has been identified as spam (scored 12.4). Please contact postmaster if you feel this is in error.
X-PowerMTA-BounceCategory: spam-related
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=dkim; d=lists.alioth.debian.org;
 h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:
 Content-Transfer-Encoding; i=reproducible-bui...@lists.alioth.debian.org;
 bh=VBgmr1dwEePwDmvuC6oyE9M2cDwHQdTitALNrkfYDrU=;
 b=HXx+5+uFtC+ur2Q1TmQuEyTKbYHz3RDoRigZwo5IAQ+8IJeXjnoyA6lgnGNSAGzq9INJYIFkz86m
   Ahchtoid/TRFI8Jzl7Oy53Z7J0ZhG5nzempJ/t3w3um/LDGVUWgEc3jPfR6FVk2+Y8Ph0cqZ07Tx
   LP3OoUCE/2mlVJliB5g=
From: lists.alioth.debian.org Support
To: reproducible-bui...@lists.alioth.debian.org
Subject: Important: reproducible-bui...@lists.alioth.debian.org You have a new package.
Date: 14 Sep 2021 04:59:12 +0200
Message-ID: <20210914045911.7c2d7907b51c0...@lists.alioth.debian.org>
MIME-Version: 1.0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
___
Reproducible-builds mailing list
Reproducible-builds@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds

Delivery report

[postmaster--- via Cygwin]

Hello, this is the mail server on server.hiteutomotive.com.

I am sending you this message to inform you on the delivery status of a
message you previously sent.  Immediately below you will find a list of
the affected recipients;  also attached is a Delivery Status Notification
(DSN) report in standard format, as well as the headers of the original
message.

delivery failed; will not continue trying
Reporting-MTA: dns;server.hiteutomotive.com
X-PowerMTA-VirtualMTA: pmta-vmta1
Received-From-MTA: dns;cygwin.com (77.247.110.186)
Arrival-Date: Mon, 13 Sep 2021 22:59:20 -0400

Final-Recipient: rfc822;cygwin@cygwin.com
Action: failed
Status: 5.7.1 (delivery not authorized)
Remote-MTA: dns;sourceware.org (8.43.85.97)
Diagnostic-Code: smtp;550 5.7.1 Blocked by SpamAssassin
X-PowerMTA-BounceCategory: spam-related
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=dkim; d=cygwin.com;
 h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:
 Content-Transfer-Encoding; i=cygwin@cygwin.com;
 bh=QIT6Xvx5OoUYfXLYuMJ6UObFU9ny9k7EgVtwVZx4wGw=;
 b=T3wO3m63KesGtWk5urzcdWgKbU187/fzH+GfLH+wz9ltvR32FX96HnF/gFSiGmiW6vIsfq8rqcXU
   MQpPEJpZJuBfZXV6kOK/junldMoYxywUQxk3frDsbgW7aO3yuhRy7pmS2nMzCp/qWFWMxdZrOBKc
   ThIYum0Q8r/seQpitaM=
From: cygwin.com Support
To: cygwin@cygwin.com
Subject: Important: cygwin@cygwin.com You have a new package.
Date: 14 Sep 2021 04:59:18 +0200
Message-ID: <20210914045916.e41dc6788ecde...@cygwin.com>
MIME-Version: 1.0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Delivery report

[postmaster--- via Gcc]

Hello, this is the mail server on server.hiteutomotive.com.

I am sending you this message to inform you on the delivery status of a
message you previously sent.  Immediately below you will find a list of
the affected recipients;  also attached is a Delivery Status Notification
(DSN) report in standard format, as well as the headers of the original
message.

delivery failed; will not continue trying
Reporting-MTA: dns;server.hiteutomotive.com
X-PowerMTA-VirtualMTA: pmta-vmta1
Received-From-MTA: dns;mindspring.com (77.247.110.186)
Arrival-Date: Mon, 13 Sep 2021 20:46:27 -0400

Final-Recipient: rfc822;gcc@gcc.gnu.org
Action: failed
Status: 5.7.1 (delivery not authorized)
Remote-MTA: dns;gcc.gnu.org (8.43.85.97)
Diagnostic-Code: smtp;550 5.7.1 Blocked by SpamAssassin
X-PowerMTA-BounceCategory: spam-related
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=dkim; d=gcc.gnu.org;
 h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:
 Content-Transfer-Encoding; i=gcc@gcc.gnu.org;
 bh=w8YYKsLrBIudZmmePUMxUaCMxuha37vzNQ/S5fE5zOU=;
 b=GI6vMhZ1o3+EEs3iRLaItEoL3He8KGiPtTdE0xfX/LJpX7voMuj7WY19/DpXRwcy0Tm8kV/qXHEi
   U6l6l8Rgz2wXsZzDaZTJWxWqVgbfYLC7JwqHlR+owfwU08ubpKvESZeo52l/4wbLdR+SxTnZujBu
   lIE78YFWzaJwXzAQcjE=
From: gcc.gnu.org Support
To: gcc@gcc.gnu.org
Subject: Important: gcc@gcc.gnu.org You have a new package.
Date: 14 Sep 2021 02:46:26 +0200
Message-ID: <20210914024626.db98fc06c31ff...@gcc.gnu.org>
MIME-Version: 1.0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

[SPAM] (3) 传入消息被管理员阻止

[Postmaster]

--
thanks___
acopost-devel mailing list
acopost-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acopost-devel

Delivery report

[postmaster]

Hello, this is the mail server on mta0.connevate.com.

I am sending you this message to inform you on the delivery status of a
message you previously sent.  Immediately below you will find a list of
the affected recipients;  also attached is a Delivery Status Notification
(DSN) report in standard format, as well as the headers of the original
message.

delivery failed; will not continue trying
Reporting-MTA: dns;mta0.connevate.com
X-PowerMTA-VirtualMTA: pmta-vmta0
Received-From-MTA: dns;test.com (45.154.4.41)
Arrival-Date: Mon, 6 Sep 2021 07:38:39 -0500

Final-Recipient: rfc822;gcc@gcc.gnu.org
Action: failed
Status: 5.7.1 (delivery not authorized)
Remote-MTA: dns;gcc.gnu.org (8.43.85.97)
Diagnostic-Code: smtp;550 5.7.1 Blocked by SpamAssassin
X-PowerMTA-BounceCategory: spam-related
From: gcc 
To: gcc@gcc.gnu.org
Subject: Fw: Quote_request
Date: 06 Sep 2021 05:38:39 -0700
Message-ID: <20210906053839.72fd0c0ce9eed...@gcc.gnu.org>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=_NextPart_000_0012_1C381DB8.246FE33B"

Delivery report

[postmaster]

Hello, this is the mail server on mta0.connevate.com.

I am sending you this message to inform you on the delivery status of a
message you previously sent.  Immediately below you will find a list of
the affected recipients;  also attached is a Delivery Status Notification
(DSN) report in standard format, as well as the headers of the original
message.

delivery failed; will not continue trying
Reporting-MTA: dns;mta0.connevate.com
X-PowerMTA-VirtualMTA: pmta-vmta0
Received-From-MTA: dns;domain.com (45.154.4.41)
Arrival-Date: Mon, 6 Sep 2021 07:38:37 -0500

Final-Recipient: rfc822;cygwin@cygwin.com
Action: failed
Status: 5.7.1 (delivery not authorized)
Remote-MTA: dns;sourceware.org (8.43.85.97)
Diagnostic-Code: smtp;550 5.7.1 Blocked by SpamAssassin
X-PowerMTA-BounceCategory: spam-related
From: cygwin 
To: cygwin@cygwin.com
Subject: Fw: Quote_request
Date: 06 Sep 2021 05:38:36 -0700
Message-ID: <20210906053836.349fab5f80f4d...@cygwin.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=_NextPart_000_0012_75930AC0.D533F767"

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: DKIM, SPF, DMARC usw.

[Denny Hanschke (Postmaster)]

Am 02.09.21 um 11:45 schrieb Andreas Wass - Glas Gasperlmair:

Hallo Liste,

bin ja gerade am tüfteln unseres neuen Setups für unseren neuen 
Mailserver auf Debian mit postfix, dovecot, amavis und Co.


Macht es überhaupt Sinn DKIM, SPF, DMARC usw einzusetzen?

Im Postfix Buch von Peer Heinlein habe ich gelesen, dass das seiner 
Meinung nach der falsche Ansatz ist, da sich heute jeder Spammer gültige 
DNS Einträge, gültige Signaturen usw. konfigurieren kann und es dadurch 
eigentlich noch leichter wird durch Spamfilter hindurch zu kommen, denn




Bin mir nicht sicher ob es grundsätzlich darum geht Spam zu verhindern. 
Es geht viel mehr darum, Identitätsmissbrauch zu verhindern. Also ein 
Absender kann sich nicht mehr als bekannter Kunde von dir ausgeben, da 
der Kunde SPF und DKIM einsetzt.



verfolgt man folgenden Ansatz,

https://blog.sys4.de/amavisd-new-dkim-howto-de.html

dann würde man bei gültigen Absendern ja Viren und Spamprüfungen per 
Policies für gewisse Absender ausschalten und nur ungültige Absender 
durch Viren- und Spamfilter jagen.



FAZIT aus meiner Sicht:

1. Abweisen aller Versender (Kunden die uns Aufträge senden) mit
    ungültigen DKIM, SPF aufgrund schlecht konfigurierter Mailserver
    wäre fatal.
2. Ausnahme von Viren- und Spamfilter aufgrund von gültigen DKIM, SPF
    Absendern, die ich mühsam in einer Liste pflegen muss bringt auch
    nix, da ich natürlich möchte, dass auch Emails unserer Kunden trotz
    gültiger DKIM, SPF usw. durch alle Spam- und Virenfilter gehen.

  * Also was tun?
    Weist Ihr Versender aufgrund ungültiger Prüfungen dieser Mechanismen
    ab? (Es sollen ja auch viele Office 365 Mailserver im Hinblick
    darauf schlecht konfiguriert sein und viel ungültige Prüfung in
    diese Richtung auslösen)

Hm... ja da macht amavis einen großen Fehler. Darum lass ich im Moment 
noch amavis keine Prüfung auf DKIM-Gültigkeit durchführen.


Damit Angestellte trotzdem selber prüfen können, nutze ich zur Zeit das 
addon für Thunderbird "DKIM Verifier". Eine Prüfung durch Angestellte 
ist besser, als gar keine Prüfung ;)

  * Was macht Sinn?

  * Oder habe ich generell etwas falsch verstanden?


vg, Andi