Hello ..
This is the second time that happens with me and I changed the server the first time.. I’ve been using my lists for months without any problems, I post to all lists from one address –which is moderated- and I accept all messages manually from the web admin..
but then after sending to the lists, the messages does not appear waiting for moderation although maillogs show that they’ve been delivered to the lists addresses.. also I noticed a warning that I used to see when thing were working fine, I don’t know if it’s the cause of the issue..
the mail log is below..
please advise..
Thanks..
Nov 4 08:44:19 ns1 postfix/cleanup[4236]: 01AD818A0041: message-id=<011a01cdba1c$d1d06ac0$75714040$(a)domain.com>
Nov 4 08:44:19 ns1 postfix/qmgr[3917]: 01AD818A0041: from=<dailymail(a)domain.com>, size=106552, nrcpt=10 (queue active)
Nov 4 08:44:19 ns1 postfix/smtpd[4227]: proxy-accept: END-OF-MESSAGE: 250 2.0.0 Ok: queued as 01AD818A0041; from=<dailymail(a)domain.com> to=<lista(a)domain.com> proto=ESMTP helo=<KhalilAbbasPC>
Nov 4 08:44:19 ns1 postfix/smtpd[4235]: disconnect from localhost.localdomain[127.0.0.1]
Nov 4 08:44:19 ns1 postfix/trivial-rewrite[4230]: warning: do not list domain domain.com in BOTH mydestination and virtual_mailbox_domains
Nov 4 08:44:19 ns1 postfix/trivial-rewrite[4230]: warning: do not list domain domain.com in BOTH mydestination and virtual_mailbox_domains
Nov 4 08:44:19 ns1 postfix/trivial-rewrite[4230]: warning: do not list domain domain.com in BOTH mydestination and virtual_mailbox_domains
Nov 4 08:44:19 ns1 postfix/trivial-rewrite[4230]: warning: do not list domain domain.com in BOTH mydestination and virtual_mailbox_domains
Nov 4 08:44:19 ns1 postfix/trivial-rewrite[4230]: warning: do not list domain domain.com in BOTH mydestination and virtual_mailbox_domains
Nov 4 08:44:19 ns1 postfix/trivial-rewrite[4230]: warning: do not list domain domain.com in BOTH mydestination and virtual_mailbox_domains
Nov 4 08:44:19 ns1 postfix/trivial-rewrite[4230]: warning: do not list domain domain.com in BOTH mydestination and virtual_mailbox_domains
Nov 4 08:44:19 ns1 postfix/trivial-rewrite[4230]: warning: do not list domain domain.com in BOTH mydestination and virtual_mailbox_domains
Nov 4 08:44:19 ns1 postfix/trivial-rewrite[4230]: warning: do not list domain domain.com in BOTH mydestination and virtual_mailbox_domains
Nov 4 08:44:19 ns1 postfix/trivial-rewrite[4230]: warning: do not list domain domain.com in BOTH mydestination and virtual_mailbox_domains
Nov 4 08:44:19 ns1 /usr/lib64/plesk-9.0/psa-pc-remote[19459]: Message aborted.
Nov 4 08:44:19 ns1 postfix/pipe[4260]: 01AD818A0041: to=<listc(a)domain.com>, relay=mailman, delay=6.8, delays=6.3/0.01/0/0.49, dsn=2.0.0, status=sent (delivered via mailman service)
Nov 4 08:44:19 ns1 postfix/pipe[4266]: 01AD818A0041: to=<listf(a)domain.com>, relay=mailman, delay=6.8, delays=6.3/0.01/0/0.49, dsn=2.0.0, status=sent (delivered via mailman service)
Nov 4 08:44:19 ns1 postfix/pipe[4258]: 01AD818A0041: to=<listb(a)domain.com>, relay=mailman, delay=6.8, delays=6.3/0.01/0/0.5, dsn=2.0.0, status=sent (delivered via mailman service)
Nov 4 08:44:19 ns1 postfix/pipe[4262]: 01AD818A0041: to=<listd(a)domain.com>, relay=mailman, delay=6.8, delays=6.3/0.01/0/0.5, dsn=2.0.0, status=sent (delivered via mailman service)
Nov 4 08:44:19 ns1 postfix/pipe[4264]: 01AD818A0041: to=<liste(a)domain.com>, relay=mailman, delay=6.8, delays=6.3/0.01/0/0.5, dsn=2.0.0, status=sent (delivered via mailman service)
Nov 4 08:44:19 ns1 postfix/pipe[4272]: 01AD818A0041: to=<listi(a)domain.com>, relay=mailman, delay=6.8, delays=6.3/0.02/0/0.49, dsn=2.0.0, status=sent (delivered via mailman service)
Nov 4 08:44:19 ns1 postfix/pipe[4270]: 01AD818A0041: to=<listh(a)domain.com>, relay=mailman, delay=6.8, delays=6.3/0.02/0/0.49, dsn=2.0.0, status=sent (delivered via mailman service)
Nov 4 08:44:19 ns1 postfix/pipe[4257]: 01AD818A0041: to=<lista(a)domain.com>, relay=mailman, delay=6.8, delays=6.3/0/0/0.51, dsn=2.0.0, status=sent (delivered via mailman service)
Nov 4 08:44:19 ns1 postfix/pipe[4268]: 01AD818A0041: to=<listg(a)domain.com>, relay=mailman, delay=6.8, delays=6.3/0.01/0/0.5, dsn=2.0.0, status=sent (delivered via mailman service)
Nov 4 08:44:19 ns1 postfix/pipe[4274]: 01AD818A0041: to=<listj(a)domain.com>, relay=mailman, delay=6.8, delays=6.3/0.02/0/0.51, dsn=2.0.0, status=sent (delivered via mailman service)
Nov 4 08:44:19 ns1 postfix/qmgr[3917]: 01AD818A0041: removed
Hello experts,
I am unable to add or subscribe any member using mass subscription option under membership management of my mailing list. I am facing the below error since yesterday:
Error: The form lifetime has expired. (request forgery check)
Please suggest me the remedy for it.
Thanks,
Amit Bhatt
I am sorry, it is version 2.1.1.15.
----- Original Message -----
From: "Amit Bhatt" <misterbhatt(a)gmail.com>
To: "Mark Sapiro" <mark(a)msapiro.net>; <Mailman-Users(a)python.org>
Sent: Saturday, November 03, 2012 9:46 PM
Subject: Re: [Mailman-Users] error message while adding members
> yes, surprisingly, the mailing list has been updated in to new version
> 1.1.15 without any effort made by me.
> I am surprised because I have never tried to update the list, is it
> possible that the updation is done from our web server end?
>
> I have noticed this change after seeing your reply.
>
> Regards,
>
> Amit Bhatt
> ----- Original Message -----
> From: "Mark Sapiro" <mark(a)msapiro.net>
> To: "Amit Bhatt" <misterbhatt(a)gmail.com>; <Mailman-Users(a)python.org>
> Sent: Saturday, November 03, 2012 8:22 PM
> Subject: Re: [Mailman-Users] error message while adding members
>
>
>> Amit Bhatt wrote:
>>>
>>>I am unable to add or subscribe any member using mass subscription option
>>>under membership management of my mailing list. I am facing the below
>>>error since yesterday:
>>>
>>>Error: The form lifetime has expired. (request forgery check)
>>
>>
>> This message comes from the new in 2.1.15 CSRF mitigation features.
>>
>> When did you upgrade to 2.1.15?
>>
>> Have you set a value for FORM_LIFETIME in mm_cfg.py? If so, what? (The
>> default setting in Defaults.py is 1 hour.)
>>
>> What the message is telling you is that the mass subscribe form you are
>> submitting was retrieved from the host longer than FORM_LIFETIME
>> before it was submitted. If this is not the case, there is some issue
>> in your web server. Perhaps the FAQ at <http://wiki.list.org/x/ioA9>
>> is applicable.
>>
>> --
>> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
>> San Francisco Bay Area, California better use your sense - B. Dylan
>>
>
Hello mailman-users,
I am new to mailman and ran into a problem
with my fresh 2.1.13 installation of mailman.
My first created list is
defined with private option for archive, so list members have to login
before they can view the archive.
The login for users works well on the
edit profile page, but not on the archive page.
After entering the
login credencials I receive a 301 redirect to the archive page.
I
consider there should be the archive shown now.
Instead there is only
the login form again.
Taking a look at the cookies in the browser I can
see that there has no cookie been set.
Do you have any idea about this
problem?
Regards from Augsburg, Germany,
Michael
Hi all,
I wanted to figure out which effect DEFAULT_EMAIL_HOST has but I didn't
have much success. The only place where I found this variable was
add_virtualhost() in mailman-install.pdf and in Defaults.py.
My question: Does DEFAULT_EMAIL_HOST have an effect on the mailman
instance when I am not using (e.g. Postfix) virtual hosts? Does it have
an effect _when_ I'm using virtual domains? And if yes, which? Or should
it always be set to a sensible value? Does it influence to which
hostname the "aliases" file belongs? And if yes, does that make sense?
I ask because when I change the value of DEFAULT_EMAIL_HOST, nothing
happens except of some address changes on the web interface. Sending
mails to the lists works without any problems.
I'm pretty confused :)
Norbert
