You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Sergei Myshliakov <si...@notes.odtel.net> on 2024/10/03 19:36:17 UTC

Adding a group member - bug ???

Hi,

In my previous post I asked how to create a group of addresses - I 
already figured it out.

Now I ran into another problem:

When I added a few members to a group with web admin api I got 500 error 
because it put all the members into the

the same row in database (I use James 3.8.1 with Derby db network 
server) and TARGET_ADDRESS field is not big enough (var(100))

the record in db looks like that:

| DOMAIN_NAME | USER_NAME | TARGET_ADDRESS |
| example.com   | test               | 
group:client2@example3.com;group:client@example3.com;group:user2@example.com;group:user@ex 
|

I think it's a bug,  web admin api should put each member into a new row.

Later when needed we can get all the members like that

select TARGET_ADDRESS from JAMES_RECIPIENT_REWRITE where 
DOMAIN_NAME='example.com' and USER_NAME='test'

Re : Adding a group member - bug ???

Posted by Benoit TELLIER <bt...@linagora.com>.
Hello
Known bug.

Cf https://issues.apache.org/jira/browse/JAMES-1409 

A rewrite of JPA code for RecipientRewriteTable is the only way to fix this.
To quote the ticket: JPA fans, feel free to have a look and drop a patch!

-- 

Best regards,

Benoit TELLIER

General manager of Linagora VIETNAM.
Product owner for Team-Mail product.
Chairman of the Apache James project.

Mail: btellier@linagora.com
Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)


Le oct. 3, 2024 9:36 PM, de Sergei Myshliakov Hi,

In my previous post I asked how to create a group of addresses - I 
already figured it out.

Now I ran into another problem:

When I added a few members to a group with web admin api I got 500 error 
because it put all the members into the

the same row in database (I use James 3.8.1 with Derby db network 
server) and TARGET_ADDRESS field is not big enough (var(100))

the record in db looks like that:

| DOMAIN_NAME | USER_NAME | TARGET_ADDRESS |
| example.com   | test               | 
group:client2@example3.com;group:client@example3.com;group:user2@example.com;group:user@ex 
|

I think it's a bug,  web admin api should put each member into a new row.

Later when needed we can get all the members like that

select TARGET_ADDRESS from JAMES_RECIPIENT_REWRITE where 
DOMAIN_NAME='example.com' and USER_NAME='test'