Thanks Mike for the tip. For now, I can receive mails from local users but not from outside users. local users mean that accounts on this same server. I can't receive mail from outside users like from gmail or Yahoo!.
This is from my maillog : Dec 24 23:23:35 kspmail postfix/smtpd[24484]: connect from wproxy.gmail.com[ 64.233.184.199] Dec 24 23:23:36 kspmail postfix/smtpd[24484]: warning: lookup [EMAIL PROTECTED], NIS domain g.la, map mail.aliases: internal yp server or client error Dec 24 23:23:36 kspmail postfix/smtpd[24484]: NOQUEUE: reject: RCPT from wproxy.gmail.com[64.233.184.199]: 451 <[EMAIL PROTECTED]>: Temporary lookup failure; from=<[EMAIL PROTECTED]> to=<[EMAIL PROTECTED]> proto=ESMTP helo=< wproxy.gmail.com> Temporary lookup failure? what's that mean? On 12/23/05, M. J. [Mike] OBrien <[EMAIL PROTECTED]> wrote: > > Hi Zamri: > The fatal 554 message says your MTA is not configured to accept mail for > kspmail.g.la. > > Couple of things. I'll explain. > > Like most stuff for Postfix this is in main.cf, Zamri. main.cf is the > file > you want to modify to fix your current issue > > Find the line that starts with "mydestination =" and make sure it contains > both the domain literal (the public IP 218.111.90.178) as well as the host > name, kspmail.g.la, localhost and I'm throwing in $myhostname wildcarded > to > myhostname just in case it's different... as follows: > > mydestination = [218.111.90.178] kspmail.g.la $myhostname [127.0.0.1] > localhost > > A little tip: You can add what you need. If you use extra lines in main.cf > use a comma to end the previous and a whitespace to start the next and > nothing to end the last. :o) like this: > > mydestination =[218.111.90.178] kspmail.g.la [127.0.0.1] localhost, > g.la yahoo.com google.com someonelese.com, > afraid.org microsoftly.com google2.com someonelese2.com, > notafraid.org alittleafraid.com googley.com someonelese.net > > At postfix.org there are a gazillion documents to help you out. > > And the second thing has to do with your NAT to a LAN host and Postfix's > need to know $myhostname ... You may know this about the kind of NAT/Port > routing you are doing but a tip nevertheless: You can actually tell > Postfix > to become the WAN-side masquerade name but Postfix will freak and fail > when > the non-routable-private LAN IP resolves to something other than > $myhostname. The way around that is to use your server's host file so that > gethostname()=$myhostname. In the /etc/hosts file, add a line to point the > non-routable IP of the box to the name you give "$myhostname". The > exisiting > entry for the host can remain. (It of course can have multiple names) See > below snippets from main.cf to get a better picture. > > [ main.cf SNIP ] > # INTERNET HOST AND DOMAIN NAMES > # The myhostname parameter specifies the internet hostname of this > # mail system. The default is to use the fully-qualified domain name > # from gethostname(). $myhostname is used as a default value for many > # other configuration parameters. > > myhostname = kspmail.g.la > > # The mydomain parameter specifies the local internet domain name. > # The default is to use $myhostname minus the first component. > # $mydomain is used as a default value for many other configuration > # parameters. > > mydomain = g.la > > # SENDING MAIL > # The myorigin parameter specifies the domain that locally-posted > # mail appears to come from. The default is to append $myhostname, > # which is fine for small sites. If you run a domain with multiple > # machines, you should (1) change this to $mydomain and (2) set up > # a domain-wide alias database that aliases each user to > # [EMAIL PROTECTED] > > myorigin = g.la > > [ end main.cf SNIP ] > > > When you get a little more savvy you might install DBMA http://dbma.ca > which does your MTA destinations automatically for as many thousand or few > virtual domains you wish to host. :o) > > Anyway. Don't despair. Sounds like you are on the verge of having a fully > functional Postfix/DBmail setup. > > > Happy Christmas to Zamri and all.. > > > Mike > > > ----- Original Message ----- > From: "zamri" <[EMAIL PROTECTED]> > To: "DBMail mailinglist" <[email protected]> > Sent: Friday, December 23, 2005 2:51 AM > Subject: Re: [Dbmail] problem receiving mails > > > thanks Mike for the answer. Now i'm moving to the next step. My box is > inside LAN and behind a firewall. The firewall has a public IP. I set > iptables to forward mail to port 25 and 143 from firewall to my box. I > have > also setup DNS MX record using the firewall's IP and domain name. > > Sending mails work OK but receiving mails NOT OK. I got this in my maillog > : > > PERM_FAILURE: SMTP Error (state 9): 554 <[EMAIL PROTECTED]>: Relay access > denied > > I am a bit blur of Postfix. Can anyone tell me which part of config files > should I alter? > > > On 12/22/05, M. J. [Mike] OBrien <[EMAIL PROTECTED]> wrote: > > Hello zamri; > Without any knowledge of your LAN setup, troubleshooting your LAN mail is > not possible. > > On your DNS question, mail won't be delivered without proper DNS zone. > That > is not true for receiving mail (IMAP or POP) but mail not delivered won't > be > received. Your LAN DNS Zone must have an MX record for SMTP to work. (If > it's all dynamic (DHCP) then of course it won't work.) > > A precautionary step: If you are truly doing everything from and as > localhost use 127.0.0.1 not "localhost" as the hostname in all configs to > avert a no-DNS problem. > > Your test environment, testing an unknown with an unknown, is somewhat > flawed. By using a new setup of Squirrelmail you are testing an unknown > DBMail system with an unknown MUA -- you'll go "WebMail Nuts" :o). > > Try using a known MUA like T-Bird or Outlook Express or Mozilla Mail or > whatever. (Did you telnet into your DBMail system to check mail?) > > Squirrelmail is usually more than a five-minute installation. An awesome > application once finished, sometimes it can be a devil to get it > configured > and working the way you want it with the many plugins and customizations > available. Until everything is stabilized it is a plug-in breaking things > or > the core installation or a missing PHP module in the build or something > else. Conclude that you should start with a minimal (basic) installation > and > add plug-ins one by one. (Don't test it against an untested DBMail > installation. ) > > > so: > 1) Fix DNS > 2) Use a working MUA for tests and get DBMail working the way you like > it.. > 3) Then have fun with the Squirrelmail manuals. :o) > > > > best... > Mike > > > > > > > ----- Original Message ----- > From: "zamri" <[EMAIL PROTECTED]> > To: "DBMail mailinglist" <[email protected] > > Sent: Wednesday, December 21, 2005 10:18 PM > Subject: [Dbmail] problem receiving mails > > > hi all, > > I have setup dbmail as instructed in INSTALL.postfix and also have setup > dbmail tables successfully. I use SquirrelMail to access emails as a > frontend. The problem that I'm facing is I can't receive emails. FYI I > want > to test the system in my LAN first. So it won't need to setup any MX > record > for it. Am I right? The hostname and the domain is localhost and > localdomain > respectively. Are there any options that I need to setup for squirrelmail > parts specific to dbmail ? I can;t find one except for the server setting > that I set to others. I set the maillog and it said 550. Do i need to set > local_recipient_maps? > > My system: > Slackware 10.2 > dbmail-2.0.7 (use dbmail-imapd & dbmail-lmtp) > postfix-2.2.7 > SquirrelMail-1.4.5 > > > > > -------------------------------------------------------------------------------- > > > > _______________________________________________ > Dbmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > > > _______________________________________________ > Dbmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > > > > > > -------------------------------------------------------------------------------- > > > _______________________________________________ > Dbmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > > _______________________________________________ > Dbmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail >
