Author Topic: Mail not sending, permissions problem  (Read 1801 times)

bruppi

  • Posts: 2
    • View Profile
Mail not sending, permissions problem
« on: July 22, 2008, 10:00:30 am »
I recently changed servers and have installed LMP, the initial test was successful (minus the bounce cgi configuration) but incredibly slow, took overnight to process a list of 1500. I followed DW's recommendations and added the concurrency updates and applied his qmail patch. Since the patch has been applied no mail will go through, it just sits in the remote queue.

When I tail -f the maillog it returns for each email:
Jul 22 09:09:03 myhostname qmail: 1216735743.590034 starting delivery 3: msg 3819542 to remote me@mydomain.com
Jul 22 09:09:03 myhostname qmail: 1216735743.590048 status: local 0/100 remote 1/400
Jul 22 09:09:03 myhostname qmail: 1216735743.597923 delivery 3: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/
Jul 22 09:09:03 myhostname qmail: 1216735743.597964 status: local 0/100 remote 0/400

Any thoughts?

DW

  • Administrator
  • Posts: 3787
    • View Profile
    • https://legacy.listmailpro.com
Mail not sending, permissions problem
« Reply #1 on: July 22, 2008, 11:00:58 am »
I have responded via the support ticket.  I think the common "queue-repair.py" script might be able to fix this.

Regards
Dean Wiebe
ListMailPRO Author & Developer - Help | Support | Hosting

bruppi

  • Posts: 2
    • View Profile
Mail not sending, permissions problem
« Reply #2 on: July 22, 2008, 07:54:03 pm »
I tried the patch and also double check the permission and no help. Now I've lost the ability to send phpmail() and when I try to send a message via telnet it throws a rcpthosts error.

maillog now shows:

Jul 22 21:47:44 myhost qmail: 1216781264.793692 delivery 8: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/


It was sending before I did patch the first time and a ./installcheck throws back a ton of owner/group problems.

I think it may be time for a remove and reinstall but i'm not 100% sure how to do that on plesk and not screw it up.