Thanks Viktor. That make thing clear.
On Tuesday, December 17, 2019, Viktor Dukhovni
wrote:
> On Tue, Dec 17, 2019 at 01:49:00AM +0100, Ralph Seichter wrote:
> > * Tom Blackwood:
> >
> > > In the outgoing message, what does "sender:" header stand for?
> >
On Tue, Dec 17, 2019 at 01:49:00AM +0100, Ralph Seichter wrote:
> * Tom Blackwood:
>
> > In the outgoing message, what does "sender:" header stand for?
>
> https://tools.ietf.org/html/rfc2822#section-3.6.2
These days one should quote 5322 instead, but perhaps a more
* Tom Blackwood:
> In the outgoing message, what does "sender:" header stand for?
https://tools.ietf.org/html/rfc2822#section-3.6.2
-Ralph
Hello
In the outgoing message, what does "sender:" header stand for?
Should it be set to envelop-mailfrom address?
Regards.
Tom
d, To, CC, MIME-Version, Content-Type, Content-
> > >Transfer-Encoding, Content-ID, Content-Description,
> > >Content-Disposition, In-
> > >Reply-To and References.
> > >
> > >This is still leading to the postfix mailing list failing DKIM once
> > >it
ply-To and References.
> >
> >This is still leading to the postfix mailing list failing DKIM once
> >it's added
> >a Sender header for owner-postfix-us...@postfix.org. Should I stop
> >oversigning
> >the Sender header? rfc5322 says the Sender header is unique if
Richard James Salts writes:
> This is still leading to the postfix mailing list failing DKIM once
> it's added a Sender header for owner-postfix-us...@postfix.org. Should
> I stop oversigning the Sender header?
Signing the following headers works for me and does not break DKIM:
A
te, Message-id, To, CC, MIME-Version, Content-Type, Content-
>Transfer-Encoding, Content-ID, Content-Description,
>Content-Disposition, In-
>Reply-To and References.
>
>This is still leading to the postfix mailing list failing DKIM once
>it's added
>a Sender header for own
t; Transfer-Encoding, Content-ID, Content-Description, Content-Disposition, In-
> Reply-To and References.
>
> This is still leading to the postfix mailing list failing DKIM once it's added
> a Sender header for owner-postfix-us...@postfix.org. Should I stop oversigning
> the Sender
n, In-
Reply-To and References.
This is still leading to the postfix mailing list failing DKIM once it's added
a Sender header for owner-postfix-us...@postfix.org. Should I stop oversigning
the Sender header? rfc5322 says the Sender header is unique if it exists so if
there was a sender header
I am wondering if there is an easy way to add a BCC to an email in the
sender/header checks, similar to REDIRECT but to send it to my redirect email
and to the original recipient. I'm aware of recipient_bcc_maps but if I
understand it correctly, that adds BCC to all emails of a parti
* Sebastian Wiesinger [2015-09-25 12:55]:
> * Wietse Venema [2015-09-18 15:51]:
> > Majordomo uses the following: Reply-To: (most preferred), From:,
> > and Apparently-From: (least preferred). It does not use Sender:.
> > The list manager runs on someone elses system. I would not want
> > to run
Sebastian Wiesinger:
> No, it's the other way around. I want off-list replies to my From:
> address (which is my main mailaddress). But I'm subscribed to the ML
> with the address in the Sender: header (which is unique for each ML).
>
> Other MLs use the Sender: header in
he other way around. I want off-list replies to my From:
address (which is my main mailaddress). But I'm subscribed to the ML
with the address in the Sender: header (which is unique for each ML).
Other MLs use the Sender: header in addition to the From: to check if
the sender is authorized to
Sebastian Wiesinger:
> Hello,
>
> a while ago I changed my mail configuration for mailinglists. I have
> individual mail addresses for every mailing list and the configuration
> now looks like this:
>
> From: Sebastian Wiesinger
> Sender: postfix-us...@ml.karotte.org
>
> This has the advantage
Hello,
a while ago I changed my mail configuration for mailinglists. I have
individual mail addresses for every mailing list and the configuration
now looks like this:
From: Sebastian Wiesinger
Sender: postfix-us...@ml.karotte.org
This has the advantage that off-list answers go to my main
maila
started interpreting mail from this address as
being an alias of another address, and added the Sender header (which
was what appeared in my mail).
The solution was simply to remove (comment out, in my case) the
relaying for this address from my Postfix configuration, and let it go
out dir
Neil wrote:
By pure luck, I had an epiphany and figured it out.
good. Can you provide details so that other people who get into the same
problem find the answer in the archives?
On 6 Nov 2008, at 13:47, Neil wrote:
On 6 Nov 2008, at 09:23, Brian Evans - Postfix List wrote:
Neil wrote:
At what point does the "Sender: " header usually get added to the
mail?
Because some (and so far the only pattern is "It shows up when
subscribing to the SpamAssass
ne) also provide a Sender: header.
Wietse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Evans - Postfix List wrote:
[...]
> It is added by the mail client, not the server.
Can you please show me some example?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.or
d by mailing lists, etc. But
it's that the Sender header contains one of my email addresses, and
not the one I'm actually sending from...
On 6 Nov 2008, at 09:23, Brian Evans - Postfix List wrote:
Neil wrote:
At what point does the "Sender: " header usually get added to the
Neil wrote:
At what point does the "Sender: " header usually get added to the mail?
it's added by the sender.
Because some (and so far the only pattern is "It shows up when
subscribing to the SpamAssassin Mailing List.") of my mails at getting
that header attache
Neil wrote:
> At what point does the "Sender: " header usually get added to the mail?
>
> Because some (and so far the only pattern is "It shows up when
> subscribing to the SpamAssassin Mailing List.") of my mails at getting
> that header attached (and with
At what point does the "Sender: " header usually get added to the mail?
Because some (and so far the only pattern is "It shows up when
subscribing to the SpamAssassin Mailing List.") of my mails at getting
that header attached (and with a bad address) and it's a
25 matches
Mail list logo
