Dear list folk,

I'm running dbmail 2.0rc4 with Exim 4 in a cygwin environment. Slightly
outdated, I know, but it's was a bitch to compile in cygwin :/ I appolgize
if this is something that has been fixed since then.

In my setup I have Exim resolve all alias etc. before they are injected into
dbmail-smtp, so that all messages are real mailbox when they reach dbmail.
Or so I thought. Previously all my hosted domains have had a "catch-all"
mailbox that mail to unkown users was redirected to. I thought I also had so
that if there was no "catch-all" mailbox, it would fail in Exim. However, I
now added a domain where I don't want a "catch-all" mailbox, and noted to my
dismay that Exim would indeed attempt to pipe it to dbmail.

Now for the strange part, when Exim tries to deliver the message, it says
the dbmail-smtp returned code 75 ("could mean temporary error"). That
doesn't make sense to me. Skimming the logs doesn't reveal much, all I note
is that a temporary message is inserted and then deleted. There is no
indication that something goes wrong inbetween. Why will dbmail-smtp not
fail with whatever code it is that signals permanent error?

I don't have hands-on access to the box over the weekend so doing real
debugging is a real pain in the *ss, so I'm sorry that I don't provide much
details.

I know I should fix my Exim config to fail this address before injecting it
into dbmail, but I need to brush up on my dark Exim magic skillz before
attempting that. In the meantime I'm just curious if anyone know why
dbmail-smtp does this.

Regards,
Robert Andersson

Reply via email to