Outbound queue problem & fetchmail question

[phoenix]

I've installed the latest M4_62 version of Zimbra this morning on a newly installed CentOS4 server. During the setup of Zimbra & fetchmail I had a slight problem which meant that mail (spam, actually) that should have gone to my local mailbox is being forwarded to another ISP (I think it was bounced). Unfotunately this mail has been in the outbound queue all day and Zimbra keeps trying to deliver it, is there any way in Zimbra to delete this mail from the queue? If it's not possible in Zimbra what else could I do to get rid of this junk? Will there be any feature added to Zimbra that will allow the management of the outbound queue for situations such as this?

I'm assuming this isn't a Zimbra problem but any help would be appreciated. I use webmin to set-up and manage fetchmail from several ISP accounts, when I had Zimbra installed on my last server I only had to enter the local username in the webmin/fetchmail config to get it delivered locally to the FQDN mailbox. On this new server I've done the same thing but fetchmail tries to deliver the mail to username@localhost rather than the FQDN mailbox name. This has caused the problem of getting mail bounced (which I've mentioned above), can anyone suggest what I may have done wrong? I've been scratching my head about this all day. I can't see anything strange in the logs other than the failed deliver messages.

[marcmac]

su - zimbra
man postsuper
for the full answer.

short answer:
postqueue -p to get queue ids
postsuper -d <qid> to delete it

As for the delivery problems - did you have dns lookups disabled on your old box? Are they enabled on the new box? Can you send mail to these accounts from the local system?

[phoenix]

Originally Posted by marcmac

su - zimbra
man postsuper
for the full answer.

short answer:
postqueue -p to get queue ids
postsuper -d <qid> to delete it

Thanks for that, I'll check it out.

Originally Posted by marcmac

As for the delivery problems - did you have dns lookups disabled on your old box? Are they enabled on the new box? Can you send mail to these accounts from the local system?

No, the DNS setting was enabled on both systems as I'm running BIND on them. I'm not sure what happened but there was an initial problem with BIND set-up so I removed it and fetchmail and Zimbra (deleted all the zimbra files), I then reinstalled BIND, fetchmail and Zimbra but still no joy delivering to just the localusername from fetchmail. Yes, I can send email locally to the users without problems. Actually this is the same box, a slight cock-up on my part meant a clean install of CentOS and Zimbra.

[marcmac]

So, fetchmail is acting differently.

Did the hostname (as returned by the hostname command) change?

Is /etc/hosts different?

[phoenix]

No, there's nothing different - it still returns a FQDN of the hostname & domain. I did keep a copy of the files from the original server and the /etc/hosts file is identical to the original server.

[marcmac]

different CENTOS versions? webmin versions? fetchmail versions? I know little about centos, and nothing about webmin.

I did find this in the fetchmail man page:

-D <domain> | --smtpaddress <domain>
(Keyword: smtpaddress) Specify the domain to be appended to
addresses in RCPT TO lines shipped to SMTP. The name of the SMTP
server (as specified by --smtphost, or defaulted to "localhost")
is used when this is not specified.

[phoenix]

As far as I can see everything is the same (certainly CentOS, BIND & fetchmail are the same) but the results would seem to indicate otherwise. I don't want to waste your time on a trivial problem so I'll dig around some more, I only asked just in case it was a stupid error on my part. Thanks for the info on fetchmail I'll see what i can do with that.

Thanks also for that info on the mail queue, it's now been removed. Do you plan to have any queue management features for deleting this kind of rubbish in Zimbra in the longer term?

[marcmac]

We've talked about it, but it's not a high priority, since the functionality is there in the postfix CLI tools.