There is a Websphere liberty server (linux) and I'm planning to configure outlook mails on that server for triggering a script upon receiving a specific type of email.
How can we make this possible?
Based on your description, I could see doing this at least two ways. You could consider using a Outlook script rule. If that won't work, you'll have to write an application that runs on Liberty, connects to Outlook and checks for new mail. If found, you'll have to parse the mail to determine if it meets your criteria and if so, invoke your script.
Related
I have a question about my application built in Oracle APEX 4.2. This application has a process to send emails (when a user changes his password or requests a password reset).
When I run this application online on my "apex.oracle.com" account, it runs fine. But when I run it on my home computer (running Windows 7), the email process doesn't work. Probably it is because my home server is not an email server.
Can someone please help me so that my home computer is able to send emails via my above mentioned application?
Thanks in advance.
you have several options:
Configure a local SMTP server so it can be use by APEX and send emails.
Connect to a remote server - like Google - and sends emails that way (you have to open a new account and connect with that and also there's some certificate problems, https://arkatec.wordpress.com/2011/08/15/sending-email-using-oracle-database-and-google-mail-service/)
Use htmldb_mail package (I haven't tried this one)
In the first options you need to construct a procedure that does all the work for you.
You can use one of this:
http://www.orafaq.com/wiki/Send_mail_from_PL/SQL
Important: keep in my that you're going to encounter permission issues with the UTL packages (grant execute on UTL_XXX to USER) and algo, if you're are working on 11g you need to create an ACL
Basically I want a lightweight CalDav server proxy, which passes the username, password and calendar name to a script and it will respond with either invalid user/pass, no such calendar or return the calendar.
The CalDav server would then return the appropriate response back to the server.
I will only have the calendars of the users stored locally on the server for caching purposes as I don't directly access to the users calendars. My script will try to login to an external site (out of my control in any way) and fetch the calendar by crawling the site.
If possible I would prefer if the server has wsgi support for communicating with my script.
I think your best bet here is to use sabre/dav and write a custom backend for it. As an example, at a company I used to work for I wrote a MongoDB backend for SabreDAV as well as getting the list of calendars from the system it was connected to. This is very similar to your use case, therefore check out this repository. You can find the backend implementation here and will need a lot of the other code to make the calendar listings work.
I would advise to do some caching and not scrape the remote site on each request, since caldav in connection with webdav-sync will want to provide updates since the last time the client synchronized, and that will be harder to do if you are scraping in the moment.
I want to send an email if the build fails to the developers, with the fail details. I'm also wants to send a success email to the project admins, etc with the address to the new test application.
What is the proper tool to send the actual mail, TeamCity or NAnt?
You could use Nant to send email, but TeamCity is more appropriate, as it can provide a centralized place for notifications, including emails.
(source: jetbrains.net)
TeamCity provides a wide range of notification possibilities to keep developers informed about the status of their projects.
Notifications can be sent by:
e-mail,
Jabber/XMPP instant messages or
can be displayed in the IDE (with the help of TeamCity plugins) or
the Windows system tray (using TeamCity Windows tray notifier).
Each user can select the events to receive notifications for on My Settings And Tools page. The notification messages can be customized globally on per-server basis.
So it is not just about how to send the mail, but also how to manage the notification process, from the server and from the client perspective.
I'm Creating a workflow that needs to send the users an email on set events. This I don't have a problem with. However can someone please confirm if you need the local windows SMTP service installed or if I can use another method for it to send the emails.
UPDATE
Ok I've just read about the E-mail Router, just need to find out where it is, and how to get to the configuration settings.
UPDATE
Update 2
Right, Iv'e looked into it and the e-mail router configuration is not used on this CRM set-up, it used an Outlook Add-in which I cant find a lot of into on.
However it appears to work flawlessly.
end update 2
Thanks
AFAIK, Microsoft CRM uses Exchange server to send out emails. Haven't you configured this during setup?
You are right that the Email Router is the way to enable outbound emails from Dynamics CRM. If you haven't done so already, I strongly encourage you to download the Dynamics CRM Implementation Guide. You can jump right to the section called "Planning e-mail integration" to read about it.
What you need to do is configure the e-mail router to operate with a POP3/SMTP server. You can use Windows Server's SMTP service for that. You can use almost any service - i have configured it to work with my gmail account, for instance.
Here are three good articles that you can read to learn more about the e-mail router.
What's New in Microsoft Dynamics CRM 4.0 E-Mail Integration
Dynamics CRM 4.0 E-mail Integration Overview
Microsoft Dynamics CRM: How to configure the On-premise and Online E-mail Router in different deployment scenarios
Now when you configure an email from a workflow, CRM will automatically forward it out through the router to your SMTP email account.
It looks like there are at least two options, one which uses the SMTP or exchange. And another which is an outlook plugin. Which syncs the emails with the owners outlook and then sends out the emails.
EDIT
So the two options which both work are:
Email Router - This appears to be the standard and can use various email servers
Outlook add-in - This sends email based on the owner/email settings in the CRM record.
This works with any email CRM wants to send, and even works with workflows.
I've not got to the bottom of why the outlook add-in has been used at this site, however the workflow functions appear to run without problem, and seamlessly to the owner/user.
end edit
I am working on .net applicaton that need to send emails to clients. I am trying to figure out what would be that best solution to send emails. Here is what i have considered. Could you please suggest what would be the best way to go for?
1>Windows server 2008 in built smtp
service.
2>Exchange server hosted in our
datacenter.
3>Use google apps for sending
emails(Basically same as gmail like
for custom domain).
I have explored all options and below are findings.
1>I think would be way to go. Also
supports drop in directory to send
emails so can achieve disconnected
email activity.
2>Application would be tied up with
availability of exchange server and
we dont have any exchange server
support personal. Only developers
poke around in exchange server and
got it working. So if option 1 is as
good as 2 then would like to go with 1.
Is there any drop in directory feature in exchange server like 1?
3>Tried gmail smtp stuff didnt
work. I was receiving timeout error.
Also there is no guarantee that
gmail will send our mail
reliability. They can decide anytime
to stop sending our mails as we are
using free standard version of
google apps.
Other questions:
I installed smtp service in windows server 2008. Now to use this do i need to change any MX record and anything? What i need to do so it can send email using my domain name. Or it can send email for any domain?
I would use a hybrid of 1 and 2. Use local SMTP, but have it relay to your exchange server. Emails will queue if it can't relay to exchange and you have one server(s) that handle all of your outgoing/incoming mail. This support doc explains this setup: http://support.microsoft.com/kb/303734
You only need an MX record if you'll be receiving mail from that domain too.
I would also put in a reverse DNS entry for your domain, which will help with spam detection.