Hi Probably, I don´t explain me very well what I try to say I will try with an example: SMTP-AUTH via SD User to auth xxx@... Mail from: xxx@... Both domains are on localdomains How can I control that the outgoing email belongs to the auth domain ? Txs in advance Pablo Murillo
I had the same problem -- because someone from China is brute-forcing all "info <at> ..." accounts.. Once they find an easy password, they abuse it with millions of spam.. - wrote code to check everyone's passwords for easyness (?) and forced ppl to change their passwords -- or I changed it for them.. especially PLESK's short form auth is a killer -- they just need to specify "info" no need for a domain next to it.. -t On 07/07/2012 09:05 PM, Pablo Murillo wrote: > Hi > > Probably, I don´t explain me very well what I try to say > > I will try with an example: > > SMTP-AUTH via SD > User to auth xxx <at> domain1.com > > Mail from: xxx <at> domain2.com > > Both domains are on localdomains > > How can I control that the outgoing email belongs to the auth domain ? > > Txs in advance > Pablo Murillo > > _______________________________________________ > spamdyke-users mailing list(Continue reading)
At this point, spamdyke will not check the authenticated username against the MAIL FROM address. This was one of the suggestions Mark Frater made in the recent "Spamdyke and Postfix" thread -- it's an interesting idea that I'm looking into. -- Sam Clippinger On Jul 7, 2012, at 1:05 PM, Pablo Murillo wrote: > Hi > > Probably, I don´t explain me very well what I try to say > > I will try with an example: > > SMTP-AUTH via SD > User to auth xxx@... > > Mail from: xxx@... > > Both domains are on localdomains > > How can I control that the outgoing email belongs to the auth domain ? > > Txs in advance > Pablo Murillo > > _______________________________________________ > spamdyke-users mailing list > spamdyke-users@... > http://www.spamdyke.org/mailman/listinfo/spamdyke-users(Continue reading)
Sam Clippinger wrote on 2012-07-09 16:37: > At this point, spamdyke will not check the authenticated username > against the MAIL FROM address. This was one of the suggestions Mark > Frater made in the recent "Spamdyke and Postfix" thread -- it's an > interesting idea that I'm looking into. Please note it may be quite valid to auth with <at> domain1 and send from <at> domain2 (i.e. when you got many domains attached to web server), so it would really be useful to be able to call own script/app to do the test. Regards, -- -- "Daddy, what "Formatting drive C:" means?"... Marcin http://wfmh.org.pl/carlos/
Hi There is a way to change the filters orders or add a new one ? I was reading the source and I didn´t find what I was looking for I need to validate the domain used on SMTP AUTH against the rcpthost file Why ? In the case of the SMTP AUTH, after a succeful loging, no more checks are made, and I need to check the domain used to login against the rcpthost file (local_domains_file variable) May be you are wondering why ? Well, we have a lot of servers whit a lot of domains, BUT we have a centralized DB for all the email accounts, so, if you connect to domai1.com to logging with pp@... and that domain is one of our domain's, the vpopmail (vchkpw) will validate the user, no matter if the domain is in the server where domain1.com is hosted or not I hope you understand, my english is not so good Txs in advance Pablo Murillo
For the most part, the order of the filters can be changed by editing the middleman() function in spamdyke.c around lines 1628, 1696 and 1756. Calls to filter_header_blacklist() are made within smtp_filter(). The filter functions are in filter.c. It would probably be best to start by using filter_sender_blacklist() as an example. -- Sam Clippinger On Jul 14, 2012, at 3:46 PM, Pablo Murillo wrote: > Hi > > There is a way to change the filters orders or add a new one ? > I was reading the source and I didn´t find what I was looking for > I need to validate the domain used on SMTP AUTH against the rcpthost file > > Why ? > > In the case of the SMTP AUTH, after a succeful loging, no more checks are > made, and I need to check the domain used to login against the rcpthost file > (local_domains_file variable) > May be you are wondering why ? > Well, we have a lot of servers whit a lot of domains, BUT we have a > centralized DB for all the email accounts, so, if you connect to domai1.com > to logging with pp@... and that domain is one of our domain's, the > vpopmail (vchkpw) will validate the user, no matter if the domain is in the > server where domain1.com is hosted or not > > I hope you understand, my english is not so good(Continue reading)
Thanks SAM!, I was looking in the wrong place! ----- Original Message ----- From: "Sam Clippinger" <samc@...> To: "spamdyke users" <spamdyke-users@...> Sent: Saturday, July 14, 2012 10:47 PM Subject: Re: [spamdyke-users] Changing filter order or add a new one For the most part, the order of the filters can be changed by editing the middleman() function in spamdyke.c around lines 1628, 1696 and 1756. Calls to filter_header_blacklist() are made within smtp_filter(). The filter functions are in filter.c. It would probably be best to start by using filter_sender_blacklist() as an example. -- Sam Clippinger On Jul 14, 2012, at 3:46 PM, Pablo Murillo wrote: > Hi > > There is a way to change the filters orders or add a new one ? > I was reading the source and I didn´t find what I was looking for > I need to validate the domain used on SMTP AUTH against the rcpthost file > > Why ? > > In the case of the SMTP AUTH, after a succeful loging, no more checks are > made, and I need to check the domain used to login against the rcpthost > file(Continue reading)
Sam,
maybe you could add a "user" filter, that would get called as the last
filter. It would simply call to a shell script if admin created one.
Admin would then point config for this filter either to a script (would
get called for every domain) or to a directory that would be structured
as graylisting is:
user_filter/
domain1.com/
custom_filter.sh (called for any user of domain1.com)
domain2.com
other_kind_of_filter.sh (for any user of domain2.com)
domain3.com
user1/
user1_script.sh (called only for user1@...)
Then admins could easily check some of their own stuff, like Pablo
needs. No spamdyke hacking, and shell scripts are really fast to create...
Just a thought,
ratko
Dne 15. 07. 2012 03:47, piše Sam Clippinger:
> For the most part, the order of the filters can be changed by editing
> the middleman() function in spamdyke.c around lines 1628, 1696 and
> 1756. Calls to filter_header_blacklist() are made within
> smtp_filter().
>
(Continue reading)Good suggestion! I've actually been wanting to add this kind of thing for a while, mostly so spamdyke could call SpamAssassin during message delivery -- the results could be used to reject the message outright instead of just modifying the headers. The message content would be passed to the external program, which could either modify it (and feed it back) or exit with a specific return code to indicate a rejection. The directory structure you describe is actually already in place -- the configuration directories are flexible enough to allow different scripts to be specified in almost any circumstance. -- Sam Clippinger On Jul 15, 2012, at 10:57 AM, Ratko Rudic wrote: > Sam, > > maybe you could add a "user" filter, that would get called as the last > filter. It would simply call to a shell script if admin created one. > > Admin would then point config for this filter either to a script (would > get called for every domain) or to a directory that would be structured > as graylisting is: > > user_filter/ > domain1.com/ > custom_filter.sh (called for any user of domain1.com) > domain2.com > other_kind_of_filter.sh (for any user of domain2.com) > domain3.com > user1/ > user1_script.sh (called only for user1@...) >(Continue reading)
RSS Feed