A quick and dirty way to *see* exactly where it's failing is to look at the debug stack trace when you get the error and you should see the line in ERJavaMail that the exception is coming from. Click on the line and it'll take you to the source. You should be able to hash out from that where exactly it's crapping out.
I left this out, but don't forget to set er.javamail.smtpAuth = true Sets whether or not Authenticated SMTP is used to send outgoing mail. If set, er.javamail.smtpUser MUST also be set (and preferably er.javamail.smtpPassword). er.javamail.smtpUser = smtpusername The username to use to login to the authenticated SMTP server. er.javamail.smtpPassword = smtppassword The password to use to login to the authenticated SMTP server. More info: http://wiki.objectstyle.org/confluence/display/WO/Project+WONDER-Frameworks-ERJavaMail John A. Larson President Precision Instruments, Inc. Ph: 847-824-4194 Fax: 866-240-7104 On Dec 15, 2010, at 9:51 PM, Jesse Tayler <[email protected]> wrote: > thanks - that's good thinking - > > it's my server, and I think I checked the port which seems ok, but that's a > good fix for sure > > it may be an authentication issue, there's another line about authentication > > I'd guess I'll setup an outgoing SMTP server which would exist to delivery > the apps email, so I might look into doing that now unless I can see what's > up with this situation. > > I was able to deliver a message via WOMail at least once! HA! > > where else might I find more trace than the backtrace of the app? I can see > the line in the javamail where is fails if you want I can paste in more of > the exception trace... > > > On Dec 15, 2010, at 10:09 PM, John Larson wrote: > >> ERMailSender tells you if it has an authentication problem, so I don't think >> it is that. >> >> This is a stab in the dark, but if you're at your desk, maybe your ISP is >> blocking port 25. I have to do this in my Application didFinishLaunching: >> >> >> ERJavaMail.sharedInstance().defaultSession().getProperties().put("mail.smtp.port", >> "587"); >> >> Is that all the trace you're getting? >> >> On Dec 15, 2010, at 5:39 PM, Jesse Tayler wrote: >> >>> oh ya, it does but does that relate to the transport error here? I figured >>> that was some sort of admin work to be done but I wasn't sure. >>> >>> I figured I was just too tired to figure it and thought I'd look again >>> tomorrow. >>> >>> Does this error look familiar? >>> >>> On Dec 15, 2010, at 6:17 PM, D Tim Cummings wrote: >>> >>>> Does your Application class extend ERXApplication? >>>> >>>> >>>> On 16/12/2010, at 8:44 AM, Jesse Tayler wrote: >>>> >>>>> ack! yes, thanks - it works better when you actually use the ERJavaMail! >>>>> >>>>> now I just get a transport error, which seems less mysterious at least -- >>>>> >>>>> >>>>> >>>>> >>>>>> ERROR er.javamail.ERMailSender - Unable to connect to SMTP Transport. >>>> >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list ([email protected]) >>> Help/Unsubscribe/Update your Subscription: >>> http://lists.apple.com/mailman/options/webobjects-dev/the_larsons%40mac.com >>> >>> This email sent to [email protected] >> >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
