HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   Developers' Forum (http://www.howtoforge.com/forums/forumdisplay.php?f=33)
-   -   ISPConfig3 interesting mail issues... (http://www.howtoforge.com/forums/showthread.php?t=32113)

ghost1227 5th March 2009 07:20

ISPConfig3 interesting mail issues...
 
I just started using ISPConfig3, and so far I love it! I am having an interesting issue though, I set up a domain and an email account to go with it... I can send fine from the email account, but whenever someone replies they get the following message back from the server.

Code:

This is the mail system at host xxx.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                  The mail system

<yyy@xxx.com>: unknown user: "yyy"



Reporting-MTA: dns; xxx.com
X-Postfix-Queue-ID: A6AF92870E
X-Postfix-Sender: rfc822; yyy@zzz.us
Arrival-Date: Thu,  5 Mar 2009 05:12:48 +0000 (UTC)

Final-Recipient: rfc822; yyy@xxx.com
Original-Recipient: rfc822;yyy@xxx.com
Action: failed
Status: 5.1.1
Diagnostic-Code: X-Postfix; unknown user: "yyy"

Anyone have any idea what's wrong here?

falko 6th March 2009 14:27

Does the MX record for xxx.com point to the correct server? You can check that with
Code:

dig mx xxx.com

quentusrex 10th March 2009 00:16

I'm having the same issue.... dig mx mydomain.com works fine...

Here is what I'm getting when sending to test@mydomain, when it should be caught and sent to the mail forwarder. The catch-all is exposed, when it shouldn't be...
================================================== ===========

This is the mail system at host mail.mydomain.net.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

<webmaster@mydomain.com> (expanded from <test@mydomain.com>): user
unknown. Command output: ERR: authdaemon: s_connect() failed: Permission
denied Invalid user specified.

Final-Recipient: rfc822; webmaster@mydomain.com
Original-Recipient: rfc822;test@mydomain.com
Action: failed
Status: 5.1.1
Diagnostic-Code: x-unix; ERR: authdaemon: s_connect() failed: Permission denied
Invalid user specified.


---------- Forwarded message ----------
From: ********@gmail.com>
To: test@mydomain.com
Date: Mon, 9 Mar 2009 15:09:49 -0700
Subject: asdf
asdf

till 10th March 2009 00:25

@ghost1227: please take a look in the mail_user table and make sure that you have a record there with the email address "yyy@xxx.com".

@quentusrex: Is the email address test@mydomain listed in the mail user table?

quentusrex 10th March 2009 01:51

Yes, it's in here. I added the vmail user to the /etc/postfix/master.cf file in the maildrop line... Now I don't get the same error...

Now I see where maildrop is suppose to deliver the mail, and I never see a log entry or the e-mail after that...

quentusrex 10th March 2009 01:53

I changed it from

# maildrop. See the Postfix MAILDROP_README file for details.
# Also specify in main.cf: maildrop_destination_recipient_limit=1
#
maildrop unix - n n - - pipe
flags=R user=vmail argv=/usr/bin/maildrop -d ${recipient} ${extension} ${recipient} ${user} ${nexthop} ${sender}



to



# maildrop. See the Postfix MAILDROP_README file for details.
# Also specify in main.cf: maildrop_destination_recipient_limit=1
#
maildrop unix - n n - - pipe
flags=R user=vmail argv=/usr/bin/maildrop -d vmail ${recipient} ${extension} ${recipient} ${user} ${nexthop} ${sender}

ghost1227 10th March 2009 04:40

Resolved
 
My issue has been resolved. It was an issue with the myhostname variable in main.cf

till 10th March 2009 11:24

Quote:

Now I see where maildrop is suppose to deliver the mail, and I never see a log entry or the e-mail after that...
Thats because you added "vmail" to the maildropline. The order of the parameters matters, so if you add vmail there all other parameters are shifted to the right and so all delivery information is wrong and the email gets lost.

I use the maildrop line "flags=R user=vmail argv=/usr/bin/maildrop -d ${recipient} ${extension} ${recipient} ${user} ${nexthop} ${sender}" on seceral mail systems in production without an error so there is no need to change it and changing it will just result in loosing emails as you see.

bigshiny90 31st March 2009 05:18

my solution
 
so i was getting the same error on my new ispconfig3 install.

here's what i did. in my case, the problem only arose when i was making an email with the same domain as the server itself. ie. blah@xxx.com and my servers hostname is xxx.com. all other new emails could have email sent to them without the email being refused.

i simply removed my server hostname from mydestination in postfix's main.cf. i guess the postfix installation or the ispconfig installation set this. i don't know if this creates any problems otherwise, but everything works now. i had previously did a manual postfix setup on another server (without ispconfig), and the 'mydestination' field also did not have the hostname.

maybe this helps somebody.

okay out...

quentusrex 3rd April 2009 19:37

I'm still getting issues. I send e-mail through my gmail account to any of my domains and I still get teh same e-mail back...

user unknown. Command output: ERR: authdaemon: s_connect() failed: Permission
denied Invalid user specified.


All times are GMT +2. The time now is 01:55.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.