How do you interpret the Delivered-To: header to determine what
address a message was really sent to? Specifically, I want to
figure out why the message below went to me (probably via a
-default address) instead of being discarded by Ezmlm's bounce-
handler.
home0 is the user account which
Norbert Bollow [EMAIL PROTECTED] wrote:
How do you interpret the Delivered-To: header [...]
[...]
Note: in the following, '**CENSORED**' replaces the localpart of
the subscriber email address, which consists of a reasonable
number (between 4 and 8) of lower-case Ascii letters.
Note that in
On Tue, Mar 13, 2001 at 08:46:19AM -0600, Charles Cazabon wrote:
Norbert Bollow [EMAIL PROTECTED] wrote:
How do you interpret the Delivered-To: header [...]
[...]
Note: in the following, '**CENSORED**' replaces the localpart of
If you want answers, don't hide the evidence that we may
"Mark Delany" [EMAIL PROTECTED] wrote:
On Tue, Mar 13, 2001 at 08:46:19AM -0600, Charles Cazabon wrote:
Norbert Bollow [EMAIL PROTECTED] wrote:
How do you interpret the Delivered-To: header [...]
[...]
Note: in the following, '**CENSORED**' replaces the localpart of
If you want
On Tue, Mar 13, 2001 at 05:14:48PM +0100, Norbert Bollow wrote:
[snip]
Anyway, if no one can answer the question based on the
information which I have shared (which is very likely all the
relevant data) then I can read the qmail source and find the
answer there.
It is not all the relevant
Norbert Bollow [EMAIL PROTECTED] wrote:
If you want answers, don't hide the evidence that we may need to find them.
Well, there are very good reasons for avoiding to publicly
post personal data about a subscriber to an infertility support
group.
If you cannot publicly post the
+ Peter van Dijk [EMAIL PROTECTED]:
| On Tue, Mar 13, 2001 at 05:14:48PM +0100, Norbert Bollow wrote:
| [snip]
| Anyway, if no one can answer the question based on the
| information which I have shared (which is very likely all the
| relevant data) then I can read the qmail source and find
Well, there are very good reasons for avoiding to publicly
post personal data about a subscriber to an infertility support
group.
Fine. If it needs to remain confidential, buy support from someone
identified on www.qmail.org and have them sign an NDA. Problem solved.
If you pay for support -
If that is the consensus of this list, I'll just go and read the
qmail source and not bother to contribute by posting the answer.
Is this what you want?
-- Norbert.
Norbert Bollow [EMAIL PROTECTED] wrote:
If you want answers, don't hide the evidence that we may need to find them.
Harald Hanche-Olsen [EMAIL PROTECTED] wrote:
Indeed. But I don't think we need the user name. The contents of
control/virtualdomains file seems much more relevant,
$ cat /var/qmail/control/virtualdomains
bentwater-atlanta.com:bwater25
surrogacy.org:home0
surrogacy.com:home1
We can understand your reasoning for not posting sensitive information,
however without such information it is VERY tough to decide what exactly is
the problem. Too much so to cause people to continue trying to help.
If you think that you have to mask your information perhaps you can send us
+ Norbert Bollow [EMAIL PROTECTED]:
| and ezmlm setup
|
| What are the configuration files/options that you feel should be
| shared?
Don't know, since I don't do ezmlm. But it seems very unlikely to be
an ezmlm problem anyway.
Your setup (which I won't repeat here, for brevity's sake) seems
To me, that To: field whose address must surely have come from the
envelope sender, at least shows that the message arrived at iname.net
with the correct envelope sender. But I'm willing to bet a modest
amount that iname.net mangled the envelope recipient of the bounce
into
Norbert Bollow writes:
Specifically, I want to figure out why the message below went to me
(probably via a -default address) instead of being discarded by
Ezmlm's bounce- handler.
Because mail.com is run by a bunch of weenies, who have somehow
modified their SMTP server (which *was*
14 matches
Mail list logo
