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 Mark Waschkowski <mw...@gmail.com> on 2007/03/28 14:26:16 UTC

problem with gateway

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

Re: problem with gateway

Posted by Mark Waschkowski <mw...@gmail.com>.
Ugh, been trying a bunch of stuff today, and nothing seems to be working.
Some of it may be DNS related, but ultimately I'm thinking that the upgrade
process caused a problem, but can't be sure. So, before I waste anyones time
here (thanks for the suggestions so far btw!) I'm going to start from
scratch tomorrow morning and do a fresh install of 2.3 and configure it all
using the new config files, and I"ll let you know if that helped or not.

The reason I'm going this route is because I'm able to send emails to JAMES,
but nothing is being registered in ANY of the logs, anywhere, and I know
from past experience that if flub something in the config files things can
stop working and it doesn't always log an exception. I'm guessing this is
user error and a fresh config will hopefully bring issues to light....

On 3/30/07, Stefano Bagnara <ap...@bago.org> wrote:
>
> This is weird because the "to-gmail.com" and the log "Sending mail to XX
> on host gmail.com" are only there if there is no gateway.
>
> What about the double log? Have you restarted james at 04:21 and then
> again at 04:23 ? if so you should see the "Adding SMTP gateway" also in
> the log 04-23 ... Can you check?
>
> Stefano
>
> Mark Waschkowski ha scritto:
> > 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 [
> > mwaschkowski@gmail.com] 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 [mwaschkowski@gmail.com]
> > 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 <mw...@gmail.com> 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 <ap...@bago.org> 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: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>


-- 
Best,

Mark Waschkowski

Re: problem with gateway

Posted by Stefano Bagnara <ap...@bago.org>.
This is weird because the "to-gmail.com" and the log "Sending mail to XX 
on host gmail.com" are only there if there is no gateway.

What about the double log? Have you restarted james at 04:21 and then 
again at 04:23 ? if so you should see the "Adding SMTP gateway" also in 
the log 04-23 ... Can you check?

Stefano

Mark Waschkowski ha scritto:
> 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 [
> mwaschkowski@gmail.com] 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 [mwaschkowski@gmail.com]
> 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 <mw...@gmail.com> 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 <ap...@bago.org> 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: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: problem with gateway

Posted by Stefano Bagnara <ap...@bago.org>.
Mark Waschkowski ha scritto:
> 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.

Thank you for the information, but smtpserver components are not related 
in anyway to the RemoteDelivery component. (Well, the RemoteDelivery 
take his heloName from the smtpserver/helloname, but this is the only 
thing and it does not relate to the use of gateway).

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: problem with gateway

Posted by Mark Waschkowski <mw...@gmail.com>.
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 <mw...@gmail.com> 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 [
> mwaschkowski@gmail.com] 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 [mwaschkowski@gmail.com]
> 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 <mw...@gmail.com> 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 < apache@bago.org> 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: server-user-unsubscribe@james.apache.org
> > > For additional commands, e-mail: server-user-help@james.apache.org
> > >
> > >
> >
> >
> > --
> > Best,
> >
> > Mark Waschkowski
>
>
>
>
> --
> Best,
>
> Mark Waschkowski




-- 
Best,

Mark Waschkowski

Re: problem with gateway

Posted by Mark Waschkowski <mw...@gmail.com>.
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 [
mwaschkowski@gmail.com] 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 [mwaschkowski@gmail.com]
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 <mw...@gmail.com> 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 <ap...@bago.org> 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: server-user-unsubscribe@james.apache.org
> > For additional commands, e-mail: server-user-help@james.apache.org
> >
> >
>
>
> --
> Best,
>
> Mark Waschkowski




-- 
Best,

Mark Waschkowski

Fetchmail and Servernames list confusion

Posted by Hans Liebenberg <ha...@cambrient.com>.
Hi,

I am using fetchmail to fetch from a domain "xxxx.co.za"

According to the James config.xml docs....

      <!-- Warning: If you are using fetchmail it is important to 
include the -->
      <!-- fetched domains in the server name list to prevent 
looping.       -->
      <servernames autodetect="true" autodetectIP="true">
<!-- *********** -->
         <servername>xxxx.co.za</servername>
         <servername>localhost</servername>
      </servernames>

Which I thought seemed strange as xxxx.co.za is a remote domain, but I 
added it regardless.
Now each time you attempt to send a message to bob@xxxx.co.za it goes 
straight into the address-error folder as I guess it tries to find bob 
as a local address.

So am I correct in saying that the docs "<!-- Warning: If you are using 
fetchmail it is important to include the -->
      <!-- fetched domains in the server name list to prevent 
looping.       -->" are either incorrect or confusing??

I fixed my problem by simply removing the domain from the config

Thanks
Hans



---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: problem with gateway

Posted by Norman Maurer <no...@apache.org>.
Hmm.. thats strange .. Did you restart the james server after adding the
gateway ?

bye
Norman

Mark Waschkowski schrieb:
> 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 [
> mwaschkowski@gmail.com] 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 [mwaschkowski@gmail.com]
> 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 <mw...@gmail.com> 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 <ap...@bago.org> 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: server-user-unsubscribe@james.apache.org
>> > For additional commands, e-mail: server-user-help@james.apache.org
>> >
>> >
>>
>>
>> -- 
>> Best,
>>
>> Mark Waschkowski
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: problem with gateway

Posted by Mark Waschkowski <mw...@gmail.com>.
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 <ap...@bago.org> 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: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>


-- 
Best,

Mark Waschkowski

Re: problem with gateway

Posted by Stefano Bagnara <ap...@bago.org>.
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: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org