To automatically generate the davmail64.ini file during installation in the absence of any environmental setup by Java-64, the DavMail installer would have to go searching for the 64-bit jvm.dll in "C:\Program Files\Java". The 32-bit Java installer does - it adds "C:\Program Files (x86)\Common Files\Oracle\Java\javapath" to the "Path" variable, and "javapath" is maintained as a shortcut to the directory containing the actual version installed. I thought leaving the port open to the world could be a slight risk, so limiting to just the domain of my 3G provider would at least block out the majority of baddies.From what I can gather, the 64-bit Java installer doesn't add anything to the environment that would allow DavMail to pick up the path to the jvm.dll file. The second point isn't as crucial as the first - basically what I was thinking was that if DavMail is running at my home always, and I expose the open ports via my router, than when I am away from on my 3G card I can still use my home DavMail installation. So now the two issues I am trying to solve are:ġ) How to set DavMail up as a user other than rootĢ) How to restrict access to the ports DavMail runs In my search for a method to access the OWA account via Thunderbird or a similar app, I discovered DavMail - it "wraps" Outlook Web Access into SMTP, IMAP, POP, and CalDav - tested it as root locally, works great! Because of this, when outside of the office I can only access my work email via Outlook Web Access (OWA) - which is quite frustrating as a number of essential features only work if you use Internet Explorer. My work email account is only accessible via Microsoft Exchange server. I'll explain the whole story in order to make sure we're all on the same page: If DavMail doesn't come with an init script, you can write one yourself, but at that point, I'd be looking at an alternatives like Postfix, which work quite well on Ubuntu. If DavMail comes with such a script, you can configure it to start at boot and stop at shutdown using the update-rc.d tool in Ubuntu. Most servers that are designed to run in the background as a daemon come packaged with a startup/shutdown script that gets installed to the /etc/init.d directory. There's also a GUI you can install called gufw, although I haven't used that. This can be configured via the Uncomplicated Firewall (ufw) tool in Ubuntu. For example, you could allow connections only from machines with IP addresses like .y. Rather than restricting by domain, which requires reverse-name lookups, it may be more efficient and robust to restrict it by subnet. Is this possible? How do I go about doing this? ()Ģ) Because I have a dynamic IP, I want to restrict access to the mail forwarding ports by Domain rather than IP. ![]() What's the best method to do this, ensuring it runs under the correct user privileges? ![]() You would simply use dynamic dns services to give yourself a domain name.ģ) I want to run the server on startup automatically. Most ISPs in my exerience block such issues.Īs for the issue. You might actually have troubles running a mail service at all. Is this possible? How do I go about doing this?ĭynamically external? or dynamic internal? If internal. ) Because I have a dynamic IP, I want to restrict access to the mail forwarding ports by Domain rather than IP. Honestly I probably wouldnt go with davmail. I'm thinking this is probably not correct? Who should it be run under, and how to I enable appropriate permissions to enable them to run it?ĭoesnt sound right. 1) I have the server installed (DavMail), but I can only run it as root.
0 Comments
Leave a Reply. |