Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-18 Thread senthil vel
Dear Ganesh, Thanks a ton... I really got some new idea regarding the fetchmail after reading the man page with the help of options provided by you. In the beginning i got some problem with the dksign .. I got the following error SMTP error: 554 qmail-dk: Cannot sign message due to inval

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-17 Thread Ganesh.payelkar
Dear Senthilvel, Kindly try this configuration for your fetchmailrc... set daemon 30 set no bouncemail set postmaster "postmas...@abc.com" set logfile /var/log/fetchmail poll 3.15.1.1 proto pop3 localdomains mail.abc.com mail abc.com no dns envelope Delivered-To: qvirtual abc

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-16 Thread senthil vel
Dear Ganesh, The current fetchmailrc contents are as follows. set postmaster "postmaster" set bouncemail set no spambounce set properties "V" set daemon 60 poll serverip proto pop3 port 110 user 'usern...@domain.com' there with password '12345' is 'usern...@domain.com' here options fetc

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-15 Thread ganesh payelkar
Dear Senthilvel, can you paste here your fetchmailrc contain ? Regards, ganesh On Wed, Aug 12, 2009 at 6:42 AM, 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

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-13 Thread Eric Shubert
senthil vel wrote: Dear Eric, Thanks for the continuous help. I have relaxed chkuser in the way that it will not check mails from certain servers. And why was that deemed necessary? Perhaps there is another method of achieving the goal here without accepting these malformed addresses.

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-13 Thread senthil vel
Dear Eric, Thanks for the continuous help. I have relaxed chkuser in the way that it will not check mails from certain servers. Apart from this issue there is no problem at all. Tomorrow i shall have a try on this fetchmail setting. I shall update if worked properly. Mean while, if there i

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-13 Thread Eric Shubert
senthil vel wrote: Dear Eric, The client needs almost all the mails sent to them. So the primary server has a relaxed chkuser. This cause the main server to receive such mails. But while using fetch mail, the qmail-inject needs to be invoked no?. So that this error occurs. It wi

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-13 Thread senthil vel
Dear Eric, The client needs almost all the mails sent to them. So the primary server has a relaxed chkuser. This cause the main server to receive such mails. But while using fetch mail, the qmail-inject needs to be invoked no?. So that this error occurs. It will be great even such

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread Eric Shubert
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 misplace

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread senthil vel
Dear Jack and Eric, Sorry for the delayed response. While looking practical, rsync is bit complected. Because half of the users are depending only in the main server (Roaming users). So we must implement directory level sync (/home/vpopmail/domains/domainname/username). Also the ssh keys

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread Eric Shubert
Jake Vickers wrote: Eric Shubert wrote: Jake Vickers wrote: Eric Shubert wrote: Jake Vickers wrote: senthil vel wrote: 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 fetchm

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread Jake Vickers
Eric Shubert wrote: Jake Vickers wrote: Eric Shubert wrote: Jake Vickers wrote: senthil vel wrote: 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

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread Eric Shubert
Jake Vickers wrote: Eric Shubert wrote: Jake Vickers wrote: senthil vel wrote: 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/vpopma

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread Jake Vickers
Eric Shubert wrote: Jake Vickers wrote: senthil vel wrote: 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

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread Eric Shubert
Jake Vickers wrote: senthil vel wrote: 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 nee

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread Jake Vickers
senthil vel wrote: 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 m

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread Eric Shubert
Are the users on the backend server using pop3, imap, or both? senthil vel wrote: 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/vpopma

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread senthil vel
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 Reg

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread Eric Shubert
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 misplace

Re: [qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread Jake Vickers
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 misplace

[qmailtoaster] fetchmail:qmail-inject: fatal: unable to parse this line:

2009-08-12 Thread senthil vel
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 uncl