On 8/12/08, Mark Sapiro wrote:
I think he was suggesting that Mailman could somehow put something like
a rot13 encoded version of the recipient's address into a personalized
list footer to sneak it past AOL's eliding of screen names.
In the ARF reports, I don't think you're going to see
On 8/13/08 1:07 AM, Brad Knowles at [EMAIL PROTECTED] wrote:
So, either way, we're screwed. AOL is determined to delete any and
all data that would actually be useful to us in our jobs, and they
are determined to file all these reports automatically.
So do what I do -- file them
Hi there,
Larry Stone:
Why even receive them at that point? They're little more than spam
themselves so maybe it's time to ban all mail from AOL as AOL will
then be a known spammer. :-(
Because you can always claim you treat their reports seriously. ;)
Actually, when lists are personalized
Dear all,
Where do I look to change Mailman layout (I know where to change
individual lists) but not sure where are files for
domian.tld/mailman/listinfo located.
I'd like to customize Mailman to look more like our organization's website.
Many thanks in advance!
--
Zbigniew Szalbot
On Sat, Aug 09, 2008 at 07:50:34AM -0700, Mark Sapiro wrote:
It's not the added headers. It's the X-BeenThere: header in the original
message. You have to remove it.
Uhm, I've checked both the original message and the bounced message (going
out of my mutt), and neither contains the
Hello,
Is there in place any method to obfuscate/hide email addresses so spammer
spiders/robots can't harvest them?
If not, could I edit a page to use an external JavaScript function to do so?
Even more basically, can JavaScript be used at all when editing pages?
Thanks.
Michael Masquith
Zbigniew Szalbot wrote:
Where do I look to change Mailman layout (I know where to change
individual lists) but not sure where are files for
domian.tld/mailman/listinfo located.
The listinfo overview page is built on the fly by
Mailman/Cgi/listinfo.py. The admin(db) pages are built the same
Danny Shain wrote:
Hi everyone,
I want to start off by saying I think it's great that this community exists,
with people willing to help people. I have a question that is dealt with on
the FAQ, but before you roll your eyes I'm still posting here because the I
didn't find the FAQ entry
Zbigniew Szalbot wrote:
Actually, when lists are personalized you can always use Message-ID to
look up your nice AOL citizen. That't what I do as I use full
personalization option.
I'm confused. How do you use the Message-ID for this? Even when
messages are fully personalized, every
Masquith, Michael CTR wrote:
Is there in place any method to obfuscate/hide email addresses so spammer
spiders/robots can't harvest them?
Are you talking about archives? If so, mild obfuscation is done by
default unless you put
ARCHIVER_OBSCURES_EMAILADDRS = No
in mm_cfg.py.
If you're
On Wed, 13 Aug 2008, Mark Sapiro wrote:
I'm confused. How do you use the Message-ID for this? Even when
messages are fully personalized, every recipient's message has the
Message-ID of the original, incoming message.
It may depend on how your MTA is set up. On my lists, there is an internal
On Wed, 13 Aug 2008, Christopher X. Candreva wrote:
On Wed, 13 Aug 2008, Mark Sapiro wrote:
I'm confused. How do you use the Message-ID for this? Even when
messages are fully personalized, every recipient's message has the
Message-ID of the original, incoming message.
It may depend on
On Wed, 13 Aug 2008, Larry Stone wrote:
That's not a Message ID, that's a queue ID. And yes, I do the same
thing.
Ah yes, of course you are right.
As you said though -- either way, it works. :-)
==
Chris Candreva -- [EMAIL PROTECTED]
Cristian Rigamonti wrote:
On Sat, Aug 09, 2008 at 07:50:34AM -0700, Mark Sapiro wrote:
It's not the added headers. It's the X-BeenThere: header in the original
message. You have to remove it.
Uhm, I've checked both the original message and the bounced message (going
out of my mutt), and
Brad Knowles wrote:
So, either way, we're screwed. AOL is determined to delete any and all
data that would actually be useful to us in our jobs, and they are
determined to file all these reports automatically.
And I'm *SURE* they will _never_ consider moving the Report to TOS button away
Mark, Thanks!
Are you talking about archives?
No.
If you're asking if you can put JavaScript in Mailman's HTML templates,
you can.
That was it. Thanks.
Michael Masquith
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 13, 2008 11:12 AM
To:
Dragon, Mark,
Thanks for the quick replies. Dragon, I'd been having a brief conversation
with Mark away from the listserv and we actually got to just about the same
point. I have a webmail account provided by my hosting which is technically
the recipient of all mailman emails, which I then have
On Wed, Aug 13, 2008 at 08:33:14AM -0700, Mark Sapiro wrote:
Let me clarify the scenario:
- Somebody sends me a message
- I think the message should really go to the list, not to me
- I bounce the message to the list (if the original sender is not subscribed
to
the list I expect to
Hi,
I have a mailman 2.1.11 installation running about 1000 mailing lists.
Each of them is bi-directionally gatewayed via NNTP.
I have been hitting the following scenario:
Email 'a' is made of a text body and email 'b' as a text attachment.
Email 'b' is made of a text body and another
Mark Sapiro writes:
Zbigniew Szalbot wrote:
Actually, when lists are personalized you can always use Message-ID to
look up your nice AOL citizen. That't what I do as I use full
personalization option.
I'm confused. How do you use the Message-ID for this? Even when
messages
But what it really comes down to is that they are arbitrarily throwing
away their customers' mail, and their customers apparently like it
that way.
I would be MORE prone to believe that their customers have absolutely
NO CLUE, Stephan and being aolers don't 'care' enough to complain
(even IF
On 8/13/08, Larry Stone wrote:
Why even receive them at that point? They're little more than spam
themselves so maybe it's time to ban all mail from AOL as AOL will then be a
known spammer. :-(
If you set yourself up to receive them, it's a lot harder for AOL to
automatically mark you as
On 8/13/08, Ed at JustBrits wrote:
I would be MORE prone to believe that their customers have absolutely
NO CLUE, Stephan and being aolers don't 'care' enough to complain
(even IF they know how to) -:)-:)!!
All their customers know is that they are doing everything they can
to make the
So, you make sure they never find out.
LMAO, Brad !
Tnx, NEEDED that !
Ed
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable
Brad Knowles wrote:
If you set yourself up to receive them, it's a lot harder for AOL to
automatically mark you as a spammer.
Actually, in my experience, AOL doesn't give a rats a-- that you are setup for
the feedback loop (at least the old program) ... if they thought you might be a
On 8/13/08, David Gibbs wrote:
Actually, in my experience, AOL doesn't give a rats a-- that you are setup
for the feedback loop (at least the old program) ... if they thought you
might be a spammer they will still rate limit your delivery even if they
send feedback to you.
Yeah, but
* David Gibbs [EMAIL PROTECTED]:
Brad Knowles wrote:
So, either way, we're screwed. AOL is determined to delete any and all
data that would actually be useful to us in our jobs, and they are
determined to file all these reports automatically.
And I'm *SURE* they will _never_ consider
27 matches
Mail list logo
