[SOLVED] can't send to an entire domain...

[REMcycle]

Hi everyone.

When I use our new Zimbra system to send mail from user@waastaff.com to our original domain, uwalumni.com, I get this response IMMEDIATELY:



This is the mail system at host mail.waastaff.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

<user@uwalumni.com>: uwalumni.com
Reporting-MTA: dns; mail.waastaff.com
X-Postfix-Queue-ID: F13062008B25
X-Postfix-Sender: rfc822; user@waastaff.com
Arrival-Date: Mon, 14 Jul 2008 16:33:10 -0500 (CDT)

Final-Recipient: rfc822; user@uwalumni.com
Original-Recipient: rfc822;user@uwalumni.com
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; uwalumni.com



This couldn't be more vague. Anyone have any ideas? I've checked every log i can find and can't seem to find anything .

Thanks!

[y@w]

So, are both these domains on the same system, or is the waastaff.com on a new server and the other domain on another?

[REMcycle]

They're on seperate servers.


A little more background...for now, the DNS is parked offsite with the domain registrar. I'm at the University of Wisconsin in a non-profit, which means that the legal dept. here has to make sure it's okay for our waastaff.com zone to be hosted by wisc.edu's DNS.

The mail server is however using the local wisc.edu DNS as a forwarder, while the A and MX records for waastaff.com are parked at the domain registrar.

Still I can't see this making a difference, as every other domain i've tried to send mail to actually works.

[y@w]

Ok, so you've verified that doing an MX record from each server resolves correctly? Also, have you created the waastaff.com domain on your new Zimbra system?

[REMcycle]

Thanks for the response...

Yes, I can resolve the MX for each domain from each side.

I'm starting to think that the spamcatcher on the uwalumni.com side is stopping these mails, as this happened before I bought and installed the commercial SSL cert.

Every mail i sent to, say msn.com from waastaff.com ended up straight in the Junk folder before I bought the cert. Maybe we just got cut off?

Think I'll call over there.

[REMcycle]

Well that was stupid, but yes, it's solved.

I put uwalumni.com in the domains list on the zimbra server because I was HOPING that my users would be able to send as a user from that domain while we transition from one domain to another.

In my ignorance, i was telling Zimbra to take every message sent to user@uwalumni.com and deliver it to itself. When the user didn't have that domain name set up as an alias, it bounced.

Duh.

what gave it away finally was checking /var/log/maillog and discovering that uwalumni.com was resolving as 127.0.0.1 by Zimbra.

Sorry for wasting your time. Thanks for the help.

[mmorse]

Don't know your entire setup but might be able to configure a Split Domain - Zimbra :: Wiki. Or add aliases to each account. Or just remove that domain from ZCS (which sounds like that's what you choose to do).