Re: [qmailtoaster] Re: POP3 Authentication on CentOS 5.5 64Bit

[Kevin Qiu]

Hello Erik,

I'd like try the new package. The old version doesn't work under 64bit 
Linux. Where could I download it?


Kevin

于 2010年11月12日 18:58, Eric Shubert 写道:

TTBOMK the plan is presently to jump to vpopmail 5.5 with QMTv2.

Going from 5.4.32 from 5.4.17 would be nice. It involves a database 
change, which qtp-convert is already able to handle.


I believe that Jake's too busy to take this on. If someone would like 
to update the spec file and package an SRPM, I expect that Jake would 
entertain putting it up on the site if/when people have tested it out.


Anyone care to take this on?



-
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: re Invalid rcpthosts client email addresses sending emails to other rcpthosts clients

[Tony White]

Hi folks,
  Will this cure my issue, at least for now...

1. Have all my users use the QMT servers via SMTP-AUTH.
2. Set spf records to only allow my ip addresses to send mail for these domains.

The original problem was/is...

email being sent to my servers using valid/invalid accounts for domains that are
on my servers. I wanted to verify the email address against valid ones to reduce
the amount of spam.
  As an example "I" have apparently sent 1500 emails to my clients including 
"myself"
each day for the last few days. Obviously this is not true.
  So  doing the spf thing should stop those buggers from using my and other 
clients
names to send email and they will need to have a username and password to 
validate
before a send is accepted!.

  It would appear that the email accounts a very old. The emails that are 
arriving have
5-10 valid domain but valid/invalid users in the To Field. The same for CC and 
BCC.
They are the same addresses in each section.


On 18/11/2010 10:10 AM, Tonix (Antonio Nati) wrote:

Il 17/11/2010 23:41, Eric Shubert ha scritto:

On 11/17/2010 03:30 PM, Tonix (Antonio Nati) wrote:

Il 17/11/2010 15:56, Eric Shubert ha scritto:

That's a problem all right. I don't expect that using the submission
port would fix that either. The spfbehavior file should be separate
for the submission port to make that happen.

Ultimately, SPF should not be enforced for authenticated users. There
has been some talk about implementing SPF in spamdyke (I've been a
proponent of this). Perhaps we can nudge Sam and get it implemented
there. That would solve the problem.



Sorry I do not understand the problem: as far as I see SPF must be
disabled on submission port and for authenticated users, otherwise none
could give to authorized servers e-mails to relay.

Sources I'm using for qmail-smtpd check SPF only if RELAYCLIENT is not set.

Regards,

Tonino




I believe Tonino's correct. On second thought, I misunderstood the problem.

The problem is that mobile users submit email via the mobile smtp service, and don't come through QMT. Those servers 
would somehow need to be included in the SPF record. It has nothing to do with QMT (which is what creates the problem, 
somewhat ironically).




I feel when using SPF you have no other choice than relaying to ISP servers. Adding all possible SMTP servers of mobile 
operator is out of our possibility :-).


Ciao!

Tonino




--
best wishes
  Tony White

Yea Computing Services
http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717

Telephone No's
VIC : 03 5797 3344
VIC : 03 9008 5614
TAS : 03 6107 9099
NT  : 08 8921 4049
SA  : 08 7123 0847
NSW : 02 8014 5547
QLD : 07 3123 6647
WA  : 08 6365 2199
FAX : 03 9008 5610 (FAX2Email)
FAX : 03 5797-3288



IMPORTANT NOTICE

This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.


-
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: Issue with qmail-inject!

[Prasad Asokan]

Hi Eric,

  The mail has bounced back to the sender saying that the
line could not be parsed. Is qmail-inject invoked for mails sent alone, or
for mails received also? I understand qmail-inject processes the headers and
adds time stamp and process ID to the headers. Correct me if I am wrong. The
mail log was found from the send logs. Is there a way to relax this
particular character from qmail-inject.


Hi Senthil Vel,


Have already went through the links before and recently.
This is not the case of a missing < , also, in the issue you were referring
to, the mail had actually reached the queue. In this case, the mail hadn't
been in the queue for long, it was bounced straight away.

Regards,
Prasad Asokan.

On 17 November 2010 21:08, Eric Shubert  wrote:

> On 11/17/2010 08:10 AM, Prasad Asokan wrote:
>
>> Hi,
>>
>> We receive failure: qmail-inject:_fatal:_unable_
>> to_parse_this_line:/To:_...@domain.com  on one of
>>
>> our QMT servers. The mail was actually sent from a different domain, to
>> one of ours, and the above mentioned e-mail ID(not hosted with us)  was
>> in the To field. The mail was bounced back. Is there a way to relax this
>> or can you help me out why this is happening?
>>
>> Regards,
>> Prasad Asokan
>>
>
> I'm not sure how qmail-inject would come into play here. Where do you see
> the message?
>
> --
> -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: QMT Use Stats

[David Milholen]

  
  
Eric,
 +1

On 11/17/2010 8:46 AM, Eric Shubert wrote:
We're
  on the same page, Dave. For those who just can't wean themselves
  off of Exchange, QMT (w/ spamdyke) makes a great front-end
  processor. I expect it does at least as well as commercial
  services (such as one that rhymes with Houdini).
  
  
  In the not too distant (I hope) future, I hope to see QMT take on
  more enterprisey features. With vpopmail 5.5, I have my eye on
  LDAP support, and perhaps AD integration after that.
  
  
  There seem to be a lot of folks wanting to ditch Exchange. The
  FOSS community will do well to providing a strong alternative in
  that area.
  
  



-- 
  
  David Milholen
  Project Engineer
  P:501-318-1300

  

Re: [qmailtoaster] Re: re Invalid rcpthosts client email addresses sending emails to other rcpthosts clients

[Tonix (Antonio Nati)]

Il 17/11/2010 23:41, Eric Shubert ha scritto:

On 11/17/2010 03:30 PM, Tonix (Antonio Nati) wrote:

Il 17/11/2010 15:56, Eric Shubert ha scritto:

That's a problem all right. I don't expect that using the submission
port would fix that either. The spfbehavior file should be separate
for the submission port to make that happen.

Ultimately, SPF should not be enforced for authenticated users. There
has been some talk about implementing SPF in spamdyke (I've been a
proponent of this). Perhaps we can nudge Sam and get it implemented
there. That would solve the problem.



Sorry I do not understand the problem: as far as I see SPF must be
disabled on submission port and for authenticated users, otherwise none
could give to authorized servers e-mails to relay.

Sources I'm using for qmail-smtpd check SPF only if RELAYCLIENT is 
not set.


Regards,

Tonino




I believe Tonino's correct. On second thought, I misunderstood the 
problem.


The problem is that mobile users submit email via the mobile smtp 
service, and don't come through QMT. Those servers would somehow need 
to be included in the SPF record. It has nothing to do with QMT (which 
is what creates the problem, somewhat ironically).




I feel when using SPF you have no other choice than relaying to ISP 
servers. Adding all possible SMTP servers of mobile operator is out of 
our possibility :-).


Ciao!

Tonino


--


in...@zioniInterazioni di Antonio Nati
   http://www.interazioni.it  to...@interazioni.it



-
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: re Invalid rcpthosts client email addresses sending emails to other rcpthosts clients

[Eric Shubert]

On 11/17/2010 03:30 PM, Tonix (Antonio Nati) wrote:

Il 17/11/2010 15:56, Eric Shubert ha scritto:

That's a problem all right. I don't expect that using the submission
port would fix that either. The spfbehavior file should be separate
for the submission port to make that happen.

Ultimately, SPF should not be enforced for authenticated users. There
has been some talk about implementing SPF in spamdyke (I've been a
proponent of this). Perhaps we can nudge Sam and get it implemented
there. That would solve the problem.



Sorry I do not understand the problem: as far as I see SPF must be
disabled on submission port and for authenticated users, otherwise none
could give to authorized servers e-mails to relay.

Sources I'm using for qmail-smtpd check SPF only if RELAYCLIENT is not set.

Regards,

Tonino




I believe Tonino's correct. On second thought, I misunderstood the problem.

The problem is that mobile users submit email via the mobile smtp 
service, and don't come through QMT. Those servers would somehow need to 
be included in the SPF record. It has nothing to do with QMT (which is 
what creates the problem, somewhat ironically).


Thanks for making me think about this a little more, Tonino.
--
-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: re Invalid rcpthosts client email addresses sending emails to other rcpthosts clients

[Tonix (Antonio Nati)]

Il 17/11/2010 15:56, Eric Shubert ha scritto:
That's a problem all right. I don't expect that using the submission 
port would fix that either. The spfbehavior file should be separate 
for the submission port to make that happen.


Ultimately, SPF should not be enforced for authenticated users. There 
has been some talk about implementing SPF in spamdyke (I've been a 
proponent of this). Perhaps we can nudge Sam and get it implemented 
there. That would solve the problem.




Sorry I do not understand the problem: as far as I see SPF must be 
disabled on submission port and for authenticated users, otherwise none 
could give to authorized servers e-mails to relay.


Sources I'm using for qmail-smtpd check SPF only if RELAYCLIENT is not set.

Regards,

Tonino


--

in...@zioniInterazioni di Antonio Nati
   http://www.interazioni.it  to...@interazioni.it



-
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: emails (outbound) stuck in queue

[Patrick Ring]

Eric,
I ran the commands as you posted them (thank you).  No errors.

Immediately the 2 (out of 7) oldest messages no longer show in the
queue.  However, there are still 5 left (one bounce message (unrelated
to the 2), 2 legitimate emails, and 2 delivery/read receipts).

I ran the commands again just to be sure, and the 5 messages are still
there.

Should they have sent fairly quickly, or might it take some time?

Thank you,

Patrick M. Ring
P. Ring Technologies
Louisiana Web Host, LLC.
985-868-4200

-Original Message-
From: Eric Shubert [mailto:e...@shubes.net] 
Sent: Wednesday, November 17, 2010 12:56 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: [qmailtoaster] Re: emails (outbound) stuck in queue

On 11/17/2010 11:30 AM, Patrick Ring wrote:
> I had a spammer hack a client's email and load up the mail queue with 
> bogus emails.
> I used qmHandle with the appropriate strings to get rid of the 
> offending emails (15600+). However, now there are 4 emails in the 
> queue that are legit, but they won't go out.
> I have tried using "qmHandle -a" to get them to process, but no luck.
> What else should I look at?
> Thank you,
> Patrick M. Ring
> P. Ring Technologies
> Louisiana Web Host, LLC.
> 985-868-4200

Off hand, I'd suggest:
# service qmail stop
# queue_repair.py -r
# service qmail start
# service qmail doqueue
--
-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 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] Courier-imap sometimes does not pass all email to qmail

[Lukas de Groen]

Hello,

For one month I am sometimes facing problems sending email from windows vista 
or windows 7 with outlook 2007 through courier-imap to qmail-toaster.  I 
switched on the debug logging mode in courier-imap.

For example I want to send an email to three persons and I can see that in the 
debug log of courier-imap (domain names have been changed) Notice that also 
email to internal email addresses is sometimes refused. The outlook client 
immediately receives an error. But the sender is not mailer-daemon but 
Systeembeheerder (sysadmin). And the report states that not all people have 
received the message and that I cannot send email through any email account 
-Via geen enkele e-mailaccount kunt u e-mail naar deze ontvanger versturen.


WRITE: * 314 FETCH (UID 2233 FLAGS () RFC822.SIZE 6592 BODY[HEADER] {734}

WRITE: From: "Harmen" 

To: "do...@abc.com",

"Francesco" ,

"pe...@cde.nl"

Subject: 7
Date: Wed, 17 Nov 2010 12:12:47 +0100

Message-ID: 


MIME-Version: 1.0

Content-Type: multipart/alternative;

boundary="=_NextPart_000_000C_01CB8650.BF30E770"

X-Mailer: Microsoft Office Outlook 12.0

Thread-Index: AcuGSF1ZRhyF1uZuQDOIZmYyjf9E2g==

Content-Language: nl

X-OlkEid: C844E42696012780A13A074C92405D1FBEF29CE9

Disposition-Notification-To: "Harmen" 



The /var/log/qmail/send/current.txt shows something else. The email is 
automatically localy archived (ok), but only delivered to one person in stead 
of three:

2010-11-17 12:15:09.689342500 new msg 5249489
2010-11-17 12:15:09.689343500 info msg 5249489: bytes 6660 from  
qp 24082 uid 89
2010-11-17 12:15:09.696192500 starting delivery 274: msg 5249489 to local 
xxx-emailarchivering.nl-postmas...@-emailarchivering.nl
2010-11-17 12:15:09.696193500 status: local 1/10 remote 0/60
2010-11-17 12:15:09.696194500 starting delivery 275: msg 5249489 to remote 
france...@bcd.com
2010-11-17 12:15:09.696195500 status: local 1/10 remote 1/60
2010-11-17 12:15:09.703754500 delivery 274: success: did_0+0+1/
2010-11-17 12:15:09.703755500 status: local 0/10 remote 1/60
2010-11-17 12:15:13.905853500 delivery 275: success: 
User_and_password_not_set,_continuing_without_authentication./_167.136.36.xxx_accepted_message./Remote_host_said:_250_2.0.0_oAHBFLqj028617_Message_accepted_for_delivery/
2010-11-17 12:15:13.905855500 status: local 0/10 remote 0/60
2010-11-17 12:15:13.905856500 end msg 5249489

The /var/log/qmail/submission/current.txt shows

2010-11-17 12:15:09.429527500 tcpserver: status: 1/100
2010-11-17 12:15:09.430122500 tcpserver: pid 24075 from 172.18.1.xx
2010-11-17 12:15:09.430248500 tcpserver: ok 24075 mail.cde.nl:172.18.1.xx:587 
:172.18.1.xx::56134
2010-11-17 12:15:09.620502500 CHKUSER relaying rcpt: from 
 remote  rcpt 
 : client allowed to relay
2010-11-17 12:15:09.620530500 policy_check: local har...@cde.nl -> remote 
france...@bcd.com (AUTHENTICATED SENDER)
2010-11-17 12:15:09.620584500 policy_check: policy allows transmission
2010-11-17 12:15:09.681454500 
simscan:[24075]:RELAYCLIENT:0.0594s:-:172.18.1.26:har...@cde.nl:france...@bcd.com
2010-11-17 12:15:12.206834500 tcpserver: end 24075 status 0
2010-11-17 12:15:12.206864500 tcpserver: status: 0/100
2010-11-17 12:16:57.246315500 tcpserver: status: 1/100


Our mail server is centos 5.5, 32 bit with the current qmail-toaster that is on 
the site http://www.qmailtoaster.com/
The mailserver was running perfectly for one year. I reinstalled the whole 
qmail-toaster mailserver, but the problem remains. I deleted the Office 2007 
from the computers and installed it again, but no results.

I don't know what to do else. Does anybody have a clue for me?

Kind regards,
Lukas de Groen



  

[qmailtoaster] Re: emails (outbound) stuck in queue

[Eric Shubert]

On 11/17/2010 11:30 AM, Patrick Ring wrote:

I had a spammer hack a client's email and load up the mail queue with
bogus emails.
I used qmHandle with the appropriate strings to get rid of the offending
emails (15600+). However, now there are 4 emails in the queue that are
legit, but they won't go out.
I have tried using "qmHandle -a" to get them to process, but no luck.
What else should I look at?
Thank you,
Patrick M. Ring
P. Ring Technologies
Louisiana Web Host, LLC.
985-868-4200


Off hand, I'd suggest:
# service qmail stop
# queue_repair.py -r
# service qmail start
# service qmail doqueue
--
-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] emails (outbound) stuck in queue

[Patrick Ring]

I had a spammer hack a client's email and load up the mail queue with
bogus emails.
I used qmHandle with the appropriate strings to get rid of the offending
emails (15600+).  However, now there are 4 emails in the queue that are
legit, but they won't go out.
 
I have tried using "qmHandle -a" to get them to process, but no luck.
What else should I look at?
 
Thank you,
Patrick M. Ring
P. Ring Technologies
Louisiana Web Host, LLC.
985-868-4200
 

[qmailtoaster] Re: re Invalid rcpthosts client email addresses sending emails to other rcpthosts clients

[Eric Shubert]

Please bring it up on the spamdyke list (gmane.mail.spam.spamdyke.user).
Thanks Martin.
--
-Eric 'shubes'

On 11/17/2010 08:44 AM, Martin Waschbuesch wrote:

I'd like to see SPF in spamdyke.

Martin

-Ursprüngliche Nachricht- From: Eric Shubert
Sent: Wednesday, November 17, 2010 3:56 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: [qmailtoaster] Re: re Invalid rcpthosts client email addresses
sending emails to other rcpthosts clients

That's a problem all right. I don't expect that using the submission
port would fix that either. The spfbehavior file should be separate for
the submission port to make that happen.

Ultimately, SPF should not be enforced for authenticated users. There
has been some talk about implementing SPF in spamdyke (I've been a
proponent of this). Perhaps we can nudge Sam and get it implemented
there. That would solve the problem.





-
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: re Invalid rcpthosts client email addresses sending emails to other rcpthosts clients

[Martin Waschbuesch]

I'd like to see SPF in spamdyke.

Martin

-Ursprüngliche Nachricht- 
From: Eric Shubert

Sent: Wednesday, November 17, 2010 3:56 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: [qmailtoaster] Re: re Invalid rcpthosts client email addresses 
sending emails to other rcpthosts clients


That's a problem all right. I don't expect that using the submission
port would fix that either. The spfbehavior file should be separate for
the submission port to make that happen.

Ultimately, SPF should not be enforced for authenticated users. There
has been some talk about implementing SPF in spamdyke (I've been a
proponent of this). Perhaps we can nudge Sam and get it implemented
there. That would solve the problem.

--
-Eric 'shubes'

On 11/17/2010 01:44 AM, Tony White wrote:

Hi Martin,
Found a big downside to it! Clients using their mobiles
for email sending can no longer send from their mobile
isp smtp server.
Bugger thought I had it beat as well.


On 17/11/2010 6:43 PM, Martin Waschbuesch wrote:

Cool! Let us know whether it has any impact. The upside to this is
that it will be harder for spammers to use your addresses to send to
other domains as well - although it is of course possible to spoof the
ip, too.
At any rate I hope this works out for you!

Martin

-Ursprüngliche Nachricht- From: Tony White
Sent: Wednesday, November 17, 2010 7:41 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] re Invalid rcpthosts client email
addresses sending emails to other rcpthosts clients

Hi Martin,
Thank you for that explanation. I had used the old spf web utility
to create the record you saw.
It would appear that that site is now the OLD one and the new
one does in fact do things differently now.
Thank you for your help, I have changed a single domain
as of now to test it before changing them all.

The site http://old.openspf.org/wizard.html, if you have time to look
at it,
does offer only the ~all option and if I had read the final page fully it
proves you are absolutely correct with your assessment.

Thanks again.


On 17/11/2010 5:24 PM, Martin Waschbuesch wrote:

Hi Tony,

OK, this *might* be something you should change. The way to read the
record is this:

The listed IP addresses are authorized to send mail for that domain.
All others are not.

HOWEVER, the '~all' tells recipients to treat this as a soft fail and
is supposed to be used for testing purposes. A lot of recipients will
accept mail from other hosts under this condition.

You might consider replacing it with this '-all'.

Fyi an excerpt from wikipedia:

+ for a PASS result. This can be omitted; e.g., +mx is the same as mx.
? for a NEUTRAL result interpreted like NONE (no policy).
~ for SOFTFAIL, a debugging aid between NEUTRAL and FAIL. Typically,
messages that return a SOFTFAIL are accepted but tagged.
- for FAIL, the mail should be rejected (see below).

Martin

-Ursprüngliche Nachricht- From: Tony White
Sent: Wednesday, November 17, 2010 1:46 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] re Invalid rcpthosts client email
addresses sending emails to other rcpthosts clients

Hi Michael,
A dig reveals this...

ycs.com.au. 7200 IN TXT "v=spf1 a mx ip4:111.223.234.146
ip4:125.168.12.213 ip4:125.168.254.24 ~all"


On 16/11/2010 6:07 PM, Martin Waschbüsch wrote:

What's the SPF record say? It should list the IPs and some options...

Von meinem iPhone gesendet

Am 16.11.2010 um 07:26 schrieb Tony White:


Hello Martin,
Thank you for your reply! I will investigate domainkeys now but the
SPF has been implemented for some time now...


On 16/11/2010 5:11 PM, Martin Waschbüsch wrote:

SPF and domainkeys can be used to do this. The policy for SPF
could be set to designating only your ip as valid and the
skim/domainkeys policy be set to 'all messages are signed'.
That should guarantee that your server will correctly identify
these mails as forgery. However, check your rules in tcp.smtp - if
one of your clients spams due to virus etc., that might bypass all
protections depending on the settings...

Von meinem iPhone gesendet

Am 16.11.2010 um 04:43 schrieb Tony White:


Hello,
Is there a way of verifying the From address that claims to be
from one of the domains
hosted here is a valid email address? There has been an increase
of spam using one or
more the domains hosted on my servers.
I am still searching the web but no searches found yet!

--

best wishes
Tony White


-

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 addition

[qmailtoaster] Re: Issue with qmail-inject!

[Eric Shubert]

On 11/17/2010 08:10 AM, Prasad Asokan wrote:

Hi,

 We receive failure: qmail-inject:_fatal:_unable_
to_parse_this_line:/To:_...@domain.com  on one of
our QMT servers. The mail was actually sent from a different domain, to
one of ours, and the above mentioned e-mail ID(not hosted with us)  was
in the To field. The mail was bounced back. Is there a way to relax this
or can you help me out why this is happening?

Regards,
Prasad Asokan


I'm not sure how qmail-inject would come into play here. Where do you 
see the message?


--
-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] Issue with qmail-inject!

[senthil vel]

Hi,

   Faced the same problem long time back.

http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg18687.html

The cause of "fatal:_unable_to_parse_this_line" is, some of the spl
characters must be added or removed from the header part which can't parsed
by qmail-inject . I faced the problem due to a missing ">".

*To:_...@domain.com
*
in that line, was there a "_" before the email id?

Analyzing the mail header or log properly for any such characters will be
more helpful. Find at which place the transition occurred. In my case the
problem was due to a MUA.

the following link might also be helpful..

http://www.gossamer-threads.com/lists/qmail/users/135716

 --S.Senthilvel

On Wed, Nov 17, 2010 at 8:40 PM, Prasad Asokan wrote:

> Hi,
>
> We receive failure: qmail-inject:_fatal:_unable_
> to_parse_this_line:/To:_...@domain.com on one of our QMT servers. The mail
> was actually sent from a different domain, to one of ours, and the above
> mentioned e-mail ID(not hosted with us)  was in the To field. The mail was
> bounced back. Is there a way to relax this or can you help me out why this
> is happening?
>
> Regards,
> Prasad Asokan
>

Re: [qmailtoaster] IPV6 support

[Jake Vickers]

On 11/16/2010 07:22 AM, Igor Smitran wrote:
What needs to be done in order to have full IPV6 support for all 
packages included in qmail-toaster? Are there any plans for IPV6 
implementation?
My company will switch to IPV6 in the beginning of next year and i 
need to know what to do with qmail.




There are some patches out there to add IPv6 to Qmail - I have no way to 
test them so would feel uncomfortable in adding them.
There was some talk (may have been on the devel list) where Erik 
Espinoza mentioned another program that did the conversion (like a 
wrapper or on the fly translator), but I do not recall what it was.



-
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] Issue with qmail-inject!

[Prasad Asokan]

Hi,

We receive failure: qmail-inject:_fatal:_unable_
to_parse_this_line:/To:_...@domain.com on one of our QMT servers. The mail
was actually sent from a different domain, to one of ours, and the above
mentioned e-mail ID(not hosted with us)  was in the To field. The mail was
bounced back. Is there a way to relax this or can you help me out why this
is happening?

Regards,
Prasad Asokan

[qmailtoaster] Re: re Invalid rcpthosts client email addresses sending emails to other rcpthosts clients

[Eric Shubert]

That's a problem all right. I don't expect that using the submission 
port would fix that either. The spfbehavior file should be separate for 
the submission port to make that happen.


Ultimately, SPF should not be enforced for authenticated users. There 
has been some talk about implementing SPF in spamdyke (I've been a 
proponent of this). Perhaps we can nudge Sam and get it implemented 
there. That would solve the problem.


--
-Eric 'shubes'

On 11/17/2010 01:44 AM, Tony White wrote:

Hi Martin,
Found a big downside to it! Clients using their mobiles
for email sending can no longer send from their mobile
isp smtp server.
Bugger thought I had it beat as well.


On 17/11/2010 6:43 PM, Martin Waschbuesch wrote:

Cool! Let us know whether it has any impact. The upside to this is
that it will be harder for spammers to use your addresses to send to
other domains as well - although it is of course possible to spoof the
ip, too.
At any rate I hope this works out for you!

Martin

-Ursprüngliche Nachricht- From: Tony White
Sent: Wednesday, November 17, 2010 7:41 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] re Invalid rcpthosts client email
addresses sending emails to other rcpthosts clients

Hi Martin,
Thank you for that explanation. I had used the old spf web utility
to create the record you saw.
It would appear that that site is now the OLD one and the new
one does in fact do things differently now.
Thank you for your help, I have changed a single domain
as of now to test it before changing them all.

The site http://old.openspf.org/wizard.html, if you have time to look
at it,
does offer only the ~all option and if I had read the final page fully it
proves you are absolutely correct with your assessment.

Thanks again.


On 17/11/2010 5:24 PM, Martin Waschbuesch wrote:

Hi Tony,

OK, this *might* be something you should change. The way to read the
record is this:

The listed IP addresses are authorized to send mail for that domain.
All others are not.

HOWEVER, the '~all' tells recipients to treat this as a soft fail and
is supposed to be used for testing purposes. A lot of recipients will
accept mail from other hosts under this condition.

You might consider replacing it with this '-all'.

Fyi an excerpt from wikipedia:

+ for a PASS result. This can be omitted; e.g., +mx is the same as mx.
? for a NEUTRAL result interpreted like NONE (no policy).
~ for SOFTFAIL, a debugging aid between NEUTRAL and FAIL. Typically,
messages that return a SOFTFAIL are accepted but tagged.
- for FAIL, the mail should be rejected (see below).

Martin

-Ursprüngliche Nachricht- From: Tony White
Sent: Wednesday, November 17, 2010 1:46 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] re Invalid rcpthosts client email
addresses sending emails to other rcpthosts clients

Hi Michael,
A dig reveals this...

ycs.com.au. 7200 IN TXT "v=spf1 a mx ip4:111.223.234.146
ip4:125.168.12.213 ip4:125.168.254.24 ~all"


On 16/11/2010 6:07 PM, Martin Waschbüsch wrote:

What's the SPF record say? It should list the IPs and some options...

Von meinem iPhone gesendet

Am 16.11.2010 um 07:26 schrieb Tony White:


Hello Martin,
Thank you for your reply! I will investigate domainkeys now but the
SPF has been implemented for some time now...


On 16/11/2010 5:11 PM, Martin Waschbüsch wrote:

SPF and domainkeys can be used to do this. The policy for SPF
could be set to designating only your ip as valid and the
skim/domainkeys policy be set to 'all messages are signed'.
That should guarantee that your server will correctly identify
these mails as forgery. However, check your rules in tcp.smtp - if
one of your clients spams due to virus etc., that might bypass all
protections depending on the settings...

Von meinem iPhone gesendet

Am 16.11.2010 um 04:43 schrieb Tony White:


Hello,
Is there a way of verifying the From address that claims to be
from one of the domains
hosted here is a valid email address? There has been an increase
of spam using one or
more the domains hosted on my servers.
I am still searching the web but no searches found yet!

--

best wishes
Tony White


-

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 is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and
inst

[qmailtoaster] Re: QMT Use Stats

[Eric Shubert]

We're on the same page, Dave. For those who just can't wean themselves 
off of Exchange, QMT (w/ spamdyke) makes a great front-end processor. I 
expect it does at least as well as commercial services (such as one that 
rhymes with Houdini).


In the not too distant (I hope) future, I hope to see QMT take on more 
enterprisey features. With vpopmail 5.5, I have my eye on LDAP support, 
and perhaps AD integration after that.


There seem to be a lot of folks wanting to ditch Exchange. The FOSS 
community will do well to providing a strong alternative in that area.


--
-Eric 'shubes'

On 11/17/2010 05:46 AM, David Milholen wrote:

  Sometimes I feel like the poster child for it even though we only have
a few servers running with it, but I am always selling the reliability
and functionality of QMT to "IT" prospects that are having issues with
MS Xchange.
Some actually make the change.
--Dave

On 11/12/2010 6:00 PM, Eric Shubert wrote:

FWIW, here's an interesting link:
http://www.securityspace.com/s_survey/data/man.200910/mxsurvey.html
That data is a year old.

Summarizing the last few years for QMT:
Year Servers Percent
11/09 1844 .20
02/09 1642 .20
02/08 1583 .17
02/07 1174 .13
11/06 1028 .11

So from 11/06 - 11/09, QMT has averaged growth of about 25% per year.
Not great market penetration (yet), but respectable growth.




--

David Milholen
Project Engineer
P:501-318-1300




-
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] QMT Use Stats

[David Milholen]

  
  
Sometimes I feel like the poster child for it even though we only
have a few servers running with it, but I am always selling the
reliability and functionality of QMT to "IT" prospects that are
having issues with MS Xchange. 
Some actually make the change.
--Dave
 
On 11/12/2010 6:00 PM, Eric Shubert wrote:
FWIW,
  here's an interesting link:
  
http://www.securityspace.com/s_survey/data/man.200910/mxsurvey.html
  
  That data is a year old.
  
  
  Summarizing the last few years for QMT:
  
  Year  Servers  Percent
  
  11/09  1844 .20
  
  02/09  1642 .20
  
  02/08  1583 .17
  
  02/07  1174 .13
  
  11/06  1028 .11
  
  
  So from 11/06 - 11/09, QMT has averaged growth of about 25% per
  year.
  
  Not great market penetration (yet), but respectable growth.
  
  



-- 
  
  David Milholen
  Project Engineer
  P:501-318-1300

  

Re: [qmailtoaster] re Invalid rcpthosts client email addresses sending emails to other rcpthosts clients

[Tony White]

Hi Martin,
  Found a big downside to it! Clients using their mobiles
for email sending can no longer send from their mobile
isp smtp server.
  Bugger thought I had it beat as well.


On 17/11/2010 6:43 PM, Martin Waschbuesch wrote:
Cool! Let us know whether it has any impact. The upside to this is that it will be harder for spammers to use your 
addresses to send to other domains as well - although it is of course possible to spoof the ip, too.

At any rate I hope this works out for you!

Martin

-Ursprüngliche Nachricht- From: Tony White
Sent: Wednesday, November 17, 2010 7:41 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] re Invalid rcpthosts client email addresses sending 
emails to other rcpthosts clients

Hi Martin,
  Thank you for that explanation. I had used the old spf web utility
to create the record you saw.
  It would appear that that site is now the OLD one and the new
one does in fact do things differently now.
  Thank you for your help,  I have changed a single domain
as of now to test it before changing them all.

The site http://old.openspf.org/wizard.html, if you have time to look at it,
does offer only the ~all option and if I had read the final page fully it
proves you are absolutely correct with your assessment.

  Thanks again.


On 17/11/2010 5:24 PM, Martin Waschbuesch wrote:

Hi Tony,

OK, this *might* be something you should change. The way to read the record is 
this:

The listed IP addresses are authorized to send mail for that domain.
All others are not.

HOWEVER, the  '~all' tells recipients to treat this as a soft fail and is supposed to be used for testing purposes. A 
lot of recipients will accept mail from other hosts under this condition.


You might consider replacing it with this '-all'.

Fyi an excerpt from wikipedia:

+ for a PASS result. This can be omitted; e.g., +mx is the same as mx.
? for a NEUTRAL result interpreted like NONE (no policy).
~ for SOFTFAIL, a debugging aid between NEUTRAL and FAIL. Typically, messages that return a SOFTFAIL are accepted but 
tagged.

- for FAIL, the mail should be rejected (see below).

Martin

-Ursprüngliche Nachricht- From: Tony White
Sent: Wednesday, November 17, 2010 1:46 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] re Invalid rcpthosts client email addresses sending 
emails to other rcpthosts clients

Hi Michael,
  A dig reveals this...

ycs.com.au. 7200IN  TXT "v=spf1 a mx ip4:111.223.234.146 ip4:125.168.12.213 ip4:125.168.254.24 
~all"



On 16/11/2010 6:07 PM, Martin Waschbüsch wrote:

What's the SPF record say? It should list the IPs and some options...

Von meinem iPhone gesendet

Am 16.11.2010 um 07:26 schrieb Tony White:


Hello Martin,
  Thank you for your reply! I will investigate domainkeys now but the
SPF has been implemented for some time now...


On 16/11/2010 5:11 PM, Martin Waschbüsch wrote:
SPF and domainkeys can be used to do this. The policy for SPF could be set to designating only your ip as valid and 
the skim/domainkeys policy be set to 'all messages are signed'.
That should guarantee that your server will correctly identify these mails as forgery. However, check your rules in 
tcp.smtp - if one of your clients spams due to virus etc., that might bypass all protections depending on the 
settings...


Von meinem iPhone gesendet

Am 16.11.2010 um 04:43 schrieb Tony White:


Hello,
  Is there a way of verifying the From address that claims to be from one of 
the domains
hosted here is a valid email address? There has been an increase of spam using 
one or
more the domains hosted on my servers.
  I am still searching the web but no searches found yet!

--

best wishes
  Tony White


-
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 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.c