You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2002/08/23 06:44:45 UTC

RE: Outgoing mail problem

Incoming messages are working just fine, but when I try to send out
using JAMES smtp it immediately routes the messages to spam. 

Did you configure the RemoteAddrNotInNetwork matcher?

	--- Noel

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Sendmail, at last an answer ! (was RE: Help Please)

Posted by Danny Angus <da...@apache.org>.
Hi,

I've worked out how to configure sendmail to route all mail, even local
mail, through James, and use SMTP AUTH if need be.

This is all contained in a new HOW-TO document at
http://jakarta.apache.org/james/james_and_sendmail.html

I hope enough of the people who've asked this question over the last year
are still subscribed to this list to see the answer!

d.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Help Please

Posted by Super-User <sk...@telegea.com>.
Danny ,

How are you ?.

Thanks for the info.

Thanks,
Srinivas.

> > bash-2.05# /usr/lib/sendmail -v skatta@telegea.com
>
> Sendmail invoked this way doesn't use James, it doesn't even use its own
> SMTP daemon... it spools it and sends it directly itself, even when the
> daemon isn't running.
>
> You cant use James to replace sendmail in this way, not very well.
>
> Furthermore you can't configure sendmail to use port 25 on the same machine
> as a mail gateway, in its wisdom it assumes this to be a misconfiguration
> and chokes. This is true whether you use 127.0.0.1 or localhost or hostname
> or host.domain name or localnet or internet IPaddreses, sendmail won't relay
> through the local machine
>
> :-(
>
> d.
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Help Please

Posted by Danny Angus <da...@apache.org>.
> bash-2.05# /usr/lib/sendmail -v skatta@telegea.com

Sendmail invoked this way doesn't use James, it doesn't even use its own
SMTP daemon... it spools it and sends it directly itself, even when the
daemon isn't running.

You cant use James to replace sendmail in this way, not very well.

Furthermore you can't configure sendmail to use port 25 on the same machine
as a mail gateway, in its wisdom it assumes this to be a misconfiguration
and chokes. This is true whether you use 127.0.0.1 or localhost or hostname
or host.domain name or localnet or internet IPaddreses, sendmail won't relay
through the local machine

:-(

d.



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Help Please

Posted by Super-User <sk...@telegea.com>.
Noel ,

How are you ?.

I have a question on JAMES SMTP.

My mailx cmd was sending mails to Internet through mailhost.

But,it was not sending mails to Internet through gateway,which  was mentioned
in
the config.xml.

Here is the my mail header.
-----------------------------------
bash-2.05# /usr/lib/sendmail -v skatta@telegea.com
test
.
skatta@telegea.com... Connecting to mailhost via relay...
-----------------------------------

I have updated config.xml for to add the gateway.

Here is the config.xml info.

------------------------------
<gateway>exchanger.telegea.com</gateway>
-------------------------------

Please advice me.

Thanks,
Srinivas.



> I meant for him to try dave@localhost explicitly when he was sending, in
> case something mailx was doing something with the null domain before the
> <user> got to James.
>
> His config.xml has localhost explicit and autodetect=true.  From his spool
> log, we can see that neither RecipientIsLocal or HostIsLocal picks up the
> mail, so something about the user address isn't being picked up as local.
> We don't have smtpserver.log or mailet.log, so we don't see either the RCPT
> TO: <user>, or where RemoteDelivery is attempting to send.
>
>         --- Noel
>
> -----Original Message-----
> From: Danny Angus [mailto:danny@apache.org]
> Sent: Saturday, August 24, 2002 4:00
> To: James Users List
> Subject: RE: Help Please
>
> in MAIL TO:<user>
> <user> is expanded to <us...@localhost> before anything else happens, sending
> mail to <user> is legal and works, but only if your server accepts for
> servername localhost.
>
> d.
>
> > -----Original Message-----
> > From: Noel J. Bergman [mailto:noel@devtech.com]
> >
> > The system is attempting to send e-mail to a remote host (that transaction
> > would be captured in mailet.log).  Apparently James does not recognize
> > "dave" as a local user, nor "null" as a local host.  Did you try
> > "dave@localhost" or "dave@a-real-domain" instead of just "dave"?
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Help Please

Posted by Super-User <sk...@telegea.com>.
Noel,

How are you ?.

My James is working fine now.

It was receiving mails and sending mails to Internet.

Thanks for all the help.

Thanks,
Srinivas.

> I meant for him to try dave@localhost explicitly when he was sending, in
> case something mailx was doing something with the null domain before the
> <user> got to James.
>
> His config.xml has localhost explicit and autodetect=true.  From his spool
> log, we can see that neither RecipientIsLocal or HostIsLocal picks up the
> mail, so something about the user address isn't being picked up as local.
> We don't have smtpserver.log or mailet.log, so we don't see either the RCPT
> TO: <user>, or where RemoteDelivery is attempting to send.
>
>         --- Noel
>
> -----Original Message-----
> From: Danny Angus [mailto:danny@apache.org]
> Sent: Saturday, August 24, 2002 4:00
> To: James Users List
> Subject: RE: Help Please
>
> in MAIL TO:<user>
> <user> is expanded to <us...@localhost> before anything else happens, sending
> mail to <user> is legal and works, but only if your server accepts for
> servername localhost.
>
> d.
>
> > -----Original Message-----
> > From: Noel J. Bergman [mailto:noel@devtech.com]
> >
> > The system is attempting to send e-mail to a remote host (that transaction
> > would be captured in mailet.log).  Apparently James does not recognize
> > "dave" as a local user, nor "null" as a local host.  Did you try
> > "dave@localhost" or "dave@a-real-domain" instead of just "dave"?
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Help Please

Posted by "Noel J. Bergman" <no...@devtech.com>.
I meant for him to try dave@localhost explicitly when he was sending, in
case something mailx was doing something with the null domain before the
<user> got to James.

His config.xml has localhost explicit and autodetect=true.  From his spool
log, we can see that neither RecipientIsLocal or HostIsLocal picks up the
mail, so something about the user address isn't being picked up as local.
We don't have smtpserver.log or mailet.log, so we don't see either the RCPT
TO: <user>, or where RemoteDelivery is attempting to send.

	--- Noel

-----Original Message-----
From: Danny Angus [mailto:danny@apache.org]
Sent: Saturday, August 24, 2002 4:00
To: James Users List
Subject: RE: Help Please


in MAIL TO:<user>
<user> is expanded to <us...@localhost> before anything else happens, sending
mail to <user> is legal and works, but only if your server accepts for
servername localhost.

d.

> -----Original Message-----
> From: Noel J. Bergman [mailto:noel@devtech.com]
>
> The system is attempting to send e-mail to a remote host (that transaction
> would be captured in mailet.log).  Apparently James does not recognize
> "dave" as a local user, nor "null" as a local host.  Did you try
> "dave@localhost" or "dave@a-real-domain" instead of just "dave"?


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Help Please

Posted by Danny Angus <da...@apache.org>.
in MAIL TO:<user>
<user> is expanded to <us...@localhost> before anything else happens, sending
mail to <user> is legal and works, but only if your server accepts for
servername localhost.

d.

> -----Original Message-----
> From: Noel J. Bergman [mailto:noel@devtech.com]
> Sent: 24 August 2002 02:13
> To: James Users List
> Subject: RE: Help Please
>
>
> The system is attempting to send e-mail to a remote host (that transaction
> would be captured in mailet.log).  Apparently James does not recognize
> "dave" as a local user, nor "null" as a local host.  Did you try
> "dave@localhost" or "dave@a-real-domain" instead of just "dave"?
>
> 	--- Noel
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Help Please

Posted by "Noel J. Bergman" <no...@devtech.com>.
The system is attempting to send e-mail to a remote host (that transaction
would be captured in mailet.log).  Apparently James does not recognize
"dave" as a local user, nor "null" as a local host.  Did you try
"dave@localhost" or "dave@a-real-domain" instead of just "dave"?

	--- Noel


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Help Please

Posted by Super-User <sk...@telegea.com>.
Noel ,

How are you ?.

Thanks for your's info.

Here is the James version,which I have installed on the Sun.

James 2.0a3-cvs

Here is the my mail cmd.

mailx -v dave

(I have created user dave from admin tool)

I have removed lines,which were belongs to spam in the config.xml .

And stopped and started the James.

The mails were staying in the outgoing dir for few secs and after that  those
were vanishing.

I am attching config.xml and spoolmanager log file.

We were using here class B Private Ip network(172.16.30.0).



Please advice me.

Thanks,
Srinivas.





> Srinivas,
>
> You may have a problem.  Here are the appropriate (edited) sections from the
> spoolmanager log:
>
> (spoolmanager.root): Checking -0 with
> org.apache.james.transport.matchers.RelayLimit
> (spoolmanager.root): Checking -0 with
> org.apache.james.transport.matchers.InSpammerBlacklist
> (spoolmanager.root): Servicing -0 by ToProcessor Mailet
> (spoolmanager): Processing -0- through spam
>
> Matching that up with config.xml:
>
>           <!-- Important check to avoid race conditions -->
>           <mailet match="RelayLimit=30" class="Null">
>           </mailet>
>
>           <!-- Check for delivery from a known spam server -->
>           <mailet match="InSpammerBlacklist=blackholes.mail-abuse.org"
>                   class="ToProcessor">
>             <processor> spam </processor>
>             <notice> Rejected - see  http://www.mail-abuse.org/rbl/
> </notice>
>           </mailet>
>
> It appears that whatever IP address you are using to contact James is listed
> in blackholes.mail-abuse.org.  Those anti-SPAM checks occur immediately.
>
>         --- Noel
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Help Please

Posted by Super-User <sk...@telegea.com>.
Noel ,

How are you ?.

Thanks for the info.

Srinivas.



> Srinivas,
>
> You may have a problem.  Here are the appropriate (edited) sections from the
> spoolmanager log:
>
> (spoolmanager.root): Checking -0 with
> org.apache.james.transport.matchers.RelayLimit
> (spoolmanager.root): Checking -0 with
> org.apache.james.transport.matchers.InSpammerBlacklist
> (spoolmanager.root): Servicing -0 by ToProcessor Mailet
> (spoolmanager): Processing -0- through spam
>
> Matching that up with config.xml:
>
>           <!-- Important check to avoid race conditions -->
>           <mailet match="RelayLimit=30" class="Null">
>           </mailet>
>
>           <!-- Check for delivery from a known spam server -->
>           <mailet match="InSpammerBlacklist=blackholes.mail-abuse.org"
>                   class="ToProcessor">
>             <processor> spam </processor>
>             <notice> Rejected - see  http://www.mail-abuse.org/rbl/
> </notice>
>           </mailet>
>
> It appears that whatever IP address you are using to contact James is listed
> in blackholes.mail-abuse.org.  Those anti-SPAM checks occur immediately.
>
>         --- Noel
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Help Please

Posted by "Noel J. Bergman" <no...@devtech.com>.
Srinivas,

You may have a problem.  Here are the appropriate (edited) sections from the
spoolmanager log:

(spoolmanager.root): Checking -0 with
org.apache.james.transport.matchers.RelayLimit
(spoolmanager.root): Checking -0 with
org.apache.james.transport.matchers.InSpammerBlacklist
(spoolmanager.root): Servicing -0 by ToProcessor Mailet
(spoolmanager): Processing -0- through spam

Matching that up with config.xml:

          <!-- Important check to avoid race conditions -->
          <mailet match="RelayLimit=30" class="Null">
          </mailet>

          <!-- Check for delivery from a known spam server -->
          <mailet match="InSpammerBlacklist=blackholes.mail-abuse.org"
                  class="ToProcessor">
            <processor> spam </processor>
            <notice> Rejected - see  http://www.mail-abuse.org/rbl/
</notice>
          </mailet>

It appears that whatever IP address you are using to contact James is listed
in blackholes.mail-abuse.org.  Those anti-SPAM checks occur immediately.

	--- Noel


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Help Please

Posted by Super-User <sk...@telegea.com>.
Noel ,

How are you ?.

I am new to James.

So,I did not find the culprit  from the log file.

Please find attached spoolmanager.log and config.xml files.

Please advice me.

Thanks,
Srinivas.


<?xml version="1.0"?>
<!--
                                README!

    This configuration file is designed to run without alteration, for simple
    tests.
    It assumes you have a DNS server on localhost and assigns a root pasword
    of root.

    For production use, or in case the defaults do not suit you, the items
    you are most likely to need to change are preceeded by a
    CHECKME! or
    CONFIRM? comment in the left
    margin.

    This is $Revision: 1.22 $
    Committed on $Date: 2002/03/11 21:46:32 $ by: $Author: serge $
-->
<config>

  <!-- The James block  -->
  <James>
<!-- CHECKME! Set this to the right email address for error reports -->
      <postmaster> Postmaster@localhost </postmaster>

<!-- CONFIRM? -->
      <!-- servernames identifies the DNS namespace served by this instance
      of James.
      If autodetect is TRUE, James wil attempt to discover its own name AND use

      any specified servernames.  If autodetect is FALSE, James will use only
      the specified servernames.  By default, the servername 'localhost' is
      specified. This can be removed, if required. -->
      <servernames autodetect="TRUE">
        <!--
        <servername>To override autodetected server names
                    uncomment this.  </servername>-->
        <servername>localhost</servername>
      </servernames>

      <!-- Set whether user names are case sensitive or insensitive -->
      <!-- Set whether to enable local aliases -->
      <usernames ignoreCase="TRUE" enableAliases="TRUE"
                                   enableForwarding="TRUE"/>



      <!-- The inbox repository is the location for users inboxes -->
      <!-- Default setting: file based repository - enter path ( :/// for
absolute) -->
      <inboxRepository>
        <repository destinationURL="file://var/mail/inboxes/"
                    type="MAIL">
        </repository>
      </inboxRepository>
      <!-- Alternative inbox repository definition for DB use. -->
      <!--  The format for the destinationURL is "db://<data-source>/<table>"
            - <data-source> is the datasource name set up in the
                    database-connections block, below
            - <table> is the name of the table to store user inboxes in
           The user name is used as <repositoryName> for this repository
config.

           <inboxRepository>
        <repository destinationURL="db://maildb/inbox/"
                    type="MAIL">
        </repository>
      </inboxRepository>
      -->
  </James>

  <!-- The James Spool Manager block  -->
  <spoolmanager>


      <!-- number of spool threads -->
      <threads> 10 </threads>

        <!-- Set the packages from which to load mailets and matches -->
        <mailetpackages>
          <mailetpackage>org.apache.james.transport.mailets</mailetpackage>
        </mailetpackages>
        <matcherpackages>
          <matcherpackage>org.apache.james.transport.matchers</matcherpackage>
        </matcherpackages>

        <!-- Processor CONFIGURATION SAMPLE:
             root is the first processor all mails enter -->
        <processor name="root">
          <!-- Checks that the MAIL FROM command was for a valid domain.
          Important for spam prevention. -->
          <!--
          <mailet match="SenderInFakeDomain" class="ToProcessor">
            <processor> spam </processor>
          </mailet>
          -->
          <!-- Important check to avoid race conditions -->
          <mailet match="RelayLimit=30" class="Null">
          </mailet>

          <!-- Check for delivery from a known spam server -->
          <mailet match="InSpammerBlacklist=blackholes.mail-abuse.org"
                  class="ToProcessor">
            <processor> spam </processor>
            <notice> Rejected - see  http://www.mail-abuse.org/rbl/ </notice>
          </mailet>

          <mailet match="InSpammerBlacklist=dialups.mail-abuse.org"
                  class="ToProcessor">
            <processor> spam </processor>
            <notice> Dialup - see http://www.mail-abuse.org/dul/ </notice>
          </mailet>

          <mailet match="InSpammerBlacklist=relays.mail-abuse.org"
                  class="ToProcessor">
            <processor> spam </processor>
            <notice> Open spam relay - see http://www.mail-abuse.org/rss/
</notice>
          </mailet>

          <!-- Sample matching to kill a message (send to Null) -->
          <mailet match="RecipientIs=badboy@badhost" class="Null">
          </mailet>

          <!-- Sends remaining mails to the transport processor for either
          local or remote delivery -->
          <mailet match="All" class="ToProcessor">
            <processor> transport </processor>
          </mailet>
        </processor>

        <!-- Processor CONFIGURATION SAMPLE: error is the processor mails with
        failure conditions enter -->
        <processor name="error">
          <!-- Logs any messages to the repository specified -->
          <mailet match="All" class="ToRepository">
            <repositoryPath> file://var/mail/error/</repositoryPath>
            <!-- <repositoryPath> db://conf/mail-error.properties
</repositoryPath> -->
            <passThrough> true </passThrough>
          </mailet>

          <!-- If you want to notify the sender their message was marked as
          spam, uncomment this
          <mailet match="All" class="NotifySender">
          </mailet>
          -->

          <!-- If you want to notify the postmaster that a message was marked
          as spam, uncomment this
          <mailet match="All" class="NotifyPostmaster">
          </mailet>
          -->
        </processor>

        <!--  Processor CONFIGURATION SAMPLE: transport is a sample custom
        processor for local or remote delivery -->
        <processor name="transport">
          <!-- Is the recipient is for a local account, deliver it locally -->
          <mailet match="RecipientIsLocal" class="LocalDelivery">
          </mailet>

          <!-- If the host is handled by this server and it did not get
          locally delivered,  this is an invalid recipient -->
          <mailet match="HostIsLocal" class="ToProcessor">
            <processor>error</processor>
          </mailet>

<!-- CHECKME!
    Anti-relay mailet: Add your network address here,
    e.g. "RemoteAddrNotInNetwork=127.0.0.1, abc.de.*"
-->

          <!-- This matcher-mailet pair can prevent relaying... if you change
          this,  you risk making your mail server an open relay point for
          spammers .
          NOTE 1: the order of matcher-mailets is important: it must come after

          valid local recipients have been dealt with but before any attempt is

          made to delivery the mail remotely.
          NOTE 2: Add your own network, if you want to relay mail outwards
          NOTE 3: If you use SMTP AUTH, you may want to comment this
          so users who are on the road can still use the server -->
          <mailet match="RemoteAddrNotInNetwork=127.0.0.1,172.16.30.*"
class="ToProcessor">
            <processor> spam </processor>
          </mailet>

          <!-- Attempt remote delivery using the specified repository for the
          spool,
          using delay time to retry delivery and the maximum number of
          retries -->
          <mailet match="All" class="RemoteDelivery">
            <outgoing> file://var/mail/outgoing/ </outgoing>
            <!-- <outgoing> db://conf/mail-outgoing.properties </outgoing> -->
            <!-- Number of milliseconds between delivery attempts -->
            <delayTime> 21600000 </delayTime>
            <!-- Number of failed attempts before returning to the sender -->
            <maxRetries> 5 </maxRetries>
            <!-- The number of threads that should be trying to deliver
outgoing messages -->
            <deliveryThreads> 1 </deliveryThreads>
            <!-- A single mail server to deliver all outgoing messages.  This
is useful if this is a backup or failover machine, or if you otherwise want all
messages to be sent only to particular mail server, regardless of the email
addresses specified in the message -->
            <!--
            <gateway> exchanger.telegea.com</gateway>
            -->
            <!-- If your gateway mail server is listening on a port other than
25, you can set James to connect to it on that port -->
            <!--
            <gatewayPort> 25 </gatewayPort>
            -->
          </mailet>
        </processor>

        <!--  Processor CONFIGURATION SAMPLE: spam is where messages detected
        as relaying or other problems will get sent.  You can either log these,

        bounce these, or just ignore them. -->
        <processor name="spam">
          <!-- If you wanted, you could just destroy messages, uncomment this
          matcher/mailet
          <mailet match="All" class="Null">
          </mailet>
          -->

          <!-- If you want to notify the sender their message was marked as
          spam, uncomment this
          <mailet match="All" class="NotifySender">
          </mailet>
          -->

          <!-- If you want to notify the postmaster that a message was marked
          as  spam, uncomment this
          <mailet match="All" class="NotifyPostmaster">
          </mailet>
          -->

          <!-- Out of the box, this will log the message to a repository -->
          <mailet match="All" class="ToRepository">
            <repositoryPath>file://var/mail/spam/</repositoryPath>
          </mailet>
        </processor>
  </spoolmanager>


<!-- CONFIRM? Enter ip address of your DNS server, one per element -->
  <dnsserver>
        <servers>
          <server>172.16.30.82</server>
          <server> 172.16.30.15</server>
        </servers>
        <authoritative>false</authoritative>
  </dnsserver>

  <remotemanager>
        <port>4555</port>
        <!-- <bind>  </bind> uncomment this if you want to bind to a specific
        inetaddress -->
        <!-- <useTLS>TRUE</useTLS> uncomment this if you want to use TLS (SSL)
        on this port -->
        <handler>
          <!-- helloName is the single host name this instance of James will
          use to identify itself  for example, in SMTP and POP3 greetings. If
          autodetect is TRUE, James will attempt to discover its own name OR
          use 'localhost'. If autodetect is FALSE, James will use the value
          given OR 'localhost' -->
          <helloName autodetect="TRUE">myMailServer</helloName>
          <administrator_accounts>

<!-- CHECKME! Change the default password! -->
            <!-- FILL ME!!!!!!  You must provide a password for your
             administrator accounts (cannot be blank) -->
            <account login="root" password="root"/>

           </administrator_accounts>
           <connectiontimeout> 60000 </connectiontimeout>
    </handler>
  </remotemanager>

  <pop3server>
        <port>110</port>
        <!-- <port>995</port> -->
        <!-- port 995 is the well-known/IANA registered port for POP3S
        ie over SSL/TLS -->
        <!-- <bind>  </bind>  uncomment this if you want to bind to a specific
        inetaddress-->
        <!-- <useTLS>TRUE</useTLS> uncomment this if you want to use TLS (SSL)
        on this port -->
        <handler>
          <!-- helloName is the single host name this instance of James will
          use to identify itself  for example, in SMTP and POP3 greetings. If
          autodetect is TRUE, James will attempt to discover its own name OR
          use 'localhost'. If autodetect is FALSE, James will use the value
          given OR 'localhost' -->
          <helloName autodetect="TRUE">myMailServer</helloName>
          <connectiontimeout>120000</connectiontimeout>
        </handler>
  </pop3server>

  <smtpserver>
        <port>25</port>
        <!--<bind></bind> uncomment this if you want to bind to a specific
        inetaddress -->
        <!--<useTLS>TRUE</useTLS> uncomment this if you want to use TLS (SSL)
        on this port -->
        <handler>
          <!-- helloName is the single host name this instance of James will
          use to identify itself  for example, in SMTP and POP3 greetings. If
          autodetect is TRUE, James will attempt to discover its own name OR
          use 'localhost'. If autodetect is FALSE, James will use the value
          given OR 'localhost' -->
          <helloName autodetect="TRUE">myMailServer</helloName>
          <connectiontimeout>360000</connectiontimeout>

      <!--<authRequired>true</authRequired> uncomment this if you want
          SMTP AUTH support. This is useful if you have users who need to use
          the email server on the road, while not having your server act as an
          open relay! -->

      <!--<verifyIdentity>true</verifyIdentity> uncomment this if you want
          to verify that the MAIL FROM: address is the same user that
          authenticated. This prevents a user of your mail server from acting
          as somebody else -->

          <!-- This sets the maximum allowed message size for the smtphandler
          in KBytes. The value defaults to 0, which means no limit.  -->
          <maxmessagesize>0</maxmessagesize>

        </handler>
  </smtpserver>

  <nntpserver>
        <port>119</port>
        <!-- <port>563</port> -->
        <!-- port 563 is the well-known/IANA registered port for NNTPS
        ie over SSL/TLS -->
        <!-- <bind>  </bind>  uncomment this if you want to bind to a specific
        inetaddress-->
        <!-- <useTLS>TRUE</useTLS> uncomment this if you want to use TLS (SSL)
        on this port -->
        <handler>
          <!-- helloName is the single host name this instance of James will
          use to identify itself  for example, in SMTP and POP3 greetings. If
          autodetect is TRUE, James will attempt to discover its own name OR
          use 'localhost'. If autodetect is FALSE, James will use the value
          given OR 'localhost' -->
          <helloName autodetect="TRUE">myMailServer</helloName>
          <connectiontimeout>120000</connectiontimeout>
        </handler>
  </nntpserver>

  <nntpauth>
     <!-- make this true, if you want only authenticated users to access
NNTP-->
     <authRequired>false</authRequired>
  </nntpauth>

  <nntp-repository>
        <!-- make this true to disallow posting to all newsgroups-->
    <readOnly>false</readOnly>
    <rootPath>file:///var/nntp/groups</rootPath>
    <tempPath>file:///var/nntp/temp</tempPath>
    <articleIDPath>file:///var/nntp/articleid</articleIDPath>
    <articleIDDomainSuffix>news.james.apache.org</articleIDDomainSuffix>
    <!-- these additional news groups would be created and exposed-->
    <newsgroups>
      <newsgroup>org.apache.james.dev</newsgroup>
      <newsgroup>org.apache.james.user</newsgroup>
      <newsgroup>org.apache.avalon.dev</newsgroup>
      <newsgroup>org.apache.avalon.user</newsgroup>
    </newsgroups>
    <spool>
          <configuration>
        <spoolPath>file:///var/nntp/spool</spoolPath>
        <!-- number of threads that process spooler related tasks -->
        <threadCount>1</threadCount>
        <!-- the spool thread(s) should idle for some time,
            if it has nothing to do  -->
        <threadIdleTime>1000</threadIdleTime>
          </configuration>
    </spool>
  </nntp-repository>

  <!-- The High Level Storage block -->
  <mailstore>
      <repositories>
        <repository
            class="org.apache.james.mailrepository.AvalonMailRepository">
          <protocols>
            <protocol>file</protocol>
          </protocols>
          <types>
            <type>MAIL</type>
          </types>
        </repository>
        <repository
            class="org.apache.james.mailrepository.AvalonSpoolRepository">
          <protocols>
            <protocol>file</protocol>
          </protocols>
          <types>
            <type>SPOOL</type>
          </types>
        </repository>

        <!-- These repositories store the entire message in the database -->
        <repository
            class="org.apache.james.mailrepository.JDBCMailRepository">
          <protocols>
            <protocol>db</protocol>
          </protocols>
          <types>
            <type>MAIL</type>
          </types>
          <config>
            <sqlFile>file://conf/sqlResources.xml</sqlFile>
          </config>
        </repository>
        <repository
            class="org.apache.james.mailrepository.JDBCSpoolRepository">
          <protocols>
            <protocol>db</protocol>
          </protocols>
          <types>
            <type>SPOOL</type>
          </types>
          <config>
            <sqlFile>file://conf/sqlResources.xml</sqlFile>
          </config>
        </repository>
        <!-- These repositories store message delivery and headers in the DB,
and the body to the filesystem -->
        <repository
            class="org.apache.james.mailrepository.JDBCMailRepository">
          <protocols>
            <protocol>dbfile</protocol>
          </protocols>
          <types>
            <type>MAIL</type>
          </types>
          <config>
            <sqlFile>file://conf/sqlResources.xml</sqlFile>
            <filestore>file://var/dbmail</filestore>
          </config>
        </repository>
        <repository
            class="org.apache.james.mailrepository.JDBCSpoolRepository">
          <protocols>
            <protocol>dbfile</protocol>
          </protocols>
          <types>
            <type>SPOOL</type>
          </types>
          <config>
            <sqlFile>file://conf/sqlResources.xml</sqlFile>
            <filestore>file://var/dbmail</filestore>
          </config>
        </repository>
      </repositories>

      <!-- Spool repository configuration -->
      <!-- The spool repository is a singular location where incoming mails
      are temporarily stored before being processed.
     (ex. file://c:/james/spool/) -->

      <!-- Default setting: file based repository - enter path ( :/// for
absolute) -->
      <spoolRepository>
        <repository destinationURL="file://var/mail/spool/"
                    type="SPOOL">
        </repository>
      </spoolRepository>

      <!-- Alternative spool repository definition for JDBC use -->

      <!--      <spoolRepository>
        <repository destinationURL="db://maildb/message/spool"
                    type="SPOOL">
        </repository>
      </spoolRepository>
      -->
  </mailstore>

  <!-- The User Storage block -->
  <users-store>
    <!-- Configure User Repositories here.
         User repositories are required for the following purposes:
            - hold information about Users of the James mail server
            - hold lists of users for the listserv mailet

         Currently, 2 different storage options are available:
            - file-based storage using Java serialisation
            - database-backed storage
         (Use of database or file-system is defined on a "per-repository"
basis)

         Note: Two user repositories are required for default configuration:
         LocalUsers - the users for whom you are providing POP3, NNTP, or
                      AUTH service
         list-james - the users of the james@localhost mailiinglist
    -->

      <!-- Default: File-based user repositories
           Use these configurations to store user info in the filesystem  -->

      <!-- The LocalUsers repository, for storing James' User info. -->
      <repository name="LocalUsers"
                  class="org.apache.james.userrepository.UsersFileRepository">
        <destination URL="file://var/users/"/>
      </repository>
      <!-- The list used by the default ListServ mailet -->
      <repository name="list-james"
                  class="org.apache.james.userrepository.UsersFileRepository">
        <destination URL="file://var/lists/list-james/"/>
      </repository>


      <!-- Database backed user repositories
           Use these configurations to store user info in a database.
           Note: the <data-source> element must refer to a connection
configured
            in the <database-connections> configuration section. -->

      <!-- The LocalUsers repository, for storing James' User info. -->

      <!--       <repository name="LocalUsers"

class="org.apache.james.userrepository.JamesUsersJdbcRepository"
                  destinationURL="db://maildb/users">
          <sqlFile>file://conf/sqlResources.xml</sqlFile>
      </repository>
      -->
      <!-- The list used by the default ListServ mailet -->
      <!--      <repository name="list-james"

class="org.apache.james.userrepository.ListUsersJdbcRepository"
                  destinationURL="db://maildb/lists/list-james">
          <sqlFile>file://conf/sqlResources.xml</sqlFile>
      </repository>
      -->

      <!-- An example mailinglist repository, with no "listName" parameter
           specified. Uses the default value from the sql definition file. -->
      <!-- Testing purposes only. -->
      <!--     <repository name="list-test"

class="org.apache.james.userrepository.ListUsersJdbcRepository"
                  destinationURL="db://maildb/lists">
          <sqlFile>file://conf/sqlResources.xml</sqlFile>
      </repository>
      -->
      <!-- An example UserRepository for DefaultUser implementations. -->
      <!-- Testing purposes only. -->
      <!--      <repository name="default-users"

class="org.apache.james.userrepository.DefaultUsersJdbcRepository"
                  destinationURL="db://maildb/DefaultUsers">
          <sqlFile>file://conf/sqlResources.xml</sqlFile>
      </repository>
      -->
  </users-store>

  <!-- The database-connections block -->
  <database-connections>
    <!-- Confugure database connections here.
         These connections are referred to by name elsewhere in the config file
-->
<!-- CHECKME! To allow James to use a database, configure the database
connection here -->
    <data-sources>
        <!-- Example, connecting to a MySQL database called "mail" on localhost

        -->
        <!--
        <data-source name="maildb"
                     class="org.apache.james.util.mordred.JdbcDataSource">
            <driver>org.gjt.mm.mysql.Driver</driver>
            <dburl>jdbc:mysql://127.0.0.1/mail</dburl>
            <user>username</user>
            <password>password</password>
            <max>2</max>
        </data-source>
        <data-source name="maildb"
                     class="org.apache.james.util.mordred.JdbcDataSource">
            <driver>com.inet.tds.TdsDriver</driver>
            <dburl>jdbc:inetdae7:127.0.0.1?database=James</dburl>
            <user>sa_james</user>
            <password>blahblah</password>
            <max>2</max>
        </data-source>
        -->
    </data-sources>
  </database-connections>

  <!-- Configuration for Cornerstone Blocks only after here
       NOTHING BELOW THIS SHOULD NEED CHANGING,
       (unless you want secure sockets (TLS)) -->

  <!-- The Storage block -->
  <objectstorage>
      <repositories>
        <repository
class="org.apache.avalon.cornerstone.blocks.masterstore.File_Persistent_Object_Repository">

        <protocols>
          <protocol>file</protocol>
        </protocols>
        <types>
          <type>OBJECT</type>
        </types>
        <models>
          <model>SYNCHRONOUS</model>
          <model>ASYNCHRONOUS</model>
          <model>CACHE</model>
        </models>
      </repository>
      <repository
class="org.apache.avalon.cornerstone.blocks.masterstore.File_Persistent_Stream_Repository">

        <protocols>
          <protocol>file</protocol>
        </protocols>
        <types>
          <type>STREAM</type>
        </types>
        <models>
          <model>SYNCHRONOUS</model>
          <model>ASYNCHRONOUS</model>
          <model>CACHE</model>
        </models>
      </repository>
    </repositories>
  </objectstorage>

  <!-- The Socket Manager block -->
  <sockets>
      <server-sockets>
        <factory name="plain"

class="org.apache.avalon.cornerstone.blocks.sockets.DefaultServerSocketFactory"
/>
        <!--
        <factory name="ssl"

class="org.apache.avalon.cornerstone.blocks.sockets.TLSServerSocketFactory">
          <keystore>
            <file>conf/keystore</file>
            <password>secret</password>
            <type>JKS</type>
            <protocol>TLS</protocol>
            <algorithm>SunX509</algorithm>
            <authenticate-client>false</authenticate-client>
          </keystore>
        </factory>
        -->
      </server-sockets>

      <client-sockets>
        <factory name="plain"

class="org.apache.avalon.cornerstone.blocks.sockets.DefaultSocketFactory" />
      </client-sockets>
  </sockets>

  <thread-manager>
      <thread-group>
        <name>default</name>

        <!-- normal priority == 5, max-priority = 10 -->
        <priority>5</priority>

        <!-- are threads deamon threads ? -->
        <is-daemon>false</is-daemon>

        <max-threads>40</max-threads>
        <!-- these are ignored at the moment but will be fixed in later
revisions -->
        <min-threads>20</min-threads>
        <min-spare-threads>20</min-spare-threads>
      </thread-group>
  </thread-manager>

</config>

----------------------------------------------------------


1030129995384 [INFO   ] (spoolmanager): JamesSpoolManager init...
1030129995385 [DEBUG  ] (spoolmanager): Got spool
1030129995481 [INFO   ] (spoolmanager): Matcher RelayLimit=30 instantiated
1030129995487 [INFO   ] (spoolmanager): Mailet Null instantiated
1030129995494 [INFO   ] (spoolmanager): Matcher
InSpammerBlacklist=blackholes.mail-abuse.org instantiated
1030129995501 [INFO   ] (spoolmanager): Mailet ToProcessor instantiated
1030129995504 [INFO   ] (spoolmanager): Matcher
InSpammerBlacklist=dialups.mail-abuse.org instantiated
1030129995506 [INFO   ] (spoolmanager): Mailet ToProcessor instantiated
1030129995508 [INFO   ] (spoolmanager): Matcher
InSpammerBlacklist=relays.mail-abuse.org instantiated
1030129995511 [INFO   ] (spoolmanager): Mailet ToProcessor instantiated
1030129995523 [INFO   ] (spoolmanager): Matcher RecipientIs=badboy@badhost
instantiated
1030129995525 [INFO   ] (spoolmanager): Mailet Null instantiated
1030129995527 [INFO   ] (spoolmanager): Matcher All instantiated
1030129995530 [INFO   ] (spoolmanager): Mailet ToProcessor instantiated
1030129995533 [INFO   ] (spoolmanager): processor root instantiated
1030129995536 [INFO   ] (spoolmanager): Matcher All instantiated
1030129995554 [INFO   ] (spoolmanager): Mailet ToRepository instantiated
1030129995558 [INFO   ] (spoolmanager): processor error instantiated
1030129995564 [INFO   ] (spoolmanager): Matcher RecipientIsLocal instantiated
1030129995571 [INFO   ] (spoolmanager): Mailet LocalDelivery instantiated
1030129995577 [INFO   ] (spoolmanager): Matcher HostIsLocal instantiated
1030129995579 [INFO   ] (spoolmanager): Mailet ToProcessor instantiated
1030129995587 [INFO   ] (spoolmanager): Matcher
RemoteAddrNotInNetwork=127.0.0.1,172.16.30.* instantiated
1030129995593 [INFO   ] (spoolmanager): Mailet ToProcessor instantiated
1030129995597 [INFO   ] (spoolmanager): Matcher All instantiated
1030129995641 [INFO   ] (spoolmanager): Mailet RemoteDelivery instantiated
1030129995648 [INFO   ] (spoolmanager): processor transport instantiated
1030129995651 [INFO   ] (spoolmanager): Matcher All instantiated
1030129995664 [INFO   ] (spoolmanager): Mailet ToRepository instantiated
1030129995673 [INFO   ] (spoolmanager): processor spam instantiated
1030129995674 [INFO   ] (spoolmanager): Spooler Manager uses 10 Thread(s)
1030129995765 [INFO   ] (spoolmanager): run JamesSpoolManager: default Worker
#10
1030129995765 [INFO   ] (spoolmanager):
spool=org.apache.james.mailrepository.AvalonSpoolRepository
1030129995767 [INFO   ] (spoolmanager): run JamesSpoolManager: default Worker
#9
1030129995767 [INFO   ] (spoolmanager):
spool=org.apache.james.mailrepository.AvalonSpoolRepository
1030129995768 [INFO   ] (spoolmanager): run JamesSpoolManager: default Worker
#7
1030129995768 [INFO   ] (spoolmanager):
spool=org.apache.james.mailrepository.AvalonSpoolRepository
1030129995769 [INFO   ] (spoolmanager): run JamesSpoolManager: default Worker
#5
1030129995770 [INFO   ] (spoolmanager):
spool=org.apache.james.mailrepository.AvalonSpoolRepository
1030129995771 [INFO   ] (spoolmanager): run JamesSpoolManager: default Worker
#4
1030129995771 [INFO   ] (spoolmanager):
spool=org.apache.james.mailrepository.AvalonSpoolRepository
1030129995772 [INFO   ] (spoolmanager): run JamesSpoolManager: default Worker
#3
1030129995772 [INFO   ] (spoolmanager):
spool=org.apache.james.mailrepository.AvalonSpoolRepository
1030129995773 [INFO   ] (spoolmanager): run JamesSpoolManager: default Worker
#2
1030129995773 [INFO   ] (spoolmanager):
spool=org.apache.james.mailrepository.AvalonSpoolRepository
1030129995862 [INFO   ] (spoolmanager): run JamesSpoolManager: default Worker
#1
1030129995863 [INFO   ] (spoolmanager):
spool=org.apache.james.mailrepository.AvalonSpoolRepository
1030129995863 [INFO   ] (spoolmanager): run JamesSpoolManager: default Worker
#6
1030129995864 [INFO   ] (spoolmanager):
spool=org.apache.james.mailrepository.AvalonSpoolRepository
1030129995864 [INFO   ] (spoolmanager): run JamesSpoolManager: default Worker
#8
1030129995865 [INFO   ] (spoolmanager):
spool=org.apache.james.mailrepository.AvalonSpoolRepository
1030130120654 [INFO   ] (spoolmanager): ==== Begin processing mail
Mail1030130120446-0 ====
1030130120658 [INFO   ] (spoolmanager): Processing Mail1030130120446-0 through
root
1030130120659 [DEBUG  ] (spoolmanager.root): Servicing mail:
Mail1030130120446-0
1030130120660 [DEBUG  ] (spoolmanager.root): Checking Mail1030130120446-0 with
org.apache.james.transport.matchers.All@6bade9
1030130120663 [DEBUG  ] (spoolmanager.root): Servicing Mail1030130120446-0 by
Postmaster aliasing mailet
1030130120664 [DEBUG  ] (spoolmanager.root): Checking Mail1030130120446-0 with
org.apache.james.transport.matchers.RelayLimit@66afb3
1030130120679 [DEBUG  ] (spoolmanager.root): Checking Mail1030130120446-0 with
org.apache.james.transport.matchers.InSpammerBlacklist@b5dac4
1030130120681 [DEBUG  ] (spoolmanager.root): Servicing Mail1030130120446-0 by
ToProcessor Mailet
1030130120711 [INFO   ] (spoolmanager): ==== Removed from spool mail
Mail1030130120446-0-!544870348 ====
1030130120732 [INFO   ] (spoolmanager): ==== Begin processing mail
Mail1030130120446-0-!544870348 ====
1030130120732 [INFO   ] (spoolmanager): Processing
Mail1030130120446-0-!544870348 through spam
1030130120733 [DEBUG  ] (spoolmanager.spam): Servicing mail:
Mail1030130120446-0-!544870348
1030130120733 [DEBUG  ] (spoolmanager.spam): Checking
Mail1030130120446-0-!544870348 with
org.apache.james.transport.matchers.All@ff0dde
1030130120733 [DEBUG  ] (spoolmanager.spam): Servicing
Mail1030130120446-0-!544870348 by ToRepository Mailet
1030130120741 [INFO   ] (spoolmanager): ==== Removed from spool mail
Mail1030130120446-0-!544870348 ====


> Look at your spoolmanager.log file to see WHICH matcher is sending your mail
> to the spam processor.
>
>         --- Noel
>
> P.S.  The James-User mailing list comes straight to my mailbox.  It is
> completely unnecessary to CC me personally.
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>







--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Help Please

Posted by "Noel J. Bergman" <no...@devtech.com>.
Look at your spoolmanager.log file to see WHICH matcher is sending your mail
to the spam processor.

	--- Noel

P.S.  The James-User mailing list comes straight to my mailbox.  It is
completely unnecessary to CC me personally.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Help Please

Posted by Super-User <sk...@telegea.com>.
Noel ,

How are you ?.

Thanks for the info.

I have updated  /apps/james/conf/config.xml for the following.

<mailet match="RemoteAddrNotInNetwork=127.0.0.1,172.16.30.*" class="To
Processor">


and stop/started the James.

But,no luck.

Still mails were going to spam folder.

Please advice me.

Thanks,
Srinivas.


> > > Did you configure the RemoteAddrNotInNetwork matcher for your local
> network?
> > I have  modified config.xml for the  following;
> > <mailet match="RemoteAddrNotInNetwork=127.0.0.1,172.16.30.0"
> class="ToProcessor">
> > My network is 172.16.30.0 .
>
> As per the instructions for RemoteAddrNotInNetwork: "Networks should be
> indicated with a wildcard *, e.g. 192.168.*", so you should have:
>
>  <mailet match="RemoteAddrNotInNetwork=127.0.0.1,172.16.30.*"
> class="ToProcessor">
>
>         --- Noel
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Help Please

Posted by "Noel J. Bergman" <no...@devtech.com>.
> > Did you configure the RemoteAddrNotInNetwork matcher for your local
network?
> I have  modified config.xml for the  following;
> <mailet match="RemoteAddrNotInNetwork=127.0.0.1,172.16.30.0"
class="ToProcessor">
> My network is 172.16.30.0 .

As per the instructions for RemoteAddrNotInNetwork: "Networks should be
indicated with a wildcard *, e.g. 192.168.*", so you should have:

 <mailet match="RemoteAddrNotInNetwork=127.0.0.1,172.16.30.*"
class="ToProcessor">

	--- Noel


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Help Please

Posted by Super-User <sk...@telegea.com>.
Vasko ,

How are you ?.

Thanks for the info.

Srinivas.

> this is my maillet in config.xml
>
>    <mailet
> match="RemoteAddrNotInNetwork=127.0.0.1,212.50.9.*,212.56.7.*,193.68.153.*"
> class="ToProcessor">
>             <processor> spam </processor>
>           </mailet>
>
> it work fine without problems 3 from 3 month
>
> Super-User wrote:
>
> >Danny,
> >
> >How are you ?.
> >
> >Thanks for the info.
> >
> >I have updated  /apps/james/conf/config.xml for the following.
> >
> >RemoteAddrNotInNetwork=127.0.0.1, 172.16.30.*
> >and stop/started the James.
> >
> >But,no luck.
> >
> >Still mails were going to spam folder.
> >
> >Please advice me.
> >
> >Thanks,
> >Srinivas.
> >
> >
> >>try "RemoteAddrNotInNetwork=127.0.0.1, 172.16.30.*"
> >>
> >>>-----Original Message-----
> >>>From: root [mailto:root]On Behalf Of Super-User
> >>>Sent: 23 August 2002 16:30
> >>>To: James Users List; noel@devtech.com
> >>>Subject: Re: Help Please
> >>>
> >>>
> >>>Noel,
> >>>
> >>>How are you ?.
> >>>
> >>>Thanks for the info.
> >>>
> >>>I have  modified config.xml for the  following;
> >>>
> >>><mailet match="RemoteAddrNotInNetwork=127.0.0.1,172.16.30.0" class="To
> >>>Processor">
> >>>
> >>>My network is 172.16.30.0 .
> >>>
> >>>I have stopped and started the JAMES.
> >>>
> >>>But,no luck.
> >>>
> >>>The inboxes dir was looks empty.
> >>>
> >>>
> >>>Please advice me.
> >>>
> >>>Thanks,
> >>>Srinivas.
> >>>
> >>>
> >>>>Did you configure the RemoteAddrNotInNetwork matcher for your
> >>>>
> >>>local network?
> >>>
> >>>>        --- Noel
> >>>>
> >>>>--
> >>>>To unsubscribe, e-mail:
> >>>>
> >>><ma...@jakarta.apache.org>
> >>>
> >>>>For additional commands, e-mail:
> >>>>
> >><ma...@jakarta.apache.org>
> >>
> >>--
> >>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> >>For additional commands, e-mail: <ma...@jakarta.apache.org>
> >>
> >>--
> >>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> >>For additional commands, e-mail: <ma...@jakarta.apache.org>
> >>
> >
> >
> >--
> >To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> >For additional commands, e-mail: <ma...@jakarta.apache.org>
> >
> >
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Help Please

Posted by Vasko Tomanov <va...@web.bg>.
this is my maillet in config.xml      

   <mailet 
match="RemoteAddrNotInNetwork=127.0.0.1,212.50.9.*,212.56.7.*,193.68.153.*" 
class="ToProcessor">
            <processor> spam </processor>
          </mailet>


it work fine without problems 3 from 3 month

Super-User wrote:

>Danny,
>
>How are you ?.
>
>Thanks for the info.
>
>I have updated  /apps/james/conf/config.xml for the following.
>
>RemoteAddrNotInNetwork=127.0.0.1, 172.16.30.*
>and stop/started the James.
>
>But,no luck.
>
>Still mails were going to spam folder.
>
>Please advice me.
>
>Thanks,
>Srinivas.
>
>
>>try "RemoteAddrNotInNetwork=127.0.0.1, 172.16.30.*"
>>
>>>-----Original Message-----
>>>From: root [mailto:root]On Behalf Of Super-User
>>>Sent: 23 August 2002 16:30
>>>To: James Users List; noel@devtech.com
>>>Subject: Re: Help Please
>>>
>>>
>>>Noel,
>>>
>>>How are you ?.
>>>
>>>Thanks for the info.
>>>
>>>I have  modified config.xml for the  following;
>>>
>>><mailet match="RemoteAddrNotInNetwork=127.0.0.1,172.16.30.0" class="To
>>>Processor">
>>>
>>>My network is 172.16.30.0 .
>>>
>>>I have stopped and started the JAMES.
>>>
>>>But,no luck.
>>>
>>>The inboxes dir was looks empty.
>>>
>>>
>>>Please advice me.
>>>
>>>Thanks,
>>>Srinivas.
>>>
>>>
>>>>Did you configure the RemoteAddrNotInNetwork matcher for your
>>>>
>>>local network?
>>>
>>>>        --- Noel
>>>>
>>>>--
>>>>To unsubscribe, e-mail:
>>>>
>>><ma...@jakarta.apache.org>
>>>
>>>>For additional commands, e-mail:
>>>>
>><ma...@jakarta.apache.org>
>>
>>--
>>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
>>For additional commands, e-mail: <ma...@jakarta.apache.org>
>>
>>--
>>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
>>For additional commands, e-mail: <ma...@jakarta.apache.org>
>>
>
>
>--
>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Help Please

Posted by Super-User <sk...@telegea.com>.
Danny,

How are you ?.

Thanks for the info.

I have updated  /apps/james/conf/config.xml for the following.

RemoteAddrNotInNetwork=127.0.0.1, 172.16.30.*
and stop/started the James.

But,no luck.

Still mails were going to spam folder.

Please advice me.

Thanks,
Srinivas.


> try "RemoteAddrNotInNetwork=127.0.0.1, 172.16.30.*"
>
> > -----Original Message-----
> > From: root [mailto:root]On Behalf Of Super-User
> > Sent: 23 August 2002 16:30
> > To: James Users List; noel@devtech.com
> > Subject: Re: Help Please
> >
> >
> > Noel,
> >
> > How are you ?.
> >
> > Thanks for the info.
> >
> > I have  modified config.xml for the  following;
> >
> > <mailet match="RemoteAddrNotInNetwork=127.0.0.1,172.16.30.0" class="To
> > Processor">
> >
> > My network is 172.16.30.0 .
> >
> > I have stopped and started the JAMES.
> >
> > But,no luck.
> >
> > The inboxes dir was looks empty.
> >
> >
> > Please advice me.
> >
> > Thanks,
> > Srinivas.
> >
> >
> > > Did you configure the RemoteAddrNotInNetwork matcher for your
> > local network?
> > >
> > >         --- Noel
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> > > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Help Please

Posted by Danny Angus <da...@apache.org>.
try "RemoteAddrNotInNetwork=127.0.0.1, 172.16.30.*"

> -----Original Message-----
> From: root [mailto:root]On Behalf Of Super-User
> Sent: 23 August 2002 16:30
> To: James Users List; noel@devtech.com
> Subject: Re: Help Please
>
>
> Noel,
>
> How are you ?.
>
> Thanks for the info.
>
> I have  modified config.xml for the  following;
>
> <mailet match="RemoteAddrNotInNetwork=127.0.0.1,172.16.30.0" class="To
> Processor">
>
> My network is 172.16.30.0 .
>
> I have stopped and started the JAMES.
>
> But,no luck.
>
> The inboxes dir was looks empty.
>
>
> Please advice me.
>
> Thanks,
> Srinivas.
>
>
> > Did you configure the RemoteAddrNotInNetwork matcher for your
> local network?
> >
> >         --- Noel
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
<ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Help Please

Posted by Super-User <sk...@telegea.com>.
Noel,

How are you ?.

Thanks for the info.

I have  modified config.xml for the  following;

<mailet match="RemoteAddrNotInNetwork=127.0.0.1,172.16.30.0" class="To
Processor">

My network is 172.16.30.0 .

I have stopped and started the JAMES.

But,no luck.

The inboxes dir was looks empty.


Please advice me.

Thanks,
Srinivas.


> Did you configure the RemoteAddrNotInNetwork matcher for your local network?
>
>         --- Noel
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Help Please

Posted by "Noel J. Bergman" <no...@devtech.com>.
Did you configure the RemoteAddrNotInNetwork matcher for your local network?

	--- Noel

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Help Please

Posted by Super-User <sk...@telegea.com>.
Hi,
How are you ?.

I have installed JAMES on my Sun server.
It was running fine.
I have created users through admin tool.

I was sending mails to pop3 users without any problem by mailx cmd.

However,the mails were going to spam folder.
Inboxes dir was empty.

Please advice me.

Thanks,
Srinivas.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: FAQ change and James enhancements [Was Re: Outgoing mail problem)

Posted by David Jenkins <da...@mdcreate.com>.
Noel J. Bergman wrote:
> Have you read RFC 1939?  The mailbox name is "a string identifying a mailbox
> (required), which is of significance ONLY to the server."
Read it and BTW, can a commiter add the doc to the
rfclist under pop3 only 1725 is under there...

Thanks,
    DJ


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: [PATCH] FAQ change

Posted by "Noel J. Bergman" <no...@devtech.com>.
David,

FWIW, I made a change to RemoteAddrNotInNetwork (and RemoteAddrInNetwork)
that allows the use of a domain name, not just an IP address.  Networks must
still be added by IP address (someday someone should add mask support).

	--- Noel


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


[PATCH] FAQ change

Posted by David Jenkins <da...@mdcreate.com>.
Going to try this again 8)  The listserv was removing my attachments.
Learned how to use cvs.  Retrieved jakarta-james. Made modifications to 
xdocs/FAQ.xml.  Changes I made:
     Added RemoteAddrNotInNetwork fix for item 3
     Did a little reformatting in the source for item 10 - it was 
causing browsers to have to scroll left/right to see the entire FAQ.
     Changed "Last Updated" message to read August instead of May

This is my first submission so be kind. ;)


     David Jenkins

RE: FAQ change and James enhancements [Was Re: Outgoing mail problem)

Posted by "Noel J. Bergman" <no...@devtech.com>.
> Could you setup user in-boxes to include the domain on multidomain
> systems?

As I said earlier:

> > But that doesn't prevent the use of the whole address, however doing so
> > would require changes to local delivery.

> Another cleaner, but more involved change would be to map
> domains in user repositories either in subdirs or in
> naming conventions for the file.

That's just it ... there is no file, necessarily.  There is a repository
abstraction.  There is one kind of repository built on the file system, and
another build on JDBC.  So what you want to deal with is the abtract model.
The local-part is used as a key into the store.  Also, don't forget that
people often want to map multiple addresses into one.  I'm not convinced,
that a virtual user table doesn't provide much of what people need; it
certainly does the trick for SendMail.  So I do think that revisiting the
user repository model is a good idea, but I'd sooner see it done
comprehensively than patchwork.

> I understand that portion, what I'm looking for is another option to the
> "black-hole" method.

I understand.  I watch SPAM spool into my system all the time, and have been
cataloging strings to delete them, so that we can parse out any legitimately
misdirected e-mail from the volumes of SPAM.  As I mentioned last week
(check the archives), I'm thinking of a shared object in the MailetContext
that can be used to inform the SMTP Handler about users to be refused.  That
way, it could refuse service and terminate them, e.g., issue a 421 and hang
up.

Actually, I'd prefer to be able to do handle spammers in iptables, and
discard their request thus consuming THEIR resources for a change, but
iptables isn't scalable.

> by reporting back that the user doesn't exist, the spammer
> will stop trying to send

No, actually, they'll use you to identify which addresses ARE valid.

As for the rest of what you said, it is a bit naive, unfortunately.  You've
no idea of the scope and scale of spam operations, and the techniques they
use to try to get under your radar.  Visit news:news.admin.net-abuse.email.


> I hate spam so much, I plan on creating a site to report

See spews, spamcop, ordb, and many many MANY other sites.

	--- Noel


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: FAQ change and James enhancements [Was Re: Outgoing mail problem)

Posted by Danny Angus <da...@apache.org>.
>  By accepting spam, spammers will continue to send

No, this is an over simplification, most spammers send probing mail first,
and only use a relay once a server has successfully relayed this mail.


> Me personally, I hate spam so much, I plan on creating a site to report
> sites that refuse to address the problem (pardon the pun 8).

There are already a number of competing and well established projects doing
just this.

d.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: FAQ change and James enhancements [Was Re: Outgoing mail problem)

Posted by David Jenkins <da...@mdcreate.com>.
Danny Angus wrote:

>>Have you read RFC 1939?  The mailbox name is "a string
>>identifying a mailbox
>>(required), which is of significance ONLY to the server."

I read it and I agree with below.  As far as a security risk I don't see 
how it's any more of a risk.... If someone is sniffing traffic, they 
know where you connected to and what username you sent anyhow (Unless 
the entire transmission is secure, which also doesn't create any higher 
security risk).  I'm truly open for discussion on this, I just currently 
don't see it.

> But that doesn't prevent the use of the whole address, however doing so
> would require changes to local delivery.

Could you setup user inboxes to include the domain on multidomain 
systems? Another cleaner, but more involved change would be to map
domains in user repositories either in subdirs or in naming conventions 
for the file.  I freely admit I don't understand the system near enough 
to know all the implications, but I'm slowly getting there.
>>Honestly, I'd love to can file system user
> There is consensus, I believe, in extending choice.

Precisely. Just because one person looks at it as a burdensome method 
does not mean it should be excluded as an option.

>>>otherwise the mail server returns a User Unknown
>>>message of some type.
>>Ah!  Gotcha.  You want to return a 550, but I believe that you
> it is better anti-spam practice not to indicate invalidity in a 550 message,
> James doesn't validate addresses at all,  [FAQ reference]

I understand that portion, what I'm looking for is another option to the 
"black-hole" method.  By accepting spam, spammers will continue to send 
(although the lucky user doesn't have to see it).  Granted, for the 
alternate method I bring up, there will be more overhead for each 
individual message (although I wouldn't imagine it's going to be much 
more than the overall black-hole method), but, by reporting back that 
the user doesn't exist, the spammer will stop trying to send AND given 
that the mappings are compared to sender address as well, I believe it 
becomes MUCH harder for spammers to emulate and bypass.
If To and From don't match they receive a 550 as Noel stated.  I also 
have a second motive for doing the comparison - tracking who is either 
selling names or has a security loophole in their site.  All the items I 
listed, used together, make for an excellent tracking system for users 
and admins alike.  Admin@trackedDomain can send to Admin@breachedDomain 
and say many of my users are complaining about receiving spam from the 
email they used on your site.

Me personally, I hate spam so much, I plan on creating a site to report 
sites that refuse to address the problem (pardon the pun 8).
> In fact James performs no pre-processing of mail during the SMTP transaction
> apart from checking the basic syntax of the SMTP conversation itself.

I'm not saying make it default behavior, just an optional processing step.

> The possibility of adding more complex behaviour to this element, and of
> adding virtual hosting to the whole mail system have been under discussion
> for at least a year but keep failing to reach concensus on any specific
> scheme, and in the meantime no commiter has taken the bull by the horns and
> implemented any stop-gap measures.
I'm studying the system now, I'm going to try to get a proposal/proof of 
concept coding done (not sure exactly when though 8).

     David Jenkins


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: FAQ change and James enhancements [Was Re: Outgoing mail problem)

Posted by Anthony Buckton <ab...@blackink.net.au>.
Hi All,

HyperSonic works wonderfully. After having hassles with some of the 
file store during some of my early configs, I switched on HyperSonic 
and never went back...

I actually now use the HyperSonic in "Server Mode" running in its own 
JVM outside of the Avalon JVM - This allows me to stop the email 
processing and analyse/manipulate the data if needed. It wasn't that 
easy under Avalon (and I wasn't all that fussed trying to work out 
Avalon)..

Regards,

Anthony

At 06:56 PM 25/08/2002 +0100, Danny Angus wrote...

> > http://jakarta.apache.org/avalon/apps/apps/hsql/index.html).  Since 
> we
> > already have a requirement on an Avalon container (Phoenix) for 
> James, it
> > didn't seem unreasonable to switch to a pure Java SQL engine from a 
> pure
> > Java file system.  As I recall, someone recently posted the XML 
> changes
> > necessary for some version of James to work with Hypersonic 
> SQL.  Just a
> > thought for consideration.
>
>By all measn support HyperSonic as well, lets not drop filesystem as a
>default.
>
>
> > By the time those are layered onto a file system driver, we
> > might end up accidentally building a database layer.
>
>Not quite sure how you work that out.
>
>
>--
>To unsubscribe, 
>e-mail:   <ma...@jakarta.apache.org>
>For additional commands, e-mail: 
><ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: FAQ change and James enhancements [Was Re: Outgoing mail problem)

Posted by "Noel J. Bergman" <no...@devtech.com>.
> > By the time those are layered onto a file system driver, we
> > might end up accidentally building a database layer.

> Not quite sure how you work that out.

Just listening to the laundry list of things, and projecting.  As I said, it
wasn't a change I expected to see, unless it becomes necessary.  I
understand the desire to keep the file system as an LCD.

	--- Noel


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: FAQ change and James enhancements [Was Re: Outgoing mail problem)

Posted by Danny Angus <da...@apache.org>.
> http://jakarta.apache.org/avalon/apps/apps/hsql/index.html).  Since we
> already have a requirement on an Avalon container (Phoenix) for James, it
> didn't seem unreasonable to switch to a pure Java SQL engine from a pure
> Java file system.  As I recall, someone recently posted the XML changes
> necessary for some version of James to work with Hypersonic SQL.  Just a
> thought for consideration.

By all measn support HyperSonic as well, lets not drop filesystem as a
default.


> By the time those are layered onto a file system driver, we
> might end up accidentally building a database layer.

Not quite sure how you work that out.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: FAQ change and James enhancements [Was Re: Outgoing mail problem)

Posted by "Noel J. Bergman" <no...@devtech.com>.
> [RFC 1939] doesn't prevent the use of the whole address, however doing so
> would require changes to local delivery.

I believe I pointed out some of the code changes that would be necessary.
If we're contemplating making a Release Build, it seems to me that it would
be preferable to make those changes afterwards, rather than risk unintended
consequences.

I use MySQL, and have no intention of switching.  My suggestion of
HypersonicSQL was precisely to accommodate the reason you gave for the file
system: "I would be very much against having any kind of third party
software specified as a run-time dependancy for storage, hence the 100% java
filesystem gets my vote even though I don't use it."  Hypersonic SQL IS a
100% pure Java SQL engine that is already available as a Avalon service (see
http://jakarta.apache.org/avalon/apps/apps/hsql/index.html).  Since we
already have a requirement on an Avalon container (Phoenix) for James, it
didn't seem unreasonable to switch to a pure Java SQL engine from a pure
Java file system.  As I recall, someone recently posted the XML changes
necessary for some version of James to work with Hypersonic SQL.  Just a
thought for consideration.

Part of what drives that thought is listening to the various things people
want to do with James in terms of additional requirements for user and mail
information.  By the time those are layered onto a file system driver, we
might end up accidentally building a database layer.

> it is better anti-spam practice not to indicate invalidity in a 550
message

I believe that he was presupposing changes that would express validity.  As
for the anti-SPAM practices, I've seen suggestions to only permitting thoses
sender that are authorized (e.g., via SMTP AUTH) to use the commands.

	--- Noel


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: FAQ change and James enhancements [Was Re: Outgoing mail problem)

Posted by Danny Angus <da...@apache.org>.
> Have you read RFC 1939?  The mailbox name is "a string
> identifying a mailbox
> (required), which is of significance ONLY to the server."

But that doesn't prevent the use of the whole address, however doing so
would require changes to local delivery.

>Honestly, I'd love to can file system user
> repositories in favor of at least using HyperSonicSQL bundled with James,
> but there does not appear to be any consensus to do that.

There is consensus, I believe, in extending choice.
If you want to use HyperSonic you can, I use MySQL, many others will be
happy with the file system.

IMO concerns seperate such that James should be capable of using several
different storage providers (RDBMs's and filesystems from different OS's)
but not restrict choice.
Then the decision regarding what to use becomes, rightly, an implementation
decision and isn't influenced unduly by James.
I would be very much against having any kind of thirdparty software
specified as a run-time dependancy for storage, hence the 100% java
filesystem gets my vote even though I don't use it.

> > otherwise the mail server returns a User Unknown
> > message of some type.
>
> Ah!  Gotcha.  You want to return a 550, but I believe that you
> are supposed
> to say that it is denied, not that it is unknown.

it is better anti-spam practice not to indicate invalidity in a 550 message,
James doesn't validate addresses at all, read
http://jakarta.apache.org/james/FAQ.html#2

In fact James performs no pre-processing of mail during the SMTP transaction
apart from checking the basic syntax of the SMTP conversation itself.

The possibility of adding more complex behaviour to this element, and of
adding virtual hosting to the whole mail system have been under discussion
for at least a year but keep failing to reach concensus on any specific
scheme, and in the meantime no commiter has taken the bull by the horns and
implemented any stop-gap measures.

d.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


FAQ change and James enhancements [Was Re: Outgoing mail problem)

Posted by "Noel J. Bergman" <no...@devtech.com>.
> As far as the namespace problem: what is preventing us from having
> people send the entire email address as the user if they want to?

Have you read RFC 1939?  The mailbox name is "a string identifying a mailbox
(required), which is of significance ONLY to the server."

As for what specifically prevents the current code from allowing
"user@domain" to be a valid POP3 mailbox name, look at James.storeMail().
See the references to recipient.getUser()?  That strips off the domain name,
and uses the local part.

Take a look at RFC 2821 (SMTP): "The syntax of the local part of a mailbox
must conform to receiver site conventions and the syntax specified in
section 4.1.2."  That section says: Mailbox = Local-part "@" Domain.

At the moment, I'll let others comment on the implications of not stripping
the domain, but let me suggest that there are good security reasons for
separating your SMTP alias from your POP3 login identity.  If we're serious
about the E for Enterprise part of the James name, then I don't think we
want a naive user mapping.

> As long as [a virtual user table] works with all configuration
> storage methods I'm fine with that.

None of them do, right now.  Mine relies, in fact, upon using SQL in
non-trivial fashion.  Honestly, I'd love to can file system user
repositories in favor of at least using HyperSonicSQL bundled with James,
but there does not appear to be any consensus to do that.

In any event, I agree with you.  I don't expect anything to happen until
after 2.1, but if you would like to familarize yourself with the repository
system, and then start a discussion about a normalized user model, PLEASE do
so.  Try to take into account other things, such as: a desire to add named
attribitutes to both user and mail objects post-2.1; various other account
related issues in addition to virtual hosting, e.g., quotas,  mailing lists,
vacation status, sub-accounts, etc., some of which may be addressed by those
attributes.

> in effect, what I want to accomplish is the following scenario:
> For email address 1234.MyUser@Mydomain only users at *@somebiz.com
> can send to me, otherwise the mail server returns a User Unknown
> message of some type.

Ah!  Gotcha.  You want to return a 550, but I believe that you are supposed
to say that it is denied, not that it is unknown.  In any event, don't
forget to add user filters to your unified data model.  :-)  Did I mention
that the data model will need to be extendable and pluggable?

You should be aware that James currently does very little verification
during the SMTP transaction.  From the sounds of recent conversations, some
of this is likely to change as needed, so long as the good mailet flow
within James is preserved.

	--- Noel



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: FAQ change and James enhancements [Was Re: Outgoing mail problem)

Posted by "Noel J. Bergman" <no...@devtech.com>.
---------------
>> That should be added as another tip in the FAQ if that isn't already in
>> route. 8)
>
> Care to write it up and submit it?  ;-)

  Sure.  I've added it and have it attached, but for future reference what
  diff command options do I use? (I'm still reacclimating to *nix -
  forgive me, the lure of Window$ sucked the memories from me 8)
---------------

David,

Nothing was attached.  However, let me skip right ahead and answer the
question.

You want to make a local copy of the CVS.  After you have done that, you can
change a file locally, and use "cvs diff -u" to generate a patch.  Please
make sure that there are NO TABS and that the LINE TERMINATION is Unix
convention (linefeeds, no carriage-returns).  When you are read, attach the
patch to an e-mail, prefix the subject with the magic tag "[PATCH]", and
send it along.

Documentation for all of this is on the James web site.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


FAQ change and James enhancements [Was Re: Outgoing mail problem)

Posted by David Jenkins <da...@mdcreate.com>.
I realized that most people would probably immediately delete given the 
older header.

  I moved this over from the Users List.

  Noel J. Bergman wrote:

>> That should be added as another tip in the FAQ if that isn't already in
>> route. 8)
>
> Care to write it up and submit it?  ;-)

  Sure.  I've added it and have it attached, but for future reference what
  diff command options do I use? (I'm still reacclimating to *nix -
  forgive me, the lure of Window$ sucked the memories from me 8)

> Hop on over to the developer list anytime.

  I subscribed to both User and Dev at the same time 8)

>> As far as the namespace problem: what is preventing us from having
>> people send the entire email address as the user if they want to?
>
  I should have specified for POP3.

> I don't know that this is really the right list to get into the subject.
> What I do in the JDBCVirtualUserTable code is implement mapping from 
> [user,
> domain] -> target, with wildcard support.  I don't support "ERROR:" type
> targets, yet.
>
>> this would be handy in the instances like postmaster, webmaster, admin,
>> etc.
>
> I handle that with a wildcard domain.


  As long as it works with all configuration storage methods I'm fine with
  that.

>> Users [are] allowed to create prefixes or suffixes of [their] userid
>
> Do admins really want to permit users to create arbitrary (sub)-accounts?
> If so, this will be an interesting discussion when it comes to accounting
> and quotas.

  These really only become aliases.  Quotas don't change, and since the
  primary userid always has to be in the name and a connecting character
  (like "." or "_") the name couldn't be mistaken for someone elses id.
  Not sure what type of accounting you mean (like in the case where a
  person is charged by email address quantity?)

>> What about users being able to associate incoming email addresses with
>> the address it was sent to and then if there isn't a match return an
>> "unknown user" error?
>
> I don't follow.
>     --- Noel

I'm still reading up on the process, but, in effect, what I want to
accomplish is the following scenario:
For email address 1234.MyUser@Mydomain only users at *@somebiz.com
can send to me, otherwise the mail server returns a User Unknown
message of some type.


Re: Outgoing mail problem

Posted by David Jenkins <da...@mdcreate.com>.
I moved this over from the Users List.

Noel J. Bergman wrote:
>>That should be added as another tip in the FAQ if that isn't already in
>>route. 8)
> Care to write it up and submit it?  ;-)
Sure.  I've added it and have it attached, but for future reference what 
diff command options do I use? (I'm still reacclimating to *nix - 
forgive me, the lure of Window$ sucked the memories from me 8)

> Hop on over to the developer list anytime.
I subscribed to both User and Dev at the same time 8)

>>As far as the namespace problem: what is preventing us from having
>>people send the entire email address as the user if they want to?
I should have specified for POP3.

> I don't know that this is really the right list to get into the subject.
> What I do in the JDBCVirtualUserTable code is implement mapping from [user,
> domain] -> target, with wildcard support.  I don't support "ERROR:" type
> targets, yet.
>>this would be handy in the instances like postmaster, webmaster, admin,
>>etc.
> I handle that with a wildcard domain.

As long as it works with all configuration storage methods I'm fine with 
that.

>>Users [are] allowed to create prefixes or suffixes of [their] userid
> Do admins really want to permit users to create arbitrary (sub)-accounts?
> If so, this will be an interesting discussion when it comes to accounting
> and quotas.
These really only become aliases.  Quotas don't change, and since the 
primary userid always has to be in the name and a connecting character 
(like "." or "_") the name couldn't be mistaken for someone elses id.
Not sure what type of accounting you mean (like in the case where a 
person is charged by email address quantity?)

>>What about users being able to associate incoming email addresses with
>>the address it was sent to and then if there isn't a match return an
>>"unknown user" error?
> I don't follow.
> 	--- Noel
I'm still reading up on the process, but, in effect, what I want to 
accomplish is the following scenario:
For email address 1234.MyUser@Mydomain only users at *@somebiz.com
can send to me, otherwise the mail server returns a User Unknown
message of some type.

-- 
If you only compete with yourself,
     you can always be a winner. - David Jenkins
Of course, you could always be a loser too. - Miles Thornton


RE: Outgoing mail problem

Posted by "Noel J. Bergman" <no...@devtech.com>.
> That should be added as another tip in the FAQ if that isn't already in
> route. 8)

Care to write it up and submit it?  ;-)

> What is the status [of Virtual Domains]?

Nothing has been done lately on the general front.  I have, but have not yet
released, a JDBCVirtualUserTable mailet that is closer to sendmail
functionality.  I posted an early overview to the developer's list a little
while back:

http://www.mail-archive.com/james-dev@jakarta.apache.org/msg03037.html

So far it is working nicely for me, so I'm feeling pretty comfortable to
post it.  As soon as things settle down for the CVS committers, I'll
probably do it.

I personally don't expect anything significant to happen with virtual
hosting until the developers sit down to talk about the user repository data
model.  I am hoping that a normalized, unified, extendable data model will
emerge.

> If no progress, I'd be very willing to help.

Hop on over to the developer list anytime.

> As far as the namespace problem: what is preventing us from having
> people send the entire email address as the user if they want to?

I don't know that this is really the right list to get into the subject.
What I do in the JDBCVirtualUserTable code is implement mapping from [user,
domain] -> target, with wildcard support.  I don't support "ERROR:" type
targets, yet.

> this would be handy in the instances like postmaster, webmaster, admin,
etc.

I handle that with a wildcard domain.

> Users [are] allowed to create prefixes or suffixes of [their] userid

Do admins really want to permit users to create arbitrary (sub)-accounts?
If so, this will be an interesting discussion when it comes to accounting
and quotas.

> What about users being able to associate incoming email addresses with
> the address it was sent to and then if there isn't a match return an
> "unknown user" error?

I don't follow.

	--- Noel


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Outgoing mail problem

Posted by David Jenkins <da...@mdcreate.com>.
Noel J. Bergman wrote:
> Incoming messages are working just fine, but when I try to send out
> using JAMES smtp it immediately routes the messages to spam. 
> 
> Did you configure the RemoteAddrNotInNetwork matcher?
> 
> 	--- Noel
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
> 
> 

Can't believe I missed that, thanks.
That should be added as another tip in the FAQ if that isn't already in
route. 8)

My next question has to do with Virtual domains:
I saw that support is still being debated on.  What is the status?
If no progress, I'd be very willing to help.
As far as the namespace problem: what is preventing us from having 
people send the entire email address as the user if they want to?
Then if this is a multidomain server and a domain is present we
parse it out for comparing to the list we serve and then compare
the whole name to the user list (or provide a mechanism like
Apache to <Include> subdirs of users for each domain)?
(Maybe if a user is entered without a domain on a multi domain system
the same userid is the same person across all domains where that userid
is not already present? - this would be handy in the instances like
postmaster, webmaster, admin, etc....).

The next two I'm almost sure require development.

First-
This one requires a scenario:
UserA has an account on DomainA and on that domain they are allowed to
create prefixes or suffixes of they're userid to they're hearts content.
these should all be valid users but should be going to the various sub
mailbox they choose (or the main mailbox).
So for example, the UserA@DomainA above creates two prefix userids:
(1) 3er45s.UserA@DomainA and
(2) 5frfg5.UserA@DomainA

(1) goes to sub mailbox UserA.Biz
(2) goes to the regular inbox

Second-
What about users being able to associate incoming email addresses with
the address it was sent to and then if there isn't a match return an
"unknown user" error?

Thanks,
      David Jenkins
-- 
If you only compete with yourself,
     you can always be a winner. - David Jenkins
Of course, you could always be a loser too. - Miles Thornton


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>