www.webdeveloper.com
Results 1 to 2 of 2

Thread: emails not sending from CentOS 5.6 VM on Win7 via PHP

  1. #1
    Join Date
    Apr 2006
    Posts
    246

    emails not sending from CentOS 5.6 VM on Win7 via PHP

    I am experiencing an issue where my CentOS 5.6 (Final) VM running on Windows 7 has stopped sending emails from my PHP code.

    I'm confident this isn't a coding issue as I have the exact same code running in my office and emails send correctly from there, hence why I believe this to be a networking/configuration issue.

    In my /etc/hosts/ file on my VM I have the following:

    Code:
    127.0.0.1 localhost.localdomain localhost
    192.168.0.9 crmpicco.co.uk m.crmpicco.co.uk dev53.localdomain
    When I run setup on my VM the DNS configuration is set to dev53.localdomain and my Primary DNS is 192.168.0.1.

    In My /var/log/maillog files I see a lot of this sort of thing:

    Code:
    Nov 19 14:36:58 dev53 sendmail[21696]: qAJEawI7021696: from=<client.care@crmpicco.co.uk>, size=12858, class=0, nrcpts=1, msgid=<1353335817.9103820024efb30b451d006dc4ab3370@PHPMAILSERVER>, proto=ESMTP, daemon=MTA, relay=localhost.localdomain [127.0.0.1]
    Nov 19 14:36:58 dev53 sendmail[21693]: qAJEawvd021693: to=newbie@fletcher.co.uk, ctladdr=client.care@crmpicco.co.uk (48/48), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=42681, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (qAJEawI7021696 Message accepted for delivery)
    Nov 19 14:36:59 dev53 sendmail[21698]: qAJEawI7021696: to=<newbie@fletcher.co.uk>, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=132858, relay=mailserver.fletcher.co.uk. [213.171.216.114], dsn=5.0.0, stat=Service unavailable
    Is this likely to be a configuration issue?

  2. #2
    Join Date
    May 2003
    Posts
    599
    service unavailable usually means there is a firewall problem somewhere I would look at seeing if you can telnet to port 25 of the destination machine from the command line of the email sserver. if it does not connect then you can assume it is a firewall problem. if the telnet attempt does connect then you know the network path for port 25 is open and the problem is probably local to the sending machine.
    We do precision guesswork

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center



Recent Articles