Serious problems in the FreeBSD version of cPanel
There are 2 serious problems that have to be adressed with the FreeBSD version of cPanel.
1. The FTP accounts from within cPanel is broken, see http://forums.cpanel.net/showthread....55&perpage=15& for more detauls on that.
2. The SMTP problem where the SMTP server replies with "535 Incorrect authentication data"
Both problems happen on the server i admin, and the server my friends admins. Basically i would like this fixed, we have allready lost 2 customers because of this.
X-Istence
I guess this is then not serious enough to be taking serious here. Where can i submit bugs for cPanel?
Last edited by X-Istencedotcom; 04-15-2003 at 02:12 PM.
It sounds to me like your smtp server itself is configured incorrectly. The message you gave suggests that you have outgoing authentication setup, and maybe you shouldn't. If you do, then you need to make sure the e-mail client is setup to do outgoing authentication for smtp (most programs like Outlook Express do this).
As far as the first problem, I have no clue on that.
Originally posted by jrehmer
It sounds to me like your smtp server itself is configured incorrectly. The message you gave suggests that you have outgoing authentication setup, and maybe you shouldn't. If you do, then you need to make sure the e-mail client is setup to do outgoing authentication for smtp (most programs like Outlook Express do this).
As far as the first problem, I have no clue on that.
Yes, outgoing auth is on in the mail client, and its not just my server that this is happening to. I have a friend who has a FreeBSd server as well and it is also screwed.
And if exim is configged wrong, i cant imagine that. It was configured by cPanel !.
Who in their right mind wouldn't require outgoing authentication?
Who's going to leave their mail server open for anyone to send out spam messages from?
Is this happening on all accounts? If not, it could be the users ISP. Some ISP's will not allow another smtp server to be used. AOL for one does this, Prodigy too. There are quite a few more and it is an issue that we've had before.
This can be avoided by running another copy of Exim on another port can't it?
AOL can't block you from sending e-mail using another POP3 account they can only block port 25 traffic as far as I'm aware.
Why in the world would they do something like that though is what I'm wondering.
What a bunch of totalitarian pricks... I can't believe that their users would tolerate that.
Who said anything about caring what SMTP server we use?
We do however need the SMTP servers on our servers to work.
If your server is properly configured, you don't need outgoing authentication. I run a rather large ISP in the St. Louis area, and we don't use any kind of outgoing authentication. If someone is on our network, then they should be allowed access to our mail server, considering the only way to access our network is by being a customer.Originally posted by rnh
Who in their right mind wouldn't require outgoing authentication?
Who's going to leave their mail server open for anyone to send out spam messages from?
IP based access rules are much better than outgoing authentication anyways (easy to get past outgoing authentication)
This is kinda hard if we have customers from Europe, Asia, and the USA, and a large amount of IP ranges for the dialup users. Meaning it wouldnt work that way.Originally posted by jrehmer
If your server is properly configured, you don't need outgoing authentication. I run a rather large ISP in the St. Louis area, and we don't use any kind of outgoing authentication. If someone is on our network, then they should be allowed access to our mail server, considering the only way to access our network is by being a customer.
IP based access rules are much better than outgoing authentication anyways (easy to get past outgoing authentication)
This isnt possible for many of us, most of us just provide hosting without dial up access... so most of us do have our servers set up properly for our needsOriginally posted by jrehmer
If your server is properly configured, you don't need outgoing authentication. I run a rather large ISP in the St. Louis area, and we don't use any kind of outgoing authentication. If someone is on our network, then they should be allowed access to our mail server, considering the only way to access our network is by being a customer.
IP based access rules are much better than outgoing authentication anyways (easy to get past outgoing authentication)
Easier than spoofing an IP#?Originally posted by jrehmer
IP based access rules are much better than outgoing authentication anyways (easy to get past outgoing authentication)
Anyway a non-ISP server without the ability to limit use to someone on it's dialup network (since it doesn't have a dialup network since it's a web host (or "IPP") and not an ISP) should never open outgoing e-mail relaying, this is one of the leading causes of the massive abundance of spam.
Last edited by rnh; 04-17-2003 at 08:26 PM.
O, so what should we tell our clients, we are sorry, but we cant give you an outgoing SMTP since it can be used for relaying.Originally posted by rnh
Easier than spoofing an IP#?
Anyway a non-ISP server without the ability to limit use to someone on it's dialup network (since it doesn't have a dialup network since it's a web host (or "IPP") and not an ISP) should never open outgoing e-mail relaying, this is one of the leading causes of the massive abundance of spam.
But that wouldnt be right, we have auth so basically they have to login to the SMTP before they can send anything. We dont have an open relay, cause that would INDEED be stupid.
Does anyone here know where exim checks if the username and pass for the auth are correct?
Still having this problem. I am gonna make sure someone from the cPanel.net staff sees this somehow.
LinkBack URL
About LinkBacks
Reply With Quote