well just specify the right port in your code. this really depends on the library you use.
bye norman Am Donnerstag, 6. Oktober 2011 schrieb Charlie Hubbard < [email protected]>: > Thanks Norman. I found that and turned it off, but I still have trouble > with it sending the email. I think the problem is that the mail client I'm > using is trying to send the mail to the default port 25, and my James server > is running on port 8825 because it's my dev box. So how do developers test > their Mailets when we are running servers locally with no MX record and > potentially on non-default ports? > > I tried looking at Postage, but it was really confusing to setup and get > working with no examples, old documentation for 2x, and looks like it's > abandoned. > > What tricks am I missing here? > > Thanks > Charlie > > On Thu, Oct 6, 2011 at 1:07 AM, Norman Maurer > <[email protected]>wrote: > >> Hi there, >> >> comment the ValidRcptHandler in smtpserver.xml. That should do the trick. >> >> Bye, >> Norman >> >> >> 2011/10/6 Charlie Hubbard <[email protected]>: >> > So I'm testing out James using command line mail agent to send email to >> it >> > from the localhost. I don't have any users configured in it, and I'm >> trying >> > to send email to an made up user. I just want to see if my mailet will >> be >> > invoked using some real email. However, James is blocking it sending how >> > mail to unknown users on the local system is rejected. Here is the >> command >> > I'm using to send the email: >> > >> > mail -s "Mailet testy testy" chuck@localhost >> > >> > Since I don't have a DNS record to route the email to this instance of >> > James, as this is my dev machine, I was using localhost to route it. >> > >> > I opened up the mailetcontainer.xml and commented out some mailets hoping >> > this would turn off local user checking. Here is what I did: >> > >> > <processor state="transport" enableJmx="true"> >> > <mailet match="SMTPAuthSuccessful" class="SetMimeHeader"> >> > <name>X-UserIsAuth</name> >> > <value>true</value> >> > </mailet> >> > >> > <!-- Disable this if you want to have case-sensitive local-parts of >> > the recipients --> >> > <mailet match="RecipientIsLocal" class="RecipientToLowerCase"/> >> > >> > <!--<mailet match="HostIsLocal" class="ToProcessor">--> >> > <!--<processor>local-address-error</processor>--> >> > <!--<notice>550 - Requested action not taken: no such user >> > here</notice>--> >> > <!--</mailet>--> >> > >> > <mailet match="All" class="com.emailarchive.mailet.ArchiveMailet"/> >> > >> > <mailet match="All" class="RemoteDelivery"> >> > <outgoingQueue>outgoing</outgoingQueue> >> > <delayTime>5 minutes</delayTime> >> > <delayTime>10 minutes</delayTime> >> > <delayTime>45 minutes</delayTime> >> > <delayTime>2 hours</delayTime> >> > <delayTime>3 hours</delayTime> >> > <delayTime>6 hours</delayTime> >> > <maxRetries>25</maxRetries> >> > <maxDnsProblemRetries>0</maxDnsProblemRetries> >> > <deliveryThreads>10</deliveryThreads> >> > <sendpartial>true</sendpartial> >> > <bounceProcessor>bounces</bounceProcessor> >> > </mailet> >> > </processor> >> > >> > You can see the local-address-error has been commented out. However, >> it's >> > still sending that message and my mailet isn't being invoked. Is there >> any >> > other configuration I need to tweak to get this to work? >> > >> > Thanks, >> > Charlie >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >
