nobaloney
NoBaloney Internet Svcs - In Memoriam †
I should have beta4 in production by the end of the week; all it's waiting for now is for me to get it in sync with the latest from DA. I'll be writing John in a moment.
Jeff
Jeff
I'm confused. The whitelist_host list is a list of systems you want to be able to send you mail; it has nothing to do with whether or not you can send email to other systems.tdldp said:We have regurlaly a listed IP which blocks us sending mails (this is because the ip has been used by wanadoo users to spam others, and as we have at our work a changing ip for security needs, we have regurlaly listed ip's)
To prevent us from being blocked when sending emails. i added as you can see in my last post our host, in whitelist_from.
SpamBlocker doesn't offer this in the most recent versions (even the one coming out shortly), but you can do it easily enough by forwarding the specific email addresses to /dev/null. Read elsewhere in the forums for instructions on how to set up a forwarder to a directory.Since that another trouble occured.
I have set my adress as catchall, some of our clients having trouble visibly to spell our adress correctly. it was preferable to be sure we get all mails in, even if there is a typo or spelling error.
Problem i have 2 adresses that have been in some manner, added in international spamming lists, and we now get, 6 times an hour, mails to those 2 adresses that land in my mailbox. Fortunately, spamassassin does his job correctly, and it detects it as spam (normal : XBL , Spamcop listing)
What i'd like to know is, how can i block in a specific list : blacklist_to, specific destinatory adresses, so that it is refused by server ??? Is this case planned in future spamblocker version ???This case can be pretty problematic, and it would be good to be able in first check that the adress is in a blacklist with catchall usage.
jlasman said:I'm confused. The whitelist_host list is a list of systems you want to be able to send you mail; it has nothing to do with whether or not you can send email to other systems.
jlasman said:SpamBlocker doesn't offer this in the most recent versions (even the one coming out shortly), but you can do it easily enough by forwarding the specific email addresses to /dev/null. Read elsewhere in the forums for instructions on how to set up a forwarder to a directory.
Jeff
Now I understand. Yes, this will whitelist your domain name for the same server. However it won't whitelist your domain name for anyone listed on other servers using the blocklisted IP#.tdldp said:We can send anytime, with any ip (even if listed) emails to ourselves and to our clients.
Get the IP# delisted or move to a different IP#.Now if there is another solution in order that our host is always allowed to send mail without checking RBL, i'll appreciate solution.
It can certainly be done in SpamBlocker, but we don't do it at this time.My problem is not to forward a specific email adress. (this adress is not suppose to exist, and those who send emails to this adress are spammers, and nothing else.)
I think that in some case, it could be good to block a destination adress known to be used by spammers, just as spamblocker blocks mail from known hosts.... I'm too newbie to traduce that in script, though i'm trying to and trying to learn. That is why i ask help or a lane to follow...
jlasman [/i][B]Get the IP# delisted or move to a different IP#.[/B][/QUOTE] Well i'd love to said:It can certainly be done in SpamBlocker, but we don't do it at this time.
Jeff
But you don't explain why we should block destination addresses. Just what problem would it resolve that isn't resolved by the forward to /dev/null?I think that in some case, it could be good to block a destination adress known to be used by spammers,
# refuse mail to any identified adress in any local domain, regardless of source
deny recipients = lsearch;/etc/virtual/destination_block
message = The destination adress is not accepted by our services - Stop spamming us.
######################################################################
# ACLs #
######################################################################
begin acl
# ACL that is used after the RCPT command
check_recipient:
# we accept if the source is local SMTP (i.e. not over TCP/IP).
# We do this by testing for an empty sending host field.
accept hosts = :
# Deny for local domains if local parts begin with a dot or
# contain @ % ! / |
deny domains = +local_domains
local_parts = ^[.] : ^.*[@%!/|]
# allow local users to send outgoing messages using slashes
# and vertical bars in their local parts but blocks outgoing
# local parts that begin with a dot, slash, or vertical bar
# but allows them within the local part. The sequence \..\
# is barred. The usage of @ % and ! is barred as before. The
# motiviation is to prevent your users (or their virii) from
# mounting certain kinds of attacks on reverse sites.
deny domains = !+local_domains
local_parts = ^[./|] : ^.*[@%!] : ^.*/\\.\\./
# accept email from anyone in the whitelist_from list
accept domains = +whitelist_from
jlasman said:tdldp,
Personally, if I were going to include the code, I'd probably want to put it after the whitelist code; by definition whitelists should supercede any blocklists.
Or shouldn't they? If not, then for what reason?
Jeff
You might as well find another control panel, now, then, sullise, since dovecot doesn't replace exim.sullise said:Exim blows monkey chunks IMHO.