2. I was able to resolve my tcp.smtp issue. I was doing everything right with the tcp.smtp file. Turns out the rcpthosts file, which I checked, had the test domain name in it with a # infront of the line. Once I removed the #, all relaying started to work the way I anticipated. 3. I do not have the option to create a new domain at this time. I am all most sure I can filter the incomming mail exactly as I do now on qmailrocks. Based on what I have read and researched about maildrop it should work on a user by user basis just like procmail is doing for me now. I just need some syntax help. Anyone out there ever use maildrop with qmailtoaster?
_____ From: Brian Trudeau [mailto:[EMAIL PROTECTED] Sent: Thursday, August 30, 2007 12:31 PM To: qmailtoaster-list@qmailtoaster.com Subject: RE: [qmailtoaster] tcp.smtp Re 2: probably because it does not send username/password to auth for relaying. Re 3: You might be able to do this from badmailto but I think it would be better routing wise to make a local only domain for those users so there is no way they can touch the internet. You will need to use virtualhosts to do this, and setup the domain on either the local system or just point to an internal ip or localhost on whatever dns host you have. -- Brian Trudeau, Network Administrator Eastek International Corporation 330 Hastings Drive, Buffalo Grove, IL 60089 Tel: (847) 353-8300 Ext. 213 Fax: (847) 353-8900 Web: http://www.eastek-intl.com <http://www.eastek-intl.com/> Email: [EMAIL PROTECTED] _____ From: Raymond Webster [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 29, 2007 4:47 PM To: qmailtoaster-list@qmailtoaster.com Subject: RE: [qmailtoaster] tcp.smtp 2. After some more testing I can only use the smtp service on qmailtoaster as the smtp host for a ThunderBird client if I include that clientsIP:allow,RELAYCLIENT="". if I take out the RELAYCLIENT part the connection is refused with the following error; "An error occurred while sending mail. The mail server responded: sorry, that domain isn't in my list of rcpthosts (#5.5.3 - chkuser). Please check the message recipients and try again." 3. I want to drop incoming email to some users, not all. _____ From: Brian Trudeau [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 29, 2007 12:32 PM To: qmailtoaster-list@qmailtoaster.com Subject: RE: [qmailtoaster] tcp.smtp Re 2: You still want the :allow line otherwise tcp.rules will ignore all connections but those listed. RELAYCLIENT="" only allows relaying to external clients without auth. Re 3: Drop incoming emails to local users or external users? If it's just you want this to be an internal email server only just make some iptable rules to block port 25 on the external network interface (or IP). -- Brian Trudeau, Network Administrator Eastek International Corporation 330 Hastings Drive, Buffalo Grove, IL 60089 Tel: (847) 353-8300 Ext. 213 Fax: (847) 353-8900 Web: http://www.eastek-intl.com <http://www.eastek-intl.com/> Email: [EMAIL PROTECTED] _____ From: Raymond Webster [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 29, 2007 10:51 AM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] tcp.smtp Hello I currently use a qmailrocks qmail configuration. I am looking into using the qmailtoaster. I have setup a test server using the CentOS 5 script and I am testing our needs on it to make sure I can deliver all of the fetures that we currently have. I will list the ones I need and some issues I have run into on each. 1. I only use one domain so all the clients (mostly Outlook Express) only use their usernames not [EMAIL PROTECTED] This issue is resolved. 2. I limit most of the users to local email only(i.e. within the domain). I do this using tcp.smtp with 127.:allow,RELAYCLIENT="" and listing all the internal IPs that are allowed to relay. The non-listed IPs can connect and send local email only. If an ouside address gets sent from an IP not listed they get a relaying error. I am not yet able to get this functionality working on toaster. If I use 127.:allow,RELAYCLIENT="" everyone seems to be able to send outside this server/domain. If I then remove the 127. and list internal_IP:allow,RELAYCLIENT="" , only that IP is permitted to connect and send mail even on the local server/domain other internal IPs get a relaying error and cannot send even local email. Is there a way to allow all accounts on this sever/domain to send local email only? 3. I drop any external email incomming to the clients that have no external email rights. I do this using procmail. I think I can use maildrop for the same purpose. Does anyone have experience using maildrop on toaster? 4. The qmailrocks configuration has virtual accounts in vpasswd database and qmailtoaster uses MySQL. I found where I should be able to copy over my entire domain structure and use "vconvert \c \s domain" to move the accounts into MySQL. Anyone have experience doing this? I am going to give it a test today. Thanks for any input in advance. Ray Webster
