Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Qmail/Mysql alias question

Status
Not open for further replies.

bazill

IS-IT--Management
Mar 21, 2005
2
US
I am currently using qmail with mysql to do the forwarding for my site customers. So if someone registers on my site they get assigned an email username@mysite.com, this email forwards all the mail sent to it, to their real email address.

I am trying to change the headers of forwarded email so it doesnt look like it came from admin@mysite.com, but show actual real senders headers. Some people complain about spam and I know its not me. So i want to be just the transparent forwarder. Does anyone know how I can quickly resolve this? Is there a config for headers I need to change/
 
That's sort of the reason why headers exist, to trace who sent what. Trasparency isn't a good thing in mail headers if it obfuscates any servers playing MX roles in the chain. Any need to return mail or messages needs these headers.

If the issue is of your customers as senders but they have their own email accounts, why aren't they sending from their real accounts once the aliased delivery reaches them?

I'm afraid I don't understand this situation well enough.

D.E.R. Management - IT Project Management Consulting
 
My customers are using @mysite.com emails because I have a better email organization and spam control. But i dont want the forwarded emails to look like they came from admin@mysite.com. I just want to be a transparent filter that controls what gets forwarded.
 
That would be better (and more compliantly) done by nominating your server as an MX record in their domains. Then you'd implement relay for their domains.

Thus instead of forwarding:
user@mysite.com -> userrealname@realdomain.com

userrealname@realdomain.com -> your SMTP -> their SMTP.

This allows you to implement extensive Spam and Virus checking on their behalf by silently acting upon the messages (tagging, killing, etc.) without tainting the headers by changing any domain names. YOUR server will still appear in the headers but it will be very clear that you're an intermediary instead of a deliverable endpoint.

AGAIN, you cannot make your mail server invisible since the RFCs of email require your email server to put a header into the message.

D.E.R. Management - IT Project Management Consulting
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top