AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: Falcon on March 08, 2009, 08:06:46 PM
-
Hello,
I have spent a fair amount of time now trying to get the e-mail reports to work, which by the way is a very desirable feature.
Is port 25 required to be open by the ISP for RB 2009 to send e-mail reports and alerts? It certainly appears so.
If so, where are the settings to change to an alternate port. I am in Canada and most major ISP's block this port, one of them being mine.
It would be almost ludicrous to think that there would not be an option available for the e-mail reports and alerts to work on a different mail server port, especially in North America.
I hope someone can provide a solution to this, or there is one forthcoming very shortly.
I am quite annoyed about this as it just seems like a big oversight on someones part to not have an alternate port available given the fact that ISP's close this port on a regular basis to help prevent spam.
Thanks,
Darryl
-
There isn't a way round it I am afraid. The software needs to connect to our server which has been set as port 25 so even if you could change the port number it would not help. In theory what you would need is another mail server or a mail server built into RB (which again can get blocked).
Most ISPs do not block ports, there is only a few which do.
-
There isn't a way round it I am afraid. The software needs to connect to our server which has been set as port 25 so even if you could change the port number it would not help. In theory what you would need is another mail server or a mail server built into RB (which again can get blocked).
Most ISPs do not block ports, there is only a few which do.
I suggest someone sits down and gets busy writing the code to use an alternate mail port. This is completely unacceptable. I am not sure where you are getting your information from, but Port 25 is blocked by a large number of ISP's and if you want your market share to grow I would be changing your mindset very quickly. Set your servers to use another alternate port and get it programmed into RB.
I won't be letting this one go and I hope other North American users will be quick to speak up.
Take a look at Shaw Communications and Telus which are major ISP's in Western Canada. They both block port 25, but hey, what's half of Canada.
Thanks
-
So far Falcon this issue has been raised by another 2 users out of the 2,000+ we have sold.
Thats not to say it won't be done however our list of priorities has others which affect more users and more important to functionality. Once they are done we hope to get round to this.
-
Why are ISP's blocking the passage of Traffic for Port 25 on IP addresses that are NOT theirs.
This seems to prevent you from using Mail systems of other ISP's while being connected to These Service Providers.
This is Unacceprable to many Big Businesses who have International Travelling employees.
I suggest that you tell your ISP to prevent inbound traffic ti their servers on Port 25 but allow the traffic for other remote IP's to flow.
-
So far Falcon this issue has been raised by another 2 users out of the 2,000+ we have sold.
Thats not to say it won't be done however our list of priorities has others which affect more users and more important to functionality. Once they are done we hope to get round to this.
I can understand benefiting the masses, but it is an advertised feature and your ignoring a weakness in the way your e-mail system works as far as even reasonable compatibility goes. Unfortunately for you, with ISP's serving hundreds of thousands of customers vs 2000 (which even with this issue, I hope your sales continue to grow) its going to be up to the developer to take care of this.
What concerns me now is what else am I going to run up against as far as compatibility goes and support for those issues. If being in another country is going to leave me in the minority and not have the benefit of being part of the masses, maybe I need to reconsider my purchase before it's too late to do something about it.
I do appreciate your prompt responses to my post which are much quicker than I expected. Your product has lots of pluses going for it, in fact its just plain cool, but I can't shake the feeling that this issue over the very desirable feature of reports and alerts should have been addressed by now, or at least in the very near future, considering how long ago some others had this issue. The port 25 issue has been a very common and known issue for the past few years, at least in North America.
-
Falcon,
The adversited feature is there and does work. Obviously there are lots of firewall software out there etc.. which is designed to block ports etc. We can't be blamed for that if they block it. I know your trying your hardest to puch this through (others have tried it with there requests).
However it simply comes down to how many customers are affected, and as mentioned earlier it was only one customer affected untill recentely we had another mention and now you. It is on the books though you need to understand there are other pressing issues.
You won't have any other issues being another country, infact this issue can occur anywhere across the word, it just depends on how strict your ISP is.
-
It is on the books though you need to understand there are other pressing issues.
I can only imagine the amount of work you are doing on this unique (and cool) product, and you also know where I stand on this issue.
You won't have any other issues being another country, in fact this issue can occur anywhere across the word, it just depends on how strict your ISP is.
True it can happen anywhere, but you would have had a great deal more complaints over this if you had more customers in my part of the world so there is a difference as to what ISP's in different parts of the world are implementing the port 25 blocking and there are some big ones.
-
I am in Eastern Canada using Rogers Communications, a major comms company across Canada. I dont know if this Port 25 thing is the same reason, but trying to send Reports has never worked for me either. When clicking on the Button, nothing happens - no error message returned, nada. To send a Report I go to the Desktop, find the C Files, select LOG file, right click on the saved report and use the Send To option which does work.
GeoT
-
I'm in Ontario, Canada on the Vianet/Efni network. I've been a RadarBox owner since July 2007 and I have never, ever been able to use the e-mail function. I've tried everything and nothing works. I've worked with my internet provider and Airnav Support and nothing has ever worked. I've asked Airnav Development Team to put a config box in their next version release hoping that will help. Maybe after 2 years with no e-mail function it might happen. Can the Airnav Dev Team write a small script for us Canadians that can't connect to server? Something? Anything? It amazes me that my Acarsd connects and e-mails with no problems and RadarBox does not. For that matter I have never had a problem with any other e-mail function or program whatsoever. I use Outlook. I've tried others including web based such as gmail and yahoo and nothing works with RadarBox.
Paul@cyyb
Can other Canadian users please check the e-mail function and post their results here. I'm glad I'm no longer that 'lone voice in the wind."
-
Hi people
In my opinion there is no one ISP in the world bloking port 25.
Actually blocking port 25 is a recognised anti-spam technique and used extensively in North America and is recommended to ISPs by the Messaging Anti-Abuse Working Group. I think Earthlink were among the first in 2000 and it became increasingly common after myDoom in 2004
-
Hi Juan, I'm not very technical but telneting mail.frontiernet.net 25 gives a 220 response and their website states
Due to an increase of complaints about spam (Internet junk mail) and computer viruses sent via outgoing e-mail messages, as of December 3, 2003, Frontier has blocked all port 25 traffic over our network from Frontier High Speed Internet customers (with dynamic IPs) that is not sent through Frontier outgoing mail servers (smtp.frontiernet.net)
-
Hi Keit L
What I can see in my case is what I wrote and did prove it
Can You prove that telnetting port 25 of an SMTP server from sone ISP the connection is rejected ?
I think that this will only happen if ISP put a specific rule of rejecting connections from one IP or one network, and this indeed can happen, but never rejecting all the connections.
Cheers
Hello,
While I appreciate your comments, the information you are providing on this particular issue is not correct, and you are diverting this thread from the acknowledged issue. If port 25 is blocked by your ISP, RB2009 will not send messages and yes I can prove it by trying to Telnet which is what I did before I even made my first post about this issue. Once again thanks for the input but the fact is port 25 is blocked and RB2009 will not send e-mails from mine and most likely others computers because of it.
-
There isn't a way round it I am afraid. The software needs to connect to our server which has been set as port 25 so even if you could change the port number it would not help.
That needn't be the case.
All RB installations can successfully connect to the RB server to upload and download network traffic, so there is absolutely no reason why you can't incorporate another protocol into RB which will pass the alert data to a process on your network server which will then generate an email.
There is no reason why RB itself needs to be configured as an SMTP client, and clearly this doesn't work for at least some users, due to circumstances beyond their control.
They are entitled to a more helpful response than simply "tough luck".
-
We haven't said "tough luck". We said it will be looked at, however more pressing issues ahead.
We are being honest so that in the next update if its not included we don't get emails saying you promised us etc..
-
Hi falcon,
I believe that You cannot connect to server at port 25, but this can be due to seval reasons. Also I suppose that this SMTP is from Your ISP ?
Coul You please post the name of the SMTP server You telneted to port 25 ?
Mine is smtp.sao.terra.com.br and You can try telnettig it ao port 25, here is connecting OK
Cheers.
Hi,
I have tried to connect to both the server you provided and also the Airnav mail server using "telnet mail.airnavsystems.com 25" without the quotes and it fails. I am only replying to this to help satisfy your determination in getting this solved. It also fails with the address you provided on port 25. I know you are trying to get this figured out, but unless you have a way to bypass port 25 blocking by the ISP you are wasting your time. AirNav Systems knows about the issue and acknowledged it so until there is a way to configure use of a different smtp port we are going nowhere with this.
Thanks
-
We haven't said "tough luck". We said it will be looked at, however more pressing issues ahead.
Then I guess we will simply have to agree to differ.
IMHO, as with other issues like the callsign bug, getting existing features to work reliably (for everyone) should be at least as high a priority as developing new functionality.
According to www.postcastserver.com/help/Port_25_Blocking.aspx, the following ISPs are known to block port 25:
AT&T
BellSouth
CableOne
Charter
Comcast ATTBI
Cox
EarthLink
Flashnet
MSN
MediaOne
MindSpring
NetZero
People PC
Sprynet
Sympatico.ca
Verio
Verizon
Although not listed, AOL do too: http://postmaster.aol.com/faq/port25faq.html
Given the above, I'd suggest that developing a solution is indeed a "pressing issue".
And if you insist on using SMTP, why not support port 587, the industry-standard default port for authenticated email ?
-
Hi ,
E-mail Reports/Alerts never worked for me .
My ISP ( Belgacom/Skynet ) is indeed blocking Port25.
http://onlinesupport-res-en.custhelp.com/cgi-bin/onlinesupport_res_en.cfg/php/enduser/std_adp.php?p_faqid=5795&p_created=1069159709&l0_self=private&p_search_text=port-25
Rgds
Dan.
-
Don't forget that when you created the logon and account on the Airnav Servers, they allocated YOU an email address within their domain.
Why not use that as your origin address for the reports.
-
Not sure what you mean jgrloit. What logon is created, we don't allocate any email address for you within our domain?
-
When first creating the login code the messages I received did say that an email address was associated with the account code - the one required for running the software.
The message at the time - 9 months ago did mention the creation of an email account.
It could have been "wrong use of english terms" or phrasing.
It may be a similar problem to the messages ref - time credit for uploading data!!!!!
-
Tools - Network Account Information informs me:
User email **ANRB123456
Doesn't appear to work though :-}
-
Also....
If someone having problems on sending receiving email reports due to the above reasons, You can do the following for testing purposes :
1- Go to : File, Preferences Home Station Data
2- Change the email for [email protected]
3- OK
4- Go to Reporter, generate, SEND NOW
I did this and my SMTP ISP server liked a lot because email received was from airnavsystems.com and the user ([email protected]) from the same domain.
Properties of data on email received sent in this way :
Received-SPF: pass (dresden.terra.com: domain of airnavsystems.com designates 74.55.96.226
as permitted sender) client-ip=74.55.96.226;
[email protected]; helo=mail.airnavsystems.com;
Received: from mail.airnavsystems.com (mail.airnavsystems.com [74.55.96.226])
by dresden.terra.com (Postfix) with ESMTP id 51C6A7000009F
for <[email protected]>; Tue, 10 Mar 2009 10:52:01 +0000 (UTC)
Received: from home07 by mail.airnavsystems.com (Merak 8.3.8) with ASMTP id
So, who never got email report working but receives a message on RadarBox :
Message Sent With seccess, can try this... ONLY for testing purpose....
Cheers.
Ok so I did as you suggested and I still get the same notice that has been haunting me since July 2007
"Could not connect to SMTP server to send auto-report"
Paul@cyyb
-
Its either a username or email to login. Its got nothing to do with email accounts being created.
-
Ok so I did as you suggested and I still get the same notice that has been haunting me since July 2007
"Could not connect to SMTP server to send auto-report"
Paul@cyyb
Hi,
As determined as Juangelb is too help, which is appreciative, the original issue as I have discussed and which has also been acknowledged by AirNav Systems remains. You won't be connecting until the way the e-mail reports / alerts function is changed if Port 25 is blocked by your ISP.
If you really want to prove your port 25 is blocked just try this simple test. Which you have probably already done but I'm just making sure.
"telnet mail.airnavsystems.com 25"
If your connection fails which you can determine by waiting up to several seconds for windows to notify you or, even if you don't want to wait for the failure notice, if it doesn't connect almost right away it probably isn't going to.
You can then do this as the final part of the test.
"telnet mail.airnavsystems.com 465"
If you are doing things correctly and your port 465 isn't blocked by the ISP you will get an almost immediate connection indicated by your screen going blank. This of course is assuming that port 465 is still open by the time you read this. I don't know why it wouldn't be but if they (AirNav or the ISP) decide to close it for some reason then this test won't work.
-
You can then do this as the final part of the test.
"telnet mail.airnavsystems.com 465"
If you are doing things correctly and your port 465 isn't blocked by the ISP you will get an almost immediate connection indicated by your screen going blank. This of course is assuming that port 465 is still open by the time you read this. I don't know why it wouldn't be but if they (AirNav or the ISP) decide to close it for some reason then this test won't work.
A simpler, and more reliable test would be "Telnet [any website URL] 80", for example Telnet www.bbc.co.uk 80. That will also produce the requisite blank screen to show you're connected, and it's reasonably safe to assume that the BBC won't have shut down all their web servers in the meantime :-)
-
A simpler, and more reliable test would be "Telnet [any website URL] 80", for example Telnet www.bbc.co.uk 80. That will also produce the requisite blank screen to show you're connected, and it's reasonably safe to assume that the BBC won't have shut down all their web servers in the meantime :-)
Yes, thanks Dave. That would be a more reliable method for testing to make sure you can actually make a valid connection with your telnet client without worrying too much whether the ports going to be open or not.
Just remember for those doing the test that you still have to connect to a mail server with a known open port 25 in this case "telnet mail.airnavsystems.com 25" without the quotes to check if your ISP is blocking port 25. The "telnet [any website URL] 80" without quotes or brackets has to do whether you can actually make a connection with your telnet client at all.
-
Thanks for your help Dave and Falcon.
Below is the response I get when I telnet mail.airnavsystems.com 25 and
telnet mail.airnavsystems.com 465
When I telnet www.efni.com 80 I connect no problem.
Paul@cyyb
-
Thanks for your help Dave and Falcon.
Below is the response I get when I telnet mail.airnavsystems.com 25 and
telnet mail.airnavsystems.com 465
When I telnet www.efni.com 80 I connect no problem.
Paul@cyyb
Hi Paul,
So there you go. Your port 25 is confirmed blocked. Who is your ISP and how long ago did you first post about your e-mail reports / alerts not working.
Darryl
-
Hi Paul,
So there you go. Your port 25 is confirmed blocked. Who is your ISP and how long ago did you first post about your e-mail reports / alerts not working?
Darryl
[/quote]
Hi Darryl
My ISP is Vianet and I first reported this problem back in July 2007. I thought all this time I was the only one on the planet that had this problem.
Pau@cyyb
-
Deer prbflight
If You receive : "Could not connect to SMTP server to send auto-report"
When trying to send report, this does mean that Radarbox was not able to connect to mail.airnavsystems.com server.
This normally is due some antivirus or other kind os protecting software, not allowing RadarBox to open a connection to port 25.
So Your case is worst than ours... we can connect, send but we die at the beach.... You die just when falling in the wather.
Cheers
Hi juangelb
I have gone as far as un-installing my anit-virus (Norton) and that didn't work...same message. I installed Win XP on a new computer - bare bones nothing but Win XP and RadarBox - still no joy. I installed Radarbox on my wifes laptop...no joy. I bypassed my router...no joy. I installed Radarbox on my new laptop running Vista...no joy. Always the same message "Could not connect to the SMTP server to send auto-report". Yet still, I have absolutely no problems, ever with any other application sending e-mail. Not even "Acarsd" which is a free application but does have a config box. I spent nearly $1000 for RadarBox and the e-mail feature has never worked. Yes I'm frustrated. I see on "the othe new forum" that the list of to-do's does not even include this fix in the top five or six items. Yes I'm frustrated but the fact that I've been a loyal Airnav customer sinnce 2003 and own most of their products keeps a spark alive that I will be heard and it will be fixed.
Cheers
Paul@cyyb
-
Airnav
Can you explain why the software must connect to your mail server please?
If it is a simple email format without requiring any processing at your end the simplest fix would be to allow the user to configure it to use their own smtp server, whether on their machine or at their ISP, together with allowing configuration of port number and use of SSL/TLS.
It is understandable that, particularly on connections with dynamic IP addresses, the ISP blocks port 25, or possibly transparently redirects it for anti-spam reasons.
-
For You to be able to send emails, you are using OUTGOING connectios !!!!!
And this obviously is not blocked !!!!!
Unless you are a customer of AOL, AT&T , BellSouth, CableOne, Charter , Comcast ATTBI, Cox, EarthLink, Flashnet, MSN, MediaOne, MindSpring, NetZero, People PC, Sprynet, Sympatico.ca, Verio, Verizon, etc, etc.
Don't you understand that ?
-
I suppose that You are a user of one of the list above.
If so, can You please post or email me the name of one SMTP server ?
No, I'm not a customer of any of those ISPs.
But you are still missing the point. An AOL customer, for example, can connect to AOL's mail server on Port 25. But they can't connect via AOL to anyone else's mail server (such as AirNav's).
See http://postmaster.aol.com/faq/port25faq.html
-
But.... what I can do if even showing all this to You, You do not believe in ?
Hello,
Based on your replies to this matter it is clear that you have some issues in accepting port 25 blocking by ISP's, and the way it affects the use of the Radarbox software. I ask you to please refrain from stretching and distorting the facts of this thread any further unless you have something truly worthwhile to add.
5- If RadarBox would let each user to select, for instance "Use outlook configuretion", or even let each user to configure whatever he wants...
I think that this problem will end .
Hold on a minute. I did find one thing that you said was close to a solution, in the quote you see directly above, but then you leave it and go on with more posts that once again proves little or no help.
Thank-you
-
But also the correct (to opposite side) it wold be more correct to say "ISPs only allow to connect to his servers at port 25, if connection is iniciated from inside his own networks" instead of "ISPs are blockin...... bla bla bla... bullshit"
You don't help your case by simply ignoring facts that don't fit your argument.
ISPs blocking Port 25 isn't rubbish - AOL is a good example of one who does it.
But don't take my word for it - take AOL's: http://postmaster.aol.com/faq/port25faq.html
"Members of America Online will not be able to connect to 3rd party mail servers using port 25."
-
I am so sorry if in some way I offended You or somene else.
I so, My apologises. Best regards. Juan
Hello Juan,
I believe you are trying to help, which I have stated before. I don't want to offend you but my patience got a little thin. You acknowledged a possible fix in point 5 in one of your last posts and then continued on which in my opinion based on the information that has already been provided by myself and others, totally unnecessary. AirNav has acknowledged this situation. There is enough information in this thread for individuals to conclude whether there port 25 is blocked and reading your posts just seems to have confused the issue on more than one occassion.
Regards,
Darryl
-
Can we keep the language in check please as well, we have had to edit two posts.
-
Reading this forum used to be a pleasure with no hint of unpleasantness only the desire to help a colleague in need of help or explanation . I know the world is going mad but lets all try to rise above it and conduct exchanges of information on our great hobby with some compassion ;always remembering that difficulties with other languages etc often lead to people not expressing themselves correctly or not grasping the explanations as quickly as may be desired. Come on guys, lighten up!
-
Come on guys, lighten up!
I thought it was light :-) No bad feelings here. I guess I should just find a few dozen more ways to get my point across. You know what they say, "patience is a virtue".
-
Hi all
I never intended to do any kind of confusiom but it seems that I did it.
So I am so sorry, my apologyses.
Tu reduce the confusion, I judged better to delete my posts here.
Best Ragards - Juan Gelb - MCSE Systems Engenneer - Cisco CCNA - SCO ACE
-
Hi all
I never intended to do any kind of confusiom but it seems that I did it.
So I am so sorry, my apologyses.
Tu reduce the confusion, I judged better to delete my posts here.
Best Ragards - Juan Gelb - MCSE Systems Engenneer - Cisco CCNA - SCO ACE
Well that's a shame Juan,
I have always found your posts interesting & informative so keep 'em coming...
I wondered why, when I read this thread I saw references to your posts being quoted but never a whole post from you...
When I changed from Pipex to O2 I found my email alert function stopped working.
On further investigation I found that my ISP does not block Port 25 per se but merely prevents UNAUTHORISED emails going through their gateway.
When you think about this it is obvious - it is there to prevent an unauthorised person sending what would amount to spam unchecked through the ISP.
Now if Airnav - instead of starting out as they usually do and say 'This only affects 1 out of 2000 users' (do you have any idea know how this makes us users feel about you and your product?) took the time to look a little further they would realise that by embedding a mini-SMTP server in their software that would nip the problem in the bud and allow us to send the email to wherever we wanted to.
I use many programs - WHS Add-Ins for example probably coded in a bedroom during school holidays that have no issue sending emails to anywhere due to the simple fact that allow the user to input username/password/server and even Port number information so they authenticate and then send the AUTHORISED email.
See attached screenshot for a free WHS Add-In where the entire size of the installation package is only 59KB for example.
This also allows for configuring to send SMS text messages.
I could put you in touch with the Author if that would help?
Falcon...ISTR saying in a previous thread that I feel your pain about the freezing menu/window issues and here I am suffering the same issue again.
I would pm you but I am unable to access your profile...I also wanted to drop Juan a pm also about the UBox(es) he uses...:-(
Regards,
-=Glyn=-
-
Update: whoever runs across this topic again...
From AirNav Development on this topic.
"This is totally corrected and tested for V2.10. Just wait a few more days."
Topic: SMTP Blocked By ISP
http://www.airnavsystems.com/forum/index.php?topic=2706.0