public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Vinícius Ferrão" <viniciusferrao@if.ufrj.br>
To: "<gentoo-server@lists.gentoo.org>" <gentoo-server@lists.gentoo.org>
Subject: Re: [gentoo-server] Disclaimer to forwarded mails to external domain?
Date: Mon, 3 Sep 2012 21:07:49 +0000	[thread overview]
Message-ID: <F2EE36C002E1514EAC274601D572FBB733073813@orgrimmar.if.ufrj.br> (raw)
In-Reply-To: <5017FAD1.2080708@orlitzky.com>


[-- Attachment #1.1: Type: text/plain, Size: 2359 bytes --]

I don't know what happened to my last message but it was never delivered. I'm sending it again:

=====================

Answers above:

On Jul 31, 2012, at 12:33 PM, Michael Orlitzky <michael@orlitzky.com>
wrote:

> On 07/31/12 01:57, Vinícius Ferrão wrote:
>> Hello dudes,
>> 
>> I'm considering to implement a new feature in my Postfix Mail
>> Filtering Gateway.
>> 
>> It would be great to add a disclaimer note to forwarded mails to an
>> external domain. Since I'm already running amavisd-new, with all his
>> friends, I was thinking to invite alterMIME to the party.
> 
> Is this so that people won't mark those messages as spam (thus pinning
> the blame on your mail server)?
> 
> If so, let me assure you that it will be ignored. I've even called some
> of our customers with forwarded addresses on the phone and personally
> asked them to stop marking stuff as spam. They still ignore me.

Actually we have user that automatic redirect messages to their personal accounts. And this behaviour is not 100% approved by the university. So I want to put a disclaimer in those people, as example: john@university.com redirects to john@gmail.com. I want to put a disclaimer in *ALL* messages redirected to external domains.

> 
>> The tricky part is how to detected which messages are automatically
>> forwarded to an external domain.
> 
> If this is a filtering gateway, I'm guessing all of your recipients are
> listed in relay_recipient_maps? If so, you should be able to override
> the default_transport (which defaults to smtp:).
> 
> For example, you could set up a disclaimer-only instance of amavis on
> port 10029, and then set the default_transport to
> smtp:[localhost]:10029. I would beware of unintended consequences,
> though. You're liable to stick a disclaimer on some things by accident.

There's no recipient check in my mail filtering gateway. I leave this job to my final destination. It's not easy to get the final destination since we have some different end destination servers and a separate mailman server.

I can't really understand your example: in this situation everything will be "disclaimed"; and I just want to modify messages to people that receive their corporate emails in their personal account.

Thanks for you help and sorry about the delay to answer your message.
Vinícius

[-- Attachment #1.2: Type: text/html, Size: 2923 bytes --]

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2354 bytes --]

  reply	other threads:[~2012-09-03 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31  5:57 [gentoo-server] Disclaimer to forwarded mails to external domain? Vinícius Ferrão
2012-07-31 15:33 ` Michael Orlitzky
2012-09-03 21:07   ` Vinícius Ferrão [this message]
2012-09-04 14:14     ` Michael Orlitzky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F2EE36C002E1514EAC274601D572FBB733073813@orgrimmar.if.ufrj.br \
    --to=viniciusferrao@if.ufrj.br \
    --cc=gentoo-server@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox