delay in mailing to lists?

delay in mailing to lists?

[Nate Beaty]

I followed the instructions in README.exim4, and set up a "lists."  
subdomain for mailing lists, but when I try to send a test email to  
my list, Exim shows the following in the log:

20060609040508.A78ADA7FEB@burnaby.textdrive.com). From  
<natron46@burnaby.textdrive.com> (host=burnaby.textdrive.com  
[207.7.108.243]) for mlmmj-test@lists.clixel.com
2006-06-08 21:04:57 1FoYEy-0001NS-As <=  
natron46@burnaby.textdrive.com H=burnaby.textdrive.com  
[207.7.108.243] P=esmtp S\x1457  
id 060609040508.A78ADA7FEB@burnaby.textdrive.com
2006-06-08 21:04:57 lowest numbered MX record points to local host:  
clixel.com (while verifying <nate@clixel.com> from host localhost  
(lists.clixel.com) [127.0.0.1])
2006-06-08 21:04:57 H=localhost (lists.clixel.com) [127.0.0.1]  
F=<mlmmj-test+bounces-13@lists.clixel.com> temporarily rejected RCPT  
<nate@clixel.com>: lowest numbered MX record points to local host
2006-06-08 21:04:57 1FoYEy-0001NS-As => mlmmj-test <mlmmj- 
test@lists.clixel.com> R=mlmmj_router T=mlmmj_transport
2006-06-08 21:04:57 1FoYEy-0001NS-As Completed

My first concern, which isn't mlmmj-related necessarily, is the  
"lowest numbered MX record points to local host" error. For all my  
Googling, I can't pinpoint what would be causing this error, except  
not having clixel.com in my local_domains (which it is, along with  
lists.clixel.com and mail.clixel.com).

Regardless, mlmmj seems to accept the message, but it doesn't  
propagate it unless I manually run the command "/usr/bin/mlmmj-maintd  
-F -d /var/spool/mlmmj" -- is this normal? Does mlmmj not send an  
email as soon as it gets it, but rather waits for the next crontab  
execution of the mlmmj-maintd command? Or is this delay caused by the  
"lowest numbered MX record points to local host" error?

I'm running debian Ubuntu Dapper Drake, with dnsmasq, Exim 4.62, and  
mlmmj-1.2.11.

Nate.

--
Clixel Design & Coding ~ http://clixel.com/

Re: delay in mailing to lists?

[Mads Martin Joergensen]

* Nate Beaty <natebeaty@gmail.com> [Jun 09. 2006 07:28]:
> I followed the instructions in README.exim4, and set up a "lists."  
> subdomain for mailing lists, but when I try to send a test email to  
> my list, Exim shows the following in the log:
> 
> 20060609040508.A78ADA7FEB@burnaby.textdrive.com). From  
> <natron46@burnaby.textdrive.com> (host=burnaby.textdrive.com  
> [207.7.108.243]) for mlmmj-test@lists.clixel.com
> 2006-06-08 21:04:57 1FoYEy-0001NS-As <=  
> natron46@burnaby.textdrive.com H=burnaby.textdrive.com  
> [207.7.108.243] P=esmtp S\x1457  
> id 060609040508.A78ADA7FEB@burnaby.textdrive.com
> 2006-06-08 21:04:57 lowest numbered MX record points to local host:  
> clixel.com (while verifying <nate@clixel.com> from host localhost  
> (lists.clixel.com) [127.0.0.1])
> 2006-06-08 21:04:57 H=localhost (lists.clixel.com) [127.0.0.1]  
> F=<mlmmj-test+bounces-13@lists.clixel.com> temporarily rejected RCPT  
> <nate@clixel.com>: lowest numbered MX record points to local host
> 2006-06-08 21:04:57 1FoYEy-0001NS-As => mlmmj-test <mlmmj- 
> test@lists.clixel.com> R=mlmmj_router T=mlmmj_transport
> 2006-06-08 21:04:57 1FoYEy-0001NS-As Completed
> 
> My first concern, which isn't mlmmj-related necessarily, is the  
> "lowest numbered MX record points to local host" error. For all my  
> Googling, I can't pinpoint what would be causing this error, except  
> not having clixel.com in my local_domains (which it is, along with  
> lists.clixel.com and mail.clixel.com).
> 
> Regardless, mlmmj seems to accept the message, but it doesn't  
> propagate it unless I manually run the command "/usr/bin/mlmmj-maintd  
> -F -d /var/spool/mlmmj" -- is this normal? Does mlmmj not send an  
> email as soon as it gets it, but rather waits for the next crontab  
> execution of the mlmmj-maintd command? Or is this delay caused by the  
> "lowest numbered MX record points to local host" error?

No, mlmmj sends it immediately, it's that error causing it. It says it
temporarily rejected it, which means that mlmmj puts it in the requeue
directory to retry next time mlmmj-maintd runs.

Can you do a find in the requeue directory after it fails?

-- 
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
 and totally illogical, with just a little bit more effort?"
                                 -- A. P. J.

Re: delay in mailing to lists?

[Jakob Hirsch]

Quoting Nate Beaty:

> I followed the instructions in README.exim4, and set up a "lists."
> subdomain for mailing lists, but when I try to send a test email to my
> list, Exim shows the following in the log:

The log shows two transactions:
First the inbound mail from natron46@burnaby.textdrive.com to
mlmmj-test@lists.clixel.com, identified by the queue id
1FoYEy-0001NS-As, which gets delivered to mlmmj.
Second, the inbound mail from mlmmj
(mlmmj-test+bounces-13@lists.clixel.com), which is rejected because
lists.clixel.com is resolved (for some reason, maybe you have it in your
/etc/hosts) to 127.0.0.1.
Are you sure you followed exactly the instructions in README.exim4? You
have to put !mlmmj_domains in the "domains" list of the dnslookup router
(and all other routers with such a negative match).

The mlmmj setup seems ok, so it's a Exim issue. If you cannot get it
running, you should post a output of
exim -d+expand -bt mlmmj-test+bounces-13@lists.clixel.com

(though it's a little OT here...)

Re: delay in mailing to lists?

[Nate Beaty]

I agree it's OT, but thanks for helping me troubleshoot this. (My  
limited linux knowledge is always slowly expanding..)

Shouldn't lists.clixel.com be in /etc/hosts? Exim and mlmmj are both  
on the local machine, and mail.clixel.com, lists.clixel.com and  
clixel.com all served from this machine also.

My /etc/hosts file has:
127.0.0.1  localhost.localdomain localhost
192.168.0.4 lists.clixel.com lists
192.168.0.4 mail.clixel.com mail
192.168.0.4 clixel.com

I don't understand why Exim claims lists.clixel.com is resolving to  
127.0.0.1, though, since it specifically points to 192.168.0.4.  
Pinging lists.clixel.com:

natebeaty@mail:~$ ping lists.clixel.com
PING lists.clixel.com (192.168.0.4) 56(84) bytes of data.
64 bytes from bruno.clixel.com (192.168.0.4): icmp_seq=1 ttld  
time=0.075 ms

> Are you sure you followed exactly the instructions in README.exim4?  
> You
> have to put !mlmmj_domains in the "domains" list of the dnslookup  
> router
> (and all other routers with such a negative match).

I did follow them, !+mlmmj_domains is in the dnslookup router. (I  
later added lists.clixel.com to dc_other_hostnames, since it's a  
local domain -- is this incorrect? This causes all !+local_domains to  
include lists.clixel.com, also.)

> The mlmmj setup seems ok, so it's a Exim issue. If you cannot get it
> running, you should post a output of
> exim -d+expand -bt mlmmj-test+bounces-13@lists.clixel.com

I've tried all sorts of things, and I assume the problem is simple  
and due to some dumb misconfiguration on my part. Below is the output  
of your command: (When I debug with "nate@clixel.com", it correctly  
skips dnslookup and matches the vdom_aliases router.)

Thanks again,
Nate.


Exim version 4.60 uid=0 gid=0 pidT30 Dûb95dfd
Berkeley DB: Sleepycat Software: Berkeley DB 4.3.29: (September  6,  
2005)
Support for: crypteq iconv() IPv6 PAM Perl GnuTLS  
move_frozen_messages Content_Scanning Old_Demime
Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz  
dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql
Authenticators: cram_md5 cyrus_sasl plaintext spa
Routers: accept dnslookup ipliteral iplookup manualroute queryprogram  
redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Fixed never_users: 0
changed uid/gid: forcing real = effective
   uid=0 gid=0 pidT30
   auxiliary group list: <none>
configuration file is /var/lib/exim4/config.autogenerated
log selectors = 00000ffc 00041001
trusted user
admin user
expanding: $1
    result: root
user name "root" extracted from gecos field "root"
originator: uid=0 gid=0 login=root name=root
sender address = root@clixel.com
Address testing: uid=0 gid\x114 euid=0 egid\x114
 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Testing mlmmj-test+bounces-13@lists.clixel.com
 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Considering mlmmj-test+bounces-13@lists.clixel.com
 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
routing mlmmj-test+bounces-13@lists.clixel.com
--------> hubbed_hosts router <--------
local_part=mlmmj-test+bounces-13 domain=lists.clixel.com
checking domains
expanding: /etc/exim4/hubbed_hosts
    result: /etc/exim4/hubbed_hosts
condition: exists{/etc/exim4/hubbed_hosts}
    result: false
expanding: partial-lsearch;/etc/exim4/hubbed_hosts
    result: partial-lsearch;/etc/exim4/hubbed_hosts
skipping: result is not used
failed to expand: ${if exists{/etc/exim4/hubbed_hosts}{partial- 
lsearch;/etc/exim4/hubbed_hosts}fail}
    error message: "if" failed and "fail" requested
failure was forced
expansion of "${if exists{/etc/exim4/hubbed_hosts}{partial-lsearch;/ 
etc/exim4/hubbed_hosts}fail}" forced failure: assume not in this list
hubbed_hosts router skipped: domains mismatch
--------> mlmmj_router router <--------
local_part=mlmmj-test+bounces-13 domain=lists.clixel.com
stripped suffix +bounces-13
checking domains
lists.clixel.com in "lists.clixel.com"? yes (matched "lists.clixel.com")
lists.clixel.com in "+mlmmj_domains"? yes (matched "+mlmmj_domains")
expanding: :$local_part
    result: :mlmmj-test
expanding: mlmmj_router /var/spool/mlmmj/${lc::$local_part}
    result: mlmmj_router /var/spool/mlmmj/:mlmmj-test
mlmmj_router /var/spool/mlmmj/:mlmmj-test
checking require_files
expanding: $local_part
    result: mlmmj-test
expanding: /var/spool/mlmmj/${lc:$local_part}
    result: /var/spool/mlmmj/mlmmj-test
file check: /var/spool/mlmmj/${lc:$local_part}
expanded file: /var/spool/mlmmj/mlmmj-test
stat() yielded 0
calling mlmmj_router router
mlmmj_router router called for mlmmj-test+bounces-13@lists.clixel.com
   domain = lists.clixel.com
expanding: Delivered-To: $local_part$local_part_suffix@$domain
    result: Delivered-To: mlmmj-test+bounces-13@lists.clixel.com
set transport mlmmj_transport
queued for mlmmj_transport transport: local_part = mlmmj-test
domain = lists.clixel.com
   errors_to=NULL
   domain_data=NULL localpart_data=NULL
routed by mlmmj_router router
   envelope to: mlmmj-test+bounces-13@lists.clixel.com
   transport: mlmmj_transport
mlmmj-test+bounces-13@lists.clixel.com
   router = mlmmj_router, transport = mlmmj_transport
search_tidyup called
 >>>>>>>>>>>>>>>> Exim pidT30 terminating with rc=0 >>>>>>>>>>>>>>>>

Re: delay in mailing to lists?

[Jakob Hirsch]

Quoting Nate Beaty:

> I've tried all sorts of things, and I assume the problem is simple and
> due to some dumb misconfiguration on my part. Below is the output of
> your command: (When I debug with "nate@clixel.com", it correctly skips
> dnslookup and matches the vdom_aliases router.)

sorry, my first thought was wrong.
It seems you are using the verp router and that it matches before the
router for local users (at least for nate@clixel.com). So can either put
all router for local users in front of the verp_router or add
!local_domains to the verp_router's domains condition.

For a proper test, run
exim -d -f mlmmj-test+bounces-13@lists.clixel.com -bt nate@clixel.com

The mlmmj domain should not be local_domains.
The reference to 127.0.0.1 you saw was about the sender host, which is
correct.

Oh, and recipient verification should be skipped for the mlmmj sender. I
will update README.exim4 for that.