Thanks For the reply.
I did as suggested but postfix accepted this mail also and then rejects
complaining
Recipient address rejected: User unknown in virtual mailbox table;
from=<[EMAIL PROTECTED]> to=<[EMAIL PROTECTED]> proto=ESMTP helo=<localhost>
It should not accepts the mail right?
Some days ago at my original amavis server logs I observed some strange lines
like
(16188-21) WARN: address modified (recip): <[EMAIL PROTECTED]> ->
<"\240singh.richa09"@gmail.com>
(16188-21) (!) lookup_sql: sql exec: err=7, 22021, DBD::Pg::st execute failed:
ERROR: invalid byte sequence for encoding "UTF8": 0xa0\nHINT: This error can
also happen if the byte sequence does not match the encoding expected by the
server, which is controlled by "client_encoding"., 7, ERROR: invalid byte
sequence for encoding "UTF8": 0xa0\nHINT: This error can also happen if the
byte sequence does not match the encoding expected by the server, which is
controlled by "client_encoding".\n
(16188-21) (!!) TROUBLE in process_request: sql exec: err=7, 22021, DBD::Pg::st
execute failed: ERROR: invalid byte sequence for encoding "UTF8": 0xa0\nHINT:
This error can also happen if the byte sequence does not match the encoding
expected by the server, which is controlled by "client_encoding". at (eval 64)
line 264, <GEN201> line 12.
(16188-21) (!) Requesting process rundown after fatal error
TIMING [total 9 ms] - bdb-open: 9 (100%)100, rundown: 0 (0%)100
(16744-07) WARN: address modified (recip): <[EMAIL PROTECTED]> ->
<"\240nitin07.sharma"@gmail.com>
(16744-07) (!) lookup_sql: sql exec: err=7, 22021, DBD::Pg::st execute failed:
ERROR: invalid byte sequence for encoding "UTF8": 0xa0\nHINT: This error can
also happen if the byte sequence does not match the encoding expected by the
server, which is controlled by "client_encoding"., 7, ERROR: invalid byte
sequence for encoding "UTF8": 0xa0\nHINT: This error can also happen if the
byte sequence does not match the encoding expected by the server, which is
controlled by "client_encoding".\n
I did google this error and found that this happens because the recipients
email-id contains some non-ascii chracters and found that RFC822 and RFC821
does not allow these chracters in the headers. So we decided to reject these
mails at Postfix level itself. But as I stated earlier I am not able to do so.
Bijayant Kumar
--- On Tue, 25/11/08, mouss <[EMAIL PROTECTED]> wrote:
> From: mouss <[EMAIL PROTECTED]>
> Subject: Re: Reject Non-Ascii characters
> To: "postfix" <postfix-users@postfix.org>
> Date: Tuesday, 25 November, 2008, 4:42 PM
> bijayant kumar a écrit :
> > Hello to list,
> >
> > I am using postfix-2.5.5 on gentoo box in a virtual
> domain environment. Some of my users just copy paste the
> email addresses which contains some non-ascii characters in
> their recipients list which results in delaying mails for
> other users because it gets stuck in amavis. I am trying to
> reject these kind of mails to enter in to postfix. I am
> trying to achieve this in my test scenario setups like.
> >
> > smtpd_recipient_restrictions =
> > check_sender_access
> pcre:/etc/postfix/ascii.pcre
> > permit_mynetworks
> > ...........
> >
> > cat /etc/postfix/ascii.pcre
> > /[^[:ascii:]]/ REJECT Non-Ascii Characters
> >
> > But i am not able to block. My postfix is accepting
> this mail. I am testing like "test @test.com"
> "[EMAIL PROTECTED]" "test<@test.com" and
> like wise.
> >
>
> I see no non-ascii chars there. try
> "[EMAIL PROTECTED]" (accented 'e'
> there).
>
> do you know that most chars are valid in addresses? you can
> restrict the
> chars used in your own addresses of course.
>
> what is the problem exactly? what gets "stuck in
> amavis"?
Get your preferred Email name!
Now you can @ymail.com and @rocketmail.com.
http://mail.promotions.yahoo.com/newdomains/aa/
