Some long dormant bits in my brain are remembering something like this
happening when the MIME type application/pgp-signature was introduced.
Before then, people were using application/pgp for such things, and
some were using other things like pgp-encrypt.
If the signature problem is a pgp signa
On Fri, 2014-04-18 at 16:23 -0700, Mark Sapiro wrote:
> On 04/17/2014 09:13 AM, Lindsay Haisley wrote:
>
> > Someone, maybe it was you, posted on this forum earlier that perhaps 90%
> > or more of spam with a yahoo.com origin (or one of their international
> > DNs) actually _does_ come from Yahoo
On 04/17/2014 09:13 AM, Lindsay Haisley wrote:
> Someone, maybe it was you, posted on this forum earlier that perhaps 90%
> or more of spam with a yahoo.com origin (or one of their international
> DNs) actually _does_ come from Yahoo and that their response to abuse
> notifications is abysmal to n
On 04/17/2014 07:40 PM, Conrad G T Yoder wrote:
> One of my users on one of my lists is seeing something odd. His own
> signatures are appearing on other people’s emails sent to a Mailman (2.1.14)
> list. Some points of info:
>
> - He has his own domain, hosted by google
> - Email is read on t
Sylvain Viart writes:
> Le 18/04/2014 09:41, Alain Williams a écrit :
> >> I may have missed some topic, but why SRS
> >> (http://en.wikipedia.org/wiki/Sender_Rewriting_Scheme) doesn't
> >> come to rescue here?
> > SRS rewrites the *envelope* sender.
> >
> > My understanding is that the YAHO
Jim Popovitch writes:
> On Thu, Apr 17, 2014 at 2:32 PM, Stephen J. Turnbull
> wrote:
>
> > So maybe it does, but in my spamtrap I have only 67/4359 (1.5%)
> > messages from Yahoo (based on grepping for "^From:.*yahoo" and
> > "^From:" respectively), vs. 658/38748 (1.7%) in my saved mail fo
Lindsay Haisley writes:
> > It's very ugly, though, especially if for some reason you have no
> > display name to work with.
>
> Agreed! But the display name is free form and strictly informational.
> Could this not be the subscriber name of the author, if it's part of the
> subscription r
Le 18/04/2014 09:41, Alain Williams a écrit :
I may have missed some topic, but why SRS
(http://en.wikipedia.org/wiki/Sender_Rewriting_Scheme) doesn't come to rescue
here?
SRS rewrites the *envelope* sender.
My understanding is that the YAHOO DKIM uses the From: header, not the envelope
sende
On 18 Apr 2014, at 02:26, Jon 1234 wrote:
> > From: t...@yingtong.co.uk
> > Date: Fri, 18 Apr 2014 00:36:37 +0100
> > ref identity I really mean at present most of the traffic is on the mailing
> > list (and the forum is more of an archive for 80% of the joint community)
> > where users compla
On 04/18/2014 12:14 AM, Sylvain Viart wrote:
> Hi,
>
>
> Le 17/04/2014 20:32, Mark Sapiro a écrit :
>> I am pleased to announce the first release candidate for Mailman 2.1.18.
>>
>> http://www.list.org
>> http://www.gnu.org/software/mailman
>> http://mailman.sourceforge.net/
>
> No topic are pre
On Fri, Apr 18, 2014 at 09:26:28AM +0200, Sylvain Viart wrote:
> Hi,
>
> I may have missed some topic, but why SRS
> (http://en.wikipedia.org/wiki/Sender_Rewriting_Scheme) doesn't come
> to rescue here?
>
> It isn't its original purpose?
> Resigning outgoing messages with messaging server own DKI
Hi,
I may have missed some topic, but why SRS
(http://en.wikipedia.org/wiki/Sender_Rewriting_Scheme) doesn't come to
rescue here?
It isn't its original purpose?
Resigning outgoing messages with messaging server own DKIM's key.
Seem to be available by setuping mm_cfg.py:
- ALLOW_FROM_IS_LI
Hi,
Le 17/04/2014 20:32, Mark Sapiro a écrit :
I am pleased to announce the first release candidate for Mailman 2.1.18.
http://www.list.org
http://www.gnu.org/software/mailman
http://mailman.sourceforge.net/
No topic are presented about the fresh release on those website, right?
So a "posta
13 matches
Mail list logo
