Did you get this fixed? The part about not being able to telnet to localhost smtp would be a problem. I seem to recall that the stock toaster doesn't use smtp auth, which is why localhost is allowed to relay in the tcp.smtp file. You'll need to check the SM config file for specifics on that.
Tek Support wrote: > Dear Eric, I too have just installed CentOS 5/QmailToaster from the > directions at > (http://wiki.qmailtoaster.com/index.php/CentOS_5_QmailToaster_Install). > By the way, it went very smooth, thank you - except this one error. > I have previously installed qmail-rocks on several slackware machines > (this is my first CentOS/QmailToaster install ever) and this was a ton > easier. I was going to use Fedora 8, but saw a note from you that it > wasn't really supported, so I changed to CentOS 5. > > However I am also getting this ambigious error when trying to send > email from squirrelmail. I didn't see any lengthy discussions about > this, so let me try to fill in any blanks the original poster forgot. > > As I said, I ran through the directions and scripts just as stated, in > the order stated in your documentation, down to the area where we > "qmailctl stat". I noticed 2 others in there that you didn't mention > (submission and submission/log). I don't know if that means anything > but I'm trying to be very clear. > > I also added on the djbdns and removed bind. It appears to be working > fine and does dns lookups, and my /etc/resolve.conf is set like this: > ---snip--- > search mydomain.com <- really my domain > nameserver 127.0.0.1 > ---end--- > > So I've added a domain (my actual domain) and a real user. However, > this server is not yet in production. It has a private IP (and it > will remain that way), and I have added the appropriate Firewall line > mentioned in your docs for private IP's, and so my real DNS does not > yet know anything about this machine. But that should not matter when > using squirrelmail to send out an email - should it? Either it will > deliver it locally to the user I have setup, or it will deliver the > message to the real (production) MX server (right?). I can change > this if you feel it's a good test, but that will of course shut down > any real emails coming in to the rest of my real users on the > production box. > > So finally, I successfully logged into squirelmail and tried to send > myself an email and I get the same error as this original poster. > "ERROR: Message not sent. Server replied: ", and I mean there is no > error or server response shown. I can attach a screen shot if > desired, but on a mailing list I don't know if that's appropriate or > if it will even accept attachments. So let me know about that. > > When doing a "View Source", the html shows this (I hope html comes > through ok in the email): > ---snip--- > <table width="100%" cellpadding="1" cellspacing="0" align="center" > border="0" bgcolor="#ababab"><tr><td><table width="100%" > cellpadding="0" cellspacing="0" align="center" border="0" > bgcolor="#ffffff"><tr><td align="center" bgcolor="#dcdcdc"><font > color="#cc0000"><b>ERROR:</b></font></td></tr><tr><td><table > cellpadding="1" cellspacing="5" align="center" border="0"><tr><td > align="left">Message not sent. Server replied: > <blockquote> > <br /> </blockquote> > ---end--- > Essentially there is no error. > > So while trying to figure this out, I flushed all of the firewall rules > iptables -F > and then I set each policy to ACCEPT > > iptables -P INPUT ACCEPT > iptables -P FORWARD ACCEPT > iptables -P OUTPUT ACCEPT > > and tried to send an email again, but no luck, I got the same message > again. It would appear not to be a firewall problem. But I also have > a copy of my firewall rules at the bottom. > > I've setup and used qmail and squirrelmail several times on different > machines and they all worked, and I'm not sure what else is going on > here. It would appear that squirrelmail is either not communicating > with the qmail (oh by the way, yes it is running - see below), or > something is wrong with the squirrelmail version I have, or something > I don't yet understand. > > [EMAIL PROTECTED] etc]# qmailctl stat > authlib: up (pid 6111) 870 seconds > clamd: up (pid 6106) 870 seconds > imap4: up (pid 6113) 870 seconds > imap4-ssl: up (pid 6117) 870 seconds > pop3: up (pid 6099) 870 seconds > pop3-ssl: up (pid 6108) 870 seconds > send: up (pid 6102) 870 seconds > smtp: up (pid 6109) 870 seconds > spamd: up (pid 6115) 870 seconds > submission: up (pid 6104) 870 seconds > authlib/log: up (pid 6112) 870 seconds > clamd/log: up (pid 6107) 870 seconds > imap4/log: up (pid 6114) 870 seconds > imap4-ssl/log: up (pid 6098) 870 seconds > pop3/log: up (pid 6105) 870 seconds > pop3-ssl/log: up (pid 6110) 870 seconds > send/log: up (pid 6103) 870 seconds > smtp/log: up (pid 6101) 870 seconds > spamd/log: up (pid 6116) 870 seconds > submission/log: up (pid 6100) 870 seconds > > > Also, I have not yet done the "Add domain keys" portion. This should > not affect my sqmail and sending, but just so you know. > > And to try several different things, I changed my local workstation > (xp) hosts file to reflect the mail.mydomain.com and logged out of > sqmail, and relogged in and tried sending an email to myself (the user > I created earlier) and again I got the blank Error. I have also tried > to telnet into the imap and imapssl ports and also into the smtp port > from the localhost, and imap works, but smtp is refussed a connection. > I'm unclear on the IMAP commands to use in telnet so I haven't done > anything other than connect. I am also unclear what port/service > squirrelmail uses when it tries to send an email outbound, through the > server. Does it connect to SMTP with SMTP auth, or does it use IMAP > to login and then hand off the outbound email to IMAP and IMAP locally > gives it to SMTP? I just don't know. > > Is there anything else I can provide you to help me reslove this. > > --- iptables -L -n --- > [EMAIL PROTECTED] ~]# iptables -L -n > Chain INPUT (policy DROP) > target prot opt source destination > DROP all -f 0.0.0.0/0 0.0.0.0/0 > ACCEPT all -- 192.168.2.0/24 0.0.0.0/0 > DROP all -- 192.168.2.25 0.0.0.0/0 > DROP all -- 127.0.0.0/8 0.0.0.0/0 > DROP all -- 10.0.0.0/8 0.0.0.0/0 > DROP all -- 192.168.0.0/16 0.0.0.0/0 > DROP all -- 224.0.0.0/4 0.0.0.0/0 > DROP all -- 0.0.0.0/8 0.0.0.0/0 > DROP all -- 255.255.255.255 0.0.0.0/0 > DROP all -- 169.254.0.0/16 0.0.0.0/0 > DROP all -- 221.240.0.102 0.0.0.0/0 > DROP all -- 203.215.94.193 0.0.0.0/0 > DROP all -- 218.71.137.68 0.0.0.0/0 > ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 > ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 8 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:20 flags:0x17/0x02 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:21 flags:0x17/0x02 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:22 flags:0x17/0x02 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:25 flags:0x17/0x02 > ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:80 flags:0x17/0x02 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:110 flags:0x17/0x02 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:113 flags:0x17/0x02 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:143 flags:0x17/0x02 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:443 flags:0x17/0x02 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:465 flags:0x17/0x02 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:587 flags:0x17/0x02 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:993 flags:0x17/0x02 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp > dpt:995 flags:0x17/0x02 > ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state > RELATED,ESTABLISHED > REJECT all -- 0.0.0.0/0 0.0.0.0/0 state NEW > reject-with icmp-port-unreachable > > Chain FORWARD (policy DROP) > target prot opt source destination > > Chain OUTPUT (policy DROP) > target prot opt source destination > ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 > ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state > NEW,ESTABLISHED > ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 state > NEW,ESTABLISHED > ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 state > NEW,RELATED,ESTABLISHED > > Chain RH-Firewall-1-INPUT (0 references) > target prot opt source destination > --- end --- > > > Thank you, > John > > > > > > >>> Re: [qmailtoaster] Please help to fix my problem >>> Eric Shubert >>> Sun, 22 Jun 2008 08:47:16 -0700 >>> >>> Ahmed Shareef wrote: >>> Dear All, >>> >>> Please help to fix my problem I have installed new qmail server on >>> centos5 64 bit successfully but I was trying send mail from web using >>> squirrel mail but I cound.t able to send I am getting above error >>> message *Message not sent. Server replied: * >>> >>> *ERROR:* >>> >>> Message not sent. Server replied: >>> >>> Thanks >> I haven't seen a blank error messages before. Not much to go on. >> >> Have you set up DNS? >> >> -- >> -Eric 'shubes' -- -Eric 'shubes' --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
