[
https://issues.apache.org/jira/browse/JAMES-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074629#comment-14074629
]
Adam Bennett edited comment on JAMES-1032 at 7/25/14 5:30 PM:
--------------------------------------------------------------
I'm curious to know what problems supporting this functionality might create? I
have made changes to the v2.3.2 source to allow for regex patterns in
servername, and it appears to work fine without other implications.
For the adventurous types, who might like to make these changes for themselves,
simply modify the isLocalServer method in the org.apache.james.James class
(v2.3.2) to support whatever matching logic you want (if explicit matching
fails). Of course keep in mind that lax matching rules could open your server
for relays.
was (Author: [email protected]):
I'm curious to know what problems supporting this functionality might create? I
have made changes to the v2.3.2. source to allow for regex patterns in
servername, and it appears to work fine without other implications.
For the adventurous types, who might like to make these changes for themselves,
simply modify the isLocalServer method in the org.apache.james.James class
(v2.3.2) to support whatever matching logic you want (if explicit matching
fails). Of course keep in mind that lax matching rules could open your server
for relays.
> wildcard (*) in servername
> --------------------------
>
> Key: JAMES-1032
> URL: https://issues.apache.org/jira/browse/JAMES-1032
> Project: James Server
> Issue Type: New Feature
> Components: James Core
> Reporter: Shahid
> Assignee: Norman Maurer
> Fix For: 3.0.0
>
>
> allow wildcard (*) in servername to handle sub-domains.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
