[Mailman-Users] Can HTML mail support footer
Hello mailman users, Mailman is only supporting footers and headers for text based mails and not for html formated mail. does any body tried to use html formatted mail with footers and headers. please write any suggestions. Thanks in Advance Vijay -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sat, 12 May 2001, J C Lawrence wrote: > Your math is off as it ignores RCPT-TO envelope size. So throw in a few more bytes times 10k and it gets even bigger > 1) If your messages are getting corrupted, AT ALL, you have far more > serious problems than how fast your system is able to deliver a list > broadcast. Something is fundamentally broken and that needs to be > fixed, now, before you start worrying about much else. > > 2) Transfer failures given a good MTA and reasonable choice of RCPT > TO bundle size should cause minimal problem in delivery rates for > the list broadcast. Empirical testing here, for my admittedly very > atypical membership/domain distribution suggests that between 5 and > 25 is my sweet spot under Postfix. Chuq IIRC has found for his > locad under Sendmail that somewhere in the 30 range is his sweet > pot. Vour mileage will vary. > > 3) If delivery failures are clogging your MTA queue and are > noticably slowing delivery rates, you need to start thinking about > reviewing your MTA configuration or using a different and more > intelligent MTA. Point > Actually, list servers are generically disk IO bound with the > primary factor in the disk IO being open/close/unlink time not > read/write time. I'm not quite the hardware guru I'd like to be yet - explain in english please? > This assumes of course that the audience has web access, and in > particular has web access at the time and on the device they would > normally read the messages. > > Example : It wouldn't work for me reading on the train on my > laptop. Who has email that does not have web access at the time they get their email? Granted I suppose it's possible that you would download your mail ahead of time before leaving home and then opening your laptop on the train. > Result? > > I get to read what I'm interested in on the list, and any time I > post to the list, I get to see everything on that thread until it > dies. Meanwhile the rest of the list passes me silently by. I > can of course go read the main list folder any time I want, which > I do periodically to update the key word lists -- but usually its > enough to just read -interesting. > > That sort of autmation would be simply impossible with the web-based > distribution you describe. The load shift is a valid concern, and does change from a 'push' to a 'pull' format. True: users who have a bland interest in the article that is being posted will probably not pull down the URL - what's the problem with this, it's saved bandwidth. Anyone who is /actually/ interested and can take the time to read/parse through 30k worth of email will take an extra second to click on a link or do what not to pull up what they want. And I do understand that this means that a person may actually pull on that link a number of times on different occasions. However it's now pulling on a webserver rather than pushing through an email server, which depending on it's configuration may have as few as one outward connection at a time (which I'm not sure how rare /that/ is, my original sendmail server only had 1 outbound, but my current qmail setup allows up to 50 outward smtp connections at once), and a webserver is designed to be pulled on a lot. Most basic configurations will start anywhere from 10 to 20 instances at once, and the 'high bandwidth' demand won't be high at all if you keep the presentation simple and clean and non-graphicy - just you like you'd get in a 30k message that got pushed out to you. Plus, if you really want to get finicky, the manner of processing http requests churns out fewer headers and data than mail. Also, unless 100% of your user base is actually reading the article, you're going to be saving bandwidth (some people may open an article more than just once, but most will read it once and be done, in which case you will come out a little bit ahead instead of a lot). The load of an entire batch (rough 300meg estimate) will also be spread out more over the course of a few days as everyone checks their mail and may or may not look at that message and cause it to draw on the url or click/paste it into a browser themselves. It all boils down to a matter of how you want to use your server. There are as many good points for as against everything I said and have been responded to with, however all the items presented have not really made an effect on my point of view. There are two sides to this debate, the client side (where the rebuttal for my view came from), and the server side (which I was presenting). If you want the best of both worlds, perhaps consider doing similar to many newspapers have done with their web presence/maling list user base. Send out a smaller email message which briefs the content of the full article and then present a link at the end which lets users get an idea of the article rather than flying blind on whether or not to follow the link or not. Cut a 30k message to 10k users down to maybe 5k in this way and y
Re: [Mailman-Users] big lists, big messages
On 5/13/01 12:22 AM, "Tib" <[EMAIL PROTECTED]> wrote: > Who has email that does not have web access at the time they get their email? Not a huge number, but not zero. As wireless mobile becomes more significant, it'll be a growing issue, not a shrinking one. > True: users who have a bland interest in the article that is being > posted will probably not pull down the URL - what's the problem with this, > it's > saved bandwidth If the piece of email is sponsored and has advertising, it's a HUGE problem. As was the original poster's note on this stuff. > However it's now pulling on a webserver rather than > pushing through an email server, which depending on it's configuration may > have > as few as one outward connection at a time (which I'm not sure how rare /that/ > is, my original sendmail server only had 1 outbound, but my current qmail > setup > allows up to 50 outward smtp connections at once), and a webserver is designed > to be pulled on a lot. Most basic configurations will start anywhere from 10 > to > 20 instances at once, and the 'high bandwidth' demand won't be high at all if > you keep the presentation simple and clean and non-graphicy - just you like > you'd get in a 30k message that got pushed out to you. Plus, if you really > want > to get finicky, the manner of processing http requests churns out fewer > headers > and data than mail. Um, Tib -- I've actually done this and measured it. Have you? You ignored pretty much all of the data in my message while responding to JC -- and you still sound like you're guessing at this stuff. Have you actually run servers in both configurations and measured response like I have? Because my numbers say you're wrong. > The load of an entire batch (rough 300meg > estimate) will also be spread out more over the course of a few days as > everyone checks their mail and may or may not look at that message and cause > it > to draw on the url or click/paste it into a browser themselves. No, it won't. There's a huge peak in the few hours after delivery, which drops radically after that and stretches out over about ten days or so. > It all boils down to a matter of how you want to use your server. And whether you want to pay for peak load capacities on your web server or the lower, spread out push capacities on your e-mail. Again, I have to ask. Have you actually done this with large lists? I'm curious if your numbers disagree with mine, or if you don't have numbers to back up what you're saying. I'd like to know if the data I've gathered may or may not be typical. If you've done it, what size lists? -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sun, 13 May 2001, Chuq Von Rospach wrote: > As wireless mobile becomes more significant, it'll be a growing issue, > not a shrinking one. Do you expect wireless mobile NOT to have web access? Hell, I use my web access when mobile much more than my email access. -- ROGER B.A. KLORESE [EMAIL PROTECTED] PO Box 14309San Francisco, CA 94114 "There is only one real blasphemy -- the refusal of joy!" -- Paul Rudnick -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On 5/13/01 12:44 AM, "Roger B.A. Klorese" <[EMAIL PROTECTED]> wrote: > Do you expect wireless mobile NOT to have web access? Hell, I use my web > access when mobile much more than my email access. No, but I expect wireless mobile to have limitations on display -- not to the level that WAP hoses you (into basically unusability), but in other directions. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sun, 13 May 2001, Chuq Von Rospach wrote: > On 5/13/01 12:22 AM, "Tib" <[EMAIL PROTECTED]> wrote: > If the piece of email is sponsored and has advertising, it's a HUGE problem. > As was the original poster's note on this stuff. If you're running on a 384k dsl then the only advertising is the stuff you put up yourself because it's your server. > Um, Tib -- I've actually done this and measured it. Have you? You ignored > pretty much all of the data in my message while responding to JC -- and you > still sound like you're guessing at this stuff. Have you actually run > servers in both configurations and measured response like I have? Because my > numbers say you're wrong. Well your numbers aren't my numbers, so of course they'll say I'm wrong, and if that's all you're intent on proving then feel free to flame/shoot down every one of my comments to me rather than wasting everyone elses time with it. > No, it won't. There's a huge peak in the few hours after delivery, which > drops radically after that and stretches out over about ten days or so. > > > It all boils down to a matter of how you want to use your server. > And whether you want to pay for peak load capacities on your web server or > the lower, spread out push capacities on your e-mail. I would think this would be a bit the opposite. For your mail server to push anything it has to look up records on the domain it's going to send to (which for 10k users I would assume to be a lot of domains), rather than just firing back a response to an ip for a data request (and will only lookup and put resolved host names into your log only if you tell it to do so). Again it would seem to me that the webserver would have an easier time with the load than the mail server. > Again, I have to ask. Have you actually done this with large lists? I'm > curious if your numbers disagree with mine, or if you don't have numbers to > back up what you're saying. I'd like to know if the data I've gathered may > or may not be typical. If you've done it, what size lists? What I have: A personally built server (PIII 500, 256mb memory, 30g hd) a 1.1 sdsl line 5 fully hosted domains 23 users (maybe a third of which are decently active for mail and web demands) 5 email lists running on mailman, the largest of which is about 300 users. mrtg to keep track of bandwidth usage basic algebra Do I run a newsletter like the original topic of this thread was about? Nope. Am I guessing a little about traffic and how it could happen if changed to the way I talked about? Yep. I say a little because I used to work for a company that was completely based off of this kind of newsletter and traffic, to the tune of about 8 million addresses, 200 mail servers, and about that many web servers. Dealing with systems on two vastly different scales (millions of users at my old company, and a handful at my own server - versus 10k towards the middle of the spectrum) turn experience into best guesses. I have never maxed out my bandwidth with list traffic, so my comments are /estimates/ of numbers and /estimates/ on behaviors of people based on myself as being 'joe average'. Tib -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] no mail delivery
Dear list-members,
I searched the archives and the whole web without any success. So, you'll understand
that any help on the following topic will be appreciated:
Trying to install Mailman-2.0.5 failed. Honestly, it's my 6th try, and I think it's
time to ask some people being more successful. Any try produced these errors: The
postings are not delivered to the list members. Additionally, a confirmation request
from any subscriber never arrives at the subscriber's mail account.
This is how I tried to install mailman on a Cobalt RaQ3 with sendmail 8.9.3:
- unpacking, creating mailman:mailman, creating /home/mailman right as shown in the
installation guide at lists.org
- my options to do ./configure were:
--prefix=/home/mailman
--with-username=mailman
--with-mail-gid=mail
--with-cgi-gid=httpd
- adding a symbolic link to /etc/smrsh:
124920 lrwxrwxrwx 1 root root 26 May 13 14:48 wrapper ->
/home/mailman/mail/wrapper
- mm_cfg.py:
from Defaults import *
# Site-specific settings
DEFAULT_HOST_NAME = 'raq.granus.net'
# DEFAULT_URL must end in a slash!
DEFAULT_URL = 'http://www.granus.net/mailman/'
PUBLIC_ARCHIVE_URL = '/pipermail'
PRIVATE_ARCHIVE_URL = '/mailman/private'
HOME_PAGE = 'index.html'
MAILMAN_OWNER = 'mailman-owner@%s' % DEFAULT_HOST_NAME
SMTPPORT = 25
- doing the last steps to create a site pass, creating a new list ('abc'), copying and
editing the /etc/aliases like this (and running newaliases successfully):
# Mailman 2.0.5 settings [13.05.01]
mailman:[EMAIL PROTECTED]
mailman-owner: mailman
## abc mailing list
## created: 13-May-2001 root
abc: "|/etc/smrsh/wrapper post abc"
abc-admin: "|/etc/smrsh/wrapper mailowner abc"
abc-request: "|/etc/smrsh/wrapper mailcmd abc"
abc-owner: abc-admin
The GUI runs pretty fine, but trying to subscribe gives no error message but an entry
like this in /var/log/maillog:
May 13 15:09:50 raq sendmail[32214]: PAA32214: from=, size=0, class=0, pri=0,
nrcpts=0, proto=ESMTP, relay=localhost [127.0.0.1]
The subscription message never arrives...
Trying to post to the test list returns 'no such user here'.
Does anybody have a clue what I was too blind to see, didn't set properly?
Thanks a lot in advance,
regards,
Hendrik.
--
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sat, 12 May 2001, Chuq Von Rospach wrote: > On 5/12/01 6:52 PM, "Ian White" <[EMAIL PROTECTED]> wrote: > > Which variables should be changed? It looks like the following could use > > some changes: > > SMTP_MAX_RCPTS = 500 > > Between 5 and 10 - that should be set for any mailman installation. 500 is > way too high for reasonable performance. This blanket statement is not always correct. It strongly depends on the MTA that you are using. My mailman installation talks to the Windows 2000 SMTP MTA, where there are no performance problems with having the batching set to a very high number. Multiple queues can send out the same message at the same time. Using high SMTP_MAX_RCPTS numbers results in a lot less disk activity and also means that all of my mail going to hotmail.com or aol.com can get sent in one transaction. The statement above is true for many Unix MTAs where the queue runner can only send one message to one file at time. If you only give the MTA a couple of messages to party on then it will only be able to talk to a couple of remote servers at a time, so sending out a single message could take quite a while. What this really means is that you should understand how your MTA works and choose a SMTP_MAX_RCPTS that works well for your MTA. I just think that blanket statements such as "500 is way too high for reasonable performance" should be avoided, as you never know what MTA the admin is using. alex -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sat, 12 May 2001 23:21:05 -0700 Chuq Von Rospach <[EMAIL PROTECTED]> wrote: > On 5/12/01 10:51 PM, "J C Lawrence" <[EMAIL PROTECTED]> wrote: >> I find this curious. I have MAX_RCPT_TO set to 5, and to >> broadcast 30 messages to a subscriber base of 1,000 (ie 6,000 >> spool entries) through qrunner to the MTA (postfix) on a dual >> PII-333 takes just over 6 seconds once started. Admittedly >> that's an appreciable time, but its also not that long a time in >> the lands of lock contention and lock timeouts. > It all comes down to how fast your MTA accepts messages. True, thus my query. > If you're running postfix with DNS deferred, you rock. If you're > running sendmail with DNS on, it's a lot slower. So it's something > you have to judge based on your own system. Aye, that's one of my more common performance refrains along with, "install and use a local cacheing name server!". Fair dunkum tho -- I'd forgotton the painful side effects of turning of DNS checks for Sendmail, and had thus ritely assumed that non-DNS-check was a default starting point. -- J C Lawrence [EMAIL PROTECTED] -(*) http://www.kanga.nu/~claw/ The pressure to survive and rhetoric may make strange bedfellows -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sun, 13 May 2001 00:22:08 -0700 (PDT) tib <[EMAIL PROTECTED]> wrote: > On Sat, 12 May 2001, J C Lawrence wrote: >> Your math is off as it ignores RCPT-TO envelope size. > So throw in a few more bytes times 10k and it gets even bigger Chuq has already addressed this point thoroughly. >> Actually, list servers are generically disk IO bound with the >> primary factor in the disk IO being open/close/unlink time not >> read/write time. > I'm not quite the hardware guru I'd like to be yet - explain in > english please? MTAs are fundamentally disk IO bound. This is one of the reason that several large mail houses run their mail spools on silicon disks (ie hard drives which sit on SCSI busses, and which are made out of RAM). Within the bottleneck that is formed by disk IO, read/write time is a smaller percentage. open/close/delete occupy the lion's share of the IO time. Ergo, volume of data processed is really not that concerning -- its the NUMBER of data items (spool entries) processed that is concerning. >> This assumes of course that the audience has web access, and in >> particular has web access at the time and on the device they >> would normally read the messages. >> >> Example : It wouldn't work for me reading on the train on my >> laptop. > Who has email that does not have web access at the time they get > their email? I do. > Granted I suppose it's possible that you would download your mail > ahead of time before leaving home and then opening your laptop on > the train. The laptop has a Wavelan card. When its at home it auto-joins the home network and picks up the mail my server has spooled for it, and delivers the mail it has waiting for outbound. I then go to work, laptop in tow, and (generally) have no more 'net access from the laptop until I retunr home. (I'm still not happy with this setup, but it kinda works ATM). Given the number of others I see on the train reading mail I'm nowhere near alone in this (tho our methods will vary on how we got there -- mine is excessively complex). -- J C Lawrence [EMAIL PROTECTED] -(*) http://www.kanga.nu/~claw/ The pressure to survive and rhetoric may make strange bedfellows -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sun, 13 May 2001 00:41:16 -0700 Chuq Von Rospach <[EMAIL PROTECTED]> wrote: > On 5/13/01 12:22 AM, "Tib" <[EMAIL PROTECTED]> wrote: >> Who has email that does not have web access at the time they get >> their email? > Not a huge number, but not zero. As wireless mobile becomes more > significant, it'll be a growing issue, not a shrinking one. Which of course means that your web page must now be WAP friendly and desktop browser friendly. Reading the web effectively on a connected Palm requires a rather different view on web design. >> The load of an entire batch (rough 300meg estimate) will also be >> spread out more over the course of a few days as everyone checks >> their mail and may or may not look at that message and cause it >> to draw on the url or click/paste it into a browser themselves. > No, it won't. There's a huge peak in the few hours after delivery, > which drops radically after that and stretches out over about ten > days or so. I wandered over to Akami a few months ago and looked at the graphs of attack time and decay rates for sites that hit Slashdot. The leading edge of the peak is typically measured in single digit minutes. The decay rates vary fairly widely depending on the time of posting, but fall into a small number of basic camps. >> It all boils down to a matter of how you want to use your server. > And whether you want to pay for peak load capacities on your web > server or the lower, spread out push capacities on your e-mail. There's also the possiblity of using your ISP's MTAs as smarthosts (which many ISPs actively encourage and some enforce/require). -- J C Lawrence [EMAIL PROTECTED] -(*) http://www.kanga.nu/~claw/ The pressure to survive and rhetoric may make strange bedfellows -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sat, 12 May 2001 23:19:15 -0700 Chuq Von Rospach <[EMAIL PROTECTED]> wrote: > On 5/12/01 10:43 PM, "J C Lawrence" <[EMAIL PROTECTED]> wrote: >> 3) If delivery failures are clogging your MTA queue and are >> noticably slowing delivery rates, you need to start thinking >> about reviewing your MTA configuration or using a different and >> more intelligent MTA. > MTA configuration is huge. Yes, and no. I posit that some MTA's ala Postfix and QMail do a good enough job that they do solve 80% of the problem, which leave only rather rare cases being interestingfrom a tuning viewpoint. > (Oh, and at times, you'll find you have to redo stuff, because > there are places where the paradigms change -- you scale to some > point, and then you have to rethink how you do things...) Yeah, I've been caught there a couple times. -- J C Lawrence [EMAIL PROTECTED] -(*) http://www.kanga.nu/~claw/ The pressure to survive and rhetoric may make strange bedfellows -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sun, 13 May 2001 01:21:52 -0700 (PDT) tib <[EMAIL PROTECTED]> wrote: > On Sun, 13 May 2001, Chuq Von Rospach wrote: >> On 5/13/01 12:22 AM, "Tib" <[EMAIL PROTECTED]> wrote: >> If the piece of email is sponsored and has advertising, it's a >> HUGE problem. As was the original poster's note on this stuff. > If you're running on a 384k dsl then the only advertising is the > stuff you put up yourself because it's your server. Unsupoortable assumption. > I would think this would be a bit the opposite. For your mail > server to push anything it has to look up records on the domain > it's going to send to (which for 10k users I would assume to be a > lot of domains)... Which given a local cacheing name server with reasonably large and enforced minimum TTLs is a small overhead. > Again it would seem to me that the webserver would have an easier > time with the load than the mail server. Web server traffic is controllable, bandwidth profiles poorly (users complain), is unschedulable and tends to be bursty. Mail traffic is implicitly controllable, bandwidth profiles easily, is schedulable, and is as flat as you care to make it. -- J C Lawrence [EMAIL PROTECTED] -(*) http://www.kanga.nu/~claw/ The pressure to survive and rhetoric may make strange bedfellows -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On 5/13/01 1:21 AM, "Tib" <[EMAIL PROTECTED]> wrote: > If you're running on a 384k dsl then the only advertising is the stuff you put > up yourself because it's your server. Not true, but also not really relevant -- I was using it only as an example, since it's my home DSL. My big stuff is somewhere else with big pipes (> 7 DS-3s, last I looked) > I would think this would be a bit the opposite. Again -- you THINK. I've done. > What I have: > A personally built server (PIII 500, 256mb memory, 30g hd) > a 1.1 sdsl line > 5 fully hosted domains > 23 users (maybe a third of which are decently active for mail and web demands) > 5 email lists running on mailman, the largest of which is about 300 users. > mrtg to keep track of bandwidth usage > basic algebra Ah, thanks. You finally admit you don't know and haven't done. I've done lists up into the seven digit size. We've experimented with URLs and click-ins. If you're talking about 300 users max, it doesn't matter what you do. ANYTHING works. It doesn't scale, though. But believe what you want. Trust your algebra. I suggest you don't sell the service until you know for sure, though with real numbers. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sun, 13 May 2001 08:46:57 -0700 (PDT) alex wetmore <[EMAIL PROTECTED]> wrote: > My mailman installation talks to the Windows 2000 SMTP MTA, where > there are no performance problems with having the batching set to > a very high number. Multiple queues can send out the same message > at the same time. Using high SMTP_MAX_RCPTS numbers results in a > lot less disk activity and also means that all of my mail going to > hotmail.com or aol.com can get sent in one transaction. There's reason to keep the RCPT TO envelope reasonably small to prevent triggering some ISP's SPAM traps. Specifically, this appears to be one of the filter points that AOL uses (and of course it then drops the caught mail silently without a bounce of warning). -- J C Lawrence [EMAIL PROTECTED] -(*) http://www.kanga.nu/~claw/ The pressure to survive and rhetoric may make strange bedfellows -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] configuration problem
Hi, I'm trying to set up mailman but I'm not getting something right. When I go to my mailman site's admin page, http://www.deangeuls.com/mailman/admin, I can see a list of links that I have set up with the ./newlist command. But when I click on one of the links to administer the list, I get nowhere. I'm Running RH7.1 and Apache. Any ideas what's wrong? I tried installing off the tarball and the RPM from Red Hat, but I can't get over this big hump. Joe -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sun, 13 May 2001, J C Lawrence wrote: > There's reason to keep the RCPT TO envelope reasonably small to > prevent triggering some ISP's SPAM traps. Specifically, this > appears to be one of the filter points that AOL uses (and of course > it then drops the caught mail silently without a bounce of warning). Do you have any details on AOL's spam filters? None of my AOL readers have complained about missing email. It looks like my largest list has 60 digested and 55 regular AOL members, so I'm guessing that their spam filter is set to a higher threshold than that. alex -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Mailman + Qmail + Virtual domain
Hello all. I installed Mailman on my server, and i want all the lists to run with domain lists.domain.com. So i setup DNS, add lists.domain.com to rcpthosts and lists.domain.com:mailman to virtualdomains under /var/qmail/control. After that, i create a test list, "newlist testlist". Then I configured /var/mailman/.qmail-default to use 'qmail-to-mailman.py'. When i subscribe using the web interface, i do get a e-mail from "[EMAIL PROTECTED]; on behalf of [EMAIL PROTECTED]", welcoming me to the list. However, every time i send a mail to [EMAIL PROTECTED], i get a bounce from MAILER-DAEMON saying: Hi. This is the qmail-send program at domain.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <[EMAIL PROTECTED]>: Sorry, no mailbox here by that name. (#5.1.1) A also tried not using 'qmail-to-mailman.py', and used a script that comes with the program that creates all the .qmail files. Same result. What i'm i doing wrong? Any help will be appreciated, tks in advance. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sun, 13 May 2001 16:16:44 -0700 (PDT) alex wetmore <[EMAIL PROTECTED]> wrote: > On Sun, 13 May 2001, J C Lawrence wrote: >> There's reason to keep the RCPT TO envelope reasonably small to >> prevent triggering some ISP's SPAM traps. Specifically, this >> appears to be one of the filter points that AOL uses (and of >> course it then drops the caught mail silently without a bounce of >> warning). > Do you have any details on AOL's spam filters? None of my AOL > readers have complained about missing email. It looks like my > largest list has 60 digested and 55 regular AOL members, so I'm > guessing that their spam filter is set to a higher threshold than > that. They appear to be using a multi-valued metric for their spam detection -- and to change their metrics regularly. See: http://members.aol.com/adamkb/aol/mailfaq/dropped-mail.html#lists -- J C Lawrence [EMAIL PROTECTED] -(*) http://www.kanga.nu/~claw/ The pressure to survive and rhetoric may make strange bedfellows -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] big lists, big messages
On Sun, 13 May 2001, J C Lawrence wrote: > On Sun, 13 May 2001 16:16:44 -0700 (PDT) > alex wetmore <[EMAIL PROTECTED]> wrote: > > > On Sun, 13 May 2001, J C Lawrence wrote: > >> There's reason to keep the RCPT TO envelope reasonably small to > >> prevent triggering some ISP's SPAM traps. Specifically, this > >> appears to be one of the filter points that AOL uses (and of > >> course it then drops the caught mail silently without a bounce of > >> warning). > > > Do you have any details on AOL's spam filters? None of my AOL > > readers have complained about missing email. It looks like my > > largest list has 60 digested and 55 regular AOL members, so I'm > > guessing that their spam filter is set to a higher threshold than > > that. > > They appear to be using a multi-valued metric for their spam > detection -- and to change their metrics regularly. See: > > http://members.aol.com/adamkb/aol/mailfaq/dropped-mail.html#lists It doesn't sound like it makes a huge difference if they are batched up at once, or if they come very quickly on different messages. "If a mailing list server sends too much mail in too short a time to a number of AOL members, AOL will consider it questionable and delete it." alex -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] porblem with one domain
Hi Guys, We, xraymedia.com, are setting up mailman (lists.xray.tv). In addition we are setting up a mail server supporting web and pop access (mail.xray.tv). Separately they both work fine. When an xray.tv user ( e.g. [EMAIL PROTECTED]) appears as a list member, he/she doesn't receive mass mail. There is one exception -- the 'welcome' message and confirmation messages do come. Question: why only half works ? Is the welcome message sending code different than the mass-mailing one ? -bk -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] porblem with one domain
On Sun, 13 May 2001 21:30:15 -0700 (PDT) Boris Krivulin <[EMAIL PROTECTED]> wrote: > Question: why only half works ? Is the welcome message sending > code different than the mass-mailing one ? Read your MTA logs with care. Its alsmost certain that the clues are there. -- J C Lawrence [EMAIL PROTECTED] -(*) http://www.kanga.nu/~claw/ The pressure to survive and rhetoric may make strange bedfellows -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
