S
Swakoo
Guest
Some updates
I have just changed all the domains in PLESK to REJECT mail instead of "bouncing with message"
I have just changed all the domains in PLESK to REJECT mail instead of "bouncing with message"
Your other posts... nope didn't.Originally posted by jamesyeeoc
'Reject' is good, it will definitely cut down on the number of bounce/doublebounce messages stuck in queue.
Have you seen any of my other posts (or other's posts) regarding qmail control files?
There are additional settings for Qmail which can also help in keeping the queue from getting overloaded.
After reaching the 'queuelifetime' value, they should be dropped from the queue.Where are the failure notices supposed to "go to" after a while being stagnant in queue?
Normally immediate, did you restart qmail or the server?Does it take a while for "reject" totake effect?
Strange that only 'most' work, as to the errors on using the qmHandle -R and having to do the -S then -R again, that is weird, never seen that happen before. Queue corruption maybe?most arguements work for qmHandle
Single or double spaces should not make any difference at all. Your server is possessed by the devil!I added one more space before "-Rt0"
This may get back to the other /var/qmail/control files which are not created by default, but you can create them manually. Do a 'man qmail-send' and 'man qmail-control' for details on these files (too much to post here). Ones to specifically note:MAILER-DAEMON@serverhostname, someare even send to "postmaster@serverhostname
These are files which are located in /var/qmail/control directory. Not all of them are created by default, so you may have to create some of them. This is just a sampling of the possible control files, not a comprehensive list...me
concurrencylocal
concurrencyremote
queuelifetime
doublebounceto (make it a single line containing just a # sign)
bouncefrom
bouncehost
Other than creating the queuelifetime file, you should also create/edit the concurrencyremote and the doublebounceto file.Originally posted by Swakoo
i added some updates after you post...
most of the failure notices are to postmaster@hostname of server.. you able to point me to a quick link as to how should i change to a valid email address.. wanna try catching all the mail so i can monitor them for the time being... cos hostname is not a valid domain name
What is the 'hostname of server'? If you SSH into the server and type the command 'hostname', does it show you the 'hostname of server' as it is in the emails? Just wondering how the hostname is not a valid domain name, or do you mean that that domain is just not created in Plesk, but the actual 'hostname of server' is a valid domain on the internet?
If this is the case, then it may be possible to create an alias for 'postmaster@'hostname of server' and point it to a valid email address such as monitorspam@yourdomain.com
(you would have to create this mail account in your Plesk)
Then edit /etc/aliases to include a line:
postmaster: monitorspam@yourdomain.com
Then edit /var/qmail/control/locals and add the 'hostname of server' on a separate line. Normally this file only contains 'localhost'
Then edit /var/qmail/control/rcpthosts and add the 'hostname of server'
Then restart qmail using the control panel, or from the commandline:
/etc/init.d/qmail restart
Then send a test message to 'postmaster@'hostname of server' and it should then end up in the mailbox for 'monitorspam@yourdomain.com'
does a long mail queue list block other mails?
It causes delays things since it takes time to process through 11000 messages
'talks about restricting the relay by configuring to 127.0.0.1/32'
Yes, you should set this, otherwise it may be possible for someone to spoof an IP as though they were a 'local' address.
and more updates here:
Questions...
Under Plesk->Server-Mail->Preference,
should Relay be put to closed?
You should set it for 'Authorization required' and checkmark 'SMTP'
And for Names for POP3/IMAP account, what s the difference between using full and short?
If you select FULL only, then your clients will be forced to use their full email address (someuser@somedomain.com) as the username in their mail clients. If you set it for short or Full then they can use either 'someuser' or 'someuser@somedomain.com'.
Will carry on the battle against the possessed server (or maybe its just me) tomorrow
thanks james!
Originally posted by Swakoo
thats long piece of info for me to digest... hang on..
meanwhile with regards to seting 127.0.0.1/32
Original is 127.0.0.0/8
- is it .0 or 1 are the end?
- if i add the /32 option, do i remove the the /8
You would replace the entire 127.0.0.0/8 with 127.0.0.1/32
This has to do with IP subnets.
127.0.0.0/1 = 0.0.0.1 to 127.255.255.254
127.0.0.0/2 = 64.0.0.1 to 127.255.255.254
127.0.0.0/4 = 112.0.0.1 to 127.255.255.254
127.0.0.0/8 = 127.0.0.1 to 127.255.255.254
127.0.0.0/16 = 127.0.0.1 to 127.0.255.254
127.0.0.0/24 = 127.0.0.1 to 127.0.0.254
127.0.0.1/32 = 127.0.0.1 only.
As you can see, you do not want to have less than /32 or you will be allowing lots of additional addresses.
what does this really do Don understand...
also an upadte.. my queue is about 2k plus..
i tried sending my mail to my 3 email accounts (local isp, my own domain email account, gmail)
The bigger the queue, the bigger the delay for all messages in the queue.
all 3 didn't receive it yet..
I check the 2 logs
/usr/local/psa/var/log/smtp_pendings.log
/usr/local/psa/var/log/maillog
but can't find any trace of the message..
how can i search if the message is still in the server and not send?
i am currently doing a "grep sayitreachyou" in /var/qmail..
You should be searching in the /var/qmail/queue directories, this is where the queued up mail is kept while waiting for delivery (either local or remote delivery).
Did you ever adjust any of the values in the control files? Such as concurrencyremote (default=20, try 250), and setup doublebounceto file? And set value in queuelifetime to a lower number (default is 604800 seconds = 1 week) Try 86400 (1 day)
thats the subject i put....
by the way, i have not receive the mail yet...
I am still concerned that your Qmail installation is corrupted, not only from the -Rt0, but also qmHandle not 'fully' working. You really may want to consider forcing a reinstall of the qmail related RPM files.
thanks
Nothing to thank me for. All I'm doing is answering questionsOriginally posted by Swakoo
I did a grep -1R "sayitreachyou" *
thats the subject i put....
what does -1R with a * at the back means? R is recursive, * is all files I suppose? Then 1? doesn't say in the --help
I suppose you found that command on some forum and saw a lowercase L 'l' and thought it was a number one '1'.From the man pages for 'grep':
-l, --files-with-matches
Suppress normal output; instead print the name of each input
file from which output would normally have been printed. The
scanning will stop on the first match.
-R, -r, --recursive
Read all files under each directory, recursively; this is equiv-
alent to the -d recurse option.
And the trailing * is telling it to search all files.
Anyway I found it in /var/qmail/queue/mess/21/4671689
The reason it listed the path/filename is due to the lowercase L option above.
How come its still there...?
The reason it is still there is because it has not been successfully delivered to the remote server (or local mailbox) yet.
There are many folders within /var/qmail/queue ... if it is in mess.. meaning...?
'mess' stands for 'messages'. The directory structure is how qmail organizes and keeps track of the messages. Not something you have to be concerned with.
Tried doing a search (still) on the different folder purpose.. i may be searching wrong.. any pointers?
You can spend countless hours scouring the www.qmail.org site and www.qmailrocks.org and using google. Search terms? qmail +queue +path +structure +directory and about a hundred different combinations. I am not that curious.
The mail in a mess? hahahaha
but anyway, outgoing mail now is stuck there... :S
What a headache....
thanks
This is basically a DNS TXT type record, the contents you would use the wizard at pobox.com, but this should not be the cause of your problems.SPF fights return-path address forgery and makes it easier to identify spoofs.
Domain owners identify sending mail servers in DNS.
SMTP receivers verify the envelope sender address against this information, and can distinguish authentic messages from forgeries before any message data is transmitted.
You can set the PTR on your server, but unless the ISP who 'owns' the IP has delegated control of the IP to you (probably not), then you will need to have them get involved on this.Originally posted by Swakoo
yup I have, mail.mydomain.com points to my mail server ip via the A record.
do I need to set the Reverse record then? Is it using PTR?
nameserver 127.0.0.1
search localdomain