Topic: Close Account Email Only?

[Lowell Fuher]

How do I shutdown / close email only on a user account?

[Quail_Linux]

How do I shutdown / close email only on a user account?

Hi moe,

I think what your after is:

(1) log into the server manager

(2) click on "users"

(3) and then click on "lock account" to the said user

HTH

[Lowell Fuher]

HTH,

Actually no.  

Initially that was the shutdown of the account when the employee left, but we need to maintain the account as we retrieve the information from both the server and the workstation.  

I need to re-establish a logon to the account but any emails coming to this particular account name to recieve a "user not on this system (or what ever)" message from the mail server.

But thanks any way...

[jackl]

Moe,

Do you retrieve mail by multi-drop, smtp or etrn.

Jack

[Lowell Fuher]

Do you retrieve mail by multi-drop, smtp or etrn.

SMPT

[Tib]

Why don't you use the user vacations message conrib and put in there whatever you want.

That way you still get the e-mail but a message goes back to the sender to let them know that the person is no longer there.

I've set things up this way a few times when people have left.

Regards,

Tib

[egerards]

The solution is rather simple: install dungog-mailblocking-1.0-4.noarch.rpm and create an extra deny rule for this account. Something like: 'deny from *@* to account@yourdomain.com'.

[CharlieBrady]

How do I shutdown / close email only on a user account?

Define exactly what you mean when you say "close email". Do you want to block POP/IMAP access? Delete all existing messages?

If you just mean "block any incoming email from the Internet to that account", then you can do it via:

/sbin/e-smith/db accounts setprop username Visible internal
/sbin/e-smith/signal-event email-update

[Lowell Fuher]

If you just mean "block any incoming email from the Internet to that account", then you can do it via:
/sbin/e-smith/db accounts setprop username Visible internal
/sbin/e-smith/signal-event email-update

Thanks Charlie!
That is exactly what I was looking for.  The reply from that server after making the change on that particular account reads;

20*.**.**.248 does not like recipient.
Remote host said: 553 Sorry, that address is in my badrcptto list.
Giving up on 20*.**.**.248.

Charlie, Glad your still around keeping us on track.  My first e-smith box was 5 years ago - think that was version 3.1..  <<GRIN>>

[Tib]

The e-mail blocking contrib will do the same thing.

Plus it's on the server-manager panel so you can turn it on or off.

Regards,

Tib

[Lowell Fuher]

The e-mail blocking contrib will do the same thing.

Are you talking about the dungog-mailblocking-1.1 rpm?

[egerards]

Are you talking about the dungog-mailblocking-1.1 rpm?

Ahum, did I not mention the rpm involved a few posts ago?

You can download it here.

Now you really should manage...  

[stefan24]

Hi Charlie!

"block any incoming email from the Internet to that account", [...] you can do it via:

/sbin/e-smith/db accounts setprop username Visible internal
/sbin/e-smith/signal-event email-update

That's what I was searching for, but it does not work here. Even "everyone@domain" is getting through from outside. I found a old post from psoren:

I have found that on a fresh install, i can reject one or more email adresses by typing them into /var/qmail/control/badrcptto. BUT then i install AntiVir and it stops working. So AntiVir gets the mails before smtpfront-qmail and smtpfront-qmail does not recognize that it's a blocked adress.
[...]
(http://forums.contribs.org/index.php?topic=23166.msg92475#msg92475)

I can see the users in /var/qmail/control/badrcptto, but they do not get not blocked at all. Any idea (beside asking Knuddi)?