Stroller wrote:
On 21 Oct 2008, at 17:24, Brian Evans - Postfix List wrote:
[...]
To get some notifications, look at notify_classes (
http://www.postfix.org/postconf.5.html#notify_classes ).
Suggest 'notify_classes = resource, software, 2bounce' until you solve
the real first problem and contact the source of the 2nd.
2bounce allows double bounces to be saved to a mailbox.
The 2bounce recipient can be defined by 2bounce_notice_recipient
I think what you're saying is that I'll NEED to save the bounces to a
mailbox.
Actually, I think he's suggesting that you direct double bounces (messages
generated because of a bounce being rejected) to some other address. That
does not have to be a local mailbox. Unless...
Currently:
$ postconf | grep -e notify_classes -e 2bounce
2bounce_notice_recipient = postmaster
notify_classes = resource, software
$
If I just add 2bounce into the notify_classes then it'll attempt to
deliver in the same way, by SMTP, and the message will again be rejected
by mail.btopenworld.com. Right?
Maybe, maybe not. If the target address is one that the BT/Yahoo server
considers local, it probably won't reject the message. If you use an address
that you don't route through that server, you don't have to worry about it.
It isn't clear how these bounces are happening in the first place. You
ignored http://www.postfix.org/DEBUG_README.html#mail and it is clear that
this Postfix instance isn't being used in the manner that the default MacOS
X Postfix configuration envisions. If this is MacOS X *Server* then that
would also be relevant, because it has a very different mail setup from the
"client" version.
Unfortunately mailboxes on OS X are an ugly mess.
Not really. There just isn't a GUI for them. Apple Mail (aka "Mail.app")
doesn't know anything about the system mailboxes in /var/mail because it is
a POP and IMAP client, and the normal usage of a MacOS X machine never
actually delivers anything to local system mailboxes.
As far as I can see
I'd have to deliver to
/Users/fred/Library/Mail/[EMAIL PROTECTED]/INBOX.mbox/Messages/
DO NOT DO THAT!
That's where Apple Mail keeps its local message store. The details of how
~/Library/Mail is used are not documented, no locking system for other
programs to make changes exists, and it DOES NOT follow any standard mail
storage standard. Dropping messages there with Postfix simply will not work.
And of course this is (once again) prone to breakage if the user (for
instance) deletes this email address & adds a new one.
That's a clue not to try to use it.
The overall fix to this problem is to look at what the user wants to do with
mail and match the external services and Postfix configuration to that need.
This user is doing something unusual, and it is impossible for anyone on
this list to guess what that is because you've not told us. It's great that
you've figured out the authentication issue and probably overcome the
current problem, but you probably want to look at this from the top down
rather than just firefighting issues as they pop up, because it seems like a
setup that will generate steady stream of little breakages.
