Jump to content

r3dlight

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About r3dlight

  • Rank
    Newbie
  1. r3dlight

    Blacklisted ... I know why

    Hi Mr Wazoo, Thanks for your response. We are no more blacklisted on SpamCopDNSBL because we have unsuscribe, But we have been blacklisted twice and I'm trying to anticipate the third time, wich will logically happen soon if nothing is changed. The first and the second time, Ip 194.250.211.27 was blacklisted. We've have two LVS server, the 1St (the one which send the mail) was the 194.250.211.27. We have recently changed the configuration so that the second (194.250.211.28) replace the 1st (194.250.211.27). I reckon it was the 1st operation we did not to be blacklisted a third time with the same IP. Now we know why it is useless. That's why you see this growing traffic for 194.250.211.28
  2. r3dlight

    Blacklisted ... I know why

    Well, Gentlemen, First of all, let me explain our position. As an ISP, one of our goal is to provide a service reaching the best quality for our customers. In that way, we are usualy more involve in fighting spams and spammers rather than to produce "unsolicited emails". We are not spammers and we don't aimed to become ones. So we're looking for solutions about this issue, with your help indeed. We provide different services, such as email forwarding, mailbox with quotas, auto-reply, anti-spam ect. You will agree that setting quotas or not, have nothing to do with being a spammer or not. By this way, being blacklisted should'not be linked to the fact that quotas are used or not. Arguments about the use of quotas have nothing to do here. Quotas makes part of our strategy. Ok let's summarize the whole thing : The blacklisting reason is : "bounce emails sent after acceptance of the email instead of being rejected by the server during the SMTP phase" In practice, that case occure when an incoming mail is forwarded from a server A to a server B (In this case, our frontal Postix to another mail plateform). Then this server check the mail and notify the server A of any error (OverQuota,recipient error etc..). Then the server A bounces with the error message. The fact is, when first forwarded to server B, email is ACCEPTED, and then BOUNCED. Excepted the fact this is not a spam, we recognized that case is exploited by spammers. Here are the preconized solutions : - Discard Bounces To discard bounce will indeed, cancel the problem. But discarding bounces will discard Over-Quotas bounces, and Invalid-recipient and any error from the sender. The mail won't be sent, and the user won't be aware of that. - Discard and re-write a "clean" email to the sender with the Error Message We've tryed with efforts to find a way to catch messages before they're discarded, the Posfix Developers themselves have explained us that bounces are never stored on the server but sent as soon as the message is received. This issue seems to occure on most of MTA. If you have any tips about that, we are interrested. - Cancel Quotas (See above) - Check for valid delivery during the SMTP process A lot of our users are from Africa, maybe distance is irrelevant on the internet but Africa backbones are those of the lowest. An important point is that a lot of our customers have their own LDAP servers, so when Postfix check for the valid user, it have to check one by one every LDAP servers until to find the valid entry. We have to multiply the ping loss with the numbers of LDAP servers requested. We've tried this way and excepted the fact the mail-queue grow very fast, we often reach the SMTP Timeout. Here's an extract of ping session with Togo (some are Synchronous Sattelite Links or RNIS) 64 bytes from 10.89.1.35: icmp_seq=12 ttl=123 time=2030 ms 64 bytes from 10.89.1.35: icmp_seq=14 ttl=123 time=1842 ms 64 bytes from 10.89.1.35: icmp_seq=15 ttl=123 time=1980 ms 64 bytes from 10.89.1.35: icmp_seq=18 ttl=123 time=2162 ms 64 bytes from 10.89.1.35: icmp_seq=19 ttl=123 time=1812 ms 64 bytes from 10.89.1.35: icmp_seq=20 ttl=123 time=1990 ms (We have similar problems with Oceania) Here is the situation. You will recognize our present set-up isn't "spam-friendly" no more than our intentions. We don't reply "we can't do that" to any suggestions, we're looking for solutions and suggestions that can be applied in our architecture without changing nor the service neither its quality. I'm still persuaded there is a solution. D.L System Administror.
  3. r3dlight

    Blacklisted ... I know why

    We are an ISP so our clients will not accept that we stop bouncing back... it's not a few 'over-quota users' but we may reach around 1500 overquota accounts during vacations and without taking care of users who write a wrong email adress without paying attention ... ...but all gmail/hotmail senders will be tag as spammers ...
  4. r3dlight

    Blacklisted ... I know why

    --> Because our postfix server MUST forwards emails to others email servers (postfix, lotus etc...), then those servers check if the account is ok or overquota or if the user is unknown and they send back the bounce to our postfix server. Spams are already filtred at the beginning by the our postfix server... I don't speak about spams here (I don't know if I'm clear) email comes here--->postfix forwards emails/&smtp ok and spamassassin cleans spams--->another email server check the account | bounce back to the sender account <------ postfix (which cannot filter bounces)<--- if overquota send back bounce to
  5. r3dlight

    Blacklisted ... I know why

    We already have spamassassin to manage spams ... ...ok but how can you make a difference between a forged email and a non-forged email ? in the case of a regular user who want to write to an account which is overquota ...
  6. r3dlight

    Blacklisted ... I know why

    Ok, thank you for your replies, ... so now my questions are : How can I inform a regular user that his email can't be delivered because the destination account is over quota for exemple...? How can I redirect bounces to a special email account with postfix 2.2 ? (header_checks doesn't checks bounced emails) ..StevenUnderwood ...yes we can't check for valid users because it would take too much time (france to africa, or even france to australia)..
  7. r3dlight

    Blacklisted ... I know why

    We have a postfix 2.2... Is a bounce generated by a mail server a spam ? I don't understand you when you speak about spams ... what do you mean ? Because ... we must forward emails (so accept them) via VPN's for our clients ...
  8. r3dlight

    Blacklisted ... I know why

    Hi & thank you for your help... Actually, it's not just for spams... for exemple: if an email is sent to a user who is just 'over quota', a bounced email is sent back to our postfix server after it was originally accepted. I've read that in the links you gave me : If you must accept delivery before you know the status of a message, then file it internally - do not send, forward or bounce it outside your organization. The errant message can be placed in a special folder or routed to your postmaster. Ok but we must notify the sender that the user was overquota ... I don't know if I'm clear (sorry again for my english). Anyway, any ideas are welcomes ...
  9. Hi all, First of all forgive me for my english ;o) it's too bad ...I know I'll try to explain my problem quikly: My company manages 200 dedicated servers and a lot of them are in Africa (so it's clearly impossible to perform a LDAP check for users because of the delay). So we're blacklisted (see I've read the FAQs ) because of that : bounce emails sent after acceptance of the email instead of being rejected by the server during the SMTP phase ... Of course, we sell an "email forwarding" service to our clients and that's the point. Actually our server cannot check for users or it would be really too long. So to fix this, I don't see any solution. I'm thinking of creating a dedicated email box (bounce[at]company.com) and redirecting every bounced email inside to recreate a new email.... but as you see, it's a really 'dirty' way to fix this problem and it seems that postfix do not perform header_checks on bounced emails... so if you could help, it would be great !! I'm new on this company and my first goal is to fix it ... I hope I won't be fired soon lol... Thank you very much for your help.
×