Hi Meaulnes,
> But: isn't the Procmail bump message a bit too verbose? Why is the
> full path of the user displayed?
There is nothing I can do about that. And you already get these kind of
detailed error messages elsewhere. Like when a user is over quota or the
vsite he belongs to is over quota:
On 13.12.18 16:42, Ken Hohhof wrote:
If you are locking the subscriber out and bouncing incoming mail, why do you want to
"suspend" the account and not just delete it? Is this just temporary to get the
subscriber to pay his bill?
well, yes and no, those are also users who deceased and their
If you are locking the subscriber out and bouncing incoming mail, why do you
want to "suspend" the account and not just delete it? Is this just temporary
to get the subscriber to pay his bill?
-Original Message-
From: Blueonyx On Behalf Of Larry Smith
Sent: Thursday, December 13,
And the real bummer still exists in that the server
still accepts the email up front, then cannot deliver
and ends up trying to bounce to a likely bogus address
or list that does not do bounces, so we end up with even
more "mailer-daemon" email in queue.
--
Larry Smith
lesm...@ecsis.net
On Thu
On 12.12.18 01:52, Michael Stauber wrote:
When an account is suspended a few things happen: - /usr/sbin/usermod -L
is used to lock the account. - The password-hash of the user gets
prefixed with ! to disable logins. - Email forwarding/autoresponder are turned off.
That's now been fixed on
