On Fri, 5 Oct 2001 19:20:33 +0100, Tim Sellar wrote: >>> >> Also, there needs to be a symlink, for the same reason, on >> /var/spool/virtual/domain.net -> domain >> > >This is not something I have previously seen in any testing but sounds like >a problem in vm-pop3d. I will see if I can duplicate it.... > >> 2/ Sendmail thinks that the virtual users don't exist, despite >> vuser_list showing that they >> do and sending test mail from within the VS arriving where is should. >> > >As explained in my previous mail, Sendmail does not play a very significant >part in the current freeVSD virtual mail implmentation. Configuration >relating to virtual users (forwarders/reponders etc) are held in procmail >recipes beneath /etc/procmailrcs/virtual/<domain>/... Sendmail will have >absolutely no awareness of the virtual users as they do not feature in any >Sendmail configuration files.
Understood, and yet here is a logfile entry: Oct 6 10:12:04 altair sendmail[14218]: KAA14218: <[EMAIL PROTECTED]>... User unknown Hmm... this virtual user *is* listed in 'vuser_list', has a mailbox, is listed in the procmail recipes ... /etc/mail/mailertable has the correct entry and the datestamp shows that the db was remade by the script. I'll chase this down and post the result. >> 3/ Procmail, after the "unknown user" msg, returns this mail to >> admin@the_new_VS, rather >> than admin@the_sending_domain. >> > >Check out the procmail recipe structure beneath /etc/procmailrcs (also see >man procmail and man procmailrc for more background). The recipe file >basically acts like a long switch/case statement with the default delivery >destination being the admin@<domain>. When a non-matching user is received >it will eventually fall through all the checks and end up in the >admin@<domain> account, as you describe. It would not be much work to >improve the recipe to actually respond to the sender of the incorrectly >addressed message as well - I just didn't go as far as implementing that at >this stage in the freely available skels. There are all sorts of >possiblities available through procmail for filtering/responding/preventing >spam etc. and the module is written to be very flexible and extendable to >take account of this. Any procmail recipe suggestions or additions would be >more than welcome... Fair enough :) When I'm finished with this I'll do something about procmail recipes - though I've had a quick glance and it's obvious that I'll need to study it all first. One other thing I've just found: trying to set a passwd for admin means that I need to know the old password - of course I don't (except for the encrypted version in 'passwd'). How do I set this? Is vuser_mbxpass the only way? >Tim Lyn ------------------------- The freeVSD Support List -------------------------- Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support Archives: http://freevsd.org/support/mail-archives/freevsd-support -----------------------------------------------------------------------------
