Scott Neader writes:
> Hi Stephen (and all). Indeed, I am having MUCH luck with this! First, the
> option to base64 encode the recipient's email as a new header with the
> RCPT_BASE64_HEADER_NAME config setting (discussed in my last post) is
> working great! In addition, as you mentioned, I
On Fri, Aug 9, 2019 at 2:55 AM Stephen J. Turnbull <
turnbull.stephen...@u.tsukuba.ac.jp> wrote:
> Have you had any luck with this in the last couple of days?
>
Hi Stephen (and all). Indeed, I am having MUCH luck with this! First, the
option to base64 encode the recipient's email as a new heade
Have you had any luck with this in the last couple of days?
Scott Neader writes:
> I have Personalization enabled, and have the subscriber's email
> address in the footer, but Comcast redacts the email address.
> Unfortunately, there are quite a few comcast.net users on this
> list, making th
On Tue, Aug 6, 2019 at 7:24 AM David Gibbs via Mailman-Users <
mailman-users@python.org> wrote:
> On Mon, Aug 5, 2019 at 11:40 PM Scott Neader wrote:
> > Do any of you have any ideas for me to identify this serial
> > 'mark-as-spammer'? Could I hack something together temporarily that
> would
>
On 8/7/2019 6:23 PM, David Gibbs via Mailman-Users wrote:
On Wed, Aug 7, 2019 at 8:18 PM David Josephson wrote:
Wouldn't it be simple enough just to use rot13, or the senders name
without the domain?
The first thing they redact is the users name.
That's if they edit (or send) the footer at
On Wed, Aug 7, 2019 at 8:18 PM David Josephson wrote:
> Wouldn't it be simple enough just to use rot13, or the senders name
> without the domain?
>
>
The first thing they redact is the users name.
David
>
> --
IBM i on Power Systems: For when you can't afford to be out of business!
I'm riding
Wouldn't it be simple enough just to use rot13, or the senders name
without the domain?
On 8/7/2019 5:20 PM, Carl Zwanzig wrote:
On 8/7/2019 1:17 PM, Scott Neader wrote:
I need a way to put some clue about the recipient into the footer, when
personalization is enabled. I've seen some past sol
On 8/7/2019 1:17 PM, Scott Neader wrote:
I need a way to put some clue about the recipient into the footer, when
personalization is enabled. I've seen some past solutions where admins
were successful in adding some type of hash or encoded version of the
recipient's email address into the footer,
On Tue, Aug 6, 2019 at 7:38 PM Grant Taylor via Mailman-Users <
mailman-users@python.org> wrote:
> On 8/5/19 10:14 PM, Scott Neader wrote:
> > Hi all! I have a list member with a comcast.net email address that is
> > marking most every list message as spam. I have Personalization enabled,
> > an
On 8/5/19 10:14 PM, Scott Neader wrote:
Hi all! I have a list member with a comcast.net email address that is
marking most every list message as spam. I have Personalization enabled,
and have the subscriber's email address in the footer, but Comcast redacts
the email address. Unfortunately, th
On Tue, Aug 6, 2019 at 7:24 AM David Gibbs via Mailman-Users <
mailman-users@python.org> wrote:
> On Mon, Aug 5, 2019 at 11:40 PM Scott Neader wrote:
> > Do any of you have any ideas for me to identify this serial
> > 'mark-as-spammer'? Could I hack something together temporarily that
> would
>
On Mon, Aug 5, 2019 at 11:40 PM Scott Neader wrote:
> Do any of you have any ideas for me to identify this serial
> 'mark-as-spammer'? Could I hack something together temporarily that would
> put maybe the first few characters of their email in the footer? (so that
> Comcast won't sense it as an
Hi all! I have a list member with a comcast.net email address that is
marking most every list message as spam. I have Personalization enabled,
and have the subscriber's email address in the footer, but Comcast redacts
the email address. Unfortunately, there are quite a few comcast.net users
on t
13 matches
Mail list logo