This is a discussion on [courier-users] dot-courier questions: dash vs plus within the Courier-Imap forums, part of the Mail Servers and Related category; Regarding the dot-courier behavior, where users can "...receive mail addressed to user-foo@domain, for arbitrary values of ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Regarding the dot-courier behavior, where users can "...receive mail
addressed to user-foo@domain, for arbitrary values of foo...", I'm curious why the dash was selected for this purpose. Is it possible to (reasonably painlessly) substitute the plus for the dash in this functionality? I've done some minimal testing with the /etc/courier/aliasdir/.courier-default file and found that I can double pipe to a script that cuts the portion from the + to the @ and returns the intended target email address. Assuming that I can figure out the correct exit status to return, to properly handle subsequent delivery failures, are there any potential problems with this workaround? One thing that I've noticed is that if the original RECIPIENT address is string1-string2+plusString@domain, and "string1" exists as a valid USER, the message never makes it to the /etc/courier/aliasdir/.courier-default process, described in the dot-courier documentation as the final step in the default delivery processing. None of the users involved in the test have a .courier-default file. This behavior suggests that Courier is seeing that string1 exists as a valid USER, looks for delivery instructions related to that USER for the RECIPIENT address "string1-string2+plusString@domain", doesn't find any (no ..courier-default file for the USER "string1"), and so fails the delivery. Given this behavior, I'm curious what will happen under the following scenario: With two different users: "jane.smith" and "jane.smith-jones", will emails sent to "jane.smith-jones@domain" ever reach her? Or will Courier attempt to deliver to "jane.smith", find no .courier-default file in the "jane.smith" home directory, and bounce the message? (Without going forward to look further for delivery instructions, as described in the Default delivery instructions section of the dot-courier documentation.) Thanks in advance for any light you can shed on this functionality. -- -Jerome ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users |
|
|||
|
Jerome Bullert writes:
> Regarding the dot-courier behavior, where users can "...receive mail > addressed to user-foo@domain, for arbitrary values of foo...", I'm > curious why the dash was selected for this purpose. Originally, for compatibility with qmail. > Given this behavior, I'm curious what will happen under the following > scenario: > With two different users: "jane.smith" and "jane.smith-jones", will > emails sent to "jane.smith-jones@domain" ever reach her? Yes. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkhaPVYACgkQx9p3GYHlUOKJxwCfVe9XGyGspH F5UPyjj9g6MH7F r+MAn1HQtP/AA2L6CP9zfzQMCvaUBwun =4Nqw -----END PGP SIGNATURE----- |