Hi,
Thank you for your thorough reply.
Sendiing restrictions was a walk in the park with Postfix. The users who are
not allowed to send and received externally don't have internet access either
(because they abused it instead of doing their work - again, I'm just the
techie, these decisions/policies are from upstairs). So they can't reach
outside mailserver either.
(1) Restricting receiving email from your own domain
# Drop mail not from your domain
:0 h
*!^From(_dot_)*(_at_)newingtoncs(_dot_)co(_dot_)za
/dev/null
OIC, thanks. But that will drop ALL mail from outside, while I only need that
for specific users. If I drop that inbetween the brackets in my recipy, will
that work? i.e.
:0h
*^To: john(_at_)newingtoncs(_dot_)co(_dot_)za
{
!^From(_dot_)*(_at_)newingtoncs(_dot_)co(_dot_)za
/dev/null
}
and for any sender outside of your domain the mail will be
silently discarded, instead of bouncing with a user unknown message.
I'm sure I could put an extra line in the recipy to send a bounce message?
After all, why give someone an email
address if they are not supposed to use it?
Internal communication. Again, this isn't my decision, and I wouldn't do it
that way, but this is what my client wants. I'm not even exactly sure how
the people manage to "abuse" e-mail to the point that it is a problem for the
company. But that's not my business.
If some users really should
only be able to mail internally, move them to an internal domain,
something like john(_at_)newingtoncs(_dot_)internal, which is clearly
identified as
an address that only works internally.
Last option, but that might end up being the easiest to implement
Thanks again
--
Kind regards
Hans du Plooy
Newington Consulting Services
hansdp at newingtoncs dot co dot za
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail