[BlueOnyx:05061] Re: Use of info, webmaster, and other aliases

[Abdul Rashid Abdullah]

Gerald,

I have an example from my own domain below.  It wasn't too obvious for me
from looking at the maillog except I have a guess that it is also sending to
the nobody account:

Jul 17 18:58:31 baraka sendmail[1229]: o6HMwVO7001229: from=root, size=52,
class=0, nrcpts=1, 
msgid=<201007172258.o6HMwVO7001229 at baraka.muntadanet.com>,
relay=root at localhost
Jul 17 18:58:31 baraka sendmail[1232]: STARTTLS=server, relay=localhost
[127.0.0.1], version=TLSv1/SSLv3, verify=NO, cipher=DHE-RSA-AES256-SHA,
bits=256/256
Jul 17 18:58:31 baraka sendmail[1229]: STARTTLS=client, relay=[127.0.0.1],
version=TLSv1/SSLv3, verify=FAIL, cipher=DHE-RSA-AES256-SHA, bits=256/256
Jul 17 18:58:31 baraka sendmail[1232]: o6HMwVof001232:
from=<root at baraka.muntadanet.com>, size=349, class=0, nrcpts=1,
msgid=<201007172258.o6HMwVO7001229 at baraka.muntadanet.com>, proto=ESMTP,
daemon=MTA, relay=localhost [127.0.0.1]
Jul 17 18:58:31 baraka sendmail[1229]: o6HMwVO7001229: to=sales at muntada.com,
ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay,
pri=30052, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent
(o6HMwVof001232 Message accepted for delivery)
Jul 17 18:58:31 baraka sendmail[1233]: o6HMwVof001232: o6HMwVoe001233:
clone: owner=muntada
Jul 17 18:58:31 baraka sendmail[1236]: o6HMwVK5001236:
Authentication-Warning: baraka.muntadanet.com: mail set sender to
owner-sales at www.muntada.com using -f
Jul 17 18:58:31 baraka sendmail[1236]: o6HMwVK5001236:
from=owner-sales at www.muntada.com, size=740, class=-60, nrcpts=2,
msgid=<201007172258.o6HMwVO7001229 at baraka.muntadanet.com>,
relay=mail at localhost
Jul 17 18:58:31 baraka dovecot: imap-login: Login: user=<inquiries>,
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
Jul 17 18:58:31 baraka dovecot: IMAP(inquiries): Disconnected: Logged out
bytes=28/236
Jul 17 18:58:31 baraka sendmail[1241]: STARTTLS=server, relay=localhost
[127.0.0.1], version=TLSv1/SSLv3, verify=NO, cipher=DHE-RSA-AES256-SHA,
bits=256/256
Jul 17 18:58:31 baraka sendmail[1236]: STARTTLS=client, relay=[127.0.0.1],
version=TLSv1/SSLv3, verify=FAIL, cipher=DHE-RSA-AES256-SHA, bits=256/256
Jul 17 18:58:32 baraka sendmail[1241]: o6HMwVLf001241:
from=<owner-sales at www.muntada.com>, size=978, class=-60, nrcpts=2,
msgid=<201007172258.o6HMwVO7001229 at baraka.muntadanet.com>, proto=ESMTP,
daemon=MTA, relay=localhost [127.0.0.1]
Jul 17 18:58:32 baraka sendmail[1236]: o6HMwVK5001236:
to=nobody,901-sales-list, ctladdr=owner-sales at www.muntada.com (8/12),
delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=168740, relay=[127.0.0.1]
[127.0.0.1], dsn=2.0.0, stat=Sent (o6HMwVLf001241 Message accepted for
delivery)
Jul 17 18:58:32 baraka sendmail[1233]: o6HMwVoe001233:
to="|/usr/local/majordomo/wrapper resend -l sales -C
/usr/local/majordomo/sites/site28/majordomo.cf 901-sales-list, nobody",
ctladdr=<sales at muntada.com> (8/0), delay=00:00:01, xdelay=00:00:01,
mailer=prog, pri=30633, dsn=2.0.0, stat=Sent
Jul 17 18:58:32 baraka sendmail[1243]: o6HMwVLf001241:
to=webmaster at muntada.com, delay=00:00:01, xdelay=00:00:00, mailer=local,
pri=169215, dsn=2.0.0, stat=Sent
Jul 17 18:58:32 baraka sendmail[1243]: o6HMwVLf001241: to=/dev/null,
ctladdr=901-sales-archival (8/0), delay=00:00:01, xdelay=00:00:00,
mailer=*file*, pri=169215, dsn=2.0.0, stat=Sent

The aliases.majordomo shows nobody.  I see this on so many of the majordomo
sections.

901-sales-approval:     muntada
901-sales-request:      "|/usr/local/majordomo/wrapper request-answer sales"
owner-901-sales:        muntada
901-sales-list: :include:/usr/local/majordomo/sites/site28/lists/sales,
901-sales-archival
901-sales-archival:     /dev/null
901-sales-owner:        muntada
901-sales:      "|/usr/local/majordomo/wrapper resend -l sales -C
/usr/local/majordomo/sites/site28/majordomo.cf 901-sales-list, nobody"

Why would it be sending to not only the list but also to nobody?

Regards,

Rashid 

On 7/17/10 11:45 AM, "Gerald Waugh" <gwaugh at frontstreetnetworks.com> wrote:

> 
> On Sat, 2010-07-17 at 16:01 -0400, Abdul Rashid Abdullah wrote:
>> Many users on my system have created mailing lists with names like info,
>> webmaster, support, sales, etc.  In the /etc/mail/aliases file I have placed
>> a # sign in front of these entries.  However, I am finding for some reason
>> that the admin account on the server has become a sort of catch all now for
>> all of these mailing lists.  The mailing lists appear to still be working
>> delivering mail to their intended recipients in addition to the admin
>> account on the server receiving these email.
>> 
>> I am not sure where the conflict is occurring but I am sure it would be best
>> that I stop receiving email that truly belongs to someone else.  Any ideas
>> on how to track down the "glitch" in the system would be appreciated.
>> 
> check maillog, see if you can track the processing.
> 
> Gerald
> 
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at blueonyx.it
> http://www.blueonyx.it/mailman/listinfo/blueonyx
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20100717/dd8e5c79/attachment.html>