[freeside] Email aliases

[Ryan Trainor]

Great! Sounds like 1.5 will cover the one niggling issue I have. Until
release I'm quite happy just running 1.4.1 and managing my aliases by
hand. Freeside is some truly excellent work and just keeps getting
better =)

Ryan

-----Original Message-----
From: ivan [mailto:ivan at 420.am] 
Sent: Friday, 11 June 2004 2:55 PM
To: ivan-freeside at sisd.com
Subject: Re: [freeside] Email aliases

On Fri, Jun 11, 2004 at 02:18:30PM +1000, Ryan Trainor wrote:
> Is it possible for me to backport the postfix export from the CVS'd 
> 1.5 to 1.4.1?

It wouldn't be trivial or I'd have checked it into FREESIDE_1_4_BRANCH
myself.  Some things about exports are different, the svc_forward table
has a new field, the web interface was updated, etc...

Most stuff that doesn't change the schema is applied to both the 1.5 and
1.4 branches.  As soon as I find some free time to update the web demo
and such I'll release the FREESIDE_1_4_BRANCH as 1.4.2beta1.

> If not I can wait for 1.5 release and then upgrade.
> 
> Does 1.5 change the behaviour of svc_forward?

It doesn't change it in any backwards-incompatible way, but yes it does
extend the table to accomidate all the situations you outline.

--
_ivan

> As I understand it in
> 1.4.1 I can add an entry to forward mail from a real freeside user to 
> another user, or to an external mailbox (eg, mail for compa-bob can go

> to compa-fred or bob at external-domain.com) but I can't get 
> info at companyA.com to go to compa-bob and info at companyB.org to go to 
> compb-mick. At least not thru freeside - it's easy enough just adding 
> lines to /etc/aliases.
> 
> Do I have that the right way round, or am I misunderstanding how 
> svc_forward works?
> 
> Ryan
> 
> -----Original Message-----
> From: ivan [mailto:ivan at 420.am]
> Sent: Wednesday, 9 June 2004 5:48 PM
> To: ivan-freeside at sisd.com
> Subject: Re: [freeside] Email aliases
> 
> 1.5 has a postfix export that generates text /etc/aliases and 
> /etc/postfix/virtual files from svc_forward records.
> 
> eg/export_template.pm is an example template for writing exports 
> (updated in 1.5 and now completely self-contained).  Probably best to 
> check CVS HEAD or ask on the -devel list before starting to write an 
> export to make sure you're not duplicating work.
> 
> --
> _ivan
> 
> 
> On Wed, Jun 09, 2004 at 02:13:23PM +1000, Ryan Trainor wrote:
> > Hi all,
> >  
> > I'm just setting up my first install of freeside and so far loving
it!
> > I'm running on RedHat EL 3.0 ES and the only real problems I've had 
> > so far have been to do with the RHN versions of RPMs not having the
> options
> > I want compiled, such as pgsql support in freeradius. The problem 
> > I'm currently trying to work thru is regarding email aliases and I 
> > think it's more a problem of me not having the concept of how 
> > freeside deals with them straight in my head. Common enough
scenario:
> >  
> > I create a mailbox for Bob from Company A, and another for John from

> > Company A. I use the usernames compa-bob and compa-john,
respectively.
> > Now Company A register companya.com and I set the catchall for the 
> > domain to compa-bob. All is good.
> > Then Bob calls and says that he wants info at companya.com to go to
John.
> > In theory I can just throw a line in /etc/aliases, or I can setup 
> > another mailbox thru freeside and a svc_forward to bounce that on to

> > John. If I go the second path then I set up a new user called info.
> > When Company B does all of the above and also wants 
> > info at companyb.com forwarded somewhere, it can't be done because the 
> > info user already exists.
> >  
> > I'm not using vpopmail, virtual domains or an sql-backed smtp server

> > - I'm using postfix 2.something because I want to stick with the 
> > RedHat Network versions of the RPMs so that when an exploit in 
> > postfix is discovered I just grab the new package via up2date. Hence

> > my choice in software is a bit restricted. My current plan is for 
> > freeside to add unix users for each mailbox with blank passwords and

> > have the pop3 server use pam_radius to authenticate them - this is 
> > working fine so far. What I'd really like is for situations like the

> > one above, somewhere is freeside that I could specify that 
> > info at companya.com goes to local user compa-john and 
> > info at companyb.com goes to compb-fred and have an export script put 
> > the appropriate lines into /etc/aliases and remove them as required.

> > I'd *really* love to be able to look at a customer in cust_main.cgi,

> > click on a mailbox account and see the aliases that point to that 
> > mailbox =)
> >  
> > Am I missing something? Is there an accepted way of making this 
> > work,
> or
> > does everyone just use vpopmail?
> >  
> > I guess the other option is to just whack together a quick web
> interface
> > to /etc/aliases and have newaliases run every 15 mins out of cron, 
> > but I'd like to keep it in freeside if possible. Most of the 
> > research I've done so far has pointed to svc_acct_sm, but that 
> > appears to have been deprecated and in my new 1.41 install there 
> > isn't a table for it in
> the
> > standard schema. If svc_acct_sm is still the best way to do it I'm
> happy
> > to stuff around and get it working of course =)
> >  
> > Any suggestions or pointers anyone has would be great.
> >  
> > Thanks guys,
> >  
> > Ryan Trainor
> 
> --
> _ivan
> 
> 

--
_ivan