groomy
Verified User
Hello, I want to delete the list of messages waiting in ssh, if someone could help me.
thank you
thank you
delete the list of messages waiting
- Thread starter groomy
- Start date
groomy
Verified User
Excuse it's mail queue and i use this code and i suppose it's good
scsi
Verified User
- Joined
- Aug 19, 2008
- Messages
- 4,531
All you have to do to remove all exim messages in the queue is do this:
http://www.cyberciti.biz/faq/exim-remove-all-messages-from-the-mail-queue/
Code:
exim -bp | exiqgrep -i | xargs exim -Mrmhttp://www.cyberciti.biz/faq/exim-remove-all-messages-from-the-mail-queue/
groomy
Verified User
thanks.. i test
groomy
Verified User
ok, thank you but why I have lots of messages every day there are 10 pages?
thank you
thank you
groomy
Verified User
Thank you for your help, but this is not the same email address used each time.
groomy
Verified User
this is the mesage
thanks, i have 50 mail by hour ??
and
thanks, i have 50 mail by hour ??
groomy
Verified User
all email for the user are going in mail queue ???
Why ?
Why ?
Richard G
Verified User
The reason for that is root is on Exim's "never user list".
Best way to handle this is to edit your /etc/aliases file, then add an email adres of you choice like this:
It would be smart to comment the following too like this:
Then save your /etc/aliases file, restart Exim and the problem should be over.
Best way to handle this is to edit your /etc/aliases file, then add an email adres of you choice like this:
Code:
root: [email protected]It would be smart to comment the following too like this:
Code:
#info: postmaster
#marketing: postmaster
#sales: postmaster
#support: postmasterThen save your /etc/aliases file, restart Exim and the problem should be over.
groomy
Verified User
thanks this is my file
and i change for :
Code:
# $Cambridge: exim/exim-src/src/aliases.default,v 1.1 2004/10/07 10:39:01 ph10 Exp $
# Default aliases file, installed by Exim. This file contains no real aliases.
# You should edit it to taste.
# The following alias is required by the mail RFCs 2821 and 2822.
# Set it to the address of a HUMAN who deals with this system's mail problems.
# postmaster: [email][email protected][/email]
# It is also common to set the following alias so that if anybody replies to a
# bounce message from this host, the reply goes to the postmaster.
# mailer-daemon: postmaster
# You should also set up an alias for messages to root, because it is not
# usually a good idea to deliver mail as root.
# root: postmaster
# It is a good idea to redirect any messages sent to system accounts so that
# they don't just get ignored. Here are some common examples:
# bin: root
# daemon: root
# ftp: root
# nobody: root
# operator: root
# uucp: root
# You should check your /etc/passwd for any others.
# Other commonly enountered aliases are:
#
# abuse: the person dealing with network and mail abuse
# hostmaster: the person dealing with DNS problems
# webmaster: the person dealing with your web site
####
diradmin: :blackhole:
Code:
# $Cambridge: exim/exim-src/src/aliases.default,v 1.1 2004/10/07 10:39:01 ph10 Exp $
# Default aliases file, installed by Exim. This file contains no real aliases.
# You should edit it to taste.
# The following alias is required by the mail RFCs 2821 and 2822.
# Set it to the address of a HUMAN who deals with this system's mail problems.
# postmaster: [email][email protected][/email]
# It is also common to set the following alias so that if anybody replies to a
# bounce message from this host, the reply goes to the postmaster.
# mailer-daemon: postmaster
# You should also set up an alias for messages to root, because it is not
# usually a good idea to deliver mail as root.
[COLOR="#FF0000"]root: [email][email protected][/email][/COLOR]
# It is a good idea to redirect any messages sent to system accounts so that
# they don't just get ignored. Here are some common examples:
# bin: root
# daemon: root
# ftp: root
# nobody: root
# operator: root
# uucp: root
# You should check your /etc/passwd for any others.
# Other commonly enountered aliases are:
#
# abuse: the person dealing with network and mail abuse
# hostmaster: the person dealing with DNS problems
# webmaster: the person dealing with your web site
####
diradmin: :blackhole:Richard G
Verified User
Correct, but use an existing email address of yourself because [email protected] was just an example I used.
Little aliases file by the way. Which operating system are you using?
Little aliases file by the way. Which operating system are you using?
groomy
Verified User
centos & custombuild & csf
nobaloney
NoBaloney Internet Svcs - In Memoriam †
As luck would have it, I've got a new machine on which I've just finished setting up CentOS6.5.
Among many others, it's got these:
As long as you've got a redirect from root to something you actually read, this will mean you'll get all those addresses at any domain that doesn't already have them. Sometimes handy, sometimes a real pain.
Over the years, I've begun to think I should remove some of them.
Jeff
Among many others, it's got these:
As long as you've got a redirect from root to something you actually read, this will mean you'll get all those addresses at any domain that doesn't already have them. Sometimes handy, sometimes a real pain.
Over the years, I've begun to think I should remove some of them.
Jeff
Richard G
Verified User
Removing them is the same as commenting them.
Some are needed by RFC's, like hostmaster and/or postmaster (depending on your DNS config).
You don't need things like webmaster, security, info, marketing, sales and support. In fact it will give problems when a customer uses them (which is often the case with support, sales and info) and their mailbox is full or suspended.
You will see that your root email address is getting the full mails which should in fact go to them.
Those addresses should not be limited to root, so that's why it's best to either remove or comment them.
Some are needed by RFC's, like hostmaster and/or postmaster (depending on your DNS config).
You don't need things like webmaster, security, info, marketing, sales and support. In fact it will give problems when a customer uses them (which is often the case with support, sales and info) and their mailbox is full or suspended.
You will see that your root email address is getting the full mails which should in fact go to them.
Those addresses should not be limited to root, so that's why it's best to either remove or comment them.
nobaloney
NoBaloney Internet Svcs - In Memoriam †
Problem with leaving these in the aliases file is that when a user sends (for example) to [email protected] and webmaster doesnt exist at that domain, the email will end up coming to you (presuming you forward root email somewhere, as I do.
If I recall correctly the RFQs require that the sending mailsever have a postmaster, not the domain, and etc.
So I create the required aliases in a domain-specific aliases file under (for example) /etc/virtual/host.example.com.
Jeff
If I recall correctly the RFQs require that the sending mailsever have a postmaster, not the domain, and etc.
So I create the required aliases in a domain-specific aliases file under (for example) /etc/virtual/host.example.com.
Jeff
groomy
Verified User
ok thank you, but I've had nothing but problems with the disk serveurn HS yesterday ..
I'm trying to redo everything new ..
I'm trying to redo everything new ..