From steve.weifenbach@hanesfinishing.com Wed Oct 25 11:22:11 2000 Date: Wed, 25 Oct 2000 09:00:29 -0400 From: Steve To: Jeremy C. Reed Subject: GNU-pop3d and Postfix [ The following text is in the "iso-8859-1" character set. ] [ Your display is set for the "US-ASCII" character set. ] [ Some characters may be displayed incorrectly. ] Here is how I set up Postfix and GNU-pop3d with your patch for vitrual domains. In main.cf: virtual_maps = hash:/etc/postfix/virtusertable alias_maps = hash:/etc/postfix/aliases alias_database = hash:/etc/postfix/aliases In virtusertable: user.name1@domainname1.com user.name1.dn1.com user.name2@domainname1.com user.name2.dn1.com user.name3@domainname1.com user.name3.dn1.com # user.name4@domainname2.com user.name4.dn2.com user.name5@domainname2.com user.name5.dn2.com user.name6@domainname2.com user.name6.dn2.com In aliases: user.name1.dn1.com: /var/spool/virtual/domainname1.com/user.name1 user.name2.dn1.com: /var/spool/virtual/domainname1.com/user.name2 user.name3.dn1.com: /var/spool/virtual/domainname1.com/user.name3 # user.name4.dn2.com: /var/spool/virtual/domainname2.com/user.name4 user.name5.dn2.com: /var/spool/virtual/domainnam2.com/user.name5 user.name6.dn2.com: /var/spool/virtual/domainname2.com/user.name6 # and so on for other domains. We currently have seven. virtusertable db is created using postmap in the /etc/postfix directory aliases db is created using postalias in the /etc/postfix directory I have directories defined: /var/spool/postfix, where postfix manages the messages /var/spool/virtual/domainname1.com, /var/spool/virtual/domainname2.com and so on for the other domains where postfix deposits the messages for the pop3 users per the virtusertable and aliases files. /etc/virtual/domainname1, /etc/virtual/domainname2 and son on for the other domains where the passwd file is kept for each domain. I used your script to create the passwd files in each /etc/virtual/domainname directory. Currently, I am developing a MySQL table with user name and password that will used to create these passwd files using the same script within another script that have all the users and passwords redirected into the passwd files for maintenance. MySQL will secure the user/passwords for me and the time to live for the intermediate script will be short. And as you know, the passwords are encrypted in the passwd file from this pop_passwd script. #!/usr/bin/perl # pop_passwd username password >> passwordfile $name = $ARGV[0]; @salt_chars = ('a'..'z','A'..'Z','0'..'9'); $salt = $salt_chars[rand(62)].$salt_chars[rand(62)]; $passwd = crypt($ARGV[1],$salt); print "$name:$passwd\n"; This is all I did after applying your patch to the GNU-pop3d source and installing. I am currently working on SASL for SMTP to authenticate the users sending mail via SMTP. People inside create any profiles they want in their email programs and send "fake" mail. If you have any direction on a better way or instructions on SASL implementation this would be great. -- Mit freundlichen Grüßen, Steve Weifenbach