What SA ISP has a open relay SMTP server?

H

hgiddy

Active Member
Joined
Apr 28, 2009
Messages
38
Reaction score
0
Morning Guys

Quick one. I have a Webafrica ADSL line which works great bar some issues with SMTP, they are currently looking at the problem, but I need a urgent interim solution.

Is there a ISP which I can register a basic account with and use their SMTP server, from the WA ADSL line, IE Open Relay SMTP. I know most ISPs dont allow this at this point :confused:

Thanks
 
You can do that with most ISPs eg. Afrihost - your ADSL line provider/manager shouldn't make a difference.
Unless, rather than WA ADSL line, you mean from your WA ADSL account... in which case, none that I know of.
 
HI Guys

Thanks for the answers. I would love to use my ISPs - Webafricas, but for some reason it is only working sporadically, their engineer has been looking at it for a week but still has no answer.

Basically it is a time criticial server application which sends sms via email when a suspect enters a vehicle(Liscence plate recognition). So it doesnt help us to get the emails late and people need to respond in seconds


Just for interest sake the application was running fine at premises A, which was also a Webafrica DSL line and account, and we simply unplugged and move the server to Premises B, which has a different Webafrica account then is start only sending the email sporadically - Absolutely changed in respect of the server settings

Eish, my quest continues
Cheers
 
SauRoNZA said:
Use your mail provider's.

Simple really.
Click to expand...

this. if you can't relay then don't relay.
just use a third party smtp with auth.
if your script can't handle auth, then change your script.
are you sure it's a mail issue and not connectivity? what do the logs say?
 
Last edited:
Is this an application you are writing or is this an email client?
Regardless weather it is a client or an app,, use port 587. If you are coding, your intro must be EHLO MyDomain followed by AUTH LOGIN. LooserName and Assword must be Base64 encoded. If that doesn't work, I don't know what will.

I hope that helps.
 
Last edited:
Gandalf123 said:
Is this an application you are writing or is this an email client?
regardless weather it is a client or an app,, use port 587. If you are coding, your intro must be EHLO MyDomain followed by AUTH LOGIN. LooserName and Assword must be Base64 encoded. If that doesn't work, I don't know what will.

I hope that helps.
Click to expand...
It wouldn't even have helped 7 years ago (before you necroed the thread). Open Relay is basically a death sentence to all SMTP customers, ask any telkomsa.net customer what happens when their ASN gets blacklisted.
 
Gandalf123 said:
Is this an application you are writing or is this an email client?
Regardless weather it is a client or an app,, use port 587. If you are coding, your intro must be EHLO MyDomain followed by AUTH LOGIN. LooserName and Assword must be Base64 encoded. If that doesn't work, I don't know what will.

I hope that helps.
Click to expand...
Did Base64 exist in 2013?

sho this is a post from the past
 
RonSwanson said:
:laugh:I think that Base64 has been around a lot longer than that, we used it in the 90s for UUCP Usenet binary attachments, I suspect that it was conceived in the mid eighties...
Click to expand...
Yep. As old as my pants tree.
 
Unles I am wrong, and everything I know about SMTP protocol has changed since I last looked, Base64 was THEEEE encoding used in the past and present to encode username, pass and attachments to an SMTP server when using AUTH LOGIN in a plain text transaction. I know Base64 is as old of the hills and can be easily decoded, but that is what the SMTP expects in text and yes @RonSwanson, email is still transported in 7 bit format hence the use of anctient old base64 encoding :D

I don't claim to be an expert in SMTP protocol in any way or form, so I would be delighted to be corrected if am wrong. I have only developed a few SMTP clients in my career.

Damn, I thought that was a 2019 post, not 2009. Please excuse me for replying to a post over 11 years old! I seriously need to get myself some glasses :eek:
 
Last edited:
Gandalf123 said:
Unles I am wrong, and everything I know about SMTP protocol has changed since I last looked, Base64 was THEEEE encoding used in the past and present to encode username, pass and attachments to an SMTP server when using AUTH LOGIN in a plain text transaction. I know Base64 is as old of the hills and can be easily decoded, but that is what the SMTP expects in text and yes @RonSwanson, email is still transported in 7 bit format hence the use of anctient old base64 encoding :D

I don't claim to be an expert in SMTP protocol in any way or form, so I would be delighted to be corrected if am wrong. I have only developed a few SMTP clients in my career.

Damn, I thought that was a 2019 post, not 2009. Please excuse me for replying to a post over 11 years old! I seriously need to get myself some glasses :eek:
Click to expand...
OK David Harris :D
 
Found this:
stackoverflow.com

Content Transfer Encoding 7bit or 8 bit

While sending email content, it is required to set "Content Transfer Encoding" header. I observed many headers of emails that I received. Some emails using "7bit" and some are using "8bit". What i...
stackoverflow.com stackoverflow.com

I don't know the inner workings of SMTP though :)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X