Differences

This shows you the differences between two versions of the page.

Link to this comparison view

domain_alias_spam_bounce [2012/01/10 22:19]
eddieburke
domain_alias_spam_bounce [2012/02/12 16:51] (current)
are old revision restored, spam removal
Line 1: Line 1:
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
 //Author: Matthew J. Salerno// //Author: Matthew J. Salerno//
  
-While building my first DBMail server, I was happy to see that the full migration from my old mail server worked almost flawlessly, I ran into one snag.  My company has many domains, and most of those domains are just aliases.  I knew that I could create an alias for every user for every aliased domain, but that would exponentially increase the size of my alias table, I could have also created and alias like @foo.bar ->deliver_to-> @foo.bar.uk, but I wanted to do something a bit cleaner and easier to manage since they are constantly adding and removing alias domains.  So what I did was create a table for managing the domains [[http://www.terrabeads.com/t-women-dresses.aspx|trendy dresses]].  I named it "dbmail_vdomains" and it's structure [[http://www.gotlandweb.com/t-cheap-hotels.aspx|budget hotels]] is very minimal.  It contains the following columns: id, domain, comment,pridomain, client_idnr.+While building my first DBMail server, I was happy to see that the full migration from my old mail server worked almost flawlessly, I ran into one snag.  My company has many domains, and most of those domains are just aliases.  I knew that I could create an alias for every user for every aliased domain, but that would exponentially increase the size of my alias table, I could have also created and alias like @foo.bar ->deliver_to-> @foo.bar.uk, but I wanted to do something a bit cleaner and easier to manage since they are constantly adding and removing alias domains.  So what I did was create a table for managing the domains.  I named it "dbmail_vdomains" and it's structure is very minimal.  It contains the following columns: id, domain, comment,pridomain, client_idnr.
  
 ---- ----
Line 61: Line 14:
 ---- ----
  
-When I created my user accounts, I used a unique client_idnr for each new domain.  So, each user had it's main alias as user@foo.bar deliver_to user_idnr, and every account and alias for the foo.bar domain uses the same client_idnr.  By giving all of the accounts in the same domain the [[http://www.americanhomemoving.com/|moving companies]] same client_idnr, you can use sql to do some nice things.  The next step is to populate the table.+When I created my user accounts, I used a unique client_idnr for each new domain.  So, each user had it's main alias as user@foo.bar deliver_to user_idnr, and every account and alias for the foo.bar domain uses the same client_idnr.  By giving all of the accounts in the same domain the same client_idnr, you can use sql to do some nice things.  The next step is to populate the table.
  
 ---- ----
Line 123: Line 76:
 ---- ----
  
-The check_recipient_access will basically lookup an e-mail address and will see if the mail server will accept mail for that account.  So all-users.cf, uses the dbmail_vdomains and the dbmail_aliases tables joining them using the client_idnr.  So it creates a list of all possible e-mail addresses including all aliases including all aliased domains.  When postfix is receiving an e-mail, it will check the recipient e-mail address to see if it accepts mail for that address.  If it finds an e-mail address that matches, it will return, OK and the mail will be accepted and processed, if no e-mail address is found, it will return "REJECT", and postfix will reject the mail, not accepting it for processing.  So far my mail server has rejected over 50,000 pieces of mail because of this.  The overhead of looking up the e-mail address is much much [[http://www.shoppharmacycounter.com/t-Adipex-Medicine.aspx|buy adipex online]] less than processing mail that couldn't be delivered in the first [[http://adipexweightlossdiet.com/fatloss.html|lose weight fast]] place.+The check_recipient_access will basically lookup an e-mail address and will see if the mail server will accept mail for that account.  So all-users.cf, uses the dbmail_vdomains and the dbmail_aliases tables joining them using the client_idnr.  So it creates a list of all possible e-mail addresses including all aliases including all aliased domains.  When postfix is receiving an e-mail, it will check the recipient e-mail address to see if it accepts mail for that address.  If it finds an e-mail address that matches, it will return, OK and the mail will be accepted and processed, if no e-mail address is found, it will return "REJECT", and postfix will reject the mail, not accepting it for processing.  So far my mail server has rejected over 50,000 pieces of mail because of this.  The overhead of looking up the e-mail address is much much less than processing mail that couldn't be delivered in the first place.
  
-[http://customcollegeessays.com/index.php college essay]  
  
  
 
domain_alias_spam_bounce.txt · Last modified: 2012/02/12 16:51 by are
 
DBMail is developed by Paul J Stevens together with developers world-wide