At 10:39 AM -0700 07/11/2002, Global Homes Webmaster wrote: >On 07/11/02 at 10:16, Warren Michelsen wrote: > >> My mail queue is filling up with email for a domain that is gone. >> They were formerly my clients but due to non-payment of long-overdue >> bills and failure to respond to my calls and email, I shut them down. > >Probably a silly question as you've probably already checked this, but are >you sure that the actual messages are queued to be relayed, or could the >queued messages be bounce messages.
Actual, incoming messages. > >> I had thought that SIMS would reject email to domains for which there >> are no router entries, with either a No-Such-Account or a >> We-Don't-Relay error. > >If there are no router entries that tell SIMS to treat the domain as local, >and no entries to forward addresses in the domain(s) elsewhere, then SIMS >should reject messages with a no-relay error (assuming you have 'relay for >clients only' enabled and the messages are coming from non-client hosts). Well, that's what I thought, and it's the reason I posted this to the list. >Others have already suggested ways to deal with this in your router, so >I'll leave it be. That will take care of this particular case, no doubt, but I cannot possibly route every possible domain for which I do not accept mail to "error". There is still the possibility of a DOS attack as described earlier. The default behavior should be to not accept mail for which there is no local account or a router entry, right? > >> I've triple-checked my router and there's nothing that I can see >> which would allow such mail to be accepted. I have used the new >> address tester in the router of the latest versions of SIMS and an >> address like. [EMAIL PROTECTED] resolves to "name at >> SMTP(domain-that-is-gone.com)" which tells me there is no local >> delivery. > >Yes, but the 'name at SMTP(domain-that-is-gone)' indicates, I believe, that >SIMS thinks it should try to deliver the message via SMTP to >domain-that-is-gone. As if the message originated locally from a trusted client. But why would SIMS do that? It occurred to me that the primary SIMS server -- the one with the queue getting these messages -- was accepting mail from my backup SIMS server -- a trusted host. Even if that were the case (it isn't), that still leaves the issue of why the backup would accept email for a domain for which it has no router entries. I keep thinking I'm missing something in the way I deleted the domains in question. Unless somehow the MX records on one name server are influencing the situation beyond directing senders to this host. Still curious. -- "Your new computer's not gonna be a Mac? Dude, you're getting a Dull!" ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
