On Thu, Apr 27, 2006 at 05:24:04PM -0700, Gordon Messmer wrote:
David Doan wrote:
I have stumbled upon a strange problem with the Aliases list. I have an
alias setup to send mail to several phones @messaging.sprintpcs.com.
When the phones are grouped together in the alias list, they do not
receive the correct FROM: information on the phone.
We ran in to the same issue at my former place of employment. It became
a problem for us, because some of our users' wireless providers would
simply drop messages with a zero-length FROM address. To resolve the
issue, we forwarded the messages using dot-courier files instead of aliases.
For example, an alias would exist named "pagegmessmer", which would
direct pages to my inbox as well as to my pager:
pagegmessmer: gmessmer, gmessmer-pager
I'd have a .courier-pager file that would, then, forward the message to
my pager's address.
It won't transfer the original FROM to the phone, but it'll make sure
that you get something other than a zero-length address. You may also
be able to pass the message to a script which sends the message in a way
that meets your needs better.
Like using "sendmail -f" from .mailfilter.
In our case, the customer did not want bounces to sprint going back to
the email box, so we did it as you did we just do it in .mailfilter.
The postmaster get's the bounces, and as a service we just let their IT
honcho know.
Note that we also ran into issues with size limitations on the phone
mailboxes--if the sprint delivery got a failure, courier would keep
retrying and put dups in the original mailbox. Sorry, I don't exactly
remember our config but now I test $SIZE and if it's too big, I don't
forward.
m
4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Courier not passi...
