Anil Jangity wrote:
>Actually, this is a internal SmartHost that doesn't require SMTP auth.
>I think a while back I had configured Mailman with --with-mailhost=localhost,
>a bunch of pages also showed "localhost" as the email domain for some of the
>list details. That's not what I wanted.
The
Actually, this is a internal SmartHost that doesn't require SMTP auth.
I think a while back I had configured Mailman with --with-mailhost=localhost, a
bunch of pages also showed "localhost" as the email domain for some of the list
details. That's not what I wanted.
I assume there won't be issues
Anil Jangity wrote:
>
>Mailman receives the mail and then posts to the same local MTA on the host
>which sends it out to Smart host.
>I am not sure we can't just have mailman send directly to the smarthost?
>
>What are the implications (on the web site as well as how Mailman functions)
>if I chan
Hi Mark,
Thanks. We're getting better performance now once we added this to our sendmail
.mc file:
FEATURE(`nocanonify')
I wanted to see if we can do further improvements.
Right now our email flow is like this for lists:
Internet -> ServerA:25 (/etc/aliases mailman) -> ServerA -> SmartHostA
Anil Jangity wrote:
>
>This sendmail server is setup to relay the mail to smarthost. When I inject a
>test mail on port 25 with RCPT and FROM to be a made up junk domain, the email
>is still delivered *immediately* to the smarthost, there is no resolver issues.
>
>If sendmail was really doing DNS
Mark, thanks for the very detailed info below.
I am still stuck on this.
This sendmail server is setup to relay the mail to smarthost. When I inject a
test mail on port 25 with RCPT and FROM to be a made up junk domain, the email
is still delivered *immediately* to the smarthost, there is no res
Anil Jangity wrote:
>Does mailman actually (if it works) send to 15 recipients at a time - per SMTP
>session?
Mailman's use of the term session is not consistent with the RFCs. What
Mailman calls SMTP_MAX_SESSIONS_PER_CONNECTION is actually in RFC 821,
2821, 5321 terms, max transactions per ses
Yes.
What exactly does that option do/mean?
Does mailman actually (if it works) send to 15 recipients at a time - per SMTP
session?
On Feb 1, 2012, at 5:02 PM, Carl Zwanzig wrote:
> On 2/1/2012 3:57 PM, Anil Jangity wrote:
>
>> I have these set in mm_cfg.py:
>>
>> SMTP_MAX_RCPTS = 15
>> SMTP_
Actually, looking at the code... it seems it might be because I have these set
for some of the lists.
VERP_PERSONALIZED_DELIVERIES = 1
OWNERS_CAN_ENABLE_PERSONALIZATION = 1
Thanks
On Feb 1, 2012, at 9:01 PM, Anil Jangity wrote:
> Yes.
> What exactly does that option do/mean?
> Does mailman ac
On 2/1/2012 3:57 PM, Anil Jangity wrote:
I have these set in mm_cfg.py:
SMTP_MAX_RCPTS = 15
SMTP_MAX_SESSIONS_PER_CONNECTION = 50
It seems Qrunner isn't honoring those?
Did you restart the qrunners after changing those settings?
z!
--
Mai
It seems it is doing about 6000 users in 35 minutes.
The problem seems to be that sendmail is doing one email connection per
recipient.
I have these set in mm_cfg.py:
SMTP_MAX_RCPTS = 15
SMTP_MAX_SESSIONS_PER_CONNECTION = 50
It seems Qrunner isn't honoring those?
>
> Look at Mailman's 'smt
Anil Jangity wrote:
>We just moved a very old mailman infrastructure mailman to Solaris and
>sendmail.
>It seems, when a message is posted, the "out" directory doesn't seem to clear
>out fast enough.
>
> 1K archive
> 1K bounces
> 1K commands
> 1K in
> 1K news
> 403K out
>
We just moved a very old mailman infrastructure mailman to Solaris and sendmail.
It seems, when a message is posted, the "out" directory doesn't seem to clear
out fast enough.
1K archive
1K bounces
1K commands
1K in
1K news
403K out
1K retry
1K shunt
1K
13 matches
Mail list logo
