[qmailtoaster] Local mailserver mx backup on the same machine

2012-04-01 Thread Sérgio Rosa
Hi all,

I'm trying to setup the following:

mail1  mail2
   | |
   | |
   ---|--
  |
nfs server

on the nfs server I export:
/var/qmail/control
/var/qmail/users
/home/vpopmail/domains

at the DNS level (mx setup) I have
domain a.com 10 mail1
domain a.com 30 mail2

domain b.com 10 mail2
domain b.com 30 mail1

domain c.com 10 client_mail_server
domain c.com 30 mail2

When, at domain c.com, the client_mail_server is down all mail I received
is refused with:
 failure:
Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/

the b.com domain is in the /var/qmail/control/rcpthosts

The idea was to have to servers that would deliver both local and perform
as MX Backup for each other, and spreading the load, but when the first mx
server is not local, things break.

Any thoughts on why?

Thank you


*Sérgio Rosa
*AWD
Serviços Internet
*Consultor*
Site:
Email:
Telm*. * http://www.awd.pt
https://www.awd.ptsergior...@awd.pt
(+351) 91 348 9195
  [image: undefined]
https://www.facebook.com/pages/AWD-Arquitectura-Web-e-Design/184497498235106


[qmailtoaster] Re: Mail issue

2012-04-01 Thread Eric Shubert

On 03/31/2012 10:28 PM, Délsio Cabá wrote:

Hi,

#reject-empty-rdns
#reject-ip-in-cc-rdns
reject-missing-sender-mx
#reject-unresolvable-rdns


These 3 that you have commented out are quite effective filters. I would 
use empty and unresolvable filters unquestionably. I believe gmail does 
this as well, although I'm not positive on that.


ip-in-cc is a reportedly a little more specialized. IIRC Sam mentioned 
that this may not be as appropriate in (non-US) settings, although I'm 
not convinced. I use it and don't have a problem receiving international 
emails, although I don't receive a lot of them.


--
-Eric 'shubes'


-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




Re: [qmailtoaster] Mail issue

2012-04-01 Thread Khan Mohamed Ashraf
On Sun, Apr 1, 2012 at 10:58 AM, Délsio Cabá del...@gmail.com wrote:

 Hi,

 This is my config file:
 dns-blacklist-entry=sbl-xbl.spamhaus.org
 dns-blacklist-entry=ix.dnsbl.manitu.net
 dns-blacklist-entry=cbl.abuseat.org
 dns-blacklist-entry=spamrbl.imp.ch
 dns-blacklist-entry=b.barracudacentral.org
 graylist-level=always
 graylist-dir=/var/spamdyke/graylist
 graylist-max-secs=5356800
 graylist-min-secs=280
 greeting-delay-secs=0
 idle-timeout-secs=60
 ip-blacklist-file=/etc/spamdyke/blacklist_ip
 ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
 ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
 ip-whitelist-file=/etc/spamdyke/whitelist_ip
 local-domains-file=/var/qmail/control/rcpthosts
 local-domains-file=/var/qmail/control/morercpthosts
 log-level=info
 log-target=SYSLOG
 max-recipients=50
 #policy-url=http://my.policy.explanation.url/
 rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
 rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
 recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
 recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
 #reject-empty-rdns
 #reject-ip-in-cc-rdns
 reject-missing-sender-mx
 #reject-unresolvable-rdns
 sender-blacklist-file=/etc/spamdyke/blacklist_senders
 sender-whitelist-file=/etc/spamdyke/whitelist_senders
 tls-certificate-file=/var/qmail/control/servercert.pem
 tls-level=smtp



 On 31 March 2012 23:18, Carlos Herrera Polo carlos.herrerap...@gmail.com
wrote:

 Can you send spamdyke's config file ?


 2012/3/31, Délsio Cabá del...@gmail.com:
  Hi,
 
  I I am also struggling with some spam on my server. I got one from the
ip
  91.227.36.144. None of the major RBL's have that IP blacklisted. So the
  email got through. Passing SPF check, Sgaylisting and RBL.
  More and more spammers are now finding ways to pass this RBL checks by
  sending emails from random IP's.
  I had to lower spamassassin from 9 to 7 now. Hope it helps
 
  Cheers
 
  On 31 March 2012 09:53, Bharath Chari qmailtoas...@arachnis.com
wrote:
 
  On Saturday 31 March 2012 12:27 PM, rajeshrudramani wrote:
 
 
 
  Hi,
 
 
  In my mail id getting spam mail from different airttel
ips.
  how to block the mails and series of ip. Please guide me.
 
   Aren't you running an RBL check? Most of this spam will be from
dynamic
  IPs. Airtel, unfortunately is amongst the top 5 spambot networks in
the
  world.
 
  Bharath
 
 
  --**--**
  -
  Qmailtoaster is sponsored by Vickers Consulting Group (
  www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and
installations.
  If you need professional help with your setup, contact them today!
  --**--**
  -
 Please visit qmailtoaster.com for the latest news, updates, and
  packages.
  To unsubscribe, e-mail: qmailtoaster-list-unsubscribe@**
  qmailtoaster.com qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-help@**
  qmailtoaster.com qmailtoaster-list-h...@qmailtoaster.com
 
 
 
 

 --
 Enviado desde mi dispositivo móvil


-
 Qmailtoaster is sponsored by Vickers Consulting Group (
www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and
installations.
  If you need professional help with your setup, contact them today!

-
 Please visit qmailtoaster.com for the latest news, updates, and
packages.

  To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com



In reply to Bharat Chari's statement Airtel, unfortunately is amongst the
top 5 spambot networks in the world. I agree. But I would not lay the
entire blame on Airtel alone.
The reason so many spambots are hosted on these networks is the low and
could not care 2 hoots about my machine being infected attitude of users
that leads to this. Educating users to be proactive about protecting their
computing environment (mostly one dominant OS) from infiltration and hijack
is a must. Major Indian ISP's such as Airtel should also participate in the
efforts to take down the command and control centers of these spambot
networks.

-- 
Khan Md. Ashraf
Chennai
India


[qmailtoaster] Re: Mail issue

2012-04-01 Thread Eric Shubert

On 04/01/2012 08:43 AM, Khan Mohamed Ashraf wrote:

In reply to Bharat Chari's statement Airtel, unfortunately is amongst
the top 5 spambot networks in the world. I agree. But I would not lay
the entire blame on Airtel alone.
The reason so many spambots are hosted on these networks is the low and
could not care 2 hoots about my machine being infected attitude of users
that leads to this. Educating users to be proactive about protecting
their computing environment (mostly one dominant OS) from infiltration
and hijack is a must. Major Indian ISP's such as Airtel should also
participate in the efforts to take down the command and control centers
of these spambot networks.


Perhaps someone should attempt to persuade Airtel to block outbound port 
25 traffic from their dhcp and/or residential subscribers that's not 
destined to their smtp servers. This is what Cox (cable) and Centurylink 
(DSL) both do in this area. I think doing so goes a long way toward 
thwarting infected machines.


Personally, I use a perimeter firewall to block any outbound port 25 
traffic that doesn't originate from my QMT host. This keeps unauthorized 
email from going out on an IP address which also services user internet 
access.


--
-Eric 'shubes'


-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




Re: [qmailtoaster] Re: Mail issue

2012-04-01 Thread Maxwell Smart

  
  


On 04/01/2012 09:07 AM, Eric Shubert wrote:
On
  04/01/2012 08:43 AM, Khan Mohamed Ashraf wrote:
  
  In reply to Bharat Chari's statement
"Airtel, unfortunately is amongst

the top 5 spambot networks in the world". I agree. But I would
not lay

the entire blame on Airtel alone.

The reason so many spambots are hosted on these networks is the
low and

could not care 2 hoots about my machine being infected attitude
of users

that leads to this. Educating users to be proactive about
protecting

their computing environment (mostly one dominant OS) from
infiltration

and hijack is a must. Major Indian ISP's such as Airtel should
also

participate in the efforts to take down the command and control
centers

of these spambot networks.

  
  
  Perhaps someone should attempt to persuade Airtel to block
  outbound port 25 traffic from their dhcp and/or residential
  subscribers that's not destined to their smtp servers. This is
  what Cox (cable) and Centurylink (DSL) both do in this area. I
  think doing so goes a long way toward thwarting infected machines.
  
  
  Personally, I use a perimeter firewall to block any outbound port
  25 traffic that doesn't originate from my QMT host. This keeps
  unauthorized email from going out on an IP address which also
  services user internet access.
  
  

This is way beyond the scope of the average user. My father for
instance could never on his own block port 25 traffic. He use to
have a Windows box and recently upgraded. I built him a Linux box
and it seems to have stopped any Malware problems he was having.

-- 
  
  



Re: [qmailtoaster] Re: Mail issue

2012-04-01 Thread Délsio Cabá
I must agree that the options:
#reject-empty-rdns
#reject-ip-in-cc-rdns
reject-missing-sender-mx
#reject-unresolvable-rdns

are very useful for blocking spam, but unfortunately I keep having
complains from some clients that emails were not coming in. I fould out
that some mail server don't even have reverse Ip configured and others have
but the reverse name had not A Records.
So I decided to disable reject-empty-rdns and reject-unresolvable-rdns.

As for reject-ip-in-cc-rdns I really don't any advantage to have this
enabled.

So I rely only in RBL.
What's the differente between dns-blacklist-entry=sbl-xbl.spamhaus.org and
dns-blacklist-entry=sbl-xbl.spamhaus.org and check-dnsrbl=
sbl-xbl.spamhaus.org ?


Any other suggestions?

On 1 April 2012 18:26, Maxwell Smart c...@yother.com wrote:



 On 04/01/2012 09:07 AM, Eric Shubert wrote:

 On 04/01/2012 08:43 AM, Khan Mohamed Ashraf wrote:

 In reply to Bharat Chari's statement Airtel, unfortunately is amongst
 the top 5 spambot networks in the world. I agree. But I would not lay
 the entire blame on Airtel alone.
 The reason so many spambots are hosted on these networks is the low and
 could not care 2 hoots about my machine being infected attitude of users
 that leads to this. Educating users to be proactive about protecting
 their computing environment (mostly one dominant OS) from infiltration
 and hijack is a must. Major Indian ISP's such as Airtel should also
 participate in the efforts to take down the command and control centers
 of these spambot networks.


 Perhaps someone should attempt to persuade Airtel to block outbound port
 25 traffic from their dhcp and/or residential subscribers that's not
 destined to their smtp servers. This is what Cox (cable) and Centurylink
 (DSL) both do in this area. I think doing so goes a long way toward
 thwarting infected machines.

 Personally, I use a perimeter firewall to block any outbound port 25
 traffic that doesn't originate from my QMT host. This keeps unauthorized
 email from going out on an IP address which also services user internet
 access.

  This is way beyond the scope of the average user.  My father for instance
 could never on his own block port 25 traffic.  He use to have a Windows box
 and recently upgraded.  I built him a Linux box and it seems to have
 stopped any Malware problems he was having.

 --

cj's_sig.png

Re: [qmailtoaster] Re: Questions on setting for the special e-mailaccount

2012-04-01 Thread Tonix (Antonio Nati)

I'm not following closely this thread, but I'm listening something odd.

For each define like CHKUSER_ALLOW_SENDER_CHAR_10 there is also in 
chkuser.c


   #if defined CHKUSER_ALLOW_SENDER_CHAR_10
(user-s[x] != CHKUSER_ALLOW_SENDER_CHAR_10)
   #endif


So, just adding another define in chkuser_setting.h is a waste of time, 
if you don't change chkuser.c too.


Tonino

P.S. I feel this check should not be used anymore, because as of today 
strange characters are widely used in email addresses.



Il 31/03/2012 09:27, q...@foxitsoftware.com ha scritto:

update.
Hi Eric,
I try the following steps,please help to check if it is OK.
1)vim /root/rpmbuild/BUILD/qmail-1.03/chkuser_settings.h
2)add
#define CHKUSER_ALLOW_SENDER_CHAR_11 ''' and  
#define CHKUSER_ALLOW_RCPT_CHAR_11 '''

/*
 * If you need more additional characters to be accepted within sender address
 * uncomment one of the following #define and edit the character value.
 * Be careful to use '*' (single hiphen) and NOT * (double hiphen) around the
 * wanted char.
 *
 * Remember: '#' and '+' are accepted by CHKUSER_ALLOW_SENDER_SRS
 *
 */
#define CHKUSER_ALLOW_SENDER_CHAR_1 '$'
#define CHKUSER_ALLOW_SENDER_CHAR_2 '%'
#define CHKUSER_ALLOW_SENDER_CHAR_3 '/'
#define CHKUSER_ALLOW_SENDER_CHAR_4 '?'
#define CHKUSER_ALLOW_SENDER_CHAR_5 '*'
#define CHKUSER_ALLOW_SENDER_CHAR_6 '^'
#define CHKUSER_ALLOW_SENDER_CHAR_7 '~'
#define CHKUSER_ALLOW_SENDER_CHAR_8 ''
#define CHKUSER_ALLOW_SENDER_CHAR_9 '#'
#define CHKUSER_ALLOW_SENDER_CHAR_10 '='
#define CHKUSER_ALLOW_SENDER_CHAR_11 '''
/*
 * If you need more additional characters to be accepted within rcpt address
 * uncomment one of the following #define and edit the character value.
 * Be careful to use '*' (single hiphen) and NOT * (double hiphen) around the
 * wanted char.
 *
 * Remember: '#' and '+' are accepted by CHKUSER_ALLOW_RCPT_SRS
 *
 */
#define CHKUSER_ALLOW_RCPT_CHAR_1 '$'
#define CHKUSER_ALLOW_RCPT_CHAR_2 '%'
#define CHKUSER_ALLOW_RCPT_CHAR_3 '/'
#define CHKUSER_ALLOW_RCPT_CHAR_4 '?'
#define CHKUSER_ALLOW_RCPT_CHAR_5 '*'
#define CHKUSER_ALLOW_RCPT_CHAR_6 '^'
#define CHKUSER_ALLOW_RCPT_CHAR_7 '~'
#define CHKUSER_ALLOW_RCPT_CHAR_8 ''
#define CHKUSER_ALLOW_RCPT_CHAR_9 '#'
#define CHKUSER_ALLOW_RCPT_CHAR_10 '='
#define CHKUSER_ALLOW_RCPT_CHAR_11 '''
3)
rpmbuild -bb --with fedora_1164 qmail-toaster.spec ---it is ok
Checking for unpackaged file(s): /usr/lib/rpm/check-files 
/root/rpmbuild/BUILDROOT/qmail-toaster-1.03-1.3.22.x86_64
Wrote: /root/rpmbuild/RPMS/x86_64/qmail-toaster-1.03-1.3.22.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/qmail-pop3d-toaster-1.03-1.3.22.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.9XekqK
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd qmail-1.03
+ '[' -n /root/rpmbuild/BUILDROOT/qmail-toaster-1.03-1.3.22.x86_64 -a 
/root/rpmbuild/BUILDROOT/qmail-toaster-1.03-1.3.22.x86_64 '!=' / ']'
+ rm -rf /root/rpmbuild/BUILDROOT/qmail-toaster-1.03-1.3.22.x86_64
+ '[' -d /root/rpmbuild/BUILD/qmail-1.03 ']'
+ rm -rf /root/rpmbuild/BUILD/qmail-1.03
+ exit 0
4)
[root@demo6 x86_64]# rpm -Uvh --replacefiles --replacepkgs qmail-*.rpm
Preparing...### [100%]
 Adding qmailtoaster users and groups.
groupadd: group 'nofiles' already exists
groupadd: group 'qmail' already exists
   1:qmail-toaster  warning: /var/qmail/control/servercert.pem created 
as /var/qmail/control/servercert.pem.rpmnew
### [ 50%]
 Creating queue/lock/trigger named pipe.
 Compiling badmimetypes.
 Compiling badloadertypes.
 Making tlsserverciphers.
 Linking tlsserverciphers to tlsclientciphers.
 Making dh_keys.
Generating RSA private key, 512 bit long modulus

...
e is 65537 (0x10001)
Generating DH parameters, 512 bit long safe prime, generator 2
This is going to take a long time
.+...+.++*++*++*++*++*++*
Generating DH parameters, 1024 bit long safe prime, generator 2
This is going to take a long time
..++++..+..++*++*++*
   2:qmail-pop3d-toaster### [100%]
Regards
2012-03-31

q...@foxitsoftware.com

*???:* q...@foxitsoftware.com
*:* 2012-03-31  14:53:24
*???:* qmailtoaster-list
*??:*
*??:* Re: Re: [qmailtoaster] Re: Questions on setting for the special 
e-mailaccount

Hi Eric,
I try the following steps,please help to check if it is OK.
1)vim /root/rpmbuild/BUILD/qmail-1.03/chkuser_settings.h
2)add #define CHKUSER_ALLOW_SENDER_CHAR_11 '''
/*
 * If you need more additional characters to be accepted within sender address
 * uncomment one of the 

[qmailtoaster] Re: Mail issue

2012-04-01 Thread Eric Shubert

On 04/01/2012 10:55 AM, Délsio Cabá wrote:

I must agree that the options:
#reject-empty-rdns
#reject-ip-in-cc-rdns
reject-missing-sender-mx
#reject-unresolvable-rdns

are very useful for blocking spam, but unfortunately I keep having
complains from some clients that emails were not coming in. I fould out
that some mail server don't even have reverse Ip configured and others
have but the reverse name had not A Records.
So I decided to disable reject-empty-rdns and reject-unresolvable-rdns.


I haven't seen that many that are misconfigured. In some cases the 
domain has moved to another host which is not quite configured correctly 
yet.


I ask my customers for the domain(s) that are being blocked, and explain 
to them that gmail is blocking email from that domain as well. Then I 
attempt to contact the admin and let them know what the problem is, and 
whitelist the domain in spamdyke.


I'm simply not willing to forgo the advantages these filters give 
everyone else due to a few lame brained mail admins. To each his own though.



So I rely only in RBL.
What's the differente between dns-blacklist-entry=sbl-xbl.spamhaus.org
http://sbl-xbl.spamhaus.org and
dns-blacklist-entry=sbl-xbl.spamhaus.org http://sbl-xbl.spamhaus.org
and |check-dnsrbl=|sbl-xbl.spamhaus.org http://sbl-xbl.spamhaus.org ?


Check with spamhaus.org on that. They have several lists.

--
-Eric 'shubes'


-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




[qmailtoaster] Re: Questions on setting for the special e-mailaccount

2012-04-01 Thread Eric Shubert

Tonino,

What is the way that you recommend turning off this function?

Thanks.

--
-Eric 'shubes'

On 04/01/2012 11:05 AM, Tonix (Antonio Nati) wrote:

I'm not following closely this thread, but I'm listening something odd.

For each define like CHKUSER_ALLOW_SENDER_CHAR_10 there is also in
chkuser.c

#if defined CHKUSER_ALLOW_SENDER_CHAR_10
 (user-s[x] != CHKUSER_ALLOW_SENDER_CHAR_10)
#endif


So, just adding another define in chkuser_setting.h is a waste of time,
if you don't change chkuser.c too.

Tonino

P.S. I feel this check should not be used anymore, because as of today
strange characters are widely used in email addresses.


Il 31/03/2012 09:27, q...@foxitsoftware.com ha scritto:

update.
Hi Eric,
I try the following steps,please help to check if it is OK.
1)vim /root/rpmbuild/BUILD/qmail-1.03/chkuser_settings.h
2)add
#define CHKUSER_ALLOW_SENDER_CHAR_11 ''' and
#define CHKUSER_ALLOW_RCPT_CHAR_11 '''
/*
 * If you need more additional characters to be accepted within sender address
 * uncomment one of the following #define and edit the character value.
 * Be careful to use '*' (single hiphen) and NOT * (double hiphen) around the
 * wanted char.
 *
 * Remember: '#' and '+' are accepted by CHKUSER_ALLOW_SENDER_SRS
 *
 */
#define CHKUSER_ALLOW_SENDER_CHAR_1 '$'
#define CHKUSER_ALLOW_SENDER_CHAR_2 '%'
#define CHKUSER_ALLOW_SENDER_CHAR_3 '/'
#define CHKUSER_ALLOW_SENDER_CHAR_4 '?'
#define CHKUSER_ALLOW_SENDER_CHAR_5 '*'
#define CHKUSER_ALLOW_SENDER_CHAR_6 '^'
#define CHKUSER_ALLOW_SENDER_CHAR_7 '~'
#define CHKUSER_ALLOW_SENDER_CHAR_8 ''
#define CHKUSER_ALLOW_SENDER_CHAR_9 '#'
#define CHKUSER_ALLOW_SENDER_CHAR_10 '='
#define CHKUSER_ALLOW_SENDER_CHAR_11 '''
/*
 * If you need more additional characters to be accepted within rcpt address
 * uncomment one of the following #define and edit the character value.
 * Be careful to use '*' (single hiphen) and NOT * (double hiphen) around the
 * wanted char.
 *
 * Remember: '#' and '+' are accepted by CHKUSER_ALLOW_RCPT_SRS
 *
 */
#define CHKUSER_ALLOW_RCPT_CHAR_1 '$'
#define CHKUSER_ALLOW_RCPT_CHAR_2 '%'
#define CHKUSER_ALLOW_RCPT_CHAR_3 '/'
#define CHKUSER_ALLOW_RCPT_CHAR_4 '?'
#define CHKUSER_ALLOW_RCPT_CHAR_5 '*'
#define CHKUSER_ALLOW_RCPT_CHAR_6 '^'
#define CHKUSER_ALLOW_RCPT_CHAR_7 '~'
#define CHKUSER_ALLOW_RCPT_CHAR_8 ''
#define CHKUSER_ALLOW_RCPT_CHAR_9 '#'
#define CHKUSER_ALLOW_RCPT_CHAR_10 '='
#define CHKUSER_ALLOW_RCPT_CHAR_11 '''
3)
rpmbuild -bb --with fedora_1164 qmail-toaster.spec ---it is ok
Checking for unpackaged file(s): /usr/lib/rpm/check-files 
/root/rpmbuild/BUILDROOT/qmail-toaster-1.03-1.3.22.x86_64
Wrote: /root/rpmbuild/RPMS/x86_64/qmail-toaster-1.03-1.3.22.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/qmail-pop3d-toaster-1.03-1.3.22.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.9XekqK
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd qmail-1.03
+ '[' -n /root/rpmbuild/BUILDROOT/qmail-toaster-1.03-1.3.22.x86_64 -a 
/root/rpmbuild/BUILDROOT/qmail-toaster-1.03-1.3.22.x86_64 '!=' / ']'
+ rm -rf /root/rpmbuild/BUILDROOT/qmail-toaster-1.03-1.3.22.x86_64
+ '[' -d /root/rpmbuild/BUILD/qmail-1.03 ']'
+ rm -rf /root/rpmbuild/BUILD/qmail-1.03
+ exit 0
4)
[root@demo6 x86_64]# rpm -Uvh --replacefiles --replacepkgs qmail-*.rpm
Preparing...### [100%]
 Adding qmailtoaster users and groups.
groupadd: group 'nofiles' already exists
groupadd: group 'qmail' already exists
   1:qmail-toaster  warning: /var/qmail/control/servercert.pem created 
as /var/qmail/control/servercert.pem.rpmnew
### [ 50%]
 Creating queue/lock/trigger named pipe.
 Compiling badmimetypes.
 Compiling badloadertypes.
 Making tlsserverciphers.
 Linking tlsserverciphers to tlsclientciphers.
 Making dh_keys.
Generating RSA private key, 512 bit long modulus

...
e is 65537 (0x10001)
Generating DH parameters, 512 bit long safe prime, generator 2
This is going to take a long time
.+...+.++*++*++*++*++*++*
Generating DH parameters, 1024 bit long safe prime, generator 2
This is going to take a long time
..++++..+..++*++*++*
   2:qmail-pop3d-toaster### [100%]
Regards
2012-03-31

q...@foxitsoftware.com

*发件人:* q...@foxitsoftware.com
*发送时间:* 2012-03-31  14:53:24
*收件人:* qmailtoaster-list
*抄送:*
*主题:* Re: Re: [qmailtoaster] Re: Questions on setting for the
special e-mailaccount
Hi Eric,
I try the following steps,please help to check if it is OK.
1)vim /root/rpmbuild/BUILD/qmail-1.03/chkuser_settings.h
2)add 

Re: [qmailtoaster] Re: Mail issue

2012-04-01 Thread Bharath Chari

On Monday 02 April 2012 04:55 AM, Eric Shubert wrote:

On 04/01/2012 10:55 AM, Délsio Cabá wrote:

I must agree that the options:
#reject-empty-rdns
#reject-ip-in-cc-rdns
reject-missing-sender-mx
#reject-unresolvable-rdns

are very useful for blocking spam, but unfortunately I keep having
complains from some clients that emails were not coming in. I fould out
that some mail server don't even have reverse Ip configured and others
have but the reverse name had not A Records.
So I decided to disable reject-empty-rdns and reject-unresolvable-rdns.


I haven't seen that many that are misconfigured. In some cases the 
domain has moved to another host which is not quite configured 
correctly yet.


I ask my customers for the domain(s) that are being blocked, and 
explain to them that gmail is blocking email from that domain as well. 
Then I attempt to contact the admin and let them know what the problem 
is, and whitelist the domain in spamdyke.


I'm simply not willing to forgo the advantages these filters give 
everyone else due to a few lame brained mail admins. To each his own 
though.



So I rely only in RBL.
What's the differente between dns-blacklist-entry=sbl-xbl.spamhaus.org
http://sbl-xbl.spamhaus.org and
dns-blacklist-entry=sbl-xbl.spamhaus.org http://sbl-xbl.spamhaus.org
and |check-dnsrbl=|sbl-xbl.spamhaus.org http://sbl-xbl.spamhaus.org ?


Check with spamhaus.org on that. They have several lists.

Coming back to Rajesh's original problem, I don't think he's using the 
spamhaus zen blocklist. Because airtel has clearly listed their dynamic 
IP blocks as not suitable for smtp in the PBL. I use zen and none of the 
Airtel dynamic IP spambots get through to me.


http://www.spamhaus.org/pbl/query/PBL243394 shows one of their IP blocks

Bharath



-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com