Bounced messages/Catch all account

[mschuler]

We have a relatively new installation (4.5.9). When we send mail to non-existent accounts within our domain, the messages do not bounce.

I don't think there currently is a catchall account, as I've never set one up (forum searches indicate there is no default).

Is there a way to determine if an account is set as catchall?

Any other ideas?

Mike

[phoenix]

A bounce will take up-to five days to get 'bounced', is there anything in the logs relating to the failed deliveries or any bounce messages or even anything in the queues?

You can check for a catch-all with the following:

zmprov gd yourdomain.com | grep zimbraMailCatchAllAddress

Believe me, you do not want to add a catch-all to your domain - it's a spammers dream.

[mschuler]

We're on the right track. (I've substituted "domain.com" for mine).

# zmprov gd domain.com | grep "CatchAll"
zimbraMailCatchAllAddress: @domain.com
zimbraMailCatchAllForwardingAddress: @domain.com

I assume I should nuke both of these? I'm sure I can search and find out how, but since you're handy...care to offer the quick command?

Mike

[phoenix]

Have a look here.

[phoenix]

You might also want to check if there is actually a catch-all account on the server with:

zmprov gaa -v | grep zimbraMailCatchAllAddress

and get rid of that entry if you find one.

[mschuler]

Thanks Bill, I had seen that before...

zmprov modifyAccount user@domain.com zimbraMailCatchallAddress ""

I'm confused why to specify the account user@domain.com? Is that supposed to be the current catchall account? If so, the command doesn't work when the current catchall is "@domain.com", as mine is.

FYI, the "zmprov gaa -v | grep Catchall" command doesn't return any entries, so thankfully that doesn't appear to be a factor.

Mike

[phoenix]

That probably means you don't have the catch-all defined on any specific account.

[mschuler]

The plot is thickening here. I'm pretty confident my problem is NOT related to a catch all account.

I originally had this server set up as "secondary" for a split domain situation (a qmail server was primary). Eventually I moved all the accounts over to my zimbra server, and changed the mx record. However, I never changed my zimbraMailTransport value back.

Currently it's set to: smtpldserver.domain.com

So, I'm relaying all outbound off my old server (not good obviously).

I have no idea what the true value should be...unless it should just be:
smtp:newserver.domain.com where newserver is the name of the machine that I'm hosting zimbra on.

Thoughts?

[phoenix]

No, it's normally unset so you can just zero that attribute. You can also do this:

zmprov md yourdomain.com zimbraMailTransport lmtp:zimbra.domain.com

[mschuler]

That was the problem. Thanks so much!!!!