Atomicorp

Scott,

I see you updated qgreylist (thank you!). But I don't know where to start with it. What does the rpm do on instalation (I mean what does it overwrite so I can back it up first, just in case)? And is there any configuration? I see mentions of mysql and various other things in another thread on greylisting, plus suggestions about how it might be turned on and off but I have no idea what you might or might not have implemented in your version.

Any chance of some beginner's instructions please?

Faris.

It doesnt overwrite anything, it just inserts itself into the SMTP chain on the box. Removing the rpm removes it from the chain, so theres nothing special you need to do other than install (yum install qgreylist) or remove it (yum remove qgreylist).

Thanks Scott.

I discovered an interesting discussion on this via google that turned out to be on the old version of site, in the comments section for the qgreylist project.

I'm itching to try this on my live machines. I'm going to try to wait but I suspect I'm going to end up doing it sooner rather than later.

I take it there's no way to whitelist certain IPs?

Faris.

They whitelist themselves eventually, and I know mike has done it manually before. Im afraid its been too long since Ive done it to point you in the right direction.

Thanks again Scott..

Well, how about this then: Is it possible and sensible to change the default retry "message". Here's what it says at the moment:


(first try:)
Temporary local problem - try later

(if it comes back too soon:)
Temporary local problem - I said try later

But I've noticed in my mail logs that some servers running greylisting actually say so. e.g. one says "greylisting in action - please retry later"

This seems sensible to me. e.g. it tells the admin of the sending server why the message was refused, and will also aid debugging if a bounce should ever be generated for any reason.

What do you think?

Faris.

Errr....

I just tried sending a message on the server that I've been testing on using authenticated smtp, and had problems.

Basically it is applying greylisting to authenticated smtp as well as incoming email.

This makes sense because it is in the path in smtp_psa

But in your message on the Plesk forum, I could have sworn you said it was compatible with smtp auth?

Faris.

Compatible yes, but that doesnt mean smtp_auth routes around it.

Ah

Faris.

urgs... my bad english and me:)

compatible? or not? ive installed qgreylist via yum.

smtp_psa looks like...
server_args = -Rt0 /var/qmail/bin/relaylock /var/qmail/bin/greylist /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true

would this work without problems?

thanks

way

//edit, just forgot
in psa 7.5.4 mailsettings are... auth needed, smtp

hello ;

What is greylist default delay time , where can i want to set it to 10 minutes

any other config files will be great

I, too, had troubles with SMTP_AUTH and ended up dumping qgreylist. The qgreylist site even lists smtp_auth as being incompatible with qgreylist. The suggested action is to run a second instance of qmail on a different port, server, or IP that is not listed in any MX records. Too much of a pain to configure for this girl...