Re: [Mailman-Users] Explicit destination causes implicitdestination bounce

2011-03-11 Thread Ian Gibbs

Thanks to you both. Adding To and From headers solves the issue, and the mail 
is accepted.

Regards,
--
Ian Gibbs
i...@flash.org.uk
Mon - Wed: +31 (0) 629  202752
Thu - Sun: +44 (0) 7815 142001

On 11/03/11 18:26, Larry Stone wrote:

On Fri, 11 Mar 2011, Mark Sapiro wrote:


Larry's response is correct except for this one detail. Actually, this
message has a Subject: header and a non-conformant "This" header and
no body. The body must be separated from the headers by an empty line.


Oops. I looked at the original way too quickly. Thanks, Mark, for correcting my 
post. The lesson in
this is that SMTP, like almost all computer command sets, is very intolerant of 
even the slightest
mistake. It does exactly what you tell it to do and has no idea what you meant 
when you get it
wrong. Using Telnet to test SMTP has its uses (I do it to make sure the 
anti-spam controls on the
commands works since that's hard to do by other means) but unless you are 
prepared to type
everything in painful detail, expect weird results. Mailman is best tested with 
real messages sent
by a proper MUA.

-- Larry Stone
lston...@stonejongleux.com
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/ian%40flash.org.uk

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Attachments AND no-attachments...

2011-03-11 Thread Richard Troy


On Thu, 10 Mar 2011, Mark Sapiro wrote:
>
> Richard Troy wrote:
> >
> >In sum, it would be _fantastic_ if list subscribers have an
> >option to receive or not receive attachments on a per-user basis, much as
> >users can now elect to recieve digests. But, as that option doesn't appear
> >to exist, I was thinking I could facilitate the same effect by using two
> >lists - maybe three.

> That information appears to have been copied from the FAQ at
> . The FAQ has since been updated to
> include information about the regular_include_lists feature in more
> recent versions of Mailman.

Thanks - overlooked somehow.

>  At first, I thought that would solve your
> issue, but it won't because if for example, you put the no-attachments
> list in regular_include_lists of the attachments list, a post to
> attachments will go to the members of both lists, but all recipients
> will get the attachments because the only content filtering applied
> will be that of the attachments list.

I was only thinking of using "accept_these_nonmembers" - as posters, I
presume - on both lists for the members of the other list: the main list
to permit no-attachment members to post to the main list, and to the
no-attachment list to permit main-list members emails to propagate
properly to the no-attach list without munging the header.

>
> So, moving on...
>
> Why not have an attachments list and a no-attachments list with
> completely disjoint membership. Make each list a member of the other.
> This is not a problem because the X-BeenThere: headers will prevent
> loops.

I didn't know about "X-BeenThere", but otherwise, that's in effect what I
was creating with my previous plan - two disjoint membership lists.

> Also, put @attachments in the no-attachments list's
> accept_these_nonmembers and vice versa so a member of either list can
> post to either list.

I don't understand that syntax - "@attachments", pointer? More data? That
would solve my problem stated in my original problem description.

> Also, put the attachments posting address in the
> no-attachments list's acceptable_aliases and vice versa.

I may have overlooked that, thanks.

> I don't think you need to mung Reply-To: at all.

In my original strategy, it's needed to help make it appear to be ONE
list as otherwise "reply to list" for non-attachment listees only post to
the non-attachment list and that's not what's intended.

> Also, you might find the FAQ at  useful.

Thanks.

> What gets filtered depends on content filtering. If you want to allow
> anything on the attachments list, just set filter_content to No.

That was the plan.

>
> If you want to allow only jpeg and gif images and plain text and HTML
> set pass_mime_types to
>
> multipart
> text/plain
> text/html
> image/jpeg
> image/gif

Is it possible to wild card, say, for example, like this:

image/*

?


> and set collapse_alternatives and convert_html_to_plaintext both to No.

Darn - we're rather partial to plain-text-only!


Looks like I've got some work to do - thanks for your help,
Richard


--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Messages approved never show up on list

2011-03-11 Thread Mark Sapiro
On 3/11/2011 7:47 AM, Doug Gaff wrote:
> text/html is definitely missing from pass_mime_type. I can add that,
> but I'm wondering why that type isn't included by default in the
> install. Are there other problems that this introduces?


Many users don't want HTML posts on their lists, even if 'converted' to
plain text.


> I've sent html to this list before via Outlook 2007, but this
> particular user is using Outlook 2010. Guess something changed.


You probably sent multipart/alternative with text/plain and text/html
alternatives. I'd be surprised if Outlook 2010 couldn't be configured to
do this too.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] The No Attachments Option

2011-03-11 Thread Mark Sapiro
Tanstaafl wrote:
>
>Cool - but where is this option found??


Non-digest options -> scrub_nondigest

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] help for sibling list/avoid duplicate emails

2011-03-11 Thread Mark Sapiro
Marcello Villani wrote:

>Hi,
>I have the following lists in my environment:
>li...@mydomain.org
>li...@mydomain.org
>li...@mydomain.org
>
>Some members are inside two or three lists.
>
>My goal is to avoid duplicate emails for people who belong to more
>than one list!!


Don't cross post .


>I installed mailman 2.1.13: as far as I know this version has "sibling
>lists" option. The problem is that I didn't find a proper instruction
>to configure them neither the commands to use them...
>
>In the "web administrative pages/non digest options" of mailman I
>found  two commands:
>regular_exclude_lists
>regular_include_lists
>
>Do I need to use them?
>Can someone help me in this configuration?


Put li...@mydomain.org and li...@mydomain.org in listA's
regular_exclude_lists and li...@mydomain.org listB's
regular_exclude_lists.

A post to all three lists will be sent to members of listC only from
listC, to members of listB who aren't members of listC only from listB
and to members of only listA from listA.

Posts to just two of the three lists work similarly.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Explicit destination causes implicitdestination bounce

2011-03-11 Thread Larry Stone

On Fri, 11 Mar 2011, Mark Sapiro wrote:


Larry's response is correct except for this one detail. Actually, this
message has a Subject: header and a non-conformant "This" header and
no body. The body must be separated from the headers by an empty line.


Oops. I looked at the original way too quickly. Thanks, Mark, for 
correcting my post. The lesson in this is that SMTP, like almost all 
computer command sets, is very intolerant of even the slightest mistake. 
It does exactly what you tell it to do and has no idea what you meant when 
you get it wrong. Using Telnet to test SMTP has its uses (I do it to make 
sure the anti-spam controls on the commands works since that's hard to do 
by other means) but unless you are prepared to type everything in painful 
detail, expect weird results. Mailman is best tested with real messages 
sent by a proper MUA.


-- Larry Stone
   lston...@stonejongleux.com
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Explicit destination causes implicitdestination bounce

2011-03-11 Thread Mark Sapiro
Larry Stone wrote:
>
>You have no To: header (or any other headers for that matter).
[...]
>> DATA
>> 354 Enter message, ending with "." on a line by itself
>> Subject:Testing from guinevere 3
>> This is a message 3
>> .
>> 250 OK id=1Py3ZU-0003YI-Rz


Larry's response is correct except for this one detail. Actually, this
message has a Subject: header and a non-conformant "This" header and
no body. The body must be separated from the headers by an empty line.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Explicit destination causes implicit destination bounce

2011-03-11 Thread Larry Stone

On Fri, 11 Mar 2011, Ian Gibbs wrote:


Dear all,

I have read http://wiki.list.org/pages/viewpage.action?pageId=4030676 FAQ 1.9 
about implicit destination. I am sending directly To: the list with no other 
recipients. The host_name setting is pumb.org.uk. The conversation I had with 
the SMTP server is shown below. It still results in an implicit destination 
error. Can anyone suggest why, please?


You have no To: header (or any other headers for that matter). The 
recipient listed on a RCPT TO: command to the SMTP server (known in the 
SMTP world as the "envelope recipient") is not the same as a To: header. 
Since the Mailman list address was not found in the message's non-existent 
To: or Cc: headers, it is an implicit destination.


To SMTP, headers are part of the message's data. They are completely 
separate from the SMTP commands that tell an SMTP server what to do with 
the message (otherwise, BCC could not work. A BCC recipient never appears 
in the headers (or wouldn't be blind) but the BCC recipient must be in the 
RCPT TO: SMTP command as how else would the destination server know to 
deliver it to the BCC recipient).



user@workstation:~$ telnet server 25
Trying IP...
Connected to server.
Escape character is '^]'. 
220 server ESMTP Exim 4.71 Fri, 11 Mar 2011 14:43:29 +

HELO workstation
250 server Hello workstation [89.16.174.50]
MAIL FROM:external@email.address 
250 OK

RCPT TO:mail...@pumb.org.uk
250 Accepted
DATA
354 Enter message, ending with "." on a line by itself
Subject:Testing from guinevere 3
This is a message 3
.
250 OK id=1Py3ZU-0003YI-Rz
QUIT
221 server closing connection
Connection closed by foreign host.


-- Larry Stone
   lston...@stonejongleux.com
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] The No Attachments Option

2011-03-11 Thread Tanstaafl
On 2011-03-11 5:27 AM, Mailman Admin wrote:
> You can move attachments from incoming emails to the archive and send
> only a link to it to recipients.
> 
> In this way only those who are interested in the attachment will have to
> download it.

Cool - but where is this option found??
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] Explicit destination causes implicit destination bounce

2011-03-11 Thread Ian Gibbs

Dear all,

I have read http://wiki.list.org/pages/viewpage.action?pageId=4030676 FAQ 1.9 about implicit 
destination. I am sending directly To: the list with no other recipients. The host_name setting is 
pumb.org.uk. The conversation I had with the SMTP server is shown below. It still results in an 
implicit destination error. Can anyone suggest why, please?


I'm in the process of migrating my lists from one server to another. I have not yet updated the MX 
records for the domain, thus my sending the mail directly to the server rather than using a mail 
program.


Thanks for the help.

user@workstation:~$ telnet server 25
Trying IP...
Connected to server.
Escape character is '^]'. 


220 server ESMTP Exim 4.71 Fri, 11 Mar 2011 14:43:29 +
HELO workstation
250 server Hello workstation [89.16.174.50]
MAIL FROM:external@email.address 


250 OK
RCPT TO:mail...@pumb.org.uk
250 Accepted
DATA
354 Enter message, ending with "." on a line by itself
Subject:Testing from guinevere 3
This is a message 3
.
250 OK id=1Py3ZU-0003YI-Rz
QUIT
221 server closing connection
Connection closed by foreign host.

--
Regards,
--
Ian Gibbs
i...@flash.org.uk
Mon - Wed: +31 (0) 629  202752
Thu - Sun: +44 (0) 7815 142001
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] help for sibling list/avoid duplicate emails

2011-03-11 Thread Marcello Villani
Hi,
I have the following lists in my environment:
li...@mydomain.org
li...@mydomain.org
li...@mydomain.org

Some members are inside two or three lists.

My goal is to avoid duplicate emails for people who belong to more
than one list!!

I installed mailman 2.1.13: as far as I know this version has "sibling
lists" option. The problem is that I didn't find a proper instruction
to configure them neither the commands to use them...

In the "web administrative pages/non digest options" of mailman I
found  two commands:
regular_exclude_lists
regular_include_lists

Do I need to use them?
Can someone help me in this configuration?


I would really appreciate your help!

Thanks,
Marcello
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Messages approved never show up on list

2011-03-11 Thread Doug Gaff
text/html is definitely missing from pass_mime_type. I can add that, but I'm 
wondering why that type isn't included by default in the install. Are there 
other problems that this introduces?

I've sent html to this list before via Outlook 2007, but this particular user 
is using Outlook 2010. Guess something changed.

Thanks for the tips.


On Mar 10, 2011, at 1:32 PM, Mark Sapiro wrote:

Stephen J. Turnbull wrote:

> Doug Gaff writes:
> 
>> This person is not subscribed to the list. They send a message, and
>> the moderator approves the message, but it never shows up on the
>> list.
> 
[...]
> The most probable reason for the discard is that the person violated
> the content rules of the list.  A typical scenario is that (1) they
> post in HTML-only format, (2) the list is set to strip HTML, and (3)
> the message ends up empty of content once the HTML is stripped.
> Without seeing your full configuration, and perhaps a sample message,
> it's hard to say, though.


Not only is auto-discard by content filtering the most likely
explanation, in the case of auto-discard following moderator approval.
it is the only explanation. The other possible auto-discards would
have either occured before the post's being held for moderator
approval or would have been bypassed for an approved post.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan


--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] The No Attachments Option

2011-03-11 Thread Mailman Admin
Hello Richard Troy

On 03/10/2011 01:42 AM, Richard Troy wrote:
> 
> Up until now many list participants on a list I manage have been
> clammoring for attachments, but in deference to some, we've prevented
> them. Now that the server has had its hardware upgraded and a new O/S
> installed (Fedora Core 14 with Mailman 2.1.13, and Postfix 2.7.1), I
> thought it'd be a good time to solve that problem. In sum, it would be
> _fantastic_ if list subscribers have an option to receive or not receive
> attachments on a per-user basis, much as users can now elect to recieve
> digests. But, as that option doesn't appear to exist, I was thinking I
> could facilitate the same effect by using two lists - maybe three.

You can move attachments from incoming emails to the archive and send
only a link to it to recipients.

In this way only those who are interested in the attachment will have to
download it.


Kind regards,
Christian Mack
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org