The domains is *NOT ALLOWED* to not accept mail addressed to
postmaster. It is a REQUIRED address. If the registrant or domain
holder doesnt want to receive mail addressed to postmaster, then I
would add one that sent to your own postmaster (which actually is a
good idea anyway, becuase that would be one address abuse reports
concerning the domain would likely to get sent to)
For all domains we host mail for , I always automatically capture
abuse@ and postmaster@ and direct it to our own postmaster address.
None of our customers has ever even *asked* about either of these
addresses, let alone requested that they be setup to receive mail any
other way. Since RFC dictates that postmaster@ go to the 'person
knowledgable about the mail system, and custom suggest that abuse@
should be directed to someone able to take authority over abuse
originating therein, this seems to make 100% sense to me.
On Sat, 23 Sep 2000, Trevor Sky Garside wrote:
> > > [...] if I have just added a new domain to the system, I have to
> > > define at least one alias or Exim will freeze incoming mail
> > > complaining about inability to lookup aliases. [...] I am wondering is
> > > how can I make it so Exim knows that the DB is blank and refuses all
> > > incoming mail for that domain?
> >
> > I don't have an answer to the question that you have actually asked, but I
> > would like to remind you that any domain accepting SMTP on port 25, must
> > have a valid postmaster@??? address.
> >
> > They may make your question moot.
> >
> > -j
> >
>
>
> It's funny that you should mention that, because that is my current
> solution. I have the domain-add script automatically creating that
> postmaster account. But in the odd case (I don't see it happening, but you
> never know) where the domain doesn't want any mail accepted (even to
> postmaster) I'd like to know how to make it work.
>
> --Trevor
>
>
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
--
