• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Use of "&" in email address

F

faris

Guest
We have a customer being blasted to hell and back by spammers because they have been using a true catchall address, and so were catching all the email sent to non-existant addresses on their domain. They were using up 10Gigs of transfer per month because of all this.

I've forced them to switch to having one pop3 mailbox with aliases for each address they really want.

This is fine except they have been advertising an email address of x&[email protected]

Plesk won't allow an alias to be created with an "&" in the address. In fact I've never seen an & in an email address ever, so I assume that like most punctuation it is not allowed.

I'm wondering if I can manually add it somehow, without breaking things? I can't figureout how though. I thought I could do something with the .qmail file but that doesn't work.

Apparently Exchange supports "&" in the address.

Faris.
 
Well, I sort of got around it by creating a mailname in Plesk (xandy) then renaming /var/qmail/mailnames/domain/xandy to x&y at the command prompt. This works perfectly.

But of course this isn't a good idea. The Plesk database still thinks it is "xandy", and I hate to think of the problems it will cause the next time we try and do a Plesk update.

Does anyone have a better suggestion?

Faris.
 
Back
Top