Sponsored Content
Full Discussion: /var/spool/mqueue issue
Operating Systems Solaris /var/spool/mqueue issue Post 302740489 by Junaid Subhani on Thursday 6th of December 2012 08:54:41 AM
Old 12-06-2012
RedHat /var/spool/mqueue issue

Hi guys .

I have a solaris machine serving as a DNS server for my environment. Everytime I go into /var/spool/mqueue , there are an aweful lot of emails with names likes:

qfqB6ChrpL006644.
When I cat the file , I get the following output:



Code:
H??Received: from machine.domain.com (machine.domain.com [172.21.5.17])
        by machine.domain.com (8.13.8+Sun/8.13.8) with ESMTP id qB6Dk5ow015892
        for <user@machine.domain.com>; Thu, 6 Dec 2012 18:46:05 +0500 (PKT)
H??Received: (from user@localhost)
        by machine.domain.com (8.14.4+Sun/8.14.4/Submit) id qB6Dk0td018573
        for orb2; Thu, 6 Dec 2012 18:46:00 +0500
H??Date: Thu, 6 Dec 2012 18:46:00 +0500 
H??From: Orb Second Instance User <ouser@machine2.domain.com>
H??Message-Id: <201212061346.qB6Dk0td018573@machine.domain.com>
H??To: user@machine2.domain.com
H??Subject: Couldn't run your "cron" job
H??MIME-Version: 1.0
H??Content-Type: text/plain

It seems that crons from other machines are sending random mails. How do I identify on other machines the script that are sending these emails to my dns server. I want them to stop.

How do I ?SmilieSmilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/var/spool/mqueue !!!

I keep having this msg on my SunOS console : Jun 29 08:57:40 bersimis sendmail: NOQUEUE: low on space (have 0, SMTP-DAEMON needs 101 in /var/spool/mqueue) I tried to make some space by deleting the files in it, but the msg came back ... Any tips ? Thanks (3 Replies)
Discussion started by: Wingman21
3 Replies

2. UNIX for Dummies Questions & Answers

NOQUEUE: low on space ( have 0, SMTP-DAEMON needs 101 in /var/spool/mqueue)

hi, I'm in Solaris 2.8 env. When i'm trying to add a ftp user account , encountered "no space in disk" .. couldn't create any user. Then check the fs disk space with "df - k " and /var/adm/syslog .. got the below message. Jun 9 03:10:53 mail sendmail: NOQUEUE: low on space (have 0,... (10 Replies)
Discussion started by: Dolly
10 Replies

3. UNIX for Dummies Questions & Answers

/VAR/SPOOL/MAIL question

Hi, We have all the user account in a home direcory where their mail is stored and retrieved by email clients. We do however have /var/spool/mail with all the user accounts in it as well Our sendmail.cf is configured to use /var/spool/mqueue as the queue so .what is /var/spool/mail being used... (3 Replies)
Discussion started by: mojoman
3 Replies

4. UNIX for Dummies Questions & Answers

Sendmail /VAR/SPOOL/MAIL

Hi, First Question: In our company our users have their mailboxes in /var/spool/mail When I look at the users file it seems as if every email sent/received is in that user file! Is this because IMAP is being used or is that just how sendmail works? Second Question: How is that when I create... (3 Replies)
Discussion started by: mojoman
3 Replies

5. UNIX for Dummies Questions & Answers

/var/spool/mail

Hi, How can i get my mail on either /var/spool/mail or /var/mail? I use mail and sendmail command to send mail. But everytime I send mail it comes to my outlook inbox and when I check with mail command I get the message "No mail for siba". (Note siba is my user Id.) (2 Replies)
Discussion started by: siba.s.nayak
2 Replies

6. UNIX for Advanced & Expert Users

Mail going to /var/spool/mqueue instead of being sent

Hello, I have a bunch of cron jobs in the crontab. For some reason mail from the cron jobs started going to /var/spool/mqueue instead of being sent. Does anyone know why mail from cron jobs would go to the queue instead of being sent? (9 Replies)
Discussion started by: xadamz23
9 Replies

7. Solaris

Solaris 9, /var/spool/clientmqueue/

Hi, We have some 2-3 Solaris 9 servers with the following issue. For every cron job which has email notifications, it is sending the emails, but it create files at /var/spool/clientmqueue/ which has similar contents. " V6 T1271362260 K1271362260 N1 P30359 MDeferred: Connection refused... (1 Reply)
Discussion started by: uxadmin007
1 Replies

8. Solaris

/var/spool/clientmqueue

Hi, solaris : 9 can we delete the files from this location /var/spool/clientmqueue . I found around 40K files lying in this location. Regards (1 Reply)
Discussion started by: maooah
1 Replies

9. AIX

/var/spool/mail/ issues

Hi My box is running with AIX 6100-06 and Im the root user of this box My /var gets filled up often to 100% When I investigate I find that it is the below file which increases rapidly /var/spool/mail/pdgadmin I dont know why this file is growing up. Can any one assist me on this.... (2 Replies)
Discussion started by: samsungsamsung
2 Replies

10. Solaris

DNS server /var/spool issue

Hello all Currently I am working in a live production environment with 100+ Solaris servers . The environment has one DNS server and one SMTP server. The problem that I am facing since the past 2 months is that the /var/spool/mqueue on my DNS server keeps getting full i.e. mails with name... (1 Reply)
Discussion started by: Junaid Subhani
1 Replies
Received(3pm)						User Contributed Perl Documentation					     Received(3pm)

NAME
Mail::Field::Received -- mostly RFC822-compliant parser of Received headers SYNOPSIS
use Mail::Field; my $received = Mail::Field->new('Received', $header); my $results = $received->parse_tree(); my $parsed_ok = $received->parsed_ok(); my $diagnostics = $received->diagnostics(); DESCRIPTION
Don't use this class directly! Instead ask Mail::Field for new instances based on the field name! Mail::Field::Received provides subroutines for parsing Received headers from e-mails. It mostly complies with RFC822, but deviates to accommodate a number of broken MTAs which are in common use. It also attempts to extract useful information which MTAs often embed within the "(comments)". It is a subclass derived from the Mail::Field and Mail::Field::Generic classes. ROUTINES
o debug Returns current debugging level obtained via the "diagnostics" method. If a parameter is given, the debugging level is changed. The default level is 3. o diagnose $received->diagnose("foo", " "); Appends stuff to the parser's diagnostics buffer. o diagnostics my $diagnostics = $received->diagnostics(); Returns the contents of the parser's diagnostics buffer. o parse The actual parser. Returns the object (Mail::Field barfs otherwise). o parsed_ok if ($received->parsed_ok()) { ... } Returns true if the parse succeed, or if it failed, but was permitted to fail for some reason, such as encountering evidence of a known broken (non-RFC822-compliant) format mid-parse. o parse_tree my $parse_tree = $received->parse_tree(); Returns the actual parse tree, which is where you get all the useful information. It is returned as a hashref whose keys are strings like `from', `by', `with', `id', `via' etc., corresponding to the components of Received headers as defined by RFC822: received = "Received" ":" ; one per relay ["from" domain] ; sending host ["by" domain] ; receiving host ["via" atom] ; physical path *("with" atom) ; link/mail protocol ["id" msg-id] ; receiver msg id ["for" addr-spec] ; initial form ";" date-time ; time received The corresponding values are more hashrefs which are mini-parse-trees for these individual components. A typical parse tree looks something like: { 'by' => { 'domain' => 'host5.hostingcheck.com', 'whole' => 'by host5.hostingcheck.com', 'comments' => [ '(8.9.3/8.9.3)' ], }, 'date_time' => { 'year' => 2000, 'week_day' => 'Tue', 'minute' => 57, 'day_of_year' => '1 Feb', 'month_day' => ' 1', 'zone' => '-0500', 'second' => 18, 'hms' => '21:57:18', 'date_time' => 'Tue, 1 Feb 2000 21:57:18 -0500', 'hour' => 21, 'month' => 'Feb', 'rest' => '2000 21:57:18 -0500', 'whole' => 'Tue, 1 Feb 2000 21:57:18 -0500' }, 'with' => { 'with' => 'ESMTP', 'whole' => 'with ESMTP' }, 'from' => { 'domain' => 'mediacons.tecc.co.uk', 'HELO' => 'tr909.mediaconsult.com', 'from' => 'tr909.mediaconsult.com', 'address' => '193.128.6.132', 'comments' => [ '(mediacons.tecc.co.uk [193.128.6.132])', ], 'whole' => 'from tr909.mediaconsult.com (mediacons.tecc.co.uk [193.128.6.132]) ' }, 'id' => { 'id' => 'VAA24164', 'whole' => 'id VAA24164' }, 'comments' => [ '(mediacons.tecc.co.uk [193.128.6.132])', '(8.9.3/8.9.3)' ], 'for' => { 'for' => '<adam@spiers.net>', 'whole' => 'for <adam@spiers.net>' }, 'whole' => 'from tr909.mediaconsult.com (mediacons.tecc.co.uk [193.128.6.132]) by host5.hostingcheck.com (8.9.3/8.9.3) with ESMTP id VAA24164 for <adam@spiers.net>; Tue, 1 Feb 2000 21:57:18 -0500' } BUGS
Doesn't use Parse::RecDescent, which it maybe should. Doesn't offer a `strict RFC822' parsing mode. To implement that would be a royal pain in the arse, unless we move to Parse::RecDescent. SEE ALSO
Mail::Field, Mail::Header AUTHOR
Adam Spiers <adam@spiers.net> LICENSE
All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2011-02-05 Received(3pm)
All times are GMT -4. The time now is 06:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy