Re: [Mailman-Users] Unable to access web interface
-Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Sunday, May 15, 2005 6:00 PM To: [EMAIL PROTECTED]; mailman-users@python.org Subject: Re: [Mailman-Users] Unable to access web interface Can you administer other lists? Does mailman write to other log files successfully? Does /usr/local/mailman/logs/error exist? if so, you might try moving it elsewhere and let Mailman create a new one and see if that helps. All lists on the mailman server web interface have the same error and I am unable to access to administer any of them. The log files seem to be fine. I zeroed them all out and they are all being written to successfully now, including the error log. I suspect there is some error in the config.pck or some other file for the list and then the failed attempt to log *that* error is what you see on the bug page. I renamed (deleted) all config.pck files for each list and the web interface shows the same bug message. This is the reason I believe that the bug message on the web interface is reading a file somewhere instead of dynamically producing the page. It has remained the same bug message no matter what I have done to any mailman files. William McLain -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems: (110, 'Connection timed out')
On Sun, May 15, 2005 at 08:48:51PM -0500, Matt England wrote: [EMAIL PROTECTED] 8:47pm [...vpopmail/etc] 136 cat /etc/tcp.smtp 127.:allow,RELAYCLIENT= Don't you also need to allow relaying from your IP address block? http://www.gnu.org/software/mailman/mailman-install/qmail-issues.html On Sun, May 15, 2005 at 10:49:11PM -0500, Matt England wrote: I can run the following test ok: [EMAIL PROTECTED] 10:35pm [~] 1 telnet localhost 25 Trying 127.0.0.1... Mailman tries to connect to your mail host (DEFAULT_EMAIL_HOST in the simplest case, but it is a function of the add_virtualhost() statements in your mm_cfg.py). This is not specified as localhost (or 127.0.0.1)... so this is not a fair test. -- Jim Tittsler http://www.OnJapan.net/ GPG: 0x01159DB6 Python Starship http://Starship.Python.net/crew/jwt/ Mailman IRC irc://irc.freenode.net/#mailman -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Allow a domain to post to a list
I've been searching but I don't found the right way to do this. This is my config file: ... # Use this option if you want to restrict posting to list members. If # you want list members to be able to post, plus a handful of other # posters, see the i posters /i setting below # # legal values are: #0 = No #1 = Yes member_posting_only = 1 # Adding entries here will have one of two effects, according to whether # another option restricts posting to members. ul li If # imember_posting_only/i is 'yes', then entries added here will have # posting privilege in addition to list members. li If # imember_posting_only/i is 'no', then emonly/em the posters # listed here will be able to post without admin approval. /ul #posters = [] posters = ['@my.uni.es'] ... And I want to allow all members of the domain my.uni.es to post to the list but I don't fint the correct syntax to do this (if it can be done) thanks people -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] How do the spammers do it?
Brad Knowles wrote: ... If the signature is automatically generated by the MUA, then the trojans/spybots can make use of this and still get through. The only way you can make this work is if you require actual human intervention on the part of the sender, That's true and is also the normal working model for signed messages. and that would probably also require human intervention on the part of the mailing list administrator -- for each and every message. That's not true. A mail signature is basically a hash value encrypted with a secret key. The public key, which is always passed along with the hash value, allows to decode the hash value and check the mail integrity. So you simply need to save the user public key, that you receive with the signed subscription confirmation mail, with the other user info. Whenever this user sends a signed mail to the list you use his public key to decode the hash value and check the mail integrity. If it's valid you may forward it to the list. The signature can be removed if desired. This would protect the list from forged mails. For lists that don't require subscription, there is no way to make a difference with spammers and normal users. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] mp3 attachment
If I send a 500K mp3 attachment to one of my lists, it disappears. I don't get any moderator requests. The acceptable file size is OK per the web interface setup. If I send the same attachment to a regular email acct, it comes through fine. I assume this has something to do with the type of allowed attachments? If so, would someone please tell me what I need to add exactly/where to allow mp3 attachments? Thanks - John -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.10 - Release Date: 5/13/2005 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems: (110, 'Connection timed out')
At 8:48 PM -0500 2005-05-15, Matt England wrote: There's absolutely zero qmail-smtpd log entries (from what I can tell) corresponding to a smtp usage from a localhost process. I'm grasping for air here and I find it rather frustrating. At this point, I'm afraid that there are relatively few people who are going to be able to help you. This may be a purely qmail problem, in which case you'd need to use their mailing lists, FAQs, documentation, etc... to help you resolve the issue. Or, this may be a problem with interactions between Mailman and qmail, and there just aren't very many people I know of who are running with this configuration. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems (qmail problems)
At 10:49 PM -0500 2005-05-15, Matt England wrote: It seems there's some problem with my SMTP server...I'm just trying to figure out what it is or how I can reproduce it other then keeping to point Mailman or phpBB forums at it (both fail for SMTP localhost connections). That sounds like a qmail problem, and you should be using their mailing lists, FAQs, documentation, etc... to help you resolve the problem. There is likely to be relatively little that we can do to help. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems (qmail problems)
At 11:48 PM -0500 2005-05-15, Matt England wrote: Another note: /usr/lib/sendmail is a qmail executable disguised as sendmail for backwards-compatibility. Unfortunately for you, qmail was never designed to be a drop-in replacement for sendmail. If you want to use qmail, you've got to drink all the djb kool-aid and completely replace everything in your OS for which there is a djb equivalent. Postfix is the only MTA that I know of that *was* designed to be a drop-in replacement for sendmail -- at least, as much as is possible. If you want to learn more about postfix, I'll be glad to give you my summary of why it's one of the best MTAs on the planet for use with mailing list servers, as well as point you at plenty of other resources that are likely to be useful to you. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] How do the spammers do it?
At 2:37 PM +0200 2005-05-16, Christophe Meessen wrote: If the signature is automatically generated by the MUA, then the trojans/spybots can make use of this and still get through. The only way you can make this work is if you require actual human intervention on the part of the sender, That's true and is also the normal working model for signed messages. Not with the plug-ins I've seen. They work to make cryptographic signatures as simple and easy to use as possible, which means that there must be absolutely no additional user involvement required. and that would probably also require human intervention on the part of the mailing list administrator -- for each and every message. That's not true. A mail signature is basically a hash value encrypted with a secret key. I am quite well acquainted with the nature of public key encryption. I've been using PGP since before the 2.6 days, I donated money to Phil for his defense, and I personally know Mike Elkins (the guy who wrote the PGP/MIME RFC, as well as the principal author of mutt, the premier PGP/MIME MUA). I don't use PGP today because it's too much of a pain to integrate with my MUA of choice on my platform of choice, although I am always close to being pushed over the edge to moving all ten-plus GB of my mail archives over to mutt, because I've been forced to futz around with this damn program one too many times. The problem is that if the crypto signature on the client side does not forcibly require the user to manually intervene and sign each and every message, then in order to achieve the result you're looking for you will instead force the list moderator to manually intervene and personally check and approve each and every message. Whenever this user sends a signed mail to the list you use his public key to decode the hash value and check the mail integrity. If it's valid you may forward it to the list. The signature can be removed if desired. This would protect the list from forged mails. But it wouldn't protect us at all against Sober.Q or whatever the latest variant is, since they already have complete control over the users MUA and they can send out millions of messages as being from that user, including all necessary cryptographic signatures. For lists that don't require subscription, there is no way to make a difference with spammers and normal users. The problem is far more complex (and worse) than that. Even for lists that do require subscriptions, there is no way you can reliably tell the difference between a legitimate mail message and spam, regardless of whether or not it was spoofed. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems (qmail problems)
Matt England wrote: It seems there's some problem with my SMTP server...I'm just trying to figure out what it is or how I can reproduce it other then keeping to point Mailman or phpBB forums at it (both fail for SMTP localhost connections). The symptoms you have described do not really arise at the level of Mailman code, even in SMTPDirect.py. If this is not strictly a qmail issue, the problems probably occur in the interface between the Python library and qmail, not in Mailman. Did you update or change Python coincident with the start of these troubles? In another post, you mentioned using Sendmail.py. I hope you have read and carefully considered all the comments in that module. -- Mark Sapiro [EMAIL PROTECTED] 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems (qmail problems)
On 5/16/05 7:11 AM, Brad Knowles [EMAIL PROTECTED] wrote: Postfix is the only MTA that I know of that *was* designed to be a drop-in replacement for sendmail -- at least, as much as is possible. Exim, also. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Unable to access web interface
William McLain wrote: The log files seem to be fine. I zeroed them all out and they are all being written to successfully now, including the error log. Are any errors being written when you get this Bug message? ... the web interface shows the same bug message. This is the reason I believe that the bug message on the web interface is reading a file somewhere instead of dynamically producing the page. It has remained the same bug message no matter what I have done to any mailman files. Unlikely, but could it be cached in your browser or a proxy? -- Mark Sapiro [EMAIL PROTECTED] 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems: (110, 'Connection timed out')
Jim Tittsler wrote: Mailman tries to connect to your mail host (DEFAULT_EMAIL_HOST in the simplest case, but it is a function of the add_virtualhost() statements in your mm_cfg.py). This is not specified as localhost (or 127.0.0.1)... so this is not a fair test. Are you sure Jim? This is the code in SMTPDirect.py def __connect(self): self.__conn = smtplib.SMTP() self.__conn.connect(mm_cfg.SMTPHOST, mm_cfg.SMTPPORT) self.__numsessions = mm_cfg.SMTP_MAX_SESSIONS_PER_CONNECTION -- Mark Sapiro [EMAIL PROTECTED] 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Allow a domain to post to a list
Miguel Tarazona Belenguer wrote: This is my config file: ... # Use this option if you want to restrict posting to list members. If # you want list members to be able to post, plus a handful of other # posters, see the i posters /i setting below # # legal values are: #0 = No #1 = Yes member_posting_only = 1 # Adding entries here will have one of two effects, according to whether # another option restricts posting to members. ul li If # imember_posting_only/i is 'yes', then entries added here will have # posting privilege in addition to list members. li If # imember_posting_only/i is 'no', then emonly/em the posters # listed here will be able to post without admin approval. /ul #posters = [] posters = ['@my.uni.es'] ... And I want to allow all members of the domain my.uni.es to post to the list but I don't fint the correct syntax to do this (if it can be done) This is an old version of Mailman. Those attributes don't exist in current versions, but assuming that current syntax might apply here, try posters = ['[EMAIL PROTECTED]'] This assumes that a regular expression is allowed in the 'posters' list and an initial '^' signals a regular expression. In current Mailman, this would be 'accept_these_nonmembers' and the above syntax would work. -- Mark Sapiro [EMAIL PROTECTED] 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mp3 attachment
John Fleming wrote: I assume this has something to do with the type of allowed attachments? If so, would someone please tell me what I need to add exactly/where to allow mp3 attachments? It depends on how your Content filtering is currently set up. The mime type of an mp3 should be 'audio/mpeg', but the sending MUA may give it another type, even 'application/octet-stream'. If you allow the latter, you might as well just turn content filtering off. Anyway, assuming your filtering is currently set up with filter_mime_types empty and some entries in pass_mime_types, you need to add audio/mpeg and if not there already, multipart/mixed to pass_mime_types. That should work for all correct mp3 attachments. -- Mark Sapiro [EMAIL PROTECTED] 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems: (110, 'Connection timed out')
At 5/16/2005 10:27 AM, Mark Sapiro wrote: Jim Tittsler wrote: Mailman tries to connect to your mail host (DEFAULT_EMAIL_HOST in the simplest case, but it is a function of the add_virtualhost() statements in your mm_cfg.py). This is not specified as localhost (or 127.0.0.1)... so this is not a fair test. Are you sure Jim? This is the code in SMTPDirect.py def __connect(self): self.__conn = smtplib.SMTP() self.__conn.connect(mm_cfg.SMTPHOST, mm_cfg.SMTPPORT) self.__numsessions = mm_cfg.SMTP_MAX_SESSIONS_PER_CONNECTION It doesn't much matter from what I can tell. I ran the following test, where lists.biz2tek.com is both the email and URL host. [EMAIL PROTECTED] 11:46am [/etc] 14 telnet lists.biz2tek.com 25 Trying 204.157.9.73... Connected to lists.biz2tek.com. Escape character is '^]'. 220 biz2tek.com ESMTP helo 250 biz2tek.com mail from:[EMAIL PROTECTED] 250 ok rcpt to:[EMAIL PROTECTED] 250 ok data 354 go ahead Subject: test just a test. . 250 ok 1116262038 qp 32097 quit 221 biz2tek.com Connection closed by foreign host. [EMAIL PROTECTED] 11:47am [/etc] 15 The above failed previously, but I updated /etc/tcp.smtp to relay from lists.biz2tek.com, and now it works...but SMTP based outbound mail still does not work. I still can get the sendmail-based mechanism (with qmail impersonating sendmail) to work, but the SMTP-based mechanism does not work. And yes, this does appear to be qmail problem (I'll followup the other notes). And yes, qmail does have a sendmail drop in as far as I can tell (I've been using it for months now). I realize this is a Mailman group, so I may stop with this thread (other then following up a couple other points) given that it appears to be a qmail issue...but any input is appreciated. :) -Matt -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems (qmail problems)
At 5/16/2005 09:11 AM, Brad Knowles wrote: At 11:48 PM -0500 2005-05-15, Matt England wrote: Another note: /usr/lib/sendmail is a qmail executable disguised as sendmail for backwards-compatibility. Unfortunately for you, qmail was never designed to be a drop-in replacement for sendmail. That's not my understanding. I've got /usr/lib/sendmail linked to a qmail gizmo, and it's been working for months now. It says so in the qmail docs. Is there something I'm missing? Also, the Sendmail.py-based Mailman stuff appears to be working with no problems for me (other then the warnings from the Mailman developrs not to use it...which is why I'm in this investigation). -Matt Postfix is the only MTA that I know of that *was* designed to be a drop-in replacement for sendmail -- at least, as much as is possible. If you want to learn more about postfix, I'll be glad to give you my summary of why it's one of the best MTAs on the planet for use with mailing list servers, as well as point you at plenty of other resources that are likely to be useful to you. Yes, this is a viable option. What more can you tell me and/or what references can you give me? I invite you to take conversation offline from the list if that's more appropriate? One curiosity: I'm curious if Postfix can support virtual domains as well as qmail can? (Maybe that's hard to answer if one does not know qmail.) When I first looked at Postfix, the seemingly massive amount of script/config-file setup was completely overwhelming to me...or was that exim I was checking out? There was some specific set of reasons why I chose qmail over Postfix, but I can't remember them. The fact that yahoo.com and smtp.com both seem to be qmail-based systems have a large pull with me, though; I get the impression Postfix hasn't been around the block as long as qmail, but that does not mean that it's not stable. Did I just start a postfix-vs-qmail rat hole? (That could probably help me, but it may take away from the list.) -Matt -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems: (110, 'Connection timed out')
At 5/16/2005 09:07 AM, Brad Knowles wrote: At this point, I'm afraid that there are relatively few people who are going to be able to help you. This may be a purely qmail problem, in which case you'd need to use their mailing lists, FAQs, documentation, etc... to help you resolve the issue. I'm leveraging those communities as well. -Matt -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Rewriting of headers
A list I administer using Mailman 2.1.5 just sent out a large blast. The list is configured like: anonymous_list - yes first_strip_reply_to - yes reply_goes_to_list - poster description - Russ Smith's Property Of The Week The moderator just sent out a post with the following headers: From: Joe Schmoe [EMAIL PROTECTED] Date: May 16, 2005 9:55:06 AM MDT To: [EMAIL PROTECTED] Subject: A True Mountain Estate in Durango Colorado And the post arrived in the subscribers' mailboxes with the following headers: From: [EMAIL PROTECTED] Date: May 16, 2005 9:55:06 AM MDT To: Joe Schmoe [EMAIL PROTECTED] Cc: Russ Smith's Property Of The Week [EMAIL PROTECTED] Subject: A True Mountain Estate in Durango Colorado Why wasn't the name of the list in the From address? And where did the cc come from? Thanks! -jag Joshua Ginsberg -- [EMAIL PROTECTED] Brainstorm Internet Network Operations 970-247-1442 x131-- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Plain text attachments
Sorry to bug y'all again... A recent posting was composed as an HTML email in MS Outlook 2k3... I've got the list configured to have a plain text footer with the unsubscribe information... In MS Outlook, Outlook Express, Horde IMP, and Apple Mail, the plain text footer was listed as an attachment but not displayed inline. Is there something stupid I'm doing to prevent the footer from being displayed inline? I usually send out plain text posts, so this whole posting HTML thing is new to me. Thanks! -jag -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Plain text attachments
On Mon, 2005-05-16 at 11:40 -0600, Joshua Ginsberg wrote: Sorry to bug y'all again... A recent posting was composed as an HTML email in MS Outlook 2k3... I've got the list configured to have a plain text footer with the unsubscribe information... In MS Outlook, Outlook Express, Horde IMP, and Apple Mail, the plain text footer was listed as an attachment but not displayed inline. Is there something stupid I'm doing to prevent the footer from being displayed inline? I usually send out plain text posts, so this whole posting HTML thing is new to me. Thanks! http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.039.htp -- John Dennis [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems (qmail problems)
At 11:57 AM -0500 2005-05-16, Matt England wrote: Yes, this is a viable option. What more can you tell me and/or what references can you give me? I invite you to take conversation offline from the list if that's more appropriate? Yes, offline is best. Did I just start a postfix-vs-qmail rat hole? (That could probably help me, but it may take away from the list.) Yeah, it's not really a good idea open up that kind of a flamefest on the list. Best to take it offline. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Mailman Bug?/no Admin level web access
I'm hoping someone can help me fix this. I installed mailman, and couldn't figure out why the web interface didn't work. It seems I CAN access any of the pages, but the admin ones. I get a lovely message in the browser: Bug in Mailman version 2.1.6rc3 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. My mailman log shows nothing, hasn't been updated since May 10th, but Apache's log shows useful information: [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [- Mailman Version: 2.1.6rc3 -] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [- Traceback --] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] Traceback (most recent call last): [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] File /usr/local/mailman/scripts/driver, line 82, in run_main [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] immediate=1) [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] File /usr/local/mailman/Mailman/Logging/StampedLogger.py, line 52, in __init__ [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] Logger.__init__(self, category, nofail, immediate) [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] File /usr/local/mailman/Mailman/Logging/Logger.py, line 49, in __init__ [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] self.__get_f() [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] File /usr/local/mailman/Mailman/Logging/Logger.py, line 67, in __get_f [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] 1) [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] File /usr/lib/python2.3/codecs.py, line 566, in open [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] file = __builtin__.open(filename, mode, buffering) [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] IOError: [Errno 13] Permission denied: '/usr/local/mailman/logs/error' [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [- Python Information -] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] sys.version = [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] 2.3.4 (#1, Feb 2 2005, 12:11:53) [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [GCC 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] sys.executable = [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] /usr/bin/python [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] sys.prefix = [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] /usr [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] sys.exec_prefix = [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] /usr [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] sys.path= [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] /usr [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] sys.platform= [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] linux2 [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [- Environment Variables -] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] \tSERVER_SOFTWARE: Apache/2.0.52 (Fedora) [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] \tSCRIPT_NAME: /mailman/admin.cgi [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] \tSERVER_SIGNATURE: addressApache/2.0.52 (Fedora) Server at imcserver.gotdns.org Port 80/address [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] \tREQUEST_METHOD: GET [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] \tHTTP_KEEP_ALIVE: 300 [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] \tSERVER_PROTOCOL: HTTP/1.1 [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04
Re: [Mailman-Users] Rewriting of headers
Joshua Ginsberg wrote: The moderator just sent out a post with the following headers: From: Joe Schmoe [EMAIL PROTECTED] Date: May 16, 2005 9:55:06 AM MDT To: [EMAIL PROTECTED] Subject: A True Mountain Estate in Durango Colorado And the post arrived in the subscribers' mailboxes with the following headers: From: [EMAIL PROTECTED] Date: May 16, 2005 9:55:06 AM MDT To: Joe Schmoe [EMAIL PROTECTED] Cc: Russ Smith's Property Of The Week [EMAIL PROTECTED] Subject: A True Mountain Estate in Durango Colorado Why wasn't the name of the list in the From address? Mailman doesn't put it there. It just puts the list's e-mail address. This changes in 2.1.6 to add the list's 'description' so the From: will look like the Cc: does above. And where did the cc come from? Thanks! It's there to facilitate replying to the list when the list is fully personalized. In this case, it's redundant because the list is also anonymous. This is fixed in 2.1.6. See http://sourceforge.net/tracker/index.php?func=detailaid=1117618group_id=103atid=300103 for a 2.1.5 patch. -- Mark Sapiro [EMAIL PROTECTED] 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Unable to access web interface
-Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Monday, May 16, 2005 8:19 AM To: [EMAIL PROTECTED]; mailman-users@python.org Subject: Re: [Mailman-Users] Unable to access web interface William McLain wrote: The log files seem to be fine. I zeroed them all out and they are all being written to successfully now, including the error log. Are any errors being written when you get this Bug message? No... but errors are being written. When I renamed (deleted) config.pck the log shows that error. ... the web interface shows the same bug message. This is the reason I believe that the bug message on the web interface is reading a file somewhere instead of dynamically producing the page. It has remained the same bug message no matter what I have done to any mailman files. Unlikely, but could it be cached in your browser or a proxy? Well, I don't know, I refreshed my browser several times with no change and I do not use a proxy nor am I aware of any proxy in use. In another effort to fixthe problem, I removed all lists and created them again, but still had the same bug page showing on the web interface. As a last resort, I removed mailman fron the system and reinstalled it. That fixed the problem. Fortunately I do not have many lists on the server so it wasn't too much work. At least it seemed easier than trying to track down the actual problem. Well, anyhow, thanks for your help William McLain -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems (qmail problems)
Matt == Matt England [EMAIL PROTECTED] writes: Matt That's not my understanding. I've got /usr/lib/sendmail Matt linked to a qmail gizmo, and it's been working for months Matt now. It says so in the qmail docs. Matt Is there something I'm missing? Dan Bernstein is a very smart guy with a different perspective on many things. This has resulted in him producing a slew of unconventional software. It works well in combination with other Bernstein software, but it is designed to be excellent software in Bernstein's opinion, NOT to be compatible with any other software in the world, except where that would make his software completely unusable. You might be amused to check Rick's Rants: http://linuxmafia.com/~rick/faq/ -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of TsukubaTennodai 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. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] messages not archiving
Hello, I've recently upgraded my list hosting server by essentially doing a fresh install on a new server and then recreating the lists and transferring over their archives over. I ran bin/arch and pickled the mailboxes. Everything is working fine, except the messages are not posting to the archives. What did I miss? I'm desperate to get this fixed. Any ideas would be welcome. Best wishes, Rae -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] messages not archiving
List Manager wrote: I've recently upgraded my list hosting server by essentially doing a fresh install on a new server and then recreating the lists and transferring over their archives over. I ran bin/arch and pickled the mailboxes. Everything is working fine, except the messages are not posting to the archives. What did I miss? Did you check the Archiving options for the list to make sure archiving is on? How about permissions? Have you run bin/check_perms? Have you looked at Mailman's error log? -- Mark Sapiro [EMAIL PROTECTED] 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] messages not archiving (fixed)
Hello, I finally was able to fix it. While delving into the server to see if anything would catch my eye I noticed that some of the ownerships were set to root so I chowned everything under archives/private to mailman:mailman and then ran bin/unshunt and it seemed to do the trick. :) Best wishes, Rae -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman Bug?/no Admin level web access
On Mon, May 16, 2005 at 02:14:02PM -0400, [EMAIL PROTECTED] wrote: I'm hoping someone can help me fix this. I installed mailman, and couldn't figure out why the web interface didn't work. It seems I CAN access any of the pages, but the admin ones. I get a lovely message in the browser: Bug in Mailman version 2.1.6rc3 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. My mailman log shows nothing, hasn't been updated since May 10th, but Apache's log shows useful information: [...] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] IOError: [Errno 13] Permission denied: '/usr/local/mailman/logs/error' Did you run bin/check_perms? The logs directory and the files within it should be group writable (and owned by the group that you specified as with-mail-gid when you built Mailman). It looks like Mailman is unable to write to your logs (which explains why they haven't changed since May 10th). -- Jim Tittsler http://www.OnJapan.net/ GPG: 0x01159DB6 Python Starship http://Starship.Python.net/crew/jwt/ Mailman IRC irc://irc.freenode.net/#mailman -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman Bug?/no Admin level web access
Elissa wrote: I'm hoping someone can help me fix this. I installed mailman, and couldn't figure out why the web interface didn't work. It seems I CAN access any of the pages, but the admin ones. I get a lovely message in the browser: Bug in Mailman version 2.1.6rc3 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. My mailman log shows nothing, hasn't been updated since May 10th, but Apache's log shows useful information: [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [- Mailman Version: 2.1.6rc3 -] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [- Traceback --] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] Traceback (most recent call last): [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] File /usr/local/mailman/scripts/driver, line 82, in run_main [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] immediate=1) [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] File /usr/local/mailman/Mailman/Logging/StampedLogger.py, line 52, in __init__ [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] Logger.__init__(self, category, nofail, immediate) [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] File /usr/local/mailman/Mailman/Logging/Logger.py, line 49, in __init__ [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] self.__get_f() [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] File /usr/local/mailman/Mailman/Logging/Logger.py, line 67, in __get_f [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] 1) [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] File /usr/lib/python2.3/codecs.py, line 566, in open [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] file = __builtin__.open(filename, mode, buffering) [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] IOError: [Errno 13] Permission denied: '/usr/local/mailman/logs/error' [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [- Python Information -] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] sys.version = [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] 2.3.4 (#1, Feb 2 2005, 12:11:53) [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [GCC 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] sys.executable = [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] /usr/bin/python [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] sys.prefix = [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] /usr [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] sys.exec_prefix = [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] /usr [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] sys.path= [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] /usr [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] sys.platform= [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] linux2 [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [- Environment Variables -] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] \tSERVER_SOFTWARE: Apache/2.0.52 (Fedora) [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] \tSCRIPT_NAME: /mailman/admin.cgi [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] \tSERVER_SIGNATURE: addressApache/2.0.52 (Fedora) Server at imcserver.gotdns.org Port 80/address [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] \tREQUEST_METHOD: GET [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] \tHTTP_KEEP_ALIVE: 300 [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] \tSERVER_PROTOCOL: HTTP/1.1 [Mon May 16 13:13:04 2005] [error] [client 127.0.0.1] [Mon May
Re: [Mailman-Users] Mailman Bug?/no Admin level web access
Elissa wrote: snip I'm using my aol address to make sure I get my mail. Well, that doesn't work. My reply to you was bounced by AOL because * 554 HVU:B1 http://postmaster.info.aol.com/errors/554hvub1.html EXPLANATION: There is at least one URL in your email that is generating substantial complaints from AOL members. Since the only URL in my message to you was a pointer to another thread in the lists archives, I suppose I can only hint at it. Go to the archives for the mailman-users list by constructing a URL with host name mail.python.org and the remainder = /pipermail/mailman-users/2005-May/044739.html. There you'll find my previous reply with another archive pointer. Also see Jim Tittsler's response in this thread. -- Mark Sapiro [EMAIL PROTECTED] 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems (qmail problems)
At 5/16/2005 09:45 AM, Mark Sapiro wrote: Matt England wrote: It seems there's some problem with my SMTP server...I'm just trying to figure out what it is or how I can reproduce it other then keeping to point Mailman or phpBB forums at it (both fail for SMTP localhost connections). The symptoms you have described do not really arise at the level of Mailman code, even in SMTPDirect.py. If this is not strictly a qmail issue, the problems probably occur in the interface between the Python library and qmail, not in Mailman. Did you update or change Python coincident with the start of these troubles? Not that I'm aware of. Note that phpBB is experiencing similar problems, and it is php based and not python based. This further points the finger at qmail...or at least both php-to-qmail and python-to-qmail. Care to offer any suggestions about how I can isolate these php-to-qmail and python-to-qmail problems...with like test scripts? How do I write it, and/or do simple, stand-alone scripts already exist? Can someone write me one? I realize I'm asking a lot from a Mailman group to help solve an apparent qmail problem...and for what it's worth, I just lobbed as massive email over to the official qmail discussion list (qmail@list.cr.yp.to), too (I had previously been posting to forum.qmailrocks.org). I'm also in discussion with Brad K. about a switch to postfix. (Note that another post shows how a 'telnet lists.biz2tek.com 25' outbound email works ok.) In another post, you mentioned using Sendmail.py. I hope you have read and carefully considered all the comments in that module. Yes, I did. Sendmail.py is only a temporary solution, possibly only for debugging purposes so that I could prove that Mailman (and outbound email in general) was working. -Matt -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outbound smtp email problems (qmail problems)
Matt England wrote:
Care to offer any suggestions about how I can isolate these php-to-qmail
and python-to-qmail problems...with like test scripts? How do I write it,
and/or do simple, stand-alone scripts already exist? Can someone write me one?
The following is an example of an interactive python session that sends
a message to two recipients in exactly the same way that SMTPDirect.py
does. Actual addresses and domains have been munged for privacy, but
the session works and causes the message to be sent via the smtp
server at 'localhost' via the default port (port = 0 to the connect
method says use the default which is 25).
The values assigned to SMTPHOST and SMTPPORT are from Defaults.py. If
you find you need to change them in any way to make this work, make
the same changes in mm_cfg.py.
msg can be as elaborate as you want.
the rcpts list should contain valid recipients - this is the only
change required for it to actually send mail.
$ python
Python 2.3.3 (#1, May 7 2004, 10:31:40)
[GCC 3.3.3 20040412 (Red Hat Linux 3.3.3-7)] on linux2
Type help, copyright, credits or license for more information.
import smtplib
msg = Subject: Test Message
... Message-Id: [EMAIL PROTECTED]
... From: [EMAIL PROTECTED]
... To: you
...
... The body
...
rcpts = ['[EMAIL PROTECTED]', '[EMAIL PROTECTED]']
env = '[EMAIL PROTECTED]'
SMTPHOST = 'localhost'
SMTPPORT = 0
x = smtplib.SMTP()
x.connect(SMTPHOST, SMTPPORT)
(220, 'sb7.example.com ESMTP Sendmail 8.12.11/8.12.11; Mon, 16 May 2005
18:08:07 -0700')
x.sendmail(env, rcpts, msg)
{}
--
Mark Sapiro [EMAIL PROTECTED] 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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman Bug?/no Admin level web access
In a message dated 5/16/2005 6:37:20 PM Eastern Daylight Time, [EMAIL PROTECTED] writes: Well, that doesn't work. My reply to you was bounced by AOL because * 554 HVU:B1 http://postmaster.info.aol.com/errors/554hvub1.html This may be true, but the server mail doesn't get checked nearly as often as the AOL account, and the server runs from a REALLY filtered server. I've noticed AOL labelling my digests as bulk mail, but I've still gotten them, while the mail from the server I created goes into my bulk folder. In response to the question about checking permissions, yes, I've run it several times, and genaliases, check_db and anything else I thought might provide a clue. All checked out ok. I did see the other thread. He trashed his log file and that restarted logging so I'll do that. We both have exactly the same issue, new install where those cgi scripts never ran from day one- and even the same errors showing up in logs. I'm no programmer, but is there something different in the admin and admindb cgi scripts? Elissa -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mp3 attachment
It depends on how your Content filtering is currently set up. The mime type of an mp3 should be 'audio/mpeg', but the sending MUA may give it another type, even 'application/octet-stream'. If you allow the latter, you might as well just turn content filtering off. Anyway, assuming your filtering is currently set up with filter_mime_types empty and some entries in pass_mime_types, you need to add audio/mpeg and if not there already, multipart/mixed to pass_mime_types. That should work for all correct mp3 attachments. Thanks for the thoughts, Mark - I figured I could fix it in this area, but I haven't been successful. First, I added audio/mpg to pass_mime_types and then also even application/octet-stream - However, even with these added, the mail just disappears - the whole email, not just the attachment. And it's not in the spam or virus traps. Finally, I even noticed that content filtering IS turned off!! So that means ANYTHING passes, right? I just don't understand why it disappears without being rejected or serving notice that moderation is needed. (That's what happens when spam is detected.) Any other ideas? - John -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.10 - Release Date: 5/13/2005 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] SOLVED Re: mp3 attachment
Anyway, assuming your filtering is currently set up with filter_mime_types empty and some entries in pass_mime_types, you need to add audio/mpeg and if not there already, multipart/mixed to pass_mime_types. That should work for all correct mp3 attachments. Actually, solved might not be quite accurate. Since my content filtering was turned OFF, it shouldn't matter if I added audio/mpeg to the pass types. However, the observation is that after I did that, it worked and allowed the mp3 attachment to come through. At first I had thought that it didn't, but I guess I didn't wait long enough, and it took a little longer for SA and ClamAV to process the message. It showed up a tad bit later than I expected, after my post! So I don't understand what happened yet, but it is working! Sorry for the bother, but I did learn something about content filtering and mime types. - John -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.10 - Release Date: 5/13/2005 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] SOLVED Re: mp3 attachment
Anyway, assuming your filtering is currently set up with filter_mime_types empty and some entries in pass_mime_types, you need to add audio/mpeg and if not there already, multipart/mixed to pass_mime_types. That should work for all correct mp3 attachments. Actually, solved might not be quite accurate. Since my content filtering was turned OFF, it shouldn't matter if I added audio/mpeg to the pass types. However, the observation is that after I did that, it worked and allowed the mp3 attachment to come through. At first I had thought that it didn't, but I guess I didn't wait long enough, and it took a little longer for SA and ClamAV to process the message. It showed up a tad bit later than I expected, after my post! So I don't understand what happened yet, but it is working! Sorry for the bother, but I did learn something about content filtering and mime ypes. - John Another very weird thing is the the limited headers on the mail that was successfully delivered with the attachment to the list: Date: Mon, 16 May 2005 21:29:30 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_NextPart_000_0003_01C55A5E.581B7FB0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Any comments about the Content Type? And I'm missing my usual headers from ClamAV and SpamAssassin for this mail only! Oh well, this is getting a little disjointed (my fault). I'll report back if and when things clarify a little. - John -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.10 - Release Date: 5/13/2005 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] SOLVED Re: mp3 attachment
John Fleming wrote: Another very weird thing is the the limited headers on the mail that was successfully delivered with the attachment to the list: Date: Mon, 16 May 2005 21:29:30 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_NextPart_000_0003_01C55A5E.581B7FB0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Any comments about the Content Type? The top level Content-Type: multipart/mixed is exactly what it should be for a message with any kind of attachment. That's why if you're filtering, you need multipart/mixed in mime_pass_types as well as audio/mpeg or whatever since the audio/mpeg is a sub part of a multipart/mixed part. And I'm missing my usual headers from ClamAV and SpamAssassin for this mail only! Oh well, this is getting a little disjointed (my fault). I'll report back if and when things clarify a little. - John Maybe the message came to you via some other route? -- Mark Sapiro [EMAIL PROTECTED] 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
