Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-07-2010, 09:57 AM
Member
 
Posts: 11
Unhappy domain alias + reject_unverified_recipient

I am using alias domain on open source version 6 .
To stop bounce spam trafic I have to add
"reject_unverified_recipient" in file "postfix_recipient_restrictions.cf"
But after doing this we frequentelly get following message in mail clinets (Out Look Express)
" 450 <username@domain.com>:Recipient address rejected: unverified address: Address verification in progress"
Is there any way to over come this problem. I searching forum from last 3 days but could not find any soloution.

Last edited by vipin65; 07-07-2010 at 10:38 AM.. Reason: to explain more
Reply With Quote
  #2 (permalink)  
Old 07-07-2010, 11:40 PM
Zimbra Consultant & Moderator
 
Posts: 20,313
Default

Quote:
Originally Posted by vipin65 View Post
Is there any way to over come this problem.
Don't use it unless you're a mail relay host, it's not necessary: Postfix Address Verification
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 07-08-2010, 01:25 AM
Member
 
Posts: 11
Default

Thanks for prompt reply. Our server is relay host (on public IP and can send mail to any server in the world ) if we remove "reject_unverified_recipient" our server start flooding bounce messages and we get black listed on many mail server. I tried many other option but could not find solution.

Last edited by vipin65; 07-08-2010 at 01:54 AM.. Reason: Better explanation
Reply With Quote
  #4 (permalink)  
Old 07-08-2010, 03:13 AM
Zimbra Consultant & Moderator
 
Posts: 20,313
Default

Quote:
Originally Posted by vipin65 View Post
Thanks for prompt reply. Our server is relay host (on public IP and can send mail to any server in the world )
It's a relay host for whom?

Quote:
Originally Posted by vipin65 View Post
if we remove "reject_unverified_recipient" our server start flooding bounce messages and we get black listed on many mail server. I tried many other option but could not find solution.
What other options have you tried (please describe in detail)? Is the person that's getting rejected a valid user of your server?
__________________
Regards


Bill
Reply With Quote
  #5 (permalink)  
Old 07-08-2010, 03:49 AM
Member
 
Posts: 11
Red face

Quote:
Originally Posted by phoenix View Post
It's a relay host for whom?
I mean if mail is not for local domain it is relayed to destination server.So when user send mail to external domain it is relayed.

What other options have you tried (please describe in detail)? Is the person that's getting rejected a valid user of your server?
I tried /opt/zimbra/conf/zmmta.cf smtpd_reject_unlisted_recipients 'yes' but no effect because our case is domain alias. I followed Managing Domains - Zimbra :: Wiki for domain alias.

User (sender) get 450 error on his mail client or 550 that id do not exist on remote server. What I want sever should accept mail from authenticated/local user and bounce back in case of failure. While in case of external/remote mail server should not accept mail through SMTP but give 550 error if RCPT TO not exist on our server.
Reply With Quote
  #6 (permalink)  
Old 07-08-2010, 04:25 AM
Zimbra Consultant & Moderator
 
Posts: 20,313
Default

Please update your forum profile with the output of the following command (do not post it in this thread):

Code:
zmcontrol -v
Quote:
Originally Posted by vipin65 View Post
I tried /opt/zimbra/conf/zmmta.cf smtpd_reject_unlisted_recipients 'yes' but no effect because our case is domain alias. I followed Managing Domains - Zimbra :: Wiki for domain alias.
This is the reason you should not be using a catchall account, can you not achieve this in any other manner?


Quote:
Originally Posted by vipin65 View Post
(sender) get 450 error on his mail client or 550 that id do not exist on remote server. What I want sever should accept mail from authenticated/local user and bounce back in case of failure.
This won't work while you are using a catchall on your server.

I asked you earlier who you are relaying for, who is it (are these just authenticated users)?
__________________
Regards


Bill
Reply With Quote
  #7 (permalink)  
Old 07-08-2010, 04:45 AM
Member
 
Posts: 11
Default

I have update profile.
If there is some better way to handle domain alias pls. let me know I will follow that. We have 2 domain.
Our deployment is simple single server for small office with approx 50 users.
We are not relaying for anybody yes just authenticated users relaying.
Regards
Vipin
Reply With Quote
  #8 (permalink)  
Old 07-08-2010, 04:50 AM
Zimbra Consultant & Moderator
 
Posts: 20,313
Default

Quote:
Originally Posted by vipin65 View Post
I have update profile.
If there is some better way to handle domain alias pls. let me know I will follow that. We have 2 domain.
Our deployment is simple single server for small office with approx 50 users.
We are not relaying for anybody yes just authenticated users relaying.
Regards
Vipin
Remove the domain alias settings you've created (especially the catchall) then add a second domain to your server and give every user an alias email address for that domain. You can then use this: Improving Anti-spam system - Zimbra :: Wiki to get rid of unwanted email and some of the other techniques in that article.
__________________
Regards


Bill
Reply With Quote
  #9 (permalink)  
Old 07-09-2010, 01:34 AM
Member
 
Posts: 11
Default

hmm.. finally I have to remove domain alias no other choice.
Reply With Quote
  #10 (permalink)  
Old 03-12-2011, 04:20 PM
New Member
 
Posts: 3
Default Try unverified_sender_defer_code option

I think the problem you experienced might be affected by two options:

a) The order in which the different actions are listed in smtpd_recipient_restrictions seems to matter. I added the "reject_unverified_recipient" option last, just before the "permit" option.

b) The "unverified_sender_defer_code" option is set to "450" by default. Therefore, if a temporary error occurs during recipient verification, the server will send a temporary error to the client, resulting in the error message. By setting this option to "250", the server will accept the recipient address, if it cannot be verified right now. Thus, the server will only send an error to the client, if the address cannot be verified because of a permanent problem.

Please tell me, if this options work for you. I am currently evaluating ZCS Network Edition and for the tests I performed, it works. However, I would like to know, if it also works in other setups before possible moving our production system to ZCS.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.