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]
