Re: [ilugd] Re: [LIH]Catch-all acount problem due to multiple recipients

2003-10-12 Thread Sudev Barar
On Sun, 2003-10-12 at 00:37, Sandip Bhattacharya wrote:
 Varun Varma wrote:
 
   
  
  True, but most hosting panels, including the one on a Cobalt [RaQ3 
  atleast], lets you add custom entries to the virtusertable file. Simply 
  don't add the catch-all account through the control panel and instead 
  add it by hand in the domuser+%1 format to virtusertable file.
 
 HEy great! That worked! That gets the last irritant in catch-all 
 accounts. I can sleep well tonight. Thanks!
  
  Remember to do a makemap on the virtusertable file.
  
  Also, remember to brush your teeth at night.
 
 huh? ... How did you know?
 
 
 - Sandip

Sandip,
Since this topic generated quite a bit to to  fro traffice can you post
A-Z steps all in one post??
-- 
Sudev Barar

Learning Linux


___
ilugd mailing list
[EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd


[ilugd] Re: [LIH]Catch-all acount problem due to multiple recipients

2003-10-11 Thread Sandip Bhattacharya
Varun Varma wrote:

Sandip Bhattacharya wrote:

This must be one of the most popular questions, but much as I search on
the web I dont see any solution.


Ummm..RTFM?

http://www.sendmail.org/faq/section3.html#3.29

A few words of caution:

- As I see it, this a problem of multidrop combined with multi-rcpt. 
You might have to put the procmail file for each account that has 
multidrop.

- There is a typo on the sendmail.org page. The following on the page:

formail -i X-Envelope-To: [EMAIL PROTECTED]

Should read:

formail -i X-Envelope-To: [EMAIL PROTECTED]

Notice the quote *after* the $ENV_TO$DOMAIN.

- This causes sendmail to make multiple copies of the message as you 
want. Since they are identical copies, except the X-Envelope-To header, 
any message identification headers are also recplicated...e.g. 
Message-Id. Depending on the mail usage you have, this might cause 
problems.

- The solution works on my sendmail server - your mileage may vary.

Am not sure. Unless I am mistaken, the page says that virtual users 
should be defined as:

@domain.com	[EMAIL PROTECTED]

This puts the envelope information in the mail address. The mailer 
understands this as a email address 
extension([EMAIL PROTECTED]). Then procmail can take this as an 
argument and deliver it using the additional X-Envelope-To: header.

But, in most control panel software like the cobalt one I am worried 
about, the default virtuser entry for the catch-all account that is 
created is of the form:

@domain.com	[EMAIL PROTECTED]

The envelope information is lost *before* delivery, so sendmail while 
receiving on behalf of domuser has no clue as to the intended envelope 
recipient.

- Sandip

--
Sandip Bhattacharyahttp://www.sandipb.net
sandip at puroga.com
Puroga Technologies Pvt. Ltd.
http://www.puroga.com


___
ilugd mailing list
[EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd


[ilugd] Re: [LIH]Catch-all acount problem due to multiple recipients

2003-10-11 Thread Sandip Bhattacharya
Varun Varma wrote:

 
True, but most hosting panels, including the one on a Cobalt [RaQ3 
atleast], lets you add custom entries to the virtusertable file. Simply 
don't add the catch-all account through the control panel and instead 
add it by hand in the domuser+%1 format to virtusertable file.
HEy great! That worked! That gets the last irritant in catch-all 
accounts. I can sleep well tonight. Thanks!
Remember to do a makemap on the virtusertable file.

Also, remember to brush your teeth at night.
huh? ... How did you know?

- Sandip

--
Sandip Bhattacharyahttp://www.sandipb.net
sandip at puroga.com
Puroga Technologies Pvt. Ltd.
http://www.puroga.com


___
ilugd mailing list
[EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd


[ilugd] Re: [LIH]Catch-all acount problem due to multiple recipients

2003-09-30 Thread Suresh Ramasubramanian
Sandip Bhattacharya [10/1/2003 12:30 AM] :

But my question is that is there a way to cajole/coerce sendmail to make
multiple copies of the mail locally (according to the envelope
recipient) therefore keeping envelope information intact before
delivering them?
Issue for your local delivery agent - procmail or whatever.  Have 
fetchmail handoff to procmail directly (see man fetchmail) - that might 
help.

___
ilugd mailing list
[EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd