550 Not Authorized

[nsilberz]

I created my accounts & mailbox.
All mails are received fine.
But i can't send a mail: i got a not authorized error.
Did i miss something?

[acoliver]

try turning off "verify identity" does that work?

[nsilberz]

How to do that?

[acoliver]

its a setting in ($JBMS_HOME/server/default/deploy/mail.ear/mail.sar/META-INF/jboss-service.xml)

if that doesn't do it then send that file here in code tags.

[nsilberz]

I changed to false, launch server again: same error

<?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">E:\JBossMailServer/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>[e-mail]</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>[e-mail]</member>
 <member>[e-mail]</member>
 <member>[e-mail]</member>
 <member>[e-mail]</member>
 <member>[e-mail]</member>
 <member>[e-mail]</member>
 <member>[e-mail]</member>
 <member>[e-mail]</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">[e-mail]</attribute>
 <attribute name="Domains">
 <domains includes-local-interfaces="true">
 <domain>myDomain.com</domain>
 <domain>myDomain.com</domain>
 <domain>tuxmedia.com</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>84.55.133.98</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>nicolas</id><password>captain</password></user>
 <user><id>olivier</id><password>captain</password></user>
 <user><id>caroline</id><password>captain</password></user>
 <user><id>jflefevre</id><password>yaya</password></user>
<!--
nom complet:Chittima myDomain
logon:chittima
psw:tanwa72
email:[e-mail]
email alternatif:[e-mail]
-->
<user><id>chittima</id><password>tanwa72</password></user>

<!--
nom complet: Philippe myDomain
logon:philippe
psw:captain
email:[e-mail]
email alternatif:[e-mail]
-->
<user><id>philippe</id><password>captain</password></user>

<!--
nom complet: Nadine myDomain
logon:nadine
psw:captain
email:[e-mail]
email alternatif:
-->
<user><id>nadine</id><password>captain</password></user>

<!--
nom complet: Pierre myDomain
logon:pierre
psw:captain
email:[e-mail]
email alternatif:
-->
<user><id>pierre</id><password>captain</password></user>
<user><id>katrin</id><password>captain</password></user>
<user><id>lena</id><password>captain</password></user>
<user><id>linette</id><password>captain</password></user>
<user><id>claude</id><password>captain</password></user>
<user><id>gilles</id><password>captain</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">myDomain.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">false</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">[e-mail]</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">myDomain.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>

[acoliver]

who are you logging in as?

[nsilberz]

nicolas

[acoliver]

What Email client is this? And what options are selected?

do this:

telnet (hostname) 25
AUTH nicolas
220 balbla
(use this too:
MAIL FROM: <[e-mail]>
RCPT TO: <[e-mail]>
DATA

From: <[e-mail]>
To: <[e-mail]>
Subject: whoa it worked

It must be my settings in my mail client!

.

quit

[acoliver]

sorry meant "use this tool: http://www.motobit.com/util/base64-decoder-encoder.asp"

[nsilberz]

with telnet, the line

RCPT TO: <[e-mail]>

makes the error

(550 Not Authorized)

[acoliver]

did you AUTH first?

[nsilberz]

no idea?

[acoliver]

scroll up.

[nsilberz]

of course.
previous lines makes no error until this one.

[nsilberz]

email client is Outlook, no particular setup