log email send to admin

[floyd]

Do you tell your customers they need to set them up?

No because I had not thought of it until you and Jeff brought it up.

I thought you were saying that DA is not RFC compliant. If anything you would have to say that either admin or the individual users are not RFC compliant. DA cannot be RFC compliant since it is not the responsibility of DA. Being RFC compliant has nothing to do with DA except that DA provides a way for people to be RFC compliant. Its the responsibility of people to set up those email addresses whether it is the admin or the users.

 

[tlchost]

No because I had not thought of it until you and Jeff brought it up.

I thought you were saying that DA is not RFC compliant. If anything you would have to say that either admin or the individual users are not RFC compliant.

It would be more accurate is I said that DA doesn't produce the RFC required email addresses when a domain is created.

There are Control Panels that do that.

I think I need to get to work on creating a message to all my customers that tells them what they need to do and how they can do it.

FWIW, they ALL come from a system that created all that for them automatically, so this will be a "learning" experience for them

 

[floyd]

come from a system that created all that for them automatically

This is the problem that I have. I don't want a control panel to do something automatically when it cannot possibly know what I want done. Yes I might want certain email addresses to be accepted but DA cannot possibly read my mind and know where that email should be delivered, whether its a local address or forwarded to another address.

So its my opinion that DA does it right. I don't want a piece of software to arbitrarily do something without my input as if there is only one way to do it.

I think we are coming to an understanding now even if we don't necessarily agree on the details. We each have a right to our opinion. I was trying to highlight the consequences of certain things.

 

[tlchost]

This is the problem that I have. I don't want a control panel to do something automatically when it cannot possibly know what I want done.

I remember when a few friends of mine started an ISP....I was the end user test case....I ued to watch them do everything via the shell...they actually seemed to enjoy it.

I don't enjoy it at all....I would rather have the CP do it for me, and allow me to change it if required.

What would make sense to me....have the CP offer a selection creating a domain such as:

Have RFC required addresses as aliases of mail email account Y N

If it's yes, they are created as aliases that can be edited...if no, then
folks who want things as you do can do their own thing.

But this is now sounding the like discussion over webmail clients.

Now I have to find which RFC specifies which addresses are required

 

[jlandes]

You could create a script that runs each time a domain is added to DA that automatically creates the required RFC addresses as forwarders that get directed to the user who own's the domain. These can then be changed, if the user wants to change them. This is how you can do it.

1. Create the file /usr/local/directadmin/scripts/custom/domain_create_post.sh if it does not already exist.
2. Put the following lines of code into the file (untested):
   
   

   #!/bin/sh
   file=/etc/virtual/$domain/aliases
   mv $file $file.tmp
   echo "abuse: $username" > $file
   echo "admin: $username" >> $file
   echo "hostmaster: $username" >> $file
   echo "postmaster: $username" >> $file
   echo "webmaster: $username" >> $file
   cat $file.tmp >> $file
   rm -f $file.tmp
   chown mail:mail $file
   chmod 600 $file
   exit 0;

3. Save, exit, and chmod the domain_create_post.sh to 755, and you're done.

If you're curious, you have to put the * at the bottom, hence the out of order methodolgy (adding the default last).

Hope this helps.

 

[tlchost]

You could create a script that runs each time a domain is added to DA that automatically creates the required RFC addresses as forwarders that get directed to the user who own's the domain. These can then be changed, if the user wants to change them.

Thanks so much....works like a charm!

 

[ihostuk]

But this is now sounding the like discussion over webmail clients.

Difference being this time I agree fully with you Thom,

I think an option in the CP would be a good idea, and I actually think if DA is going to manage the adding of domains, then it should also handle making the necesasry email addresses to ensure RFC compliance.

Myself I added them all to forward to my system account,

Just my two cen....pence

 

[floyd]

Myself I added them all to forward to my system account

My question all along is how is DA going to know that is what you want it to do? What if you want it to go to your system account but other users for other domains want it to go somewhere else?

If DA is going to do this then there has to be a way to tell DA to a certain thing for each user because each user is going to want something different.

 

[ihostuk]

That could be catered for in the CP surely by having a default option, then maybe in the user-email section having a new part called RFC E-mail Address location, where a user if they feel could change the default setting of where mail gets sent eg, forwarder, seperate mail-box etc

Best of both worlds, RFC compliance, and the ability to tell DA exactly what you want it to do with emails that get sent to them.

 

[tlchost]

Difference being this time I agree fully with you Thom,

One of your weaker moments, but I'm sure the community at large will forgive you.

I think an option in the CP would be a good idea, and I actually think if DA is going to manage the adding of domains, then it should also handle making the necesasry email addresses to ensure RFC compliance.

Jeremy's script works like a charm....

Myself I added them all to forward to my system account,

Yes...you could replace the $username with some other value.

Another way to have the RFC required addresses be answered would be to use the catchall....but in the world of spam, that doesn't sound too good to me.

As an aside....do any of RBLs list a domain/ip address if mail to the RFC required addresses aren't answered?

 

[nobaloney]

I guess I'll have to look at how Cobalt did it to get a list of the required aliases.

Though I agree with others who say DA shouldn't be enforcing RFC compliant, I posted the list near the top of this thread. I posted it for admin, but it would be the same list for users.

I go above and beyond RFC compliance, though .

Jeff

 

[nobaloney]

I would say the users are not RFC compliant. I do not think this should be one of DA's jobs. I do not want DA doing this for me. Like I said before how is DA going to know where you want [email protected] to go to? Do you want [email protected] to go to its own mailbox or do you want it to be forwarded to another mailbox?

I agree with you Floyd, and I set it up only for admin. I know where it's supposed to go because it's part of my setup questionnaire form.

I don't know what the BQ OS does, but old Cobalts automatically aliased postmaster to the server admin. Not a good idea IMHO.

Thom, I simply tell my clients:

Internet rules (the RFCs) require that your domain has a postmaster address and an abuse address, both of which much receive email and be read by a real live human, so please set them up, either as mailboxes you check, or as forwards to a mailbox you check regularly. You should probably also read either your main login email box, or forward it somewhere as well, as the server will often send email to and from that email address.

I do it a bit more complex... with exact examples in a customized welcome email.

You can do the same.

Jeff

Jeff