headers
Brian Parish | 1 Nov 2005 04:32

Trying again with the latest version - bug in install doc?

I got 2.1.5 supposedly working, although it was failing to send messages to 
mailing list subscribers.  Anyway, instead of debugging that I have decided 
to try the latest version.

Installed from source using the default locations.  Everything looks smooth 
until genaliases.  Same problem as first time around, except that then I 
thought the reason was a fault in my settings in mm_cfg.py

bin/genaliases runs without any errors, but generates only data/aliases, not 
data/virtual-mailman

By the time we get to this step, the install docs have had me enter 
virtual-mailman in my postfix/main.cf, so the fact that it isn't generated 
breaks postfix very effectively.  Presumably some later step creates the 
circumstances under which virtual-mailman is created?

Anyway, my mm_cfg.py looks like this:

---------------------
# Put YOUR site-specific settings below this line.
IMAGE_LOGOS = '/icons/'
MTA = 'Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['univexhosting.com']
DEFAULT_URL_HOST   = 'www.univexsystems.com'
DEFAULT_EMAIL_HOST = 'univexhosting.com'

# Because we've overriden the virtual hosts above add_virtualhost
# MUST be called after they have been defined.

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mark Sapiro | 1 Nov 2005 05:20

Re: Trying again with the latest version - bug ininstall doc?

Brian Parish wrote:
>
>Installed from source using the default locations.  Everything looks smooth 
>until genaliases.  Same problem as first time around, except that then I 
>thought the reason was a fault in my settings in mm_cfg.py
>
>bin/genaliases runs without any errors, but generates only data/aliases, not 
>data/virtual-mailman
>
>By the time we get to this step, the install docs have had me enter 
>virtual-mailman in my postfix/main.cf, so the fact that it isn't generated 
>breaks postfix very effectively.  Presumably some later step creates the 
>circumstances under which virtual-mailman is created?
>
>Anyway, my mm_cfg.py looks like this:
>
>---------------------
># Put YOUR site-specific settings below this line.
>IMAGE_LOGOS = '/icons/'
>MTA = 'Postfix'
>POSTFIX_STYLE_VIRTUAL_DOMAINS = ['univexhosting.com']
>DEFAULT_URL_HOST   = 'www.univexsystems.com'
>DEFAULT_EMAIL_HOST = 'univexhosting.com'
>
># Because we've overriden the virtual hosts above add_virtualhost
># MUST be called after they have been defined.
>
>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>---------------------
>and:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Brian Parish | 1 Nov 2005 05:42

Re: Trying again with the latest version - bug ininstall doc?

On Tuesday 01 November 2005 15:20, Mark Sapiro wrote:
> Brian Parish wrote:
> >Installed from source using the default locations.  Everything looks
> > smooth until genaliases.  Same problem as first time around, except that
> > then I thought the reason was a fault in my settings in mm_cfg.py
> >
> >bin/genaliases runs without any errors, but generates only data/aliases,
> > not data/virtual-mailman
> >
> >By the time we get to this step, the install docs have had me enter
> >virtual-mailman in my postfix/main.cf, so the fact that it isn't generated
> >breaks postfix very effectively.  Presumably some later step creates the
> >circumstances under which virtual-mailman is created?
> >
> >Anyway, my mm_cfg.py looks like this:
> >
> >---------------------
> ># Put YOUR site-specific settings below this line.
> >IMAGE_LOGOS = '/icons/'
> >MTA = 'Postfix'
> >POSTFIX_STYLE_VIRTUAL_DOMAINS = ['univexhosting.com']
> >DEFAULT_URL_HOST   = 'www.univexsystems.com'
> >DEFAULT_EMAIL_HOST = 'univexhosting.com'
> >
> ># Because we've overriden the virtual hosts above add_virtualhost
> ># MUST be called after they have been defined.
> >
> >add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> >---------------------
> >and:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mark Sapiro | 1 Nov 2005 05:46

Re: Bad error message

Dwight Tovey wrote:
>
>It was driving me nuts because the 'nofiles' group does exist in
>/etc/group and was being used by some of the qmail processes.  After much
>digging around, I finally found that the message was coming from the
>'mailman' program itself.  In src/common.c, line 142, there is a fatal()
>call in 'check_caller()' if the caller's GID fails to resolve to a name
>(getgrgid() returns a NULL).  The error message though is misleading.  I
>thought that it had a group name (nofiles) and couldn't resolve it to a
>GID.  Since there was a 'nofiles' group, I didn't know what was going on. 
>As it turned out, the qmail delivery program was running under a GID that
>didn't have a group entry and was thus triggering the error.
>
>I think a better error message would be something like:
>"Failure to find group name for GID %d:...".  Once I changed the message
>to that, it was easy to see what was going on.

Sorry you had such a runaround on this. If you had searched the
archives of this list, you might have found
http://mail.python.org/pipermail/mailman-users/2005-October/046934.html
which might have helped.

Anyway, thanks for the report. I have developed a patch for the message
which will make it to SourceForge and into CVS as soon as I have a
chance to compile and test it.

--

-- 
Mark Sapiro <msapiro <at> value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
(Continue reading)

Permalink | Reply | 0 comments |
headers
Brian Parish | 1 Nov 2005 05:50

Re: Trying again with the latest version - bug ininstall doc?

On Tuesday 01 November 2005 15:42, Brian Parish wrote:
> On Tuesday 01 November 2005 15:20, Mark Sapiro wrote:
> > Brian Parish wrote:
> > >Installed from source using the default locations.  Everything looks
> > > smooth until genaliases.  Same problem as first time around, except
> > > that then I thought the reason was a fault in my settings in mm_cfg.py
> > >
> > >bin/genaliases runs without any errors, but generates only data/aliases,
> > > not data/virtual-mailman
> > >
> > >By the time we get to this step, the install docs have had me enter
> > >virtual-mailman in my postfix/main.cf, so the fact that it isn't
> > > generated breaks postfix very effectively.  Presumably some later step
> > > creates the circumstances under which virtual-mailman is created?
> > >
> > >Anyway, my mm_cfg.py looks like this:
> > >
> > >---------------------
> > ># Put YOUR site-specific settings below this line.
> > >IMAGE_LOGOS = '/icons/'
> > >MTA = 'Postfix'
> > >POSTFIX_STYLE_VIRTUAL_DOMAINS = ['univexhosting.com']
> > >DEFAULT_URL_HOST   = 'www.univexsystems.com'
> > >DEFAULT_EMAIL_HOST = 'univexhosting.com'
> > >
> > ># Because we've overriden the virtual hosts above add_virtualhost
> > ># MUST be called after they have been defined.
> > >
> > >add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> > >---------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mark Sapiro | 1 Nov 2005 05:53

Re: Trying again with the latest version - bugininstall doc?

Brian Parish wrote:
>
>Hmmm.  At this point in the install, I don't have any lists.  No less confused 
>here, but I guess I'll go ahead and continue with the additional steps in the 
>hope that once I have a list to fix, I can fix it and thereby address this 
>problem.  If that works, surely the sequence of steps in the install doc is 
>borked.

That's the problem. You won't need to run fix_url. Just create the site
list (mailman) and rerun genaliases.

genaliases doesn't create a virtual-mailman file unless there is at
least one list with a host_name matching a name in
POSTFIX_STYLE_VIRTUAL_DOMAINS.

--

-- 
Mark Sapiro <msapiro <at> value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
Permalink | Reply | 0 comments |
headers
Stephen J. Turnbull | 1 Nov 2005 09:36
Picon
Favicon

Re: Help

>>>>> "Mark" == Mark A Lombardo <Mark.A.Lombardo> writes:

    Mark> I must be coming across as really thick and stupid.

Not at all, although it's maddening all around to run into this kind
of communication block.  Mark S is usually very successful at
explaining but let me try from a somewhat different angle.

    Mark> If I have set the tag to reply to poster, and I hit reply,
    Mark> then there is no way of mailman knowing which email address
    Mark> that came from

That's right.  It is not possible to prevent people who otherwise have
permission to post from posting replies, except by having someone
approve or deny every message.  So mailman doesn't try.

    Mark> How do I set that the reply only comes to the person that
    Mark> posted the mail, and not the list, I thought setting the
    Mark> reply to poster it would only send the mal to the person who
    Mark> posted, and not the rest of the list. Is this not correct?

No, but that's not your fault; that's precisely what the English says.
The problem is that there is no standard provision in email for
requesting personal replies.  There is a non-standard header called
"Mail-Followup-To", but only a minority of MUAs (MUA = message user
agent, or mail program) respect it.  As far as I know none of the ones
commonly used on Windows or the Mac do.

The best we can guarantee is that Mailman won't encourage mail to go
to the list.  This is done by _not_ setting Reply-To.  That is all
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stephen J. Turnbull | 1 Nov 2005 09:53
Picon
Favicon

Re: ISO-8859-1/Latin1 vs UTF-8

>>>>> "Bernd" == Bernd Petrovitsch <bernd <at> firmix.at> writes:

    >> Content-Type: header specifying charset=utf-8. For reasons I
    >> don't understand, the HTML standard says the server provided
    >> Content-Type: charset takes priority over that specified by an
    >> HTML META tag.

    Bernd> I don't understand it either but it is so.

One reason is that the server may very well translate the encoding
based on negotiation with the client.  (I guess you could argue that
it should remove the charset attribute from the META tag if it does.)

A second reason is that admins will occasionally translate encodings
and not even be aware that some users who are too smart for their own
good have used META tags.

    Bernd> BTW I usually disable the feature in the webserver config.

While I think the standard got the precedence right, this feature
should be disabled by default.

--

-- 
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.
Permalink | Reply | 0 comments |
headers
Rene Hertell | 1 Nov 2005 10:12

Formatting the Subject-field in other languages

Hi all,

I have been searching for some time now a way in cleaning up the
subject-field when people send messages with email-clients that use
different locale that English, but I could not find any solution.

I've got the impression that Mailman cleans multiple Re's and Fw's from
the subject-line (and not the email-client), but now when a user sends
an message with an email-client that uses other abbreviations as the
English ones, they just stick there. This is an example of a subject
sent in a Finnish mailing-list:

[HUV] VS:  VS:  VS:  VS:  VS:  VS:  VS:  VS:  Järvenpää

So, Here you see that as normal Re: is instead VS:

I tried also to dig in the Mailman-code, but as python is not so
familiar to me, I could not figure out in what place this "Subject-line"
clean-up is situated.

I'm running Mailman 2.1.6 on a Debian-woody server.

Best Regards,

René
Permalink | Reply | 0 comments |
headers
lkolchin | 1 Nov 2005 12:02
Picon
Picon

memberships reminder sent twice to all members

Hello All,

My lists members got "mailing list memberships reminder" twice, i.e. they get the same reminder in two
separate e-mails.

How can I solve this problem?

 

Best Regards,

Leon Kolchinsky
Permalink | Reply | 1 comment |

Gmane