On Wed, 12 Oct 2011 15:08:37 +0530 "J. Bakshi" <joyd...@infoservices.in> wrote:
> On Wed, 12 Oct 2011 04:00:21 -0500 > Duane Hill <duih...@gmail.com> wrote: > > > On Wed, 12 Oct 2011 13:05:51 +0530 > > "J. Bakshi" <joyd...@infoservices.in> wrote: > > > > > On Tue, 11 Oct 2011 20:40:03 +0200 > > > Jeroen Geilman <jer...@adaptr.nl> wrote: > > > > > > > On 2011-10-11 09:52, Tõnu Samuel wrote: > > > > > On Tue, 2011-10-11 at 13:14 +0530, J. Bakshi wrote: > > > > >> Hello Kirill, > > > > >> > > > > >> I need incoming mail rejected for nore...@mail.com as well as a > > > > >> notification send to the user about the mail rejection. > > > > > Backscatter robot. You send mail to foo...@example.com. > > > > > example.com rejects your mail with "Over quota" or "on vacation". > > > > > You receive this message and send "we said NO REPLY!". > > > > > Example.com sends "over quota" again.... > > > > > > > > Nonsense. You REJECT the message and the remote server will (if > > > > configured properly) not attempt further delivery. > > > > > > > > A no-reply address is very common; this is why your earlier comment > > > > about this needing to be read doesn't make much sense. > > > > The RFC lists clearly which addresses should go to a mailbox read > > > > periodically by a human being; "noreply" is not one of them. > > > > > > > > Of course, proper list or mass-mailing management consists of > > > > sending null senders in the first place, and/or utilizing VERP in > > > > outgoing email. > > > > > > > > In the OP's case, it is trivially solved with a > > > > check_recipient_access map consisting of nothing but > > > > > > > > nore...@example.com REJECT We said no! > > > > > > > > At no point does the postfix system send a MESSAGE in response to > > > > delivery attempts to this address - instead, it will reject the > > > > recipient. > > > > > > > > > > Thanks, Exactly what I am searching for. > > > > > > So I have modified my main.cf as > > > > > > ` ` ` ` > > > smtpd_recipient_restrictions = > > > permit_mynetworks, > > > permit_sasl_authenticated, > > > check_recipient_access hash:/etc/postfix/restrictioinincoming, > > > reject_unauth_destination > > > > > > ` ` ` ` ` > > > > > > and the /etc/postfix/restrictioinincoming has > > > > > > ` ` ` ` > > > nore...@mail.com REJECT We said noreply! > > > ` ` ` ` > > > > > > then > > > > > > # postmap /etc/postfix/restrictioinincoming > > > # /etc/init.d/postfix restart > > > > > > But still I can send mail at nore...@mail.com > > > > > > Have I missed anything ? > > > > Where was the message sent from? If the host you sent from is within > > mynetworks or authenticated, the message would have gone through. > > > Uh, ok... I have tested from a different domain and it is working perfectly > fine. > So, how can I then also restrict mynetworks or authenticated for that > particular > account ? > > TIA Solved , order matters... check_recipient_access hash:/etc/postfix/restrictioinincoming should be checked at first Thanks a lot
