Thanks Jake and Eric,
Both the servers are QMT. The main server works very best
in all aspects including spam fighting. If we are using rsync instead
of fetchmail, is it enough to sync the
/home/vpopmail/domains/domainname directory? Or we need to look
something more?
Thanks and Regards,
S.Senthilvel,
On Wed, Aug 12, 2009 at 7:29 PM, Eric Shubert<e...@shubes.net> wrote:
> senthil vel wrote:
>>
>> Dear list,
>>
>> We are using qmail toaster in a local server. ie, fetch mail
>> will fetch mails from the main server and distribute the mail to the
>> qmail users. The out ging mails are routed via the main server using
>> smtproutes.
>>
>> The problem is, when a mail is having misplaced or improper or
>> unclosed or unopened < or >, the rest of the mails also cant fetched.
>> The fetch mail log tells like that,
>>
>> fetchmail: 1 message for u...@domain.com at serverip (188763 > octets).
>>
>> qmail-inject: fatal: unable to parse this line:
>>
>> To: "user_\" <user"@mydomain.com>,
>> ""@senderdomain.com
>>
>> fetchmail: reading message user"@mydomain....@serverip:1 of 1
>> (188763 octets) (log message incomplete)fetchmail: error writing message
>> text
>> fetchmail: MDA error while fetching from user"@mydomain....@serverip
>> fetchmail: Query status=6 (IOERR)
>>
>> as a temperory solution, we use outlook to directly download the mail
>> from main server. But this continues for more than 20 users per day.
>> Is there any way to permanently fix the issue?
>>
>> Thanks and Regards,
>> S.Senthilvel,
>>
>
> This is more of a fetchmail issue than a qmt issue. I don't blame you for
> asking here though. ;) I haven't used fetchmail much, and don't know of a
> fix or another workaround off hand.
>
> I feel the urge to ask though, why QMT is on the backend instead of the
> front end? QMT with spamdyke is one of the best front ends you can find. It
> is even well suited as a front end to MS Exchange (for those who just can't
> live without MSE). The only reason I can think of to have your configuration
> is that only some of the domain's users are on the QMT system. If that's not
> the case, I'd simply direct the MX for the domain to the QMT host (and
> retire the "main server").
>
> --
> -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
