You should direct your responses at the whole list so others who might be able to help you will get more information about your problem. I don't have any more advice. Sorry.

-Jared

On Apr 10, 2004, at 12:24 AM, BJ Quinn wrote:

right, I'm not having that problem -- everything works fine except for the
fact that the confirmation email comes in with the wrong "from" address.
there aren't any errors, and TMDA is actually working as expected, except
for the fact that it doesn't seem to want to let me configure what the
"from" address says for its confirmation messages, so when the 1st user gets
the confirmation message from the 2nd user, it's from the forwarded address,
not the original address, and the 1st user therefore doesn't allow it
through, because that address was never whitelisted!


-BJ

----- Original Message -----
From: "Jared" <[EMAIL PROTECTED]>
Newsgroups: gmane.mail.spam.tmda.user
Cc: "TMDA Users" <[EMAIL PROTECTED]>
Sent: Friday, April 09, 2004 12:50 PM
Subject: Re: Confirmation message From: header problem


Well, the forwarding server mattered in my case because procmail would
rewrite the envelope sender to be the user that is forwarding the mail.
So everything was whitelisted because the envelope sender of all the
mails was the same, trusted address.


I really don't know if this is related but are you taking care to do
this:
<http://tmda.net/faq.cgi?req=show&file=faq04.011.htp>

Beyond that, I'm not sure what the problem could be.

-Jared

On Apr 9, 2004, at 10:34 AM, BJ Quinn wrote:

Well, first of all, the server forwarding the mail is qmail, and I'm
using
dot-qmail files to forward the mail. But why would the forwarding
server
matter? Everything works fine until mail reaches the server that it is
forwarded to, and TMDA sends out a confirmation request with the
domain of
the final destination server - the recipient of the confirmation
request
gets it (albeit after it's forwarded to him), but it's not the
forwarding
server that is changing the "from" header for the confirmation request
is
it? Isn't it TMDA on the final destination server that is assuming
that you
want to send out a confirmation request "from" the email address the
mail
ended up at?


-BJ Quinn

----- Original Message -----
From: "Jared" <[EMAIL PROTECTED]>
Newsgroups: gmane.mail.spam.tmda.user
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, April 08, 2004 10:08 PM
Subject: Re: Confirmation message From: header problem


How are you forwarding the mail? If you are using procmail, then there
is a way to reset the envelope sender. Check the archives. I have had
this exact issue before. If you're not using procmail, then I'm not
sure how to fix it but I'm sure it's the same problem.


Pertinent archived message:
<http://mla.libertine.org/tmda-users/2004-01/msg00527.html>

-Jared

On Apr 8, 2004, at 9:19 PM, BJ Quinn wrote:

Ok here's my problem.  I have an email server with TMDA installed.
On
it
are two email addresses both of which have TMDA enabled.  Both are
also
forwarded from another server.  So what happens is...

There are 2 servers.
originaldomain.com is the destination for all email for these 2 users
forwardeddomain.com is just where that email is forwarded to and
where
TMDA
is installed


I send [EMAIL PROTECTED] an email from user2, using
forwardeddomain.com as the outgoing SMTP server, but the MUA is
configured
to use [EMAIL PROTECTED] as the From address.
[EMAIL PROTECTED] gets put on on user2's whitelist because of
the
bare=append TMDA rule.


The email gets forwarded from [EMAIL PROTECTED] to
[EMAIL PROTECTED] (the one TMDA is on)  user1 doesn't
recognize
[EMAIL PROTECTED] in his whitelist, so user1 sends
[EMAIL PROTECTED] a confirmation request.  Up until this
point,
everything's fine.  However, user1's confirmation request gets sent
with a
From header of [EMAIL PROTECTED] (It doesn't seem to matter
what I
put in the outgoing rules file -- does this apply to confirmation
requests?)

Now, user2 gets a confirmation request from
[EMAIL PROTECTED],
which
he's never heard of, so he just drops it in the pending queue, and
neither
user ever hears from each other. How do I change this so user2 gets
a
confirmation request from [EMAIL PROTECTED], so it gets
through,
because that address has already been added to user2's whitelist?


-BJ Quinn



_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users






_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users

Reply via email to