In the last days I made a SMTP client in C language which connects over SSL to the SMTP-relay of my provider.
This works just fine, but now I do not understand how to receive an E-Mail.
I have a running linux-server where I want to store all Mail's which are adressed to my Domain.
Which 'service' is responsible for this?
POP3 services are responsible to recieve mails.
Related
I have use Outbound Message in salesforce. When the Trigger is Occur on the particular object outbound Message to pass particular End URL. here I want to receive the Outbound Message from the Mulesoft(EndPoint URL) . I have tried HTTP,UDP,TCP,Genric these Kind of endpoint URL but its not working. How i can Use the Mulesoft end point URL. by using Local host its possible or not. Because I have used Localhost:8081 this kind of URL only. what are all the way i have to receive salesforce outbound Message. Thanks
The target of the outbound message must be accessible from the web. It has to have some meaningful domain name or IP address (and if you're behind a firewall you need to allow messages from SF pool of IP addresses to pass through).
http://wiki.developerforce.com/page/Creating_an_Outbound_Messaging_Notification_Service_with_Eclipse_3.2#Testing_Your_Service
Testing can be a bit of a tricky wicket if you are not developing on a
machine that is accessible from the internet. Following the sample, we
have deployed our web service to localhost:8080. It is not possible
for the salesforce.com servers to make a request to that address.
Let's say we have several clients connected to App Engine using Channel API. Each client sends messages, which should be propagated to other conntected clients according to some rules. The tricky part is that clients may not be to the same App Engine instance.
Is there any way to push data from one instance to the others?
(Yes, I know about Memcache, but this would require some kind of polling.)
You're asking two questions here.
a. Can you push data from one instance to another without the use of polling. The answer is generally no.
b. Can one client send messages to the server that can be propagated to other clients? Yes, and this does not require propagating messages to other server-side instances.
Consider the Channel API as a service. Clients are connected to the Channel API service; they are not connected to any particular instance. Therefore any instance can send messages to any client.
You'll need to store the Channel tokens of your clients in the datastore, in some way that's queryable to match your rules.
Your client makes an HTTP request to send a message to your server.
The handler on the server queries for channel tokens that it needs to propagate the message to (either from memcache or datastore).
The handler on the server sends messages to all the clients.
If the list of destination clients is extremely large, you might want to do steps 3/4 in a task queue where the operation can run longer.
It does not matter what instance a client is connected to, that's hidden from you by the API.
Clients can only "reply" to message via standard HTTP commands, they don't actually have any way to respond via the channel API directly.
So Client A on server A1 wants to sent a message to client B on server B1.
Client A posts to a handler. That might be instance A1 or B1. It does not matter which as the server now passes the message on to client B whatever server client B is connected to via the Channel API.
The real point is that no App Engine instance has any data at all, in general. So it does not matter which instance you connect to, it might be the 99th instance or the very first to start up. So you have to design your application so that it's irrelevant what instance is in use.
Client sends message to server via HTTP.
Server sends message to N clients via the channel API.
Channel API does not make a fixed frontend-instance-to-client connection. Any frontend instance can push message to channel if it knows the channel ID.
What you need to do is pass messages cross-channel.
User one sends message normally to server (e.g. via GET)
Server looks up channel ID of second user and pushes the message
Repeat procedure in other direction: second user to first user.
I'm working on a project in which I'm trying to get Ozeki to send and receive SMS messages from my Nokia 3110 classic.I have also configured the inbound route,outbound route,GSM modem service provider and standard user correctly.Sending messages is working fine but not receiving them. Please give me some solutions to this.
Does your service provider definitely support inbound SMS from all other operators? SMS routing is notoriously tricky with many operators and gateway providers supporting only a selection of other providers.
Nokia phones work best with SMSEnabler not with ozekiNG.please start using SMSEnabler instead which uses http api to send and receive SMS like ozeki.I was having the same problem you can't help it.
I need one server to receive ip requests from clients(there are not in the same intranet), and I can
route all the response packets to a special gateway server, and then I send the response packages to
clients after some processing. it is like VPN, but I want to do some development based one
opensource project, so i can control it myself.
any suggestion? thanks!
There is OpenVPN which is as the name already suggests open source.
You could set up the server on the local one as a kind of proxy (or reverse-proxy depending on your viewpoint) and have the clients connect to it.
It depends what protocol you're using, maybe it has explicit proxy capability or you can get an existing proxy program, or just proxy it using a simple socket forwarder program.
I am trying to figure out how to handle authentication and data for client applications who will connect to eachother. In other words, each client app would authenticate to.. and use a central service to find out info about the other client so that they can connect directly. Specifically, what should I deploy to accomplish this and maintain security and privacy?
One way to implement this would be via ssl. Let us assume you have a client A that wishes to talk to client B via a central server C. Client A will first connect to C via SSL & will request info about client B. C will furnish B's info & will also send an encryption key over SSL for A to communicate with B. B will also perodically check with C over ssl for any communication requests from other clients. If there is any, it will download the respective key from C again via ssl. Now A can directly communicate with B using the downloaded encryption key from C. This gives both privacy and security for client communications.