Hello world,
first of all, the Mailman wiki at http://wiki.list.org/ is really very
helpful. I've come to find it's structure very clean and easy to
understand. Especially the FAQ part is very, very helpful and saved me
lots of time when trying to troubleshoot a problem.
But - there is one thing
Try applying the attached Decorate.patch.txt patch to
Mailman/Handlers/Decorate.py and restart mailman.
Then try the post and report what you find in Mailman's 'debug' log.
Thanks again, Mark. Here's what shows up in the debug log (email
address anonymized to protect the innocent; it was an
First, I was wrong here. I was so horrified at the thought of having lost
all those old messages that I got the date wrong. It's actually worse than I
remembered. The last archive update appears to have happened in early
July... not early August. My last backup from the old server was September
Follow-up to last message. Wasn't sure exactly how to examine the contents
of the ourlist.mbox file in /usr/local/mailman/archives/private/ourlist.mbox
SO, I opened it with emacs just to see what it contained. The last message
in that file is one I posted on July 7th.
The prospects of recovering
Hello everyone,
It appears we hit the 32k-inodes-per-directory limit in ext2fs today, so
mailman can't create any new lists. We could of course move the lists to
an XFS filesystem, but I was wondering if there is a way to not have
mailman create 2 entries in the lists directory for every mailing
Hi all!
I have a problem. When i send a email to my mailing list, i always got this
error:
*Oct 27 22:48:13 kim postfix/smtpd[10355]: connect from
col0-omc2-s9.col0.hotmail.com[65.55.34.83]
Oct 27 22:48:14 kim postfix/smtpd[10355]: NOQUEUE: reject: RCPT from
On Mon, Oct 27, 2008 at 02:10:40PM -0700, Mark Sapiro wrote:
My question is why is mail to mailmain@ seemingly getting delivered to
[EMAIL PROTECTED]
My first guess, assuming you've verified the above by actually sending
your own message to [EMAIL PROTECTED], is that your MTA aliases or
Josh Clark wrote:
Try applying the attached Decorate.patch.txt patch to
Mailman/Handlers/Decorate.py and restart mailman.
Then try the post and report what you find in Mailman's 'debug' log.
Thanks again, Mark. Here's what shows up in the debug log (email
address anonymized to protect the
William Lebel wrote:
I have a problem. When i send a email to my mailing list, i always got this
error:
*Oct 27 22:48:13 kim postfix/smtpd[10355]: connect from
col0-omc2-s9.col0.hotmail.com[65.55.34.83]
Oct 27 22:48:14 kim postfix/smtpd[10355]: NOQUEUE: reject: RCPT from
/etc/aliases is the location of my aliases file and that's where postfix
is pointing. I cannot change the owner to the aliases and aliases.db or
else I can't run newaliases.
I ran ./configure --with-mail-god=nobody
and I have default_privs = nobody
Any other suggestions?
Jewel
-
Hi friends.
With Mailman, is there any clue in a received message header that the original
message went through moderation and was approved -- as opposed to being sent
unmoderated?
Also, I sent this previously through my From address' smtp server, but
python.org tagged it as spam, which
Michael Welch
With Mailman, is there any clue in a received message header that the original
message went through moderation and was approved -- as opposed to being sent
unmoderated?
There is an X-Mailman-Approved-At: header.
Also, I sent this previously through my From address' smtp
[EMAIL PROTECTED] wrote:
/etc/aliases is the location of my aliases file and that's where postfix
is pointing. I cannot change the owner to the aliases and aliases.db or
else I can't run newaliases.
I ran ./configure --with-mail-god=nobody
and I have default_privs = nobody
Any other
[EMAIL PROTECTED] wrote, in reply:
/etc/aliases is the location of my aliases file and that's where postfix
is pointing. I cannot change the owner to the aliases and aliases.db or
else I can't run newaliases.
I ran ./configure --with-mail-god=nobody
and I have default_privs = nobody
Any other
Thanks again, Mark, this is all *very* appreciated.
I'm interested in how many of these addresses are u'...', and how
they got to be that way.
Of the 1639 e-mail addresses, 349 are u'...' I don't have any great
ideas about what might be out of the ordinary about my installation.
I've
Here is what main.cf has as far as alias settings:
alias_maps = hash:/etc/aliases
When I run a locate aliases here are all the places it exists and am not
sure what to put:
/etc/aliases
/etc/aliases.db
/etc/alsa/cards/aliases.alisp
/etc/alsa/cards/aliases.conf
/etc/alternatives/mta-aliasesman
Josh Clark wrote:
Thanks again, Mark, this is all *very* appreciated.
I'm interested in how many of these addresses are u'...', and how
they got to be that way.
Of the 1639 e-mail addresses, 349 are u'...' I don't have any great
ideas about what might be out of the ordinary about my
[EMAIL PROTECTED] wrote:
Here is what main.cf has as far as alias settings:
alias_maps = hash:/etc/aliases
When I run a locate aliases here are all the places it exists and am not
sure what to put:
snip
What Barry is talking about may or may not be exactly what is described
in the installation
TGPlatt, WebMaster wrote:
Could this be a group/owner-ship issue?
Yes. It took me a while, but I finally connected you with our exchanges
from last June/July :)
It hadn't occurred to me to look for mailman's error log. Plus I had no idea
where it was. I've seen it mentioned but I'd seen
19 matches
Mail list logo
