iPlus Info Browser includes a "nobody report" that will tell you every domain that has a nobody alias.
http://www.martekware.com > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:Imail_Forum- > [EMAIL PROTECTED] On Behalf Of Robert E. Spivack > Sent: Wednesday, September 20, 2006 7:27 PM > To: [email protected] > Subject: RE: [IMail Forum] Comcast mail blocking - diagnosis and request > for help disabling aliases/forwarding > > Javascript editing of webmail is too kludgy. I would prefer a tool that > runs server-side, even if it is a batch file that has to be scheduled it > is better than client-side hacks. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox > Sent: Tuesday, September 19, 2006 9:52 AM > To: [email protected] > Subject: Re: [IMail Forum] Comcast mail blocking - diagnosis and request > for help disabling aliases/forwarding > > How about restricting mail system administration to not allow entry of > nobody aliases? Should be some simple javascript additions to handle > this. > > Darin. > > > ----- Original Message ----- > From: "Robert E. Spivack" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Tuesday, September 19, 2006 12:48 PM > Subject: [IMail Forum] Comcast mail blocking - diagnosis and request for > help disabling aliases/forwarding > > > Like others here, we have seen one of our mail servers blocked from > sending email to Comcast with the rejection message of spam not allowed. > > After extensive monitoring, I believe I have tracked down the root > cause. We have a few users that had a "nobody" alias configured on > their domain with a forwarding rule sending all incoming email to > Comcast. > > They also had turned off all their spam filtering. The result is that > dictionary-attack type spam was being accepted by their incoming mailbox > (because of the "nobody" alias) and then forwarded to Comcast. > > Because of the presumably multiple emails forwarded to Comcast from the > same account/mail server, it was triggering spam detection filters on > Comcast end. > > Unfortunately it would appear that Comcast (like AOL) does not > distinguish between the real source of the email and the unfortunate > victim (our mail server/stupid user). > > I have taken remedial steps for this user (deleting their "nobody" alias > and disabling their mail forwarding to Comcast. > > I'm looking for an automated method to enforce these restrictions > (disallow nobody alias, disallow forwarding to Comcast or aol addresses) > server-wide and was wondering what is the best way to do this? > > Two possible solutions: > > Some kind of batch file process that scans the IMail registry entries > and deletes nobody entries and changes rules that forward to Comcast/aol > to forward to null, or -- > > Setting up another server as a gateway for outbound mail and somehow > implementing these restrictions on the gateway (and then setting the > other mail servers to use the gateway as the smarthost for all outbound > mail delivery.) > > Hopefully, some of you have already implemented something like this and > can provide guidance and assistance. > > TIA > To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html > List Archive: > http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ > Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ > > To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html > List Archive: > http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ > Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ > To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html > List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ > Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
