Tellier Benoit created JAMES-2752:
-------------------------------------
Summary: MappingSource::wildcard is being ignored during the RRT
process
Key: JAMES-2752
URL: https://issues.apache.org/jira/browse/JAMES-2752
Project: James Server
Issue Type: Bug
Components: RRT
Affects Versions: master, 3.3.0, 3.3.1
Reporter: Tellier Benoit
This issue follows the user mailing list thread
https://www.mail-archive.com/[email protected]/msg15949.html
User Story:
{code:java}
When I send an email to James
James rewrites the Recipient to a fixed address (WILCARD ->
[email protected])
{code}
This need had been expressed by two distinct members of the community.
`MappingSource::wildcard` is the most straightforward way to implement this (a
simple address would do the trick) but sadly MappingSource wildcard testing is
not part of the AbstractRecipientRewriteTableTest test suite and thus is not
supported.
{code:java}
// This is failing but it should not !!!
@Test
public void wildcardRewritesShouldBeResolvedForAnyInput() throws Exception {
Mapping mappingForward = Mapping.address(ADDRESS);
virtualUserTable.addMapping(MappingSource.wildCard(), mappingForward);
assertThat(virtualUserTable.getResolvedMappings(USER,
Domain.LOCALHOST)).containsOnly(mappingForward);
}
{code}
What we should do:
- Testing for MappingSource.wildard within AbstractRecipientRewriteTableTest
- Support it for non-deprecated implementations - deprecated implementations
can ignore this feature
- Integration tests :
- Using the CLI I can set up a wildcard address rewrite cf
DataCommandsIntegrationTest
- Using webadmin I can set up a wildcard
address/forward/group/alias/domain entry (cf unit tests + integration tests)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
