Menu
▾
▴
jboss-dev-forums — The jboss development forum posts
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
(157) |
May
(789) |
Jun
(608) |
Jul
(554) |
Aug
(868) |
Sep
(654) |
Oct
(994) |
Nov
(803) |
Dec
(982) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(1006) |
Feb
(1054) |
Mar
(1345) |
Apr
(1305) |
May
(1392) |
Jun
(1016) |
Jul
(265) |
Aug
(1) |
Sep
(8) |
Oct
(9) |
Nov
(8) |
Dec
(19) |
| 2007 |
Jan
(20) |
Feb
(10) |
Mar
(20) |
Apr
(8) |
May
(4) |
Jun
(1) |
Jul
(6) |
Aug
(3) |
Sep
(6) |
Oct
(12) |
Nov
(7) |
Dec
(13) |
| 2008 |
Jan
(5) |
Feb
(4) |
Mar
(34) |
Apr
(32) |
May
(22) |
Jun
(21) |
Jul
(30) |
Aug
(18) |
Sep
(30) |
Oct
(23) |
Nov
(86) |
Dec
(51) |
| 2009 |
Jan
(25) |
Feb
(26) |
Mar
(34) |
Apr
(47) |
May
(38) |
Jun
(25) |
Jul
(36) |
Aug
(9) |
Sep
(8) |
Oct
(10) |
Nov
(4) |
Dec
(17) |
| 2010 |
Jan
(7) |
Feb
(9) |
Mar
(26) |
Apr
(49) |
May
(52) |
Jun
(48) |
Jul
(39) |
Aug
(27) |
Sep
(9) |
Oct
(14) |
Nov
(7) |
Dec
(10) |
| 2011 |
Jan
(12) |
Feb
(9) |
Mar
(17) |
Apr
(33) |
May
(39) |
Jun
(36) |
Jul
(29) |
Aug
(26) |
Sep
(29) |
Oct
(38) |
Nov
(35) |
Dec
(27) |
| 2012 |
Jan
(20) |
Feb
(34) |
Mar
(29) |
Apr
(33) |
May
(45) |
Jun
(46) |
Jul
(50) |
Aug
(35) |
Sep
(55) |
Oct
(68) |
Nov
(79) |
Dec
(45) |
| 2013 |
Jan
(67) |
Feb
(20) |
Mar
(55) |
Apr
(52) |
May
(25) |
Jun
(25) |
Jul
(34) |
Aug
(27) |
Sep
(21) |
Oct
(21) |
Nov
(19) |
Dec
(12) |
| 2014 |
Jan
(10) |
Feb
(8) |
Mar
(13) |
Apr
(18) |
May
(36) |
Jun
(26) |
Jul
(17) |
Aug
(19) |
Sep
(13) |
Oct
(8) |
Nov
(7) |
Dec
(5) |
| 2015 |
Jan
(11) |
Feb
(2) |
Mar
(13) |
Apr
(15) |
May
(7) |
Jun
(2) |
Jul
(4) |
Aug
(3) |
Sep
(3) |
Oct
|
Nov
(2) |
Dec
(1) |
| 2016 |
Jan
(3) |
Feb
(5) |
Mar
(19) |
Apr
(34) |
May
(9) |
Jun
(10) |
Jul
(5) |
Aug
(10) |
Sep
(5) |
Oct
(11) |
Nov
(19) |
Dec
(7) |
| 2017 |
Jan
(4) |
Feb
(4) |
Mar
(8) |
Apr
(5) |
May
(12) |
Jun
(5) |
Jul
(11) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: jc7442 <do-...@jb...> - 2006-07-07 14:57:47
|
Do you know what's other tool can be used for integration tests ? I have try to investigate several of them but I did not succeed to find one which fit my requirements. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956209#3956209 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956209 |
|
From: <tom...@jb...> - 2006-07-07 14:57:26
|
Don't know that JRUnit would be the best tool to for testing clients calling on an application server. However, this could be done if write your own org.jboss.jrunit.extensions.ServerTestCase and withint setUp() method call main() method of org.jboss.Main. Of course will have to make sure have all the jars you need for jboss server on classpath. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956202#3956202 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956202 |
|
From: msegvich <do-...@jb...> - 2006-07-07 14:57:21
|
I'm on jboss 4.0.4 GA, Windows XP. I can successfully run the following manually without a problem: | run.bat -c default - b localhost | However, when I try to run the example build.xml (using ant -v test) I get the following: | test: | [server:start] Starting server "default" with command: | [server:start] C:\Program Files\Java\jdk1.5.0_06\bin\java -cp C:\jboss-4.0.4\bin | \run.jar;C:\Program Files\Java\jdk1.5.0_06\lib\tools.jar -Xmx128m -Djava.endors | ed.dirs=C:\jboss-4.0.4/lib/endorsed org.jboss.Main -c default -b localhost | | BUILD FAILED | C:\jboss-test-1.0.0.CR1\examples\build.xml:83: Error starting server "default": | Server failed to start; see logs. exit code: 1 | at org.jboss.ant.taskdefs.server.StartServerTask.execute(StartServerTask | .java:54) | at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) | at org.apache.tools.ant.Task.perform(Task.java:364) | at org.apache.tools.ant.Target.execute(Target.java:341) | at org.apache.tools.ant.Target.performTasks(Target.java:369) | at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) | at org.apache.tools.ant.Project.executeTarget(Project.java:1185) | at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe | cutor.java:40) | at org.apache.tools.ant.Project.executeTargets(Project.java:1068) | at org.apache.tools.ant.Main.runBuild(Main.java:668) | at org.apache.tools.ant.Main.startAnt(Main.java:187) | at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) | at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) | Caused by: java.io.IOException: Server failed to start; see logs. exit code: 1 | at org.jboss.test.util.server.ServerController.waitForServer(ServerContr | oller.java:174) | at org.jboss.test.util.server.ServerController.startServer(ServerControl | ler.java:110) | at org.jboss.test.util.server.ServerManager.startServer(ServerManager.ja | va:127) | at org.jboss.ant.taskdefs.server.StartServerTask.execute(StartServerTask | .java:50) | ... 12 more | --- Nested Exception --- | java.io.IOException: Server failed to start; see logs. exit code: 1 | at org.jboss.test.util.server.ServerController.waitForServer(ServerContr | oller.java:174) | at org.jboss.test.util.server.ServerController.startServer(ServerControl | ler.java:110) | at org.jboss.test.util.server.ServerManager.startServer(ServerManager.ja | va:127) | at org.jboss.ant.taskdefs.server.StartServerTask.execute(StartServerTask | .java:50) | at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) | at org.apache.tools.ant.Task.perform(Task.java:364) | at org.apache.tools.ant.Target.execute(Target.java:341) | at org.apache.tools.ant.Target.performTasks(Target.java:369) | at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) | at org.apache.tools.ant.Project.executeTarget(Project.java:1185) | at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe | cutor.java:40) | at org.apache.tools.ant.Project.executeTargets(Project.java:1068) | at org.apache.tools.ant.Main.runBuild(Main.java:668) | at org.apache.tools.ant.Main.startAnt(Main.java:187) | at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) | at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) | Both error and output log files are empty. Not sure what I'm doing wrong. Any pointers would be appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956204#3956204 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956204 |
|
From: rrajesh <do-...@jb...> - 2006-07-07 14:49:56
|
You need to pass your JBoss home directory while calling ant. ant test -Djboss.home=YOUR_JBOSS_HOME_DIRECTORY(which is your 4.0.4.GA installation) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956206#3956206 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956206 |
|
From: ferrari <do-...@jb...> - 2006-07-07 14:01:23
|
I found the problem: the jboss.bind.address is always set to 0.0.0.0 by default then the remote stub does not work with Pooled Invoker. Setting it to the server node IP address (run.sh -b ip.addr) solves the problem. I'd suggest to include this point in the PooledInvokerConfig Wiki page (http://wiki.jboss.org/wiki/Wiki.jsp?page=PooledInvokerConfig) Thanks for your attention. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956195#3956195 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956195 |
|
From: j2ee_junkie <do-...@jb...> - 2006-07-07 13:48:55
|
Dear gang, Well after a good night's rest (something of a rarety these days with my 3mo old son) and a shot of coffee, the light bulb over the head finally turned on. I am reluctant to admit that it was not until then that I really understood the problem purposed and all of your suggestions. That said, I would like to point out that the RealmMapping interface was designed to be a point of access for Principal to Role mapping. As such there needs to be a way to configure this mapping for the RealmMapping implementor to store and use. As Scott pointed out, currently this is a "legacy overloaded use of JAAS". I now understand and agree. Also, Scott has pointed out the benefits of creating a security context that can store this mapping, among other things. This is good, but it still does not explain how to configure the mapping. For that, I seem to agree with Anil and Sohil. The JaasSecurityManager as a RealmMapping should have a way to configure the mapping other than thru the use of the JAAS login. The login config then seems to be the logical place to be extended to provide a per security domain mapping. Another idea that comes to mind is to create a new AuthenticationManager and RealmMapping class (for this discussion I will call it NewSecurityManager) that performs JAAS login to obtain identity (like JaasSecurityManager), but does not depend on Roles to be assigned to Subject. The login will just assign Principals to the Subject as JAAS intended. Then a pluggable means to configure the mapping from Principals to Application Role could be created. Such pluggins could contact a persistent store (db, ldap, file) or be configured dynamically. The pluggin used would be a NewSecurityManager config parameter. Just my updated thoughts. enjoy, cgriffith View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956191#3956191 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956191 |
|
From: <man...@jb...> - 2006-07-07 10:54:52
|
anonymous wrote : | | This task still says 2.0 -- I thought it was moved to 2.1 as its an internal thing. But for Ben's needs it looks like it needs to be 2.0 anyway. | Will you be able to do this in the 2.0.0 timeframe? I hope to release an alpha by the end of the month. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956156#3956156 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956156 |
|
From: wa7son <do-...@jb...> - 2006-07-07 10:32:26
|
I just found out what the problem was: http://issues.apache.org/bugzilla/show_bug.cgi?id=12355 I was a known Apache bug. It is fixed in Apache 2.2.x but not yet backported to 2.0.x. There is a patch available for Apache 2.0.54. We are running Apache 2.0.58 and the patch worked fine here as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956146#3956146 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956146 |
|
From: <aco...@jb...> - 2006-07-07 10:18:16
|
Very interesting. What DB is this? It looks like your storage is messed up or the messages are stuck in the queue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956137#3956137 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956137 |
|
From: <aco...@jb...> - 2006-07-07 10:14:14
|
Note that I no longer reply to very strict "user" requests in the development forum. Wide latitude is given for user-developer requests. This is the only notification on why I (in particular) am ignoring you (in the generic). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956133#3956133 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956133 |
|
From: <max...@jb...> - 2006-07-07 10:01:13
|
note that i'm not 100% sure facet is the answer to everything, but it at least is a good way to integrate into the built-in "configurability" of WTP View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956129#3956129 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956129 |
|
From: <max...@jb...> - 2006-07-07 10:00:25
|
Facet tutorial with code and slides: http://www.eclipsecon.org/2006/Sub.do?id=241 And here is a snippet from Konstantin (the guy behind the facets) on how to enable facets for non-WTP projects. There exists an api for converting an existing project into a faceted project. That api is... import org.eclipse.wst.common.project.facet.core.ProjectFacetsManager; import org.eclipse.wst.common.project.facet.core.IFacetedProject; final IFacetedProject fpj = ProjectFacetsManager.create( , true, <IProgressMonitor ) That will make the project "facet-enabled", but will not install any facets, set any facets as fixed, or associate the project with a runtime. To then install a java facet, you can do this: import org.eclipse.jst.common.project.facet.JavaFacetUtils; fpj.installProjectFacet( JavaFacetUtils.JAVA_50, null, ) Adjust appropriately depending on which version of the java facet you want. Converting an existing project into a faceted project and auto-detecting which facets should be install is not a typical WTP usecase, so we have no neat api for doing all of this or the associated ui. Thus, if you roll out this functionality, you would not be duplicating anything. Depending on how generic you make it, it may be appropriate to push it down into WTP. Hope that answers your questions. Let me know if you have any other. Thanks, - Konstantin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956127#3956127 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956127 |
|
From: julien.chambert <do-...@jb...> - 2006-07-07 09:24:25
|
Hello,
I don't manage to display webdav graph on a remote host....
When i try to use kosmos portlet on the localhost evrything is ok. on a remote host everythings are displayed except the chart.
I use a vm to launch the server (jboss-4.0.3, jboss portal 2.2.1, kosmos0.2.0rc2). I access the portlet by the host machine( the machine which launched vmware). I check the webdav repository with konqueror on the remote machine everything is ok...
To test the browser, I install kosmos on a second vm and I try to display the portlet with the first vm, the problem is the same.
Is this problem an install or configuration problem or a kosmos problem?
thanks for yours answer
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956121#3956121
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956121
|
|
From: <hei...@jb...> - 2006-07-07 09:14:37
|
We regard JBossWS+JBossXB as one distribution package. That means we are going communicate WS1.0.2 together with XBCR6. Poeple know how to upgrade XB when a new WS version is released and they expect it to run against the most current AS release, Branch_4_0 and jboss-head. What i am trying to avoid is having to tell them they should use different XB releases for these scenarios. A WS release may work in these environments or it may not. But it's all or nothing. And 'All' includes a particular XB release. If the next XB release can fullfill these requirements, then it's fine. But if you stick to the branch we need to backport all relevant changes. So, if XB 1.0 GA is not going to be released before the next AS, what's the benefit of maintaining a speparate XB codebase for the most current AS? However, it's your decision. But if you stick to your approach, please make sure the next XB release labels the AS sources as well, so we may easiliy recreate that release in order to port fixes to it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956120#3956120 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956120 |
|
From: <mar...@jb...> - 2006-07-07 08:50:11
|
Fine for now. I think the important thing at the moment is getting the text. We can sort out where it goes later. A developer's guide update is OK. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956113#3956113 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956113 |
|
From: fabiorusso <do-...@jb...> - 2006-07-07 08:23:02
|
That absolutely solved my problem! Got firebird working. Now I can easily and quickly unit test my ejb3 classes locally :-) Thank you so much! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956102#3956102 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956102 |
|
From: enazareno <do-...@jb...> - 2006-07-07 08:02:19
|
Hi Jason,
I really appreciate your taking the time to helping me out. Like I said, I'm quite a newbie with email as I haven't tried setting one up before. When I try to ping mail.ramesesinc.com, it responds so I assume that the DNS is ok (is this the wrong assumption?). My setup is like this - I have a linux machine where I've installed Jboss and is also the DNS server. Another machine runs on XP which is the client that runs the Outlook express.
As to the number of records:
messagedata = 0
storeitemmetadata = 44
paged_mail_store = 44
paged_mail_store_pages = 44
I will also try your suggestion to double check. Thanks again
Regards,
Elmo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956095#3956095
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956095
|
|
From: enazareno <do-...@jb...> - 2006-07-07 07:40:05
|
Hi,
Here's some additional info I printed from the server when sending mail
| 15:33:57,727 INFO [Server] Got request
| 15:33:57,744 INFO [Server] waiting for request
| 15:33:57,814 INFO [ConnectionHandler] connected: /10.0.0.3 to: /10.0.0.11 until: 1152257757728
| 15:33:58,475 INFO [Mail] all headers after loading: Return-Path: <el...@ra...>
| Received: from dev01 (dev01.lan 10.0.0.3) by mail.ramesesinc.com/JBossMail 1.0M4 (10.0.0.11)
| with SMTP id 1152257638474975.6487508340551; Fri, 7 Jul 2006 15:33:58 +0800 (PHT)
| Message-ID: <001101c6a196$944f5030$0300000a@dev01>
| Reply-To: "elmo" <el...@ra...>
| From: "elmo" <el...@ra...>
| To: <el...@ra...>,
| <elm...@ya...>
| Subject: Test Mail
| Date: Fri, 7 Jul 2006 15:25:52 +0800
| MIME-Version: 1.0
| Content-Type: multipart/alternative;
| boundary="----=_NextPart_000_000E_01C6A1D9.A2001F50"
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Mailer: Microsoft Outlook Express 6.00.2800.1106
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
|
| 15:33:58,613 INFO [AbstractStore] Creating store item
| 15:34:02,056 INFO [JMSMailListener] PUT MESSAGE ON QUEUE:org.jboss.mail.message.Mail@13b9fb
| 15:34:02,141 INFO [JMSMailListener] PUT MESSAGE ON QUEUE:org.jboss.mail.message.Mail@13b9fb
| 15:34:02,422 INFO [ConnectionHandler] ConnectionHandler finished
| S:
| 220 mta185.mail.mud.yahoo.com ESMTP YSmtp service ready
| 15:35:18,361 INFO [STDOUT] C:
| EHLO [127.0.0.1]
| 15:35:19,128 INFO [STDOUT] S:
| 250-mta185.mail.mud.yahoo.com
| 15:35:19,129 INFO [STDOUT] S:
| 250-8BITMIME
| 15:35:19,130 INFO [STDOUT] S:
| 250-SIZE 31981568
| 15:35:19,131 INFO [STDOUT] S:
| 250 PIPELINING
| 15:35:19,150 INFO [STDOUT] C:
| MAIL FROM:<el...@ra...>
| 15:35:19,934 INFO [STDOUT] S:
| 250 sender <el...@ra...> ok
| 15:35:19,936 INFO [SMTPSender] Sending mail from: <el...@ra...>
| 15:35:19,937 INFO [STDOUT] C:
| RCPT TO:<elm...@ya...>
| 15:35:21,497 INFO [STDOUT] S:
| 250 recipient <elm...@ya...> ok
| 15:35:21,503 INFO [SMTPSender] Delivering to: <elm...@ya...>
| 15:35:21,870 INFO [STDOUT] C:
| DATA
| 15:35:23,837 INFO [STDOUT] S:
| 354 go ahead
| 15:35:23,922 INFO [STDOUT] C:
| Return-Path: <el...@ra...>
| 15:35:23,924 INFO [STDOUT] C:
| Received: from dev01 (dev01.lan 10.0.0.3) by mail.ramesesinc.com/JBossMail 1.0M4 (10.0.0.11)
| 15:35:23,929 INFO [STDOUT] C:
| with SMTP id 1152257638474975.6487508340551; Fri, 7 Jul 2006 15:33:58 +0800 (PHT)
| 15:35:23,934 INFO [STDOUT] C:
| Message-ID: <001101c6a196$944f5030$0300000a@dev01>
| 15:35:23,940 INFO [STDOUT] C:
| Reply-To: "elmo" <el...@ra...>
| 15:35:23,941 INFO [STDOUT] C:
| From: "elmo" <el...@ra...>
| 15:35:23,946 INFO [STDOUT] C:
| To: <el...@ra...>,
| 15:35:23,946 INFO [STDOUT] C:
| <elm...@ya...>
| 15:35:23,947 INFO [STDOUT] C:
| Subject: Test Mail
| 15:35:23,947 INFO [STDOUT] C:
| Date: Fri, 7 Jul 2006 15:25:52 +0800
| 15:35:23,948 INFO [STDOUT] C:
| MIME-Version: 1.0
| 15:35:23,949 INFO [STDOUT] C:
| Content-Type: multipart/alternative;
| 15:35:23,949 INFO [STDOUT] C:
| boundary="----=_NextPart_000_000E_01C6A1D9.A2001F50"
| 15:35:23,950 INFO [STDOUT] C:
| X-Priority: 3
| 15:35:23,951 INFO [STDOUT] C:
| X-MSMail-Priority: Normal
| 15:35:23,951 INFO [STDOUT] C:
| X-Mailer: Microsoft Outlook Express 6.00.2800.1106
| 15:35:23,952 INFO [STDOUT] C:
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
| 15:35:23,963 INFO [STDOUT] C:
|
| 15:35:23,963 INFO [STDOUT] C:
| This is a multi-part message in MIME format.
| 15:35:23,964 INFO [STDOUT] C:
|
| 15:35:23,965 INFO [STDOUT] C:
| ------=_NextPart_000_000E_01C6A1D9.A2001F50
| 15:35:23,965 INFO [STDOUT] C:
| Content-Type: text/plain;
| 15:35:23,966 INFO [STDOUT] C:
| charset="iso-8859-1"
| 15:35:23,966 INFO [STDOUT] C:
| Content-Transfer-Encoding: quoted-printable
| 15:35:23,967 INFO [STDOUT] C:
|
| 15:35:23,968 INFO [STDOUT] C:
| Test Mail
| 15:35:23,968 INFO [STDOUT] C:
| ------=_NextPart_000_000E_01C6A1D9.A2001F50
| 15:35:23,969 INFO [STDOUT] C:
| Content-Type: text/html;
| 15:35:23,969 INFO [STDOUT] C:
| charset="iso-8859-1"
| 15:35:23,970 INFO [STDOUT] C:
| Content-Transfer-Encoding: quoted-printable
| 15:35:23,971 INFO [STDOUT] C:
|
| 15:35:23,971 INFO [STDOUT] C:
| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
| 15:35:23,972 INFO [STDOUT] C:
| <HTML><HEAD>
| 15:35:23,973 INFO [STDOUT] C:
| <META http-equiv=3DContent-Type content=3D"text/html; =
| 15:35:23,974 INFO [STDOUT] C:
| charset=3Diso-8859-1">
| 15:35:23,975 INFO [STDOUT] C:
| <META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
| 15:35:23,976 INFO [STDOUT] C:
| <STYLE></STYLE>
| 15:35:23,976 INFO [STDOUT] C:
| </HEAD>
| 15:35:23,976 INFO [STDOUT] C:
| <BODY bgColor=3D#ffffff>
| 15:35:23,977 INFO [STDOUT] C:
| <DIV><FONT face=3DArial size=3D2>Test Mail</FONT></DIV></BODY></HTML>
| 15:35:23,978 INFO [STDOUT] C:
|
| 15:35:23,979 INFO [STDOUT] C:
| ------=_NextPart_000_000E_01C6A1D9.A2001F50--
| 15:35:23,980 INFO [STDOUT] C:
|
| 15:35:23,980 INFO [STDOUT] C:
|
| 15:35:23,980 INFO [STDOUT] C:
|
| 15:35:25,008 INFO [STDOUT] S:
| 250 ok dirdel
| 15:35:25,009 INFO [STDOUT] C:
| QUIT
And heres some output when I issue telnet 110 which returns nothing on LIST
| 15:43:51,156 INFO [Server] Got request
| 15:43:51,157 INFO [Server] waiting for request
| 15:43:52,199 INFO [ConnectionHandler] connected: /10.0.0.1 to: /10.0.0.11 until: 1152258351156
| 15:44:02,995 WARN [CmdUSER] pop username set to elmo
|
Regards,
Elmo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956089#3956089
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956089
|
|
From: <go...@ic...> - 2006-07-07 07:35:06
|
first, though may not matter, not sure how the DNS implementation is on JBCS, but your x says ramesesinc.com but all the server names you used, or that are listed, state mail.ramesesinc.com you might change it so they all match, just to be safe, you could be having DNS issue's. Is the name of your server really mail.ramesesinc.com? If not, it may be tripping you up, and you may need to either fix DNS server, or your etc/hosts file - <!-- | Local domain group. The server will try to deliver any message to any | user | with the exact string in the @ clause locally. --> | - <mbean code="org.jboss.mail.domaingroup.DomainGroup" name="jboss.mail:type=MailServices,name=DomainGroup,group=Local"> | <attribute name="Postmaster" replace="true" trim="true" serialDataType="text">pos...@ra...</attribute> | - <attribute name="Domains" replace="true" trim="true" serialDataType="text"> | - <domains includes-local-interfaces="true"> | <domain>ramesesinc.com</domain> <!-- register the protocols you want to use | --> | <attribute name="Servername" replace="true" trim="true" serialDataType="text">mail.ramesesinc.com</attribute> you really should copy and post all the output you get when running .bat or .sh file , namely, post the data from this process 1. execute bat 2. wait till server is started 3. send an email using out look to yo...@yo..., as well as you@localhost, and you@localhost.localdomain, might as well try sending to other users as well, as m4 had an "unknown user" bug/fix, that could be causing this issue, but we cant tell as we dont have log 4. have outlook, check the mail on server (it doesnt list an error, correct?) then select all text, copy, paste, and post as code if it looks nice in purdy! you also, maight check the mail for the other users in outlook also, in case they get mail and you dont ("unknown user" again) sending an email to you@localhost (and other users), may be one of the simplest tests, as it doesnt use DNS as much, less prone to error if it lets you send mail to you@localhost or someone@localhost, then it's probably your DNS again, do you have any data in database? I.e. in the tables I mentioned? Telnet 216.122.130.130 25 | EHLO [hi] | MAIL FROM:<jg...@my...> | RCPT TO:<jasong@localhost> | RCPT TO:<ja...@my...> | DATA | FROM: JG...@my... | TO: Ja...@my... | TO: jasong@localhost | SUBJECT: Send Response | | this is another telnet test email | | | . | quit also, again, post the headers of the email that was successfully sent outside the domain so, to do: change server name in jboss-service.xml post log file try send mail to other users try receive mail for other users (outlook) look in your database for existence of mail data try and sendmail using telnet to outside mail acct without authenticating try and sendmail using telnet to outside mail acct with authenticating also, from your server, you might try an nslookup of ramesesinc.com and mail.ramesesinc.com make sure your dns is working locally, and get rid of those other DNS servers, till your issue is resolved, though it will interfere with sending out of domain mail, for example, to yahoo, may not be able to lookup. I'll do a diff of your and mine service.xml tomorrow, though dont know when I might have time, also, !!!Andrews Back!!! He'll probably be able to help, possibly without asking you go through all these steps... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956087#3956087 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956087 |
|
From: <max...@jb...> - 2006-07-07 06:59:19
|
How about ask the user what he want it deployed as if it is "undefined" ? And leave and option to simply choose to deploy (system copy) without verification. Then remember that setting for that resource. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956077#3956077 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956077 |
|
From: enazareno <do-...@jb...> - 2006-07-07 06:54:57
|
Hi Jason,
Thanks for your help. Here's the whole jboss-service.xml.
| <?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE server
| PUBLIC "-//JBoss//DTD MBean Service 4.0//EN"
| "http://www.jboss.org/j2ee/dtd/jboss-service_4_0.dtd">
|
| <server>
|
| <!--
| JBoss Mail Server 1.0 milestone 3 configruation.
| Please see
| http://wiki.jboss.org/wiki/Wiki.jsp?page=JBMSInstallingM3 for more
| configuration details.
| -->
|
| <!-- The SSL domain setup -->
| <mbean code="org.jboss.security.plugins.JaasSecurityDomain"
| name="jboss.security:service=JaasSecurityDomain,domain=Mail+SSL">
| <constructor>
| <arg type="java.lang.String" value="Mail+SSL"/>
| </constructor>
| <attribute
| name="KeyStoreURL">/opt/jboss-mail-server/versions/1.0M4/server/default/conf/jbmail.store</attribute>
| <attribute name="KeyStorePass">jbmsrulez123</attribute>
| </mbean>
|
|
| <!--
| <mbean code="org.jboss.mail.maillist.memory.MemoryMailListManager"
| name="jboss.mail:type=MailServices,name=MailListManager">
| <attribute name="MailingLists">
| <mailingLists>
| <mailingList>
|
| <listAddress>testlist@localhost.localdomain</listAddress>
|
| <property><name>replyToList</name><value>true</value></property>
| <property><name>subjectPrefix</name><value>Test
| List</value></property>
|
| <property><name>prefixAutoBracketed</name><value>true</value></property>
|
| <property><name>attachmentAllowed</name><value>false</value></property>
|
| <property><name>membersOnly</name><value>true</value></property>
| <members>
| <member>test@localhost.localdomain</member>
| <member>acoliver@localhost.localdomain</member>
| <member>test@localhost.localdomain</member>
| <member>jboss@localhost.localdomain</member>
| <member>eric@localhost.localdomain</member>
| <member>mikea@localhost.localdomain</member>
| <member>mikek@localhost.localdomain</member>
| <member>kabir@localhost.localdomain</member>
| </members>
| </mailingList>
| </mailingLists>
| </attribute>
| </mbean>
| -->
|
| <!--
| Queue for messages meant for posting replies to nukes forums
| -->
| <!--
| <mbean code="org.jboss.mq.server.jmx.Queue"
| name="jboss.mq.destination:service=Queue,name=nukespost">
| <depends
| optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
| -->
|
| <!--
| Queue for messages meant for a mail list hosted by this server
| -->
| <!-- <mbean code="org.jboss.mq.server.jmx.Queue"
| name="jboss.mq.destination:service=Queue,name=maillist">
| <depends
| optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
| -->
| <!--
| Queue for messages which will be delivered to users in a domain served
| by this
| server. (local users with an account here)
| -->
| <mbean code="org.jboss.mq.server.jmx.Queue"
| name="jboss.mq.destination:service=Queue,name=onServer">
| <depends
| optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
|
| <mbean code="org.jboss.mq.server.jmx.Queue"
| name="jboss.mq.destination:service=Queue,name=localMail">
| <depends
| optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
|
| <mbean code="org.jboss.mq.server.jmx.Queue"
| name="jboss.mq.destination:service=Queue,name=remoteMail">
| <depends
| optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
|
| <!--
| Queue for messages which will be delivered to users in a domain not
| served by
| this server.
| -->
| <mbean code="org.jboss.mq.server.jmx.Queue"
| name="jboss.mq.destination:service=Queue,name=offServer">
| <depends
| optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
|
| <!--
| Local domain group. The server will try to deliver any message to any
| user
| with the exact string in the @ clause locally.
| -->
| <mbean code="org.jboss.mail.domaingroup.DomainGroup"
| name="jboss.mail:type=MailServices,name=DomainGroup,group=Local">
| <attribute name="Postmaster">pos...@ra...</attribute>
| <attribute name="Domains">
| <domains includes-local-interfaces="true">
| <domain>ramesesinc.com</domain>
| <domain>localdomain</domain>
| </domains>
| </attribute>
| </mbean>
|
|
|
|
| <!--
| The SMTPSender MBean is used to send mails to remote hosts. It also
| maintains
| the DNS server list.
| -->
| <mbean code="org.jboss.mail.smtp.sender.SMTPSender"
| name="jboss.mail:type=MailServices,name=SMTPSender">
| <!-- if no servers then uses the default DNS servers from the
| host's resolution path. -->
| <attribute name="DNSServers">
| <servers>
| <server>10.0.0.11</server>
| <server>10.0.0.138</server>
| <server>127.0.0.1</server>
| <server>mail.ramesesinc.com</server>
| </servers>
| </attribute>
|
| </mbean>
|
| <!-- StaticUserRepository maintains the user account information as
| part of
| this configuration. You must specify the username and password
| below.
| Each user will be accepted as a local mailbox for any domain in
| the
| local domain group. You should be using JAAS login modules
| instead (like
| the database login module). Using SUR requires a restart for
| each change.
| -->
| <mbean code="org.jboss.mail.userrepository.StaticUserRepository"
|
| name="jboss.mail:type=MailServices,name=UserRepository,uimanageable=true">
| <attribute name="Users">
| <users>
| <user><id>elmo</id><password>tinoy2005</password></user>
| <user><id>jojo</id><password>tinoy2005</password></user>
| <user><id>worgie</id><password>tinoy2005</password></user>
| <user><id>jessie</id><password>tinoy2005</password></user>
| </users>
| </attribute>
| </mbean>
|
| <!-- UserRepository implementation for JAAS
| Uncomment and comment StaticUserRepository above to enable
| A JAAS security domain must be configured in conf/login-config.xml
| Currently only authenticates a user, no roles are checked
|
| <mbean code="org.jboss.mail.userrepository.jaas.JaasUserRepository"
|
| name="jboss.mail:type=MailServices,name=UserRepository,uimanageable=true">
| <xmbean state-action-on-update="restart">
| <depends>jboss.security:service=JaasSecurityManager</depends>
| <description>JBossMail user repository for JAAS</description>
| <descriptors>
| <persistence persistPolicy="OnUpdate"/>
| <persistence-manager
| value="org.jboss.mx.persistence.DelegatingPersistenceManager"/>
| </descriptors>
|
| <class>org.jboss.mail.userrepository.jaas.JaasUserRepository</class>
| <attribute access="read-write" getMethod="getSecurityDomain"
| setMethod="setSecurityDomain">
| <description>Security domain as configured in
| login-config.xml</description>
| <name>securityDomain</name>
| <type>java.lang.String</type>
| jboss-mail
| </attribute>
| <attribute access="read-write" getMethod="getPostmasterRole"
| setMethod="setPostmasterRole">
| <description>Role to identify a user as a postmaster</description>
| <name>postmasterRole</name>
| <type>java.lang.String</type>
| postmaster
| </attribute>
| <operation impact="ACTION_INFO">
| <name>authenticateUser</name>
| <description>Try to authenticate a user</description>
| <parameter>java.lang.String</parameter>
| <return-type>boolean</return-type>
| </operation>
| </xmbean>
| <attribute name="SecurityDomain">jboss-mail</attribute>
| </mbean-->
|
| <!-- UserRepository implementation for JAAS
| Uncomment and comment StaticUserRepository above to enable
| A JAAS security domain must be configured in conf/login-config.xml
| Currently only authenticates a user, no roles are checked
|
| <mbean code="org.jboss.mail.userrepository.jaas.JaasUserRepository"
|
| name="jboss.mail:type=MailServices,name=UserRepository,uimanageable=true,apop=true">
| <xmbean state-action-on-update="restart">
| <depends>jboss.security:service=JaasSecurityManager</depends>
| <description>JBossMail user repository for JAAS</description>
| <descriptors>
| <persistence persistPolicy="OnUpdate"/>
| <persistence-manager
| value="org.jboss.mx.persistence.DelegatingPersistenceManager"/>
| </descriptors>
|
| <class>org.jboss.mail.userrepository.jaas.JaasUserRepository</class>
| <attribute access="read-write" getMethod="getSecurityDomain"
| setMethod="setSecurityDomain">
| <description>Security domain as configured in
| login-config.xml</description>
| <name>securityDomain</name>
| <type>java.lang.String</type>
| jboss-mail
| </attribute>
| <attribute access="read-write" getMethod="getPostmasterRole"
| setMethod="setPostmasterRole">
| <description>Role to identify a user as a postmaster</description>
| <name>postmasterRole</name>
| <type>java.lang.String</type>
| postmaster
| </attribute>
| <operation impact="ACTION_INFO">
| <name>authenticateUser</name>
| <description>Try to authenticate a user</description>
| <parameter>java.lang.String</parameter>
| <return-type>boolean</return-type>
| </operation>
| </xmbean>
| <attribute name="SecurityDomain">jboss-mail-apop</attribute>
| </mbean-->
|
|
|
| <!--
| Hibernate based store that uses a Paging mechanism
| to achieve partial I/O across a range of databases
| -->
| <mbean code="org.jboss.mail.store.paged.PagedStore"
| name="jboss.mail:type=MailServices,name=PagedStore">
| <attribute name="PageSize">65536</attribute>
| <attribute name="Compress">true</attribute>
| <attribute name="CompressBufferSize">65536</attribute>
| <attribute name="StartIndex">0</attribute>
| <attribute name="Hashed">false</attribute>
| <!--depends>jboss.mail:service=Hibernate</depends-->
| </mbean>
|
|
|
| <!-- Mail Body Manager -->
| <mbean code="org.jboss.mail.message.MailBodyManager"
| name="jboss.mail:type=MailServices,name=MailBodyManager">
| <attribute name="UseStore">true</attribute>
| <depends optional-attribute-name="Store"
|
| proxy-type="attribute">jboss.mail:type=MailServices,name=PagedStore</depends>
| </mbean>
|
| <mbean code="org.jboss.mail.mailbox.MailboxServiceImpl"
| name="jboss.mail:type=MailServices,name=MailboxManager"
| xmbean-dd="META-INF/Mailbox-xmbean.xml">
| <depends optional-attribute-name="BodyManager"
|
| proxy-type="attribute">jboss.mail:type=MailServices,name=MailBodyManager</depends>
| </mbean>
|
| <!--
| JMS is used to asynchronously process mails, however the bodies are
| not stored via JMS as JBossMQ, the present
| JBosss messaging solution, doesn't do this efficiently. This
| instance is to support nukes mail list integration.
| -->
| <!--
| <mbean code="org.jboss.mail.maillistener.NukesPosterJMSMailListener"
| name="jboss.mail:type=MailServices,name=NukesPosterJMSListener">
| <constructor>
| <arg type="java.lang.String" value="java:/ConnectionFactory"/>
| <arg type="java.lang.String" value="java:/ConnectionFactory"/>
| </constructor>
| <attribute
| name="NukesForumPoster">nukes.modules:name=NukesForumMailPoster</attribute>
| <attribute name="DestinationType">queue</attribute>
| <attribute name="Destination">nukespost</attribute>
| <depends
| optional-attribute-name="DomainGroup">jboss.mail:type=MailServices,name=DomainGroup,group=Local</depends>
| <depends>jboss.mq:service=DestinationManager</depends>
| <depends>jboss.mq.destination:name=maillist,service=Queue</depends>
| </mbean> -->
|
| <!--
| This JMS mail listener is used to pass things to the mail list
| processing plugins (MDBs).
| -->
| <!--
| <mbean code="org.jboss.mail.maillistener.MailListJMSMailListener"
| name="jboss.mail:type=MailServices,name=MailListJMSListener">
| <constructor>
| <arg type="java.lang.String" value="java:/ConnectionFactory"/>
| <arg type="java.lang.String" value="java:/ConnectionFactory"/>
| </constructor>
|
| <attribute name="DestinationType">queue</attribute>
| <attribute name="Destination">maillist</attribute>
| <depends>jboss.mq:service=DestinationManager</depends>
|
| <depends>jboss.mq.destination:name=maillist,service=Queue</depends>
| <depends
| optional-attribute-name="MailListManager">jboss.mail:type=MailServices,name=MailListManager</depends>
| </mbean>
| -->
|
| <!--
| JMS is used to asynchronously process mails, however the bodies are
| not stored via JMS as JBossMQ, the present
| JBosss messaging solution, doesn't do this efficiently. This is
| used for normal mail processing.
| -->
| <mbean code="org.jboss.mail.maillistener.JMSMailListener"
| name="jboss.mail:type=MailServices,name=MailListener">
| <constructor>
| <arg type="java.lang.String" value="java:/ConnectionFactory"/>
| <arg type="java.lang.String" value="java:/ConnectionFactory"/>
| </constructor>
|
| <depends>jboss.mq:service=DestinationManager</depends>
| <!--
| <depends>jboss.management.local:j2eeType=JCAManagedConnectionFactory,name=JmsXA</depends>-->
|
|
| <depends>jboss.mq.destination:name=localMail,service=Queue</depends>
|
| <depends>jboss.mq.destination:name=remoteMail,service=Queue</depends>
| <depends
| optional-attribute-name="DomainGroup">jboss.mail:type=MailServices,name=DomainGroup,group=Local</depends>
| <!-- queue or topic -->
| <attribute name="DestinationType">queue</attribute>
| <!-- posts which are OnServer meaning they are for our domain and
| presumably a "local" user
| and won't go through an additional SMTP server should be sent
| here -->
| <attribute name="OnServerPostDestination">localMail</attribute>
| <!-- posts which are OffServer meaning they will go through an
| additional SMTP server before
| finally being received should go here -->
| <attribute name="OffServerPostDestination">remoteMail</attribute>
| <!-- Specifies the retry policy for failed local mail recipients.
| You can add as many retryTime
| elements as you like. Each retryTime element specifies the
| time in seconds to wait before
| redelivery, and they are processed from the top. Once you run
| out of retry entries a bounce
| message is generated for the sender. In the configuration
| shown below, if a message fails
| it will retry after a minute, if the retry fails
| it will retry again after a further two minutes, if the
| retry fails
| it will retry after after a further ten minutes, if the
| retry fails
| it will retry after after a further hour, if the retry
| fails
| it will retry after after a further hour, if the retry
| fails
| it will generate a bounce message
| -->
| <attribute name="LocalRetryTimes">
| <localRetryTimes>
| <retryTime>60</retryTime>
| <retryTime>120</retryTime>
| <retryTime>600</retryTime>
| <retryTime>3600</retryTime>
| <retryTime>3600</retryTime>
| </localRetryTimes>
| </attribute>
| <!-- Specifies the retry policy for failed remote mail recipients.
| You can add as many retryTime
| elements as you like. Each retryTime element specifies the
| time in seconds to wait before
| redelivery, and they are processed from the top. Once you run
| out of retry entries a bounce
| message is generated for the sender. In the configuration
| shown below, if a message fails
| it will retry after a minute, if the retry fails
| it will retry again after a further two minutes, if the
| retry fails
| it will retry after after a further ten minutes, if the
| retry fails
| it will retry after after a further hour, if the retry
| fails
| it will retry after after a further hour, if the retry
| fails
| it will generate a bounce message
| -->
| <attribute name="RemoteRetryTimes">
| <remoteRetryTimes>
| <retryTime>60</retryTime>
| <retryTime>120</retryTime>
| <retryTime>600</retryTime>
| <retryTime>3600</retryTime>
| <retryTime>3600</retryTime>
| </remoteRetryTimes>
| </attribute>
| </mbean>
|
| <mbean code="org.jboss.mail.MailListenerChainService"
| name="jboss.mail:type=MailServices,name=MailListenerChain"
| xmbean-dd="META-INF/chain-xmbean.xml">
|
| <depends>jboss.mail:type=MailServices,name=MailListener</depends>
| <attribute name="Listeners">
| <listeners>
| <!-- Uncomment to allow replies to go to Nukes
|
| <value>jboss.mail:type=MailServices,name=NukesPosterJMSListener</value>
| -->
|
| <listener>jboss.mail:type=MailServices,name=MailListener</listener>
| </listeners>
| </attribute>
| </mbean>
|
|
| <!--
| Mail Listener responsible for delivering mails to local mailboxes.
| -->
| <mbean code="org.jboss.mail.mailhandler.localmailbox.LocalDelivery"
| name="jboss.mail:type=MailServices,name=LocalDelivery">
| <depends optional-attribute-name="MailboxManager"
|
| proxy-type="attribute">jboss.mail:type=MailServices,name=MailboxManager</depends>
| <depends optional-attribute-name="Router"
|
| proxy-type="org.jboss.mail.MailListener">jboss.mail:type=MailServices,name=MailListener</depends>
| </mbean>
|
| <!--
| Mail Listener chain for mails to be delivered locally.
| Any listeners that are specific to locally delivered mail should be
| added here. E.g. SPAM filtering.
| -->
| <mbean code="org.jboss.mail.MailListenerChainService"
| name="jboss.mail:type=MailServices,name=LocalDeliveryChain"
| xmbean-dd="META-INF/chain-xmbean.xml">
| <depends>jboss.mail:type=MailServices,name=LocalDelivery</depends>
| <attribute name="Listeners">
| <listeners>
|
| <listener>jboss.mail:type=MailServices,name=LocalDelivery</listener>
| </listeners>
| </attribute>
| </mbean>
|
| <!--
| Mail Listener responsible for delivering mails to remote addresses.
| -->
| <mbean code="org.jboss.mail.mailhandler.remote.RemoteDelivery"
| name="jboss.mail:type=MailServices,name=RemoteDelivery">
| <depends optional-attribute-name="Router"
|
| proxy-type="org.jboss.mail.MailListener">jboss.mail:type=MailServices,name=MailListener</depends>
| <depends optional-attribute-name="DomainGroup"
|
| proxy-type="attribute">jboss.mail:type=MailServices,name=DomainGroup,group=Local</depends>
| <depends optional-attribute-name="Sender"
|
| proxy-type="attribute">jboss.mail:type=MailServices,name=SMTPSender</depends>
| </mbean>
|
| <!--
| Mail Listener chain for mails to be delivered remotely.
| -->
| <mbean code="org.jboss.mail.MailListenerChainService"
| name="jboss.mail:type=MailServices,name=RemoteDeliveryChain"
| xmbean-dd="META-INF/chain-xmbean.xml">
| <depends>jboss.mail:type=MailServices,name=RemoteDelivery</depends>
| <attribute name="Listeners">
| <listeners>
|
| <listener>jboss.mail:type=MailServices,name=RemoteDelivery</listener>
| </listeners>
| </attribute>
| </mbean>
|
|
| <!--
| SMTPProtocol is used for a "Server" instance. This is an
| unencrypted
| protocol
| -->
| <mbean code="org.jboss.mail.smtp.SMTPProtocol"
| name="jboss.mail:type=MailServices,name=SMTPProtocol">
|
| <depends optional-attribute-name="DomainGroup"
|
| proxy-type="attribute">jboss.mail:type=MailServices,name=DomainGroup,group=Local</depends>
| <depends optional-attribute-name="MailBodyManager"
|
| proxy-type="attribute">jboss.mail:type=MailServices,name=MailBodyManager</depends>
| <depends optional-attribute-name="ListenerChain"
|
| proxy-type="org.jboss.mail.MailListenerChain">jboss.mail:type=MailServices,name=MailListenerChain</depends>
| <depends optional-attribute-name="UserRepository"
|
| proxy-type="attribute">jboss.mail:type=MailServices,name=UserRepository,uimanageable=true</depends>
|
|
| <depends>jboss.security:service=JaasSecurityDomain,domain=Mail+SSL</depends>
| <attribute name="SecurityDomain">java:/jaas/Mail+SSL</attribute>
| <!--register the protocols you want to use -->
| <attribute name="Servername">mail.ramesesinc.com</attribute>
| <!--
| auth-required - optional, default = true: Determines whether we
| require the
| user to login to the SMTP server in order to send the mail. By
| default we
| do require it. I'd rather folks say that JBMail doesn't work at
| all than
| say its an open relay....if YOU misconfigure it you CAN make it
| an open
| relay....Its going to warn you in big bold fat letters. This is
| only
| required to send mail to some SMTP server outside of your domain
| -->
| <attribute name="AuthRequired">true</attribute>
| <!--
| JBMail can not be configured as an open relay, you must specify a
| list of domains
| to allow relaying to.
| -->
| <attribute name="RelayByDomain">false</attribute>
| <!--
| auth-allowed means that users are allowed to login. This is
| othogonal to AuthRequired.
| Where AuthRequired means "auth required in order to send mail",
| AuthAllowed means
| "is anyone able to log in at all?" A completely open relay (spam
| machine) would not
| require authenticaiton and might not even allow it (so it can't
| be tracked or whatever).
| One reason to FORBID authentication is if you want users to only
| authenticate over SSL but
| want a seperate instance of SMTP (on the same box even) to
| receive mails from the outside for
| local users.
| -->
| <attribute name="AuthAllowed">true</attribute>
| <!--
| auth methods allowed. DO NOT CHANGE THIS (unless you really know
| what
| you are doing and have a very good reason to)
| -->
| <attribute name="AuthMethods">AUTH LOGIN PLAIN</attribute>
|
| <!-- verify the identity -->
| <attribute name="VerifyIdentity">true</attribute>
| <attribute name="MaxMessageSize">10000000</attribute>
| <!-- block size for messages (should be about your average message
| size) -->
| <attribute name="BlockSize">4096</attribute>
| <!-- rfc 2487 related properties -->
| <attribute name="RequireTls">false</attribute>
| <attribute name="RequireTlsForAuth">false</attribute>
| <attribute name="RequireClientCert">false</attribute>
| <!-- change to true for TLS support -->
| <attribute name="TlsEnabled">true</attribute>
| <attribute name="PostMaster">pos...@ra...</attribute>
| <!--
| The maximum number of received headers allowed (to avoid
| looping).
| If greater than this the message is not accepted. Default is 100
| if not present
| -->
| <attribute name="MaxReceivedHdrs">100</attribute>
| <!--
| The number of received headers before we start inspecting them
| looking
| for our server to see if more than maxOwnReceivedHdrs are present
| Default is 20 if not present
| -->
| <attribute name="ReceivedHdrsThreshold">20</attribute>
| <!--
| The number of received headers for our server allowed.
| Default is 5 if not present
| -->
| <attribute name="MaxOwnReceivedHdrs">5</attribute>
| </mbean>
|
| <!-- defines an SMTP server. -->
| <mbean code="org.jboss.mail.Server"
| name="jboss.mail:type=MailServices,name=SMTP">
| <depends>jboss.mail:type=MailServices,name=SMTPProtocol</depends>
| <!-- protocol should reference SMTP -->
| <attribute
| name="Protocol">jboss.mail:type=MailServices,name=SMTPProtocol</attribute>
| <!-- port to listen on -->
| <attribute name="Port">25</attribute>
| <!-- which addresses to listen on 0.0.0.0 = all or localhost means
| only the localhost -->
| <attribute name="Address">0.0.0.0</attribute>
| <!-- timeout between commands (not presently supported) -->
| <!-- note from mikea: rfc 821 sets strict guidelines on allowable
| timeouts -->
| <attribute name="Timeout">30000</attribute>
| <!-- timeout for the connection regardless of whether it is
| finished. Thus it will kill the
| socket and thread mid-stream/operation. This should be big
| enough to allow whatever the
| messages you're sending while defending against folks who
| might try to DoS your server
| by keeping a large number of connections alive -->
| <!-- note from mikea: 10 mb in 120 seconds is about 100 kb/s -
| which may or may not be
| the actual bandwidth achieved depending on server. therefore,
| i believe this value should
| be set somewhat higher to avoid timing out on 10mb emails,
| and other methods be used to detect DoS's -->
| <attribute name="Life">120000</attribute>
| <attribute name="PoolSize">5</attribute>
| </mbean>
|
|
|
|
| <mbean code="org.jboss.mail.pop3.POP3Protocol"
| name="jboss.mail:type=MailServices,name=POP3Protocol">
|
| <depends>jboss.security:service=JaasSecurityDomain,domain=Mail+SSL</depends>
| <attribute name="SecurityDomain">java:/jaas/Mail+SSL</attribute>
| <depends>jboss.mail:type=MailServices,name=MailListener</depends>
| <depends optional-attribute-name="MailboxManager"
|
| proxy-type="attribute">jboss.mail:type=MailServices,name=MailboxManager</depends>
| <depends optional-attribute-name="UserRepository"
|
| proxy-type="attribute">jboss.mail:type=MailServices,name=UserRepository,uimanageable=true</depends>
| <!--depends optional-attribute-name="APOPUserRepository"
|
| proxy-type="attribute">jboss.mail:type=MailServices,name=UserRepository,uimanageable=true,apop=true</depends-->
| <!--register the protocols you want to use -->
| <attribute name="Servername">mail.ramesesinc.com</attribute>
| <attribute name="TlsEnabled">true</attribute>
| <attribute name="RequireTls">false</attribute>
| <!-- enable for forcing clients to use their own certificats
| -->
| <attribute name="RequireClientCert">false</attribute>
| </mbean>
|
|
|
| <!-- defines a POP server. -->
| <mbean code="org.jboss.mail.Server"
| name="jboss.mail:type=MailServices,name=POP3">
| <depends>jboss.mail:type=MailServices,name=POP3Protocol</depends>
| <!-- options are presently POP or SMTP, we want POP -->
| <attribute
| name="Protocol">jboss.mail:type=MailServices,name=POP3Protocol</attribute>
| <!-- port to listen on -->
| <attribute name="Port">110</attribute>
| <!-- which addresses to listen on 0.0.0.0 = all or localhost means
| only the localhost -->
| <attribute name="Address">0.0.0.0</attribute>
| <!-- timeout between commands (not presently supported) -->
| <attribute name="Timeout">30000</attribute>
| <!-- timeout for the connection regardless of whether it is
| finished. Thus it will kill the
| socket and thread mid-stream/operation. This should be big
| enough to allow whatever the
| messages you're sending while defending against folks who
| might try to DoS your server
| by keeping a large number of connections alive -->
| <attribute name="Life">120000</attribute>
| <attribute name="PoolSize">5</attribute>
| <attribute name="UsesSSL">false</attribute>
| </mbean>
|
|
| <!-- fetchmail example see
| http://wiki.jboss.org/wiki/Wiki.jsp?page=HowToConfigurePOPFetchmailForJBossMailServer1.0M4 for
| details
| <mbean code="org.jboss.mail.fetchmail.Popper"
| name="jboss.mail:type=Fetchmail,name=Popper,instance=example">
| must be unique
| <attribute name="Servername">foo.nowhere.com</attribute>
| <attribute name="PopPort">110</attribute>
| <attribute name="PopUser">remoteuser</attribute>
| <attribute name="Password">mypassword</attribute>
| <attribute name="LocalUser">andy@localhost</attribute>
| <attribute name="DeleteAfterPop">false</attribute>
| <depends optional-attribute-name="SMTPProtocol"
|
| proxy-type="org.jboss.mail.smtp.SMTPProtocolMBean">jboss.mail:type=MailServices,name=SMTPProtocol</depends>
| </mbean>
|
| <mbean code="org.jboss.varia.scheduler.Scheduler"
|
| name="jboss.mail:service=Scheduler,name=Popper,instance=example"> unique
| <attribute name="StartAtStartup">true</attribute>
| this needs to match your Popper instance's mbean name
| <attribute
| name="SchedulableMBean">jboss.mail:type=Fetchmail,name=Popper,instance=example</attribute>
| <attribute name="SchedulableMBeanMethod">pop()</attribute>
| <attribute name="InitialStartDate">NOW</attribute>
| <attribute name="SchedulePeriod">10000</attribute>
| <attribute name="InitialRepetitions">-1</attribute>
| </mbean>
| -->
|
| </server>
|
Now, that you mention it, I'm not so sure if the SMTP is the culprit and not POP3. If it is able to send the mail remotely, does it mean it can send also locally? I was assuming that since I can send mail to my yahoo account, that it can also send mails in the intranet. What I also noticed in Outlook express is that port 110 does not use security, while port 995 is secured. Do you think its my Outlook express configuration? How do I test SMTP via telnet? Thanks again.
Regards,
Elmo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956076#3956076
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956076
|
|
From: <cle...@jb...> - 2006-07-07 06:34:36
|
UnifiedINvokers is only available on 4.0.x. maybe this page could give you some hints: http://wiki.jboss.org/wiki/Wiki.jsp?page=SPECjAppServer2004 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956068#3956068 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956068 |
|
From: <go...@ic...> - 2006-07-07 02:19:46
|
oh, and I did a windiff between your mbeans and mine, and they were basically the same... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956049#3956049 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956049 |
|
From: <go...@ic...> - 2006-07-07 02:19:07
|
then in pop3 mbean says "mail.ramesesinc.com" can you POST your install script, if you created one? Covering the sensitive stuff obviously... it doesnt look like TLS/WTLS is messing you up, as you telnetted in w/out encryption. It sounds like something with the user name/alias/mailbox, or domain. But you said it (same mail server) let you email an outside account, which means your allowing that domain for relay? Can you POST the headers from that email that successflly made it to the outside account? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956048#3956048 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956048 |
|
From: <go...@ic...> - 2006-07-07 02:05:53
|
yeah, but are you sure, cus when you telnetted, you did telnet mail.ramesesinc.com 110 | | Trying 10.0.0.11... | | Connected to mail.ramesesinc.com. ??? is there any data in the database, i.e. in messagedata, storeitemmetadata, paged_mail_store, and paged_mail_store_pages do you have any errors in output? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956047#3956047 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956047 |
1965 messages has been excluded from this view by a project administrator.
