Thanks Sergey.
We might consider this as an alternate solution.
/Ludwig

-----Ursprungligt meddelande-----
Från: USHAKOV, Sergey [mailto:[email protected]] 
Skickat: den 3 april 2011 06:51
Till: James Users List
Ämne: Re: Is James for us?

Hi Ludwig, sorry if going offtopic :)

If your problem is just in SMTP connectivity between different locations,
then you might consider using some VPN...

Myself being a moderately frequent traveler, I have faced the problem of
sending email with port 25 blocked by ISP many times. Finally I've got the
problem solved with VPN configured to tunnel into my corporate LAN. OpenVPN
does the job pretty well, especially with HTTP proxy feature enabled...

Regards,
Sergey



----- Original Message -----
From: "Eric Charles" <[email protected]>
To: "James Users List" <[email protected]>
Sent: Friday, April 01, 2011 2:37 PM
Subject: Re: Is James for us?


> Hi,
>
> You can find information to embed 2.3 in tomcat on 
> http://wiki.apache.org/james/Embedded.
> I successfully used that some time ago.
>
> The 3.0 trunk (unstable) has a generated war that you can simply drop in 
> tomcat (easier).
>
> Tks,
> - Eric
>
> Side note: I was fan to embed servers in web containers, but now I prefer 
> to have all servers separated. If any interaction is need between the 
> container and the mail server, I use JMX for that.
>
>
> On 1/04/2011 10:36, Ludwig Magnusson wrote:
>> Hi!
>>
>> We are considering using james in our project but after having looked
>> through the documentation I haven't really understood if what we want to 
>> do
>> is possible or how to do it.
>>
>>
>>
>> This is our situation:
>>
>> We have a webapp that is running on several different machines. A 
>> production
>> server, a staging server and all local servers that are used during
>> development. The problem is that sending mail through our webapp does not
>> always work because the smtp server at our production server does not 
>> accept
>> mail from certain locations. Sometimes we are at the mercy of different 
>> ISPs
>> that sometimes block mail going out.
>>
>>
>>
>> We thougt a good solution would be to bundle the james-smtp server with 
>> our
>> webapp. When we start our webapp, we also start the james smtp-server and
>> send mail through that one. In that case, we would always have a working
>> mail server and the app would be less platform-dependent.
>>
>>
>>
>> I have searched the james documentation but I am having a hard time 
>> finding
>> information about this. I looked in the javadoc for version 2.3 and found

>> a
>> SMTPServer class but that one seems to be missing in version 3. And 
>> version
>> 2 does not seem to be available in the maven repository.
>>
>>
>>
>> Could anyone point me in the right direction? =)
>>
>> Thanks
>>
>> /Ludwig
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to