Internal system's bounced mail is bouncing to my server

Discuss the Scalix Server software

Moderators: ScalixSupport, admin

rgmhtt
Posts: 70
Joined: Wed Jan 04, 2006 4:37 pm
Location: Oak Park

Internal system's bounced mail is bouncing to my server

Postby rgmhtt » Fri Aug 04, 2006 5:34 pm

I am running CE v 10 on Centos v 4.3. (finally pulled down 10.0.1 to upgrade?)

I am having a serious problem with rejected mail to the extent that AOL thnks I am a spammer (which dnsstuff reports I am not).

Here is the senario:

An internal server gets mail to its host name, the MX record for this server WAS my main server (I have changed that for now and waiting for it to propagate). So the mail comes into my server that forwards it to this internal server.

Of course the spam is for a non-existant userid, and my server gets the error message.

This produces the first email that goes to sxadmin.

Now of course, my server tries to sent the invalid user mail message back to the 'source', and I am getting connection refused and other types of messages. So my mqueue sits there with over 200 queued messages. After 4 days of trying, root gets a message about the failed delivery.

Actually I have not sorted out all the messages that go to sxadmin and root, but those boxes fill up too soon.

Now I don't want to just drop all this mail on the floor. It is POSSIBLE that a vaild user got the a userid wrong.

So I am trying to figure out how to NOT generate an unknown userid message (to root and or sxadmin) when the internal server rejects the email.

Then if, on the 1st try the bounce message does not go back to the sending address, then drop it on the floor.

Is this a rational approach and how do I pull iit off?

I am only starting to learn spamassasin and procmail....

rgmhtt
Posts: 70
Joined: Wed Jan 04, 2006 4:37 pm
Location: Oak Park

Postby rgmhtt » Fri Aug 04, 2006 7:25 pm

Well, for right now we are setting this internal server to drop mail if the userid is not in the passwd or alias file.

That will stop the noise until we can figure this out differently.

But I would think that the try once run (or maybe twice) would be a nice way to handle all the mail I get to my server (I am setting up spamassasin, but I suspect some of the unknown userid mail will pass spamassasin's tests).

So I still want to learn how to handle this.


Return to “Scalix Server”



Who is online

Users browsing this forum: No registered users and 3 guests

cron