One more thing, I have two smtp servers setup in the config and assembly
because my internet provider doesn't allow for 25 traffic, like so:

  <smtpserver enabled="true">
     <!-- port 25 is the well-known/IANA registered port for SMTP -->
     <port>25</port>

  <smtpserverXYZ enabled="true">
     <!-- port 25 is the well-known/IANA registered port for SMTP -->
     <port>XYZ</port>

which allows me to connect to james from home over port XYZ and do testing
easily.

Mark

On 3/30/07, Mark Waschkowski <[EMAIL PROTECTED]> wrote:

OK, here is the log that I'm getting from james:

==> mailet-2007-03-30-04-21.log <==
30/03/07 04:21:36 INFO  James.Mailet: RemoteDelivery: Adding SMTP gateway:
k2smtpout.secureserver.net:25

==> mailet-2007-03-30-04-23.log <==
30/03/07 04:23:52 INFO  James.Mailet: RemoteDelivery: Remotely delivering
mail Mail1175253802531-11
30/03/07 04:23:52 INFO  James.Mailet : RemoteDelivery: Sending mail to [
[EMAIL PROTECTED] on host gmail.com
30/03/07 04:23:52 INFO  James.Mailet: RemoteDelivery: Remote delivery
thread (14) will process mail Mail1175253802531-11-to-gmail.com
30/03/07 04:23:52 INFO  James.Mailet: RemoteDelivery: Attempting to
deliver Mail1175253802531-11-to-gmail.com
30/03/07 04:23:53 INFO  James.Mailet: RemoteDelivery: Attempting delivery
of Mail1175253802531-11-to-gmail.com to host gmail-smtp-in.l.google.com.
at 64.233.163.27 for addresses [EMAIL PROTECTED]
30/03/07 04:23:53 INFO  James.Mailet: RemoteDelivery: Could not connect to
SMTP host: 64.233.163.27, port: 25

I'm not sure why there are two mailet log files, but the *-23 file
continues with trying all the other alt1, alt2 etc. mail servers for gmail.

I don't understand why its trying to connect to the smtp host when the
gateway was specified? Here is a snippet from my config.xml file:

 <!-- 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">
            <bounceProcessor>error</bounceProcessor>
            <!--
                        <outgoing> file://var/mail/outgoing/ </outgoing>
                        -->
            <!-- alternative database repository example below -->

            <outgoing> db://maildb/zzspool/outgoing </outgoing>
            <!-- Delivery Schedule based upon RFC 2821, 4.5.4.1 -->
            <!-- 5 day retry period, with 4 attempts in the first
                 hour, two more within the first 6 hours, and then
                 every 6 hours for the rest of the period. -->
            <delayTime>  5 minutes </delayTime>
            <!--
            <delayTime> 10 minutes </delayTime>
            <delayTime> 45 minutes </delayTime>
            <delayTime>  3 hours </delayTime>
            <delayTime>  12 hours </delayTime>
            -->
            <maxRetries> 1 </maxRetries>

            <!-- The number of threads that should be trying to deliver
outgoing messages -->
            <deliveryThreads> 40 </deliveryThreads>

            <!-- If false the message will not be sent to given server if
any recipients fail -->
            <sendpartial>false</sendpartial>

            <!-- A single mail server to deliver all outgoing messages.
-->
            <!-- This is useful if this server is a backup or failover
machine, -->
            <!-- or if you want all messages to be routed through a
particular mail server, -->
            <!-- regardless of the email addresses specified in the
message -->
            <!-- -->
            <!-- The gateway element specifies the gateway SMTP server
name. -->
            <!-- If your gateway mail server is listening on a port other
than 25, -->
            <!-- you can set James to connect to it on that port using the
gatewayPort -->
            <!-- element. -->
            <!-- Although normally multiple addresses are implemented
through proper -->
            <!-- DNS configuration, the RemoteDelivery mail does allow
specifying -->
            <!-- multiple gateway elements, each of which may also have a
port -->
            <!-- e.g., mygateway:2525 -->
            <!-- the gatewayPort element is used as a default -->

            <gateway>k2smtpout.secureserver.net</gateway>
            <gatewayPort>25</gatewayPort>
            <debug>true</debug>
         </mailet>
      </processor>

I've upgraded from 2.2 to 2.3.

Thanks,

Mark

On 3/29/07, Mark Waschkowski <[EMAIL PROTECTED]> wrote:
>
> Yes, your are right Stefano, for some reason they didn't display when I
> first looked at them during a 'tail mail* -f' but then showed up when I
> re-did the command. I had to watch the Raptors vs Maimi game last night, so
> didn't get a chance to play with it, but will be spending all day tomorrow
> (my day off) on it, and will let you know what I find in the logs.
>
> Thanks,
>
> Mark
>
> On 3/28/07, Stefano Bagnara < [EMAIL PROTECTED]> wrote:
> >
> > Adding a gateway is the right solution.
> >
> > Can you tell us what is your James version?
> >
> > And what are the logs? in the jamesfolder/apps/james/logs/mailet*.log
> > you should at least see the attempts.
> >
> > Stefano
> >
> > Mark Waschkowski ha scritto:
> > > Hi,
> > >
> > > I just switched over to a godaddy dedicated server and realized that
> > they
> > > require the use of an smtp gateway (and also come with a default
> > limit of
> > > 1000 relays / day) as described here:
> > >   http://help.godaddy.com/article.php?article_id=122
> > > Ugh. Well, I've already spent the time to configure everything else,
> > so I
> > > tried updating james' <gateway> setting with the specified one, and
> > then
> > > ran
> > > a test to send an email. I was tailing the James logs at the time
> > and
> > > saw no
> > > activity whatsoever. So I repeated the test, but still nothing. Did
> > I do
> > > something wrong?
> > >
> > > Thanks,
> > >
> > > Mark
> > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Best,
>
> Mark Waschkowski




--
Best,

Mark Waschkowski




--
Best,

Mark Waschkowski

Reply via email to