[qmailtoaster] POP3 not stoped working

2008-06-27 Thread Rugemalira
I need your help to restore pop3  back to work. IMAP is working perfectly.   I get the following errors When I telnet localhost on port 25 I get 554 mail server permanently rejected message(#5.3.0)   From outlook express, all users get This user has no $HOME/Maildir   I am running the latest ver

RE: [qmailtoaster] Emails rejected

2008-06-27 Thread António Pedro Lima
Olá José! É bom ler na língua materna, mas se calhar e a bem da lista vamos discutir o problema em Inglês, assim há mais gente a ajudar a ser ajudada! :-) I will check that about the zen.spamhaus.org because that is happening too, and with a non dynamic ip address. But the ISP providing that IP

Re: [qmailtoaster] Emails rejected

2008-06-27 Thread Jake Vickers
António Pedro Lima wrote: Jake, the problem is as shown bellow: Jun 23 09:07:07 mail spamdyke[13510]: DENIED_RDNS_MISSING from: [EMAIL PROTECTED] to: [EMAIL PROTECTED] origin_ip: 80.251.166.132 origin_rdns: (unknown) auth: (unknown) Turn off rdns checking in spamdyke:

Re: [qmailtoaster] POP3 not stoped working

2008-06-27 Thread Jake Vickers
Rugemalira wrote: I need your help to restore pop3 back to work. IMAP is working perfectly. I get the following errors When I telnet localhost on port 25 I get 554 mail server permanently rejected message(#5.3.0) From outlook express, all users get This user has no $HOME/Maildir

Re: [qmailtoaster] Emails rejected

2008-06-27 Thread Jose Mario Pires
I am just guessing here, but I think the examples show two different situations: On the first example, it looks like SpamAssassin didn't like the contents (headers included) of the message and scored it tooo high (16.2). I am not sure what is the score above which the mail is rejected, but I

RE: [qmailtoaster] Emails rejected

2008-06-27 Thread António Pedro Lima
Thank you Jake... I'll try it that way... But I have a huge amount of junk and spam being blocked that way... Lets see if I'm not opening too much the gates Thanks -Mensagem original- De: Jake Vickers [mailto:[EMAIL PROTECTED] Enviada: sexta-feira, 27 de Junho de 2008 11:48 Para:

Re: [qmailtoaster] Emails rejected

2008-06-27 Thread Jake Vickers
António Pedro Lima wrote: Thank you Jake... I'll try it that way... But I have a huge amount of junk and spam being blocked that way... Lets see if I'm not opening too much the gates You can't have it both ways I don't think. Look at the spamdyke options and see if there's a whitelist

[qmailtoaster] outgoing mail don't check blacklist?

2008-06-27 Thread Tolga Cengiz

Re: [qmailtoaster] outgoing mail don't check blacklist?

2008-06-27 Thread Jake Vickers
No, why would it? I think there's some instructions on the wiki still for running outgoing mail through spamassassin though. Running your outgoing mail through a blacklist would only check our mail server's IP address, unless you're implying that you want to check the user's IP addresses which

RE: [qmailtoaster] Emails rejected

2008-06-27 Thread António Pedro Lima
Your only other option is to get the other mail server admin to learn how to properly run a mail server. That's where your real problem lies. You couldn't be more true But that is a problem with no solution :-( -Mensagem original- De: Jake Vickers [mailto:[EMAIL PROTECTED]

[qmailtoaster] SENDER_NOCHECK=1

2008-06-27 Thread Dan Herbon
So out of nowhere people sending email on their blackberries started getting the 5.1.0 - Unknown address error 571-'sorry, sender address has invalid format (#5.7.1 - chkuser)' errors. I located the fix on the toaster wiki which basically says to add in SENDER_NOCHECK=1. Does adding this

Re: [qmailtoaster] SENDER_NOCHECK=1

2008-06-27 Thread Jake Vickers
Dan Herbon wrote: So out of nowhere people sending email on their blackberries started getting the 5.1.0 - Unknown address error 571-'sorry, sender address has invalid format (#5.7.1 - chkuser)' errors. I located the fix on the toaster wiki which basically says to add in SENDER_NOCHECK=1.

Re: [qmailtoaster] SENDER_NOCHECK=1

2008-06-27 Thread Jose Mario Pires
I think I had the same problem some months ago, when a client complained that he wasn't able to send mail to us. Luckily their postmaster is an adept of open source fan, so he agreed with me that it should be another dumb thing of his Exchange, but while I didn't comment this with anyone else less