PayPal IPN simulator "We're sorry, we could not send an IPN." - paypal-ipn

I'm getting this answer when trying to use PayPal's IPN Simulator ("We're sorry, we could not send an IPN").
I know there are all kinds of ways I could be doing something wrong on my end, but I think I have covered all of them by now. My callback works when I send a POST request with dummy transaction data myself, from a computer in a different network than my server is in. There appears to be no firewall/proxy/connectivity/topology issues, server is there, port is open, and yet the simulator does not send IPNs.
I'm NOT using HTTPS and my server is NOT listening on port 80, does the IPN service has any restrictions on either protocol or port? If not I really have no idea what might be wrong.
Thanks, any help will be greatly appreciated.

It looks like that the IPN simulator does not want to work on ports different than 80.
Also, you should check if you need to add additional headers like host (http 1.1) and connection close. I'm saying this because they are missing from the example script from paypal (PHP impl)

Related

Canvas not sending mails. Doubts regarding outgoing_mail.yml

I've recently installed Canvas LMS on a cloud server. Everything was ok, except for outgoing mails. I'm really new at this, and I don't know how it works. I would appreciate very much if someone could help me with some doubts...
1- What is correct?
a) address: smtp.gmail.com
b) address: "smtp.gmail.com"
Which data should be quoted in outgoing_mail.yml?
2- I've tried filling the fields with my personal gmail address info, but I receive a warning mail about suspicious activities. That means that Canvas actually tries to connect to my gmail account. That's a good sign! But even when I tell to gmail that I recognize this activity, it won't let me continue...
When I enter the Yahoo's smtp information, nothing happens... not even a warning mail...
3- I wanna know if I have to run "canvas_init restart" everytime I edit that configuration file. And "/etc/init.d/apache2 restart"?
I really need your help!! Many thanks in advance!!!

SAS (WPS) cannot send email via SMTP. See error code

I am using WPS, a diluted version of SAS, and I cannot send emails through the SMTP server using the normal (and fairly well documented) config flags.
I keep receiving the error message:
SSL exception: Could not initialise security context [80090322]
Having found some forum posts, the description for this issue is that the SMTP server is expecting authentication using a certificate. When I mentioned this to the IT team, nothing came from it. Having used SAS for a significant period, you would normally and quite simply apply some very basic information into the config file (see below).
I've been given the admin username and password, I've used an array of different ports, but still the same error message persists.
Does anyone have any ideas on how to make SAS/WPS connect to a secure SMTP? Config file is:
-emailsys SMTP
-emailhost 10.0.x.x
-emailport 23 (Port 23 was opened for my use, we are not able to use port 25).
The error message persists even if I force the credentials via -emailid and -emailpw.
Thanks in advance,
Dan
The fix for this is to utilise a fully qualified domain name, rather than an IP address or other method.
I know this is very old, but I had a really bad time trying to figure this same problem out and I'd like to post my solution here for people who might need it in the future.
Basically, this problem happens because SAS/WPS is trying to validate the certificate he has gotten from the smtp server when trying to interact with it (ie.: send an e-mail).
There are 2 solutions:
You can define the location were the trusted certificators are stored for the system to validate it.
You can define the server option TLS_HOSTVALIDATION to NONE by doing something like OPTIONS TLS_HOSTVALIDATION=NONE
I hope this helps.

Payflow Link silent post url

I have a silent post url set up. I know that my code for the silent post url works in that if i send a form with information to this url, it carries out the instructions I have set for it -- waiting to receive silent post from Paypal when someone makes a payment.
The customer for whom i am working has a separate processor - not Paypal. They use the Payflow link as a gateway only.
In spite of having the silent post url set up, we're not getting anything back from Paypal when someone makes a payment. Is it because Paypal is not the processor, or is there some other reason maybe?
Found out why it wasn't working. The host had shut of TLS 1.0 months ago. Paypal (and maybe other services) still uses TLS 1.0. Once the host was made aware of this, they set up a workaround for me. There wasn't any error message on my server because the messages sent from paypal never got through. The initial handshake that they tried to send via TLS 1.0 failed, so the rest of the information was never attempted.

IPN Simulator does not work on non .com first level domains

I'm trying to test using the IPN Simulator and can't get it to work with anything other than first level .com domain
Anything like
domain.co.uk or
subdomain.domain.com
is giving me errors. (We could not send an IPN due to an HTTP error.)
This makes it more difficult, as I'm obviously not going to be testing on my live domain.
Am I missing something?
Thanks,
Stevo
My website did not respond 200 on the POST request.
Only responded 200 on a GET request, which is all I tested. After fixing my web server, all seems fine

Anonymous SMTP Service

Does anyone know of a free, anonymous smtp service? I want to give users of my app the ability to occasionally send me an anon email without having to configure a server of enter their email account. I guess I could setup a gmail account for this purpose and embed the credentials in the app but I hope it won't be necessary. In case it sways your answer, this is a thick client (.NET Console) app.
I think that what you're asking for is called an open relay.
If there were such a thing, wouldn't it immediately be swamped by spammers?
You might be better off setting up some kind of commenting tool on your website, that sends you an email with the contents of whatever form the user submits. Then if you go that far, it shouldn't be difficult to add a form to your app that automatically makes the full HTTP request (transparent to the user, in the background).
If you run your own mail server, you can simply configure the app to deliver mail directly to it. Many web hosting companies also provide mail hosting if you don't want to run it on your own hardware. Gmail via Google Apps for your domain might be an option. It's free. But their anti-spam measures might prevent delivery. Better to have a server you can control, I think. Bottom line, though, is you don't need an anonymous SMTP relay server to get the job done.