1 2 Previous Next 17 Replies Latest reply on Jul 11, 2006 4:12 PM by Jay Glass

    how to test POP3 in Outlook

    Elmo Novice

      Hello,

      I have tried setting up the mail server and configured outlook as the client. There is no problem in my SMTP and sending mail remotely. However I want to test my mail locally. I have tested my DNS and its working fine. When I try to send to myself I cannot see the mail in my inbox. I have not tried setting up a mail server before so I'm not really familiar with how this goes. I can see there is a message in the database but it seems its not being pulled into outlook. There are no errors and I can connect to POP3 at port 110 via telnet. Is there something I'm not doing right? Appreciate any suggestions.

      Regards,

      Elmo

        • 1. Re: how to test POP3 in Outlook
          Jay Glass Novice

          are you authenticating, did you set it to require auth? Did you set it to require TLS or ?WTLS??

          When you connect to it on POP using telnet, can you issue the commands to list a users mail?

          • 2. Re: how to test POP3 in Outlook
            Elmo Novice

            Hi,

            Thanks for the reply. This is my jboss-service.xml :

            <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>
            


            And when i telnet :


            telnet mail.ramesesinc.com 110
            Trying 10.0.0.11...
            Connected to mail.ramesesinc.com.
            Escape character is '^]'.
            +OK POP3 Server (JBMAIL POP3 Server version 1.0M4) ready <61.1152236103151@mail.ramesesinc.com>
            USER elmo
            +OK
            PASS tinoy2005
            +OK
            LIST
            +OK 0 messages (0 octets)
            .



            When sending mail, I used outlook express and composed mail to two addresses:
            elmo@mail.ramesesinc.com and the other is my yahoo mail. The yahoo mail receives it but my local mail does not. Would appreciate any help.

            Regards,

            Elmo


            • 3. Re: how to test POP3 in Outlook
              Elmo Novice

              Sorry i misttyped this


              When sending mail, I used outlook express and composed mail to two addresses:
              elmo@mail.ramesesinc.com and the other is my yahoo mail.


              should be : elmo@ramesesinc.com, not elmo@mail.ramesesinc.com

              Regards,

              Elmo

              • 4. Re: how to test POP3 in Outlook
                Jay Glass Novice

                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?



                • 5. Re: how to test POP3 in Outlook
                  Jay Glass Novice

                  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?

                  • 6. Re: how to test POP3 in Outlook
                    Jay Glass Novice

                    oh, and I did a windiff between your mbeans and mine, and they were basically the same...

                    • 7. Re: how to test POP3 in Outlook
                      Elmo Novice

                      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">postmaster@ramesesinc.com</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">postmaster@ramesesinc.com</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


                      • 8. Re: how to test POP3 in Outlook
                        Jay Glass Novice

                        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">postmaster@ramesesinc.com</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 you@yourdomain.com, 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:<jglass@my.domain.com>
                        RCPT TO:<jasong@localhost>
                        RCPT TO:<jasong@my.domain.com>
                        DATA
                        FROM: JGlass@my.domain.com
                        TO: JasonG@my.domain.com
                        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...

                        • 9. Re: how to test POP3 in Outlook
                          Elmo Novice

                          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: <elmo@ramesesinc.com>
                          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" <elmo@ramesesinc.com>
                          From: "elmo" <elmo@ramesesinc.com>
                          To: <elmo@ramesesinc.com>,
                           <elmonazareno@yahoo.com>
                          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:<elmo@ramesesinc.com>
                          15:35:19,934 INFO [STDOUT] S:
                          250 sender <elmo@ramesesinc.com> ok
                          15:35:19,936 INFO [SMTPSender] Sending mail from: <elmo@ramesesinc.com>
                          15:35:19,937 INFO [STDOUT] C:
                          RCPT TO:<elmonazareno@yahoo.com>
                          15:35:21,497 INFO [STDOUT] S:
                          250 recipient <elmonazareno@yahoo.com> ok
                          15:35:21,503 INFO [SMTPSender] Delivering to: <elmonazareno@yahoo.com>
                          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: <elmo@ramesesinc.com>
                          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" <elmo@ramesesinc.com>
                          15:35:23,941 INFO [STDOUT] C:
                          From: "elmo" <elmo@ramesesinc.com>
                          15:35:23,946 INFO [STDOUT] C:
                          To: <elmo@ramesesinc.com>,
                          15:35:23,946 INFO [STDOUT] C:
                           <elmonazareno@yahoo.com>
                          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

                          • 10. Re: how to test POP3 in Outlook
                            Elmo Novice

                            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



                            • 11. Re: how to test POP3 in Outlook
                              Andrew Oliver Master

                              Very interesting. What DB is this? It looks like your storage is messed up or the messages are stuck in the queue.

                              • 12. Re: how to test POP3 in Outlook
                                Jay Glass Novice

                                oh, yeah, that looks a little messed up...messagedata is empty, where in it looks like you have actually received about 44 emails

                                as andrew has pointed out, did you mess with the headers in anyway, as I think thats whats in message data, mainly

                                • 13. Re: how to test POP3 in Outlook
                                  Jay Glass Novice

                                  Andrew, cant this also occur, when messages are actually being delivered, i.e. delivered to outlook, but user forgot to uncheck "remove/delete messages from server"

                                  then they would'nt exist in messagedata, but would exist elsewhere?

                                  • 14. Re: how to test POP3 in Outlook
                                    Elmo Novice

                                    Hi Andrew and Jason,

                                    I am using MySQL 5. I am out of the office right now but there's an option that I've checked in outlook something like delete after some days. Will this have an effect? I will try to check it out on Monday. But I've been thinking about Jason's suggestion to remove security. I remember when I installed it it requires SSL when sending but there is no security when receiving POP3. I will try to reinstall it and remove the security. I have observed when I try the send/receive option in Outlook I can see the ff quick messages - Authenticating ... and then Disconnecting. I am not very familiar with this stuff so basically I don't know how to test it. I don't even know how to see the logs in Outlook. I am using Outlook bec. most people use it but if I have the time I will try Mozilla. But I assume this shouldn't be a problem. Anyway, I appreciate all your help. Thanks and have a good weekend.

                                    Regards,

                                    Elmo

                                    1 2 Previous Next