View Full Version : Deinstalling inetd :-((
tom
5th November 2006, 23:02
I've deinstalled inedt after I've found nothing to start with inetd.conf. Now the whole Mailtransport is'nt working anymore. No imap, no pop, now sasld, no bind... :mad:
Even all postfixfiles are gone, all proftpfiles are gone, all sasldfiles are gone, all bindfiles are gone...
This is gone courier-imap courier-imap-ssl courier-pop courier-pop-ssl...
and of course all the depending config files. And there is NO backup.
What a fuck:eek:
So I saw: ISPconfig is using the ined massively. I know that I'v demolished a lot nearly everything by removing inetd.
I realy don't understand why?
How could this shit happend?
Why apt-get remove --purge remove postfix, proftp etc. ?
I think I habe to reinstall postfix and proftp.
But I'm not sure what else are missing?
:confused:
tom
6th November 2006, 01:09
Ok, It's fixed now:)
I've installed an configured the missing parts (deleted by apt-get inetd!!!) and used this golden opportunity to upgrade isp and it works:)
And the Mailboxes are and dns entries are still there...
But still I dont understand why apt-get remove inetd removed all the other things.
falko
6th November 2006, 15:55
So I saw: ISPconfig is using the ined massively. I know that I'v demolished a lot nearly everything by removing inetd.
ISPConfig doesn't use inetd, but lots of other packages do.
When you ran apt-get remove inetd
it should have shown you which packages are going to be removed...
tom
6th November 2006, 16:39
sorry,sorry
tom
6th November 2006, 16:41
Ok, It's fixed now:)
It's fixt everything:
I can't sent or receive mail.
----- The following addresses had permanent fatal errors -----
<admin@xyz.de>
(reason: 550 <admin@xyz.de>: Recipient address rejected: User unknown in local recipient table)
tom
6th November 2006, 17:43
It's fixt everything:
I can't sent or receive mail.
----- The following addresses had permanent fatal errors -----
<admin@xyz.de>
(reason: 550 <admin@xyz.de>: Recipient address rejected: User unknown in local recipient table)
I added this line in main.cf and it works.
virtual_maps = hash:/etc/postfix/virtusertable
I've not seen this line before and even there is no syntax highlighting for this line in my shell. Is that usual?
There is another prob with proftpd. I can't log in.
With the same user and password as I can send mails with postfix it is'nt possible to login the ftp account?
Befehl: USER web1_admin
Antwort: 331 Password required for web1_admin.
Befehl: PASS ************
Antwort: 530 Login incorrect.
???
till
6th November 2006, 22:03
I've not seen this line before and even there is no syntax highlighting for this line in my shell. Is that usual?
The line is usual.
There is another prob with proftpd. I can't log in.
With the same user and password as I can send mails with postfix it is'nt possible to login the ftp account?
Any errors in the syslog or xferlog?
tom
6th November 2006, 23:37
The line is usual.
Any errors in the syslog or xferlog?
sorry, of course, I was looking for an proftplog but I could'nt find it...
no such user 'web'
notice: unable to resolve '~web/': No such file or directory
that was strange no such user 'web'
But that ~web/ in proftpd_ispconfig.conf was wrong.
It has to be
DefaultRoot "~/web/
An everything is fine :-)
tom
7th November 2006, 20:43
Unfortunately I've found one fault more
I it not possible to send a mail from localhost to postfix:
Nov 7 19:25:46 server-x postfix/smtp[29184]: 1581F1F5FF: to=<admispconfig@localhost.localdomain>, relay=none, delay=96737, status=deferred (connect to localhost.localdomain[1.2.3.4]: Connection refused)
?
till
8th November 2006, 11:12
Is localhost.localdomain listed in the file /etc/postfix/local-host-names ? If not, add it at the end. Make sure that localhost.localdomain is also listed for the IP 127.0.0.1 in the /etc/hosts file.
tom
8th November 2006, 12:08
Is localhost.localdomain listed in the file /etc/postfix/local-host-names ? If not, add it at the end. Make sure that localhost.localdomain is also listed for the IP 127.0.0.1 in the /etc/hosts file.Yes, thanks.
I found the local ip in hosts.deny. Now it's ok.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.