Vm to Email Not Working

Discussion in 'General' started by tknman0700, Dec 17, 2009.

  1. tknman0700

    Joined:
    Oct 30, 2009
    Messages:
    49
    Likes Received:
    0
    I have read through the EWT manual but still no luck..
    Are there any debug steps that I can take on figuring out why my voicemails are not coming through as emails?
    I see the maillog files.. I tried to delete them because they were so large that getting them to my machine over my wan link was slow.
    There is now nothing in the maillog files...

    How can I go about understanding why my mail is not being delivered?
    Thanks
     
  2. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    The problem was revealed in the files you deleted, you deleted maillog itself, this will disable the logging, easy answer reboot your machine, harder but faster answer, type man logrotate in bash and follow it.
     
  3. tknman0700

    Joined:
    Oct 30, 2009
    Messages:
    49
    Likes Received:
    0
    Awesome.. box is rebooting now
    Will try again..

    mail is working because i can send by mail -s "test" me@mydomain.com and it works fine, but asterisk no email the voicemail.
     
  4. tknman0700

    Joined:
    Oct 30, 2009
    Messages:
    49
    Likes Received:
    0
    found this when i try to leave msg

    Dec 17 13:08:51 StLouisElastix postfix/postdrop[3276]: warning: mail_queue_enter: create file maildrop/293667.3276: Permission denied
     
  5. tknman0700

    Joined:
    Oct 30, 2009
    Messages:
    49
    Likes Received:
    0
    [root@StLouisElastix log]# postfix check
    postfix/postfix-script: warning: not owned by group postdrop: /var/spool/postfix/public
    postfix/postfix-script: warning: not owned by group postdrop: /var/spool/postfix/maildrop

    There is no postdrop group to grant access though
     
  6. tknman0700

    Joined:
    Oct 30, 2009
    Messages:
    49
    Likes Received:
    0
    I chmod these folders to 777 and it seems to correct the problem but there is no postgroup to grant access to so I am confused to the correct resolution.
     
  7. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    There should be

    cat /etc/group|grep post

    should return something like

    mail:x:12:mail,postfix
    postdrop:x:90:
    postfix:x:89:

    if so

    chown postfix:postdrop /var/spool/postfix/public
    chown postfix:postdrop /var/spool/postfix/maildrop

    should fix it.
     
  8. tknman0700

    Joined:
    Oct 30, 2009
    Messages:
    49
    Likes Received:
    0
    ok that got it.. the smiley messed it up through...
    Code:
    chown postfix:postdrop /var/spool/postfix/public
    chown postfix:postdrop /var/spool/postfix/maildrop
     
  9. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    You should chown 755 immediately or risk . . .
     
  10. tknman0700

    Joined:
    Oct 30, 2009
    Messages:
    49
    Likes Received:
    0
    Thank you for your help here... I am unsure how something like this would have happened but I appreciate your help!
     
  11. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    :) :)

    It is my experience that machines do what you tell them, not what you want them to do. Deep introspection will perhaps reveal the steps you (or some rogue agent) did to create this mis-configuration.

    Glad you got it working.
     

Share This Page