Re: Problem with failed remote SMTP connections
On Feb 22 2000, Fred Backman wrote: > The second problem is SMTP servers which are down, such as this > one (again I can give you a list of many such servers): > > rexx.riskymail.com Which shows that they've appropriately chosen their domain name. :-) []s, Roger... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rogerio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/ Nectar homepage: http://www.linux.ime.usp.br/~rbrito/opeth/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Large queues (was: Re: Problem with failed remote SMTP connections)
On Feb 22 2000, Russell Nelson wrote: > Okay: a growing queue is not a problem in and of itself. qmail deals > very nicely with a large queue. Yes. The problem might be the time spent in the kernel part of the filesystem code. > If you handle such a volume of mail that the queue is usually large > (<25K separate messages), then you should change conf-split, > recompile, and reinstall to /var/qmail2. I don't know what is the operating system in question (if it was mentioned, I'm sorry), but reiserfs could also help... []s, Roger... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rogerio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/ Nectar homepage: http://www.linux.ime.usp.br/~rbrito/opeth/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: Problem with failed remote SMTP connections
Russell Nelson wrote: > If mail is not being delivered obviously something is wrong. It's > sufficient for you to verify that the problem is not on your end, > unless you're really into sysadmining other people's machines for > them just because you have mail to be delivered to users there. Mail is being delivered fine locally, but kind of struggling remotely due to a large amount of bogus/unconfigured remote domains. We have about 10K messages in the queue now, where qmail is failing to deliver to remote domains such as these three (to mention just a few, I can give you many many more domains). The problem with these are missing MX records: 163.com amanda.elsitio.com 21f.com The second problem is SMTP servers which are down, such as this one (again I can give you a list of many such servers): rexx.riskymail.com
Re: Problem with failed remote SMTP connections
Fred Backman writes: > Russell Nelson wrote: > > > Fred Backman writes: > > > Our queue is growing due to failed smtp connections. > > > > So? This is not, in itself, a problem. > > Tell my managers :-) Okay: a growing queue is not a problem in and of itself. qmail deals very nicely with a large queue. If you handle such a volume of mail that the queue is usually large (<25K separate messages), then you should change conf-split, recompile, and reinstall to /var/qmail2. > I agree, it's just that the delivery of emails is already getting delayed > by hours just because of these failed connections. It's mainly bounces > from mailing lists. If mail is not being delivered obviously something is wrong. It's sufficient for you to verify that the problem is not on your end, unless you're really into sysadmining other people's machines for them just because you have mail to be delivered to users there. -- -russ nelson <[EMAIL PROTECTED]> http://russnelson.com Crynwr sells support for free software | PGPok | "Ask not what your country 521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
Re: Problem with failed remote SMTP connections
Russell Nelson wrote: > Fred Backman writes: > > Our queue is growing due to failed smtp connections. > > So? This is not, in itself, a problem. Tell my managers :-) I agree, it's just that the delivery of emails is already getting delayed by hours just because of these failed connections. It's mainly bounces from mailing lists.
Re: Problem with failed remote SMTP connections
Fred Backman writes: > Our queue is growing due to failed smtp connections. So? This is not, in itself, a problem. -- -russ nelson <[EMAIL PROTECTED]> http://russnelson.com Crynwr sells support for free software | PGPok | "Ask not what your country 521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
Re: Problem with failed remote SMTP connections
> Can anyone please advice what to do? Sometimes I look for an alternative host in this domain or the parent domain that accepts the mails - then I establish an entry in smtproutes. Some annoying newsletters that don't accept bounces or are not reachable I block via badmailfrom (if the bounces are the problem). It all depends on your policy. You also could simply wait until the mails bounce. Often the problem goes away after hours or days. Regards, Frank
Problem with failed remote SMTP connections
Our queue is growing due to failed smtp connections. There are two main reasons: (1) there is an smtp server but it's refusing us to connect to it, and (2) the domain has no smtp server to connect to. See below for examples. The queue keeps growing and syslog is reporting a lot of "Sorry,_I_wasn't_able_to_establish_an_SMTP_connection." Can anyone please advice what to do? Thanks, Fred telnet po.netnet.com.sg 25 -- fails telnet mail.teen-mail.com 25 -- fails # nslookup -type=MX lists.hearme.com Server: dns1.telia.com Address: 194.22.190.10 hearme.com origin = hearme.com mail addr = hostmaster.hearme.com serial = 221800 refresh = 3600 (1 hour) retry = 900 (15 mins) expire = 864000 (10 days) minimum ttl = 900 (15 mins) # nslookup -type=MX server.snap.com Server: dns1.telia.com Address: 194.22.190.10 Authoritative answers can be found from: snap.com origin = sv-ns1.snap.com mail addr = hostmaster.snap.com serial = 222103 refresh = 900 (15 mins) retry = 600 (10 mins) expire = 2592000 (30 days) minimum ttl = 900 (15 mins)
