On Sun, Dec 4, 2011 at 9:15 PM, /dev/rob0 <r...@gmx.co.uk> wrote:

> Please stop top-posting your replies. Thank you.
>
 I am sorry about that.

>
> On Sunday 04 December 2011 01:04:44 Ignacio wrote:
> > Fixing the application is not possible since we don't own
> > source code and owner company doesn't want to change it.
> > On the application we are just be able to set a smtp server.
>
> A good example of why not to trust proprietary software for your
> important tasks.
>
> > English is not my first language so I probably haven't explain
> > the problem very well. I will do my best right now.
>
> This is not a language barrier; this is a ... protocol barrier. It
> seems that you do not understand mail and SMTP very well. Your OP
> sounded as if the headers needed to change for some reason. Since we
> now know that envelope senders and recipients are what matters, it's
> time to move beyond.
>
> Unfortunately elsewhere in the thread you indicated that your example
> sender and recipients are not static. In this post I am again
> answering what you said, not what you might have meant.
>
I have used header_checks to add a CC field containing original sender
address. This way when there is a reply to e-mail, original sender will
receive the reply also.

>
> > The application connects to a smtp server and sent an e-mail as:
> > SENDER: user1@domain
> > TO: user2@domain;user3@domain
> >
> > From this smtp server we would like to relay e-mail to Corporate
> > Exchange server.This server needs authentication to relay e-mail.
> > Since user1 password changes every week, we would like to set a
> > generic user whose password will not change. Therefore, sender
> > must be changed to genericuser@domain.
>
> For the rewriting:
> http://www.postfix.org/ADDRESS_REWRITING_README.html#canonical
> http://www.postfix.org/postconf.5.html#sender_canonical_maps
> http://www.postfix.org/canonical.5.html
>
> For the authentication:
> http://www.postfix.org/SASL_README.html#client_sasl
> http://www.postfix.org/postconf.5.html#smtp_sasl_password_maps
>
I used generic config file to change original sender.


>
> > Also it is needed that
> > original sender (user1@domain) became a recipient of e-mail in
> > Corporate Exchange server ( I thought this could be achieved by
> > setting CC field in the e-mail, but it seems I was wrong).
>
> http://www.postfix.org/postconf.5.html#sender_bcc_maps
> containing:
> genericuser@domain                      user1@domain
>
> > Is postfix able to do this? If not, is there any other app to do
> > that?
>
> This is only going to work if the sender is always the same, but
> perhaps you can come up with a mapping which will meet your needs. If
> not, you might be stuck with going back to the software vendor and
> demanding value for your money already spent. (Good luck with that!
> They already have your money!)
>
I just did some quick tests in a test environment and it seems to work
properly with different senders. BCC map is being applied before rewriting
sender address so with a mapping like
user1@domain user1@domain
user2@domain user2@domain
...
I got a BCC sent to original sender.


>
> > Thank you very much. I hope to have explained better myself.
>
> There was no mention in this post about the senders and recipients
> changing; you consistently used the same four example addresses. So we
> could only assume the problem only involved those addresses.
> --
>    Offlist mail to this address is discarded unless
>    "/dev/rob0" or "not-spam" is in Subject: header
>

Thank you very much for your help. It was very useful to get a working
solution to solve my problem. Now I only have to set it up in production
environment. Hope it will work as well as it did in tests! :)

Reply via email to