Posts by hempelr

Thanks - that solved it, it was an easy tast

Hi all,

I wanted to use circular (german Rundmail) to all users on a i-mscp installation (i-MSCP 1.5.3 Build: 2018120800 on Debian Stretch) but after attemp to send a failure message appears and no mail will be sent and the following failure messages where send per mail:

What is to do, that that function can be used?

uhhh - thanks...it would be better to let the fingers off

Thanks for the good job of i-mscp.
If you are bored, such a script would be a plan

Hi all,

are there possibilities and/or tutorials to migrate a single user from one server to another (with mail, webcontent and databaseses and all passwords without interaction of that user self) ?

On both server is i-mscp, on the source is i-MSCP 1.5.4 Build: 20180606, on the target is i-MSCP 1.5.3 Build: 2018120800

Thanks for some hints

Greetings from the OreMountains in Germany

hempelr

on last saturday a domain of a user were deactivated, because the expiration time was over, then yesterday I've extended the expiration time in and the mail client could access again.But....all mails sendet at every mailaccount would not relaied, they where send back with an undelivery message. Then just a hour ago I created a new mail account for testing and logged in via webmail. And since then all mailaccounts are active again, also the web-blocksite is gone.

But this is rather strange - is this a normal behavior if the domain is not manuell activated bevor it is changed?

Hallo to all,

I've upgradet to version 1.4.7. from 1.4.3 and now its not possible to send mail neither with nor without encryption. Webmail says authentication fails, telnet connection on port 25 is ok, ehlo answer looks god but rcp to does it not...and all mailclients say, that authentificantion fails...

rcpt to:recepient@mailserver.tld
554 5.7.1 <recepient@mailserver.tld>: Relay access denied

Receiving runs well - affected all my servers which run imscp. One of these hosts som custumer mailaccounts and they are not very amused...:(
I have no Idea what is to do.
Neither auth.log nor mail.info nor mail.log gives a hint

System is Debian Jessie 8.8, it is a vServer

What could be wrong now?

Thanks Nuxwin, nice to hear that you'll fix it and that there is meanwhile a patch...

mhm - let me try to explain:
If the expiration date of a domain is set in imscp (pic1), then the accessibility of this domain will be deactivatet after this date is reached (loo pic2)
Then if that deactivatet domain will be activatet and a new expiration date in the future has been set manually (in the date field pic1) the domain is reachable per http and https, but the mailaccounts not.
Custumers can not acces their mailaccounts as before the deactivation of the domain. Because this occured every time, if a account was deactivatet, searched and found, that every password on every mailaccount of the former deactivatet domain where changed. And they where not changed back to its former value after the manual reactivation of the domain. Thats the reason, because no user can login at his mailaccount nor a client nor with webmail.
Is this a feature or a bug? - because it is not jokey to search, why mailaccounts dont went well....

I use 1.2.9 on a Debian wheezy Root with some Customers / Customer-Domains.
Every year the point at the expirience day the customer give feedback, that no mail is possible.
Then I activate the domain and in the past all went fine, but suddenly the mailpasswords are changed and no user on an expired and new activatet domain can send or receive mails.
Whats the reason? And is this behavior also in 1.2.11?
It took about one hour to find the reason, why the mailaccounts on a newly activated domain does not run - only on a look into the database and mailtable I did found the reason.
Is this a feature or a bug?

no speical characters...
Its on a imscp-customer/user not mailuser, it's false on all mail-accounte on all this imscp-user-account...
On my testserver its also only one user, the same imscp-version, but debian is jessy newes version (actual today 15:00)
Ths is yet strange...I'll test an update to imscp 1.2.10 on this testserver in the hope,that I have not to cry for help