Yes, it works :) Tks!
The documentation from help drove me into error:
addmapping ([table=virtualusertablename]) [tou...@todomain] [fromMapping]
... and I tought I had tried this combination some time ago without success.
So far so good.
Eric
On 04/21/2010 09:03 AM, Norman Maurer wrote:
Ho Eric,
I don't have the source handy atm.
But I think it should Be:
addmapping [email protected] [email protected]
bye
Norman
2010/4/20, Eric Charles<[email protected]>:
Hi Norman,
Yes, spoolmanager.xml contains :
<mailet match="All" class="VirtualUserTable">
<virtualusertable>DefaultVirtualUserTable</virtualusertable>
</mailet>
To complete the explanation, when
addmapping [email protected] [email protected]
is done, I even don't receive any mail at all on the [email protected].
When I remove the mapping, I receive again the mails on [email protected].
Tks,
Eric
On 04/20/2010 10:04 PM, Norman Maurer wrote:
Cool ; we love contributions. About the mapping problem.... Are you
sure you have the VirtualUserTable mailet defined in he
spoolmanager.xml ?
Bye
Norman
2010/4/20, Eric Charles<[email protected]>:
Hi Norman,
I will try to resolve JAMES-990 for the exception at startup.
For the mapping, suppose [email protected] exists. Via remotemanager:
addmapping [email protected] [email protected]
Send a mail to [email protected]
See in the log [email protected] and [email protected]:
INFO 20:18:57,537 | james.smtpserver | Successfully spooled mail
Mail1271787537534-29795 from [email protected] on 195.238.6.53 for
[[email protected]]
Succesfully spooled, but not seen via imap/pop3.
Tks,
Eric
On 04/07/2010 06:22 PM, Norman Maurer wrote:
Hi Eric,
the error about not able to add domain should be fixed in current
trunk. If you still have the problem open an jira issue.
What is the problem with the mappings?
Could you give me some details?
Thx
Norman
2010/4/7, Eric Charles<[email protected]>:
Hi Oleg,
This is usually the steps I take to configure james (from trunk):
- James.xml :<enableVirtualHosting> true</enableVirtualHosting>
- spring-beans.xml : comment<bean id="domainlist"
class="org.apache.james.domain.XMLDomainList" />
- spring-beans.xml : uncomment<bean id="domainlist"
class="org.apache.james.vut.JDBCVirtualUserTable" />
- domainlists.xml : uncomment
<repositoryPath>db://maildb/domain</repositoryPath>
<sqlFile>file://conf/sqlResources.xml</sqlFile>
This should allow james to work with an embedded derby to manage
multiple domains.
run.sh :
- the first time, you will get a
org.apache.commons.configuration.ConfigurationException: Configured
defaultdomain could not get added to DomainList (not very welcome
message...)
- don't worry, run twice: it works.
telnet localhost 4555 (root / root)
adddomain test.com
listdomains
Domains:
test.com
localhost
127.0.1.1
204.12.0.50
127.0.1.1
adduser [email protected] badpwd
User [email protected] added
listusers
Existing accounts 1
user: [email protected]
I still have a small concern about mapping.
forward and alias have been removed
(http://markmail.org/message/4ihtdtqiggcu74cl).
I tried to make the trick with the mapping function (say for example
[email protected] is the same as [email protected] and the same as
[email protected]), but I didn't succeed to make it work.
Hope this help you.
Tks,
Eric
On 01/-10/-28163 08:59 PM, wrote:
ok if you want virtualhosting use the JDBCDomainList or XMLDomainList.
Then when you add a new user to the server you would connect via
telnet to remotemanager and use the FQUN (like [email protected])
when adding a user. Be sure to first create the domain if you use
JDBCDomainList via remotemanager. If you use XMLDomainList you just
need to add the domain to the domainnames config.
Both of these DomainList implementation works without problems in
conjunction with virtualhosting. So can you give me a hint "where" it
says to disable virtual hosting ? Maybe its outdated info ..
Thx,
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
